Bump ASFHyP3/actions from 0.4.0 to 0.7.1

[dependabot[bot]]

Bumps ASFHyP3/actions from 0.4.0 to 0.7.1.

Release notes

Sourced from ASFHyP3/actions's releases.

Actions v0.7.1

Fixed

• reusable-docker-ghcr.yml no longer attempts to push a Docker image if run from a fork.

Actions v0.7.0

Changed

• conda environments are now provisioned with micromamba in all reusable workflows
• reusable-pytest.yml and reusable-pytest.yml no longer accept a conda_env_name input and will use the environment named in the calling repo's environment.yml

Actions v0.6.0

Changed

• reusable-version-info.yml now uses setuptools_scmfor generating version numbers as the use of setup.py is discouraged
• reusable-git-object-name.yml now handles lightweight as well as annotated tags

Fixed

• All uses of the GitHub Action set-output command have been upgraded, due to forthcoming depreciation

Actions v0.5.0

Added

• reusable-relese-checklist-comment.yml reusable workflow to add a comment to PRs with a release checklist for developers and reviewers

Changed

• reusable-pytest.yml now accepts (only) a JSON list of python version strings and will setup a matrix of test jobs for multiple python versions. python_version usage has changed from

    python_version: "3.9"            # Optional; default shown  
  

  to

      # Optional; default shown
      python_versions: >-
        ["3.8", "3.9", "3.10"]
  

  Note: A single python version can be specified like ["3.9"].

Removed

• Removed support for secret scanning with gitleaks-action, which now requires a paid license to use the latest version.

Changelog

Sourced from ASFHyP3/actions's changelog.

[0.7.1]

Fixed

• reusable-docker-ghcr.yml no longer attempts to push a Docker image if run from a fork.

[0.7.0]

Changed

• conda environments are now provisioned with micromamba in all reusable workflows
• reusable-pytest.yml and reusable-pytest.yml no longer accept a conda_env_name input and will use the environment named in the calling repo's environment.yml

[0.6.0]

Changed

• reusable-version-info.yml now uses setuptools_scmfor generating version numbers as the use of setup.py is discouraged
• reusable-git-object-name.yml now handles lightweight as well as annotated tags

Fixed

• All uses of the GitHub Action set-output command have been upgraded, due to forthcoming depreciation

[0.5.0]

Added

• reusable-relese-checklist-comment.yml reusable workflow to add a comment to PRs with a release checklist for developers and reviewers

Changed

• reusable-pytest.yml now accepts (only) a JSON list of python version strings and will setup a matrix of test jobs for multiple python versions. python_version usage has changed from

    python_version: "3.9"            # Optional; default shown  
  

  to

      # Optional; default shown
      python_versions: >-
        ["3.8", "3.9", "3.10"]
  

  Note: A single python version can be specified like ["3.9"].

Removed

• Removed support for secret scanning with gitleaks-action, which now requires a paid license to use the latest version.

Commits

• 2eabaf5 Merge pull request #58 from ASFHyP3/develop
• e190b05 Merge pull request #55 from ASFHyP3/dependabot/github_actions/aws-actions/con...
• af4b1ae Merge pull request #54 from ASFHyP3/dependabot/github_actions/ASFHyP3/actions...
• eca406e Merge pull request #57 from ASFHyP3/docker-push-forks
• de84686 Update Changelog
• fc91f9b skip tag steps
• a53544f fix github actions expression
• 3906852 Do not push docker image if repo is a fork
• 87dab4d Bump aws-actions/configure-aws-credentials from 1 to 2
• df220bd Bump ASFHyP3/actions from 0.6.0 to 0.7.0
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[jhkennedy]

@dependabot rebase

[dependabot[bot]]

Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry!

If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[jhkennedy]

closing in favor of #236

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.