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 snok/container-retention-policy from 1 to 2 #172

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 16, 2023

Bumps snok/container-retention-policy from 1 to 2.

Release notes

Sourced from snok/container-retention-policy's releases.

v2.0.0

What's Changed

The two major changes in this release is that we now support deleting over 100 packages, as we will traverse the paginated API results. The second being that we've switched the action from running in a container, to running as a composite action. Neither change should break normal workflows.

New Contributors

Full Changelog: snok/container-retention-policy@v1...v2.0.0

v1.5.1

Changes

  • Increased the number of packages fetched from 30 to 100 (#44)

v1.5.0

This release adds the possibility of using wildcards in the image-names attribute. This changes the behaviour of the action from a single-image retention tool, to potentially being used as a more general policy. See #39 for doc changes.

v1.4.2

Improvements

  • Adds explicit error handling for HTTP timeout errors (#30, #29)

v1.4.1

Fixes

v1.4.0

  • Makes the output for public images that cannot be deleted a little friendlier

  • Adds deleted, failed, and needs-github-assistance action outputs, containing lists of images and versions.

    For those unfamiliar with how to interact with Github action outputs: if you specify and id of, e.g., "delete-images" to the action when run, you can access its outputs in subsequent steps, using ${{ steps.delete-images.outputs.deleted }}.

    The outputs can be used to, e.g., skip trying to delete the same images in subsequent runs. See this post for details.

    Thanks @​Siemienik for the idea, and help on the implementation.

v1.3.4

Limit action to running 50 requests concurrently. This fixes an issue where the HTTPX client would throw errors on exceeding 100 connections (#19)

... (truncated)

Commits
  • 482ce28 Merge pull request #56 from lukasz-mitka/patch-1
  • 9a06221 Fix multiline
  • 6c1efda Change tests as well
  • 48f8776 Fix output
  • 192ba6d fix: Handle missing 'link' header attribute
  • 02b1c7a Merge pull request #48 from artazar/keep_at_least_filtered
  • 2d1b1bd Merge branch 'main' into keep_at_least_filtered
  • 3863241 Merge pull request #55 from snok/v2-upgrade
  • b1ae540 Merge branch 'main' into keep_at_least_filtered
  • f82e63c feat: Add pagination to list package functions
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

Bumps [snok/container-retention-policy](https://github.com/snok/container-retention-policy) from 1 to 2.
- [Release notes](https://github.com/snok/container-retention-policy/releases)
- [Commits](snok/container-retention-policy@v1...v2)

---
updated-dependencies:
- dependency-name: snok/container-retention-policy
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file major Major semver labels Feb 16, 2023
@some-natalie some-natalie merged commit 0e1dc9d into main Feb 16, 2023
@some-natalie some-natalie deleted the dependabot/github_actions/snok/container-retention-policy-2 branch February 16, 2023 16:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file major Major semver
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant