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

New Release ? #3809

Closed
kashifest opened this issue Nov 29, 2022 · 13 comments
Closed

New Release ? #3809

kashifest opened this issue Nov 29, 2022 · 13 comments

Comments

@kashifest
Copy link

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.

@kashifest
Copy link
Author

Current CVEs reported on latest release:
CVE-2021-44716, golang: net/http: limit growth of header canonicalization,https://avd.aquasec.com/nvd/cve-2021-44716
CVE-2022-27664, golang: net/http: handle server errors after sending GOAWAY, https://avd.aquasec.com/nvd/cve-2022-27664

@kashifest
Copy link
Author

/cc @milosgajdos

@milosgajdos
Copy link
Member

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

@kashifest
Copy link
Author

ok, I would still hope for a patch release to atleast get rid of the CVEs meanwhile ?

@milosgajdos
Copy link
Member

That makes sense. We'll get to it -- I believe @wy65701436 is attempting to update Go in #3808

Once that's sorted we'll do a patch release

@kitemongerer
Copy link

Are there any updates on when a new release will be cut?

@tristanmorgan
Copy link

#3808 has been replaced by #3812 and still in progress.

@flavianmissi
Copy link
Contributor

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.
I'm not sure what the backport process is around here, but I'd be happy to help out with 2815 if necessary.

@davidspek
Copy link
Collaborator

@flavianmissi I created a PR to backport that change into 2.8. See #3893

@davidspek
Copy link
Collaborator

@flavianmissi Just thought I'd let you know it is now included in release 2.8.2.

@tianouya-db
Copy link

tianouya-db commented Aug 16, 2023

@davidspek is there a plan to backport this fix to earlier versions, e.g. 2.7?

@davidspek
Copy link
Collaborator

@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.

@milosgajdos
Copy link
Member

milosgajdos commented Dec 19, 2023

Closing, we've just made the first v3 release https://github.com/distribution/distribution/releases/tag/v3.0.0-alpha.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants