build(deps): bump github.com/docker/distribution from 2.7.1+incompatible to 2.8.1+incompatible by dependabot[bot] · Pull Request #17 · unacast/act
Bumps github.com/docker/distribution from 2.7.1+incompatible to 2.8.1+incompatible.
Release notes
Sourced from github.com/docker/distribution's releases.
v2.8.1
Welcome to the v2.8.1 release of registry!
The 2.8.1 registry release fixes the Go module issues that have popped up in the v2.8.0
There have been no changes made in the released binaries other than the bump of the Go runtime.
See the changelog below for a full list of changes.
CI
- ci: use proper git ref for versioning #3595
- Go: make Go version explicit and pin it to the latest 1.16 release #3604
Contributors
- CrazyMax
- Milos Gajdos
Changes
96cc1fdbFIx typoe744906fUpdate 2.8.1. release notes- Prepare for v2.8.1 release (#3596)
6736d188Prepare for v2.8.1 release- [2.8 backport] ci: use proper git ref for versioning (#3595)
80acbdf0ci: use proper git ref for versioningDependency Changes
This release has no dependency changes
The previous release can be found at v2.8.0
v2.8.0
registry 2.8.0
Welcome to the v2.8.0 release of registry!
The 2.8.0 registry release has been a long time overdue. This is the first step towards the last 2.x release. No further active development will continue on 2.x branch. Security vulnerability patches to 2.x might be considered, but all active development will be focussed on v3 release due in 2022. This release includes a security vulnerability fix along with a few minor bug fixes and improvemnts in documentation and CI.
... (truncated)
Commits
b5ca020Merge pull request #3605 from milosgajdos/update-release-notes1b5f094Merge pull request #3604 from crazy-max/2.8-go-1.16.1596cc1fdFIx typoe744906Update 2.8.1. release notes3df9fcego 1.16.159a0196bMerge pull request #3596 from milosgajdos/fix-go-mod-v2.8.16736d18Prepare for v2.8.1 releasee4a447dMerge pull request #3595 from crazy-max/2.8-ci-gitref80acbdfci: use proper git ref for versioningdcf6639Update README so the release pipeline works properly.- 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)