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

Bump gcr.io/paketo-buildpacks/encrypt-at-rest from 4.5.15 to 4.5.18 #1343

Merged
merged 1 commit into from Mar 26, 2024

Conversation

paketo-bot
Copy link
Member

@paketo-bot paketo-bot commented Feb 29, 2024

@paketo-bot paketo-bot requested a review from a team as a code owner February 29, 2024 04:10
@paketo-bot paketo-bot added semver:patch A change requiring a patch version bump type:dependency-upgrade A dependency upgrade labels Feb 29, 2024
@paketo-bot paketo-bot changed the title Bump gcr.io/paketo-buildpacks/encrypt-at-rest from 4.5.15 to 4.5.16 Bump gcr.io/paketo-buildpacks/encrypt-at-rest from 4.5.15 to 4.5.17 Mar 7, 2024
@paketo-bot paketo-bot force-pushed the update/package/encrypt-at-rest branch from 9614412 to 2e4121e Compare March 7, 2024 04:10
Bumps gcr.io/paketo-buildpacks/encrypt-at-rest from 4.5.15 to 4.5.18.

Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@paketo-bot paketo-bot changed the title Bump gcr.io/paketo-buildpacks/encrypt-at-rest from 4.5.15 to 4.5.17 Bump gcr.io/paketo-buildpacks/encrypt-at-rest from 4.5.15 to 4.5.18 Mar 26, 2024
@paketo-bot paketo-bot force-pushed the update/package/encrypt-at-rest branch from 2e4121e to d6541d4 Compare March 26, 2024 02:32
@anthonydahanne anthonydahanne merged commit e16b08c into main Mar 26, 2024
4 checks passed
@anthonydahanne anthonydahanne deleted the update/package/encrypt-at-rest branch March 26, 2024 15:46
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.

None yet

2 participants