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
New Release ? #3809
Comments
Current CVEs reported on latest release: |
/cc @milosgajdos |
There is no immediate plan for a new release -- but there is a Project milestone that contains a list of issues we'd like to get fixed for the RC at least: https://github.com/distribution/distribution/milestone/22 |
ok, I would still hope for a patch release to atleast get rid of the CVEs meanwhile ? |
That makes sense. We'll get to it -- I believe @wy65701436 is attempting to update Once that's sorted we'll do a patch release |
Are there any updates on when a new release will be cut? |
If there's going to be a patch release, could we add #2815 to it? it was added to the 2.8 milestone, but it doesn't seem like it made into the release. |
@flavianmissi I created a PR to backport that change into 2.8. See #3893 |
@flavianmissi Just thought I'd let you know it is now included in release 2.8.2. |
@davidspek is there a plan to backport this fix to earlier versions, e.g. 2.7? |
@tianouya-db There’s currently no plan to backport the fix to earlier versions. Currently we’re putting all effort into the release of v3. |
Closing, we've just made the first |
Is there any timeline when we will have a new release? The last release was in March and still uses older golang versions which is susceptible to multiple CVEs and the main branch has gone far ahead. It will be really nice if we can expect a release now.
The text was updated successfully, but these errors were encountered: