fix: package.json homepage links to use the main branch
#6336
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
So with the
fast-xml-parservulnerability I was trying to trace down if updating would help, and I started at the npm package page for @aws-sdk/core. Thehomepagelink was out of date and led to a 404.I looked at the
package.jsonfiles inclients/*andpackages/*looking forhomepagevalues not using themainbranch, and corrected them tomain.Testing
No code testing, a documentation change.
Checklist
@publictag and enable doc generation on the package?By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.