Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uses request-add-entry action instead of registry action #174

Merged
merged 1 commit into from
Feb 8, 2021

Conversation

ekcasey
Copy link
Member

@ekcasey ekcasey commented Feb 8, 2021

Summary

Uses ghcr.io/buildpacks/actions/registry/request-add-entry:4.0.1 action in generated pipelines instead of ghcr.io/buildpacks/actions/registry:main

Use Cases

ghcr.io/buildpacks/actions/registry:main action is not documented in the buildpacks/github-actions README and has not been updated in several months.

Checklist

  • I have viewed, signed, and submitted the Contributor License Agreement.
  • I have added an integration test, if necessary.

registry:main action is not documented in the buildpacks/github-actions README and has not been updated in serveral months.

Signed-off-by: Emily Casey <ecasey@vmware.com>
@ekcasey ekcasey requested a review from a team February 8, 2021 19:37
@ekcasey ekcasey added semver:patch A change requiring a patch version bump type:dependency-upgrade A dependency upgrade labels Feb 8, 2021
@ekcasey ekcasey changed the title Uses registry/request-add-entry:4.0.1 GHA instead of registry:main Uses request-add-entry action instead of registry action Feb 8, 2021
@ekcasey ekcasey merged commit c8f945c into main Feb 8, 2021
@ekcasey ekcasey deleted the request-add-entry branch February 8, 2021 19:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver:patch A change requiring a patch version bump type:dependency-upgrade A dependency upgrade
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant