-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
feat(maven): Remove unnecessary HTML page fetches #32662
feat(maven): Remove unnecessary HTML page fetches #32662
Conversation
Currently, for every package we're fetching:
If first 3 are done correctly, seems like we don't need the latter one. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently, for every package we're fetching:
* `maven-metadata.xml` * GET the latest POM file (for `homepage`/`sourceUrl`) * HEAD the POM file of the selected/filtered release (often matches with GET of the latest one) * [Maven Central only] HTML index page
If first 3 are done correctly, seems like we don't need the latter one.
If I'm not mistaken "GET the latest POM file (for homepage
/sourceUrl
)" is done after populating the list of releases, i.e.., any release that is unknown at this point won't be pulled. Hence, the "[Maven Central only] HTML index page" step is actually second, not last. Do you agree?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
otherwise LGTM
🎉 This PR is included in version 39.35.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Changes
It doesn't seem necessary now when we're able to obtain all necessary information by querying the corresponding POM file of a particular package version.
Context
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: