turkdevops / play-with-docker

You know it, you use it, now it's time to improve it. PWD!.
http://play-with-docker.com
MIT License
0 stars 0 forks source link

Bump github.com/docker/distribution from 2.6.0-rc.1.0.20170726174610-edc3ab29cdff+incompatible to 2.8.0+incompatible #69

Open dependabot[bot] opened 1 year ago

dependabot[bot] commented 1 year ago

Bumps github.com/docker/distribution from 2.6.0-rc.1.0.20170726174610-edc3ab29cdff+incompatible to 2.8.0+incompatible.

Release notes

Sourced from github.com/docker/distribution's releases.

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.

See changelog below for full list of changes.

Bugfixes

  • Close the io.ReadCloser from storage driver #3370
  • Remove empty Content-Type header #3297
  • Make ipfilteredby not required in cloudfront storage middleware #3088

Features

  • Add reference.ParseDockerRef utility function #3002

CI build

  • First draft of actions based ci #3347
  • Fix vndr and check #3001
  • Improve code quality by adding linter checks #3385

Documentation

  • Add redirect for old URL #3197
  • Fix broken table #3073
  • Adding deprecated schema v1 instructions #2987
  • Change should to must in v2 spec (#3495)

Storage drivers

  • S3 Driver: add support for ceph radosgw #3119

Security

Changes

  • Prepare for v2.8.0 release (#3552)
    • d5d89a46 Make this releaes a beta release first.
    • 1ddad0ba Apply suggestions from code review

... (truncated)

Commits


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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/turkdevops/play-with-docker/network/alerts).