Repository navigation
Align npm publish with trusted publishing and normalize package metadata - #18
Merged
Merged
Conversation
Agent-Logs-Url: https://github.com/hustcc/amapcn/sessions/70dde235-8ad9-4536-8684-162f1aeb035f Co-authored-by: hustcc <7856674+hustcc@users.noreply.github.com>
Agent-Logs-Url: https://github.com/hustcc/amapcn/sessions/3be074a1-2d6d-4dbb-a097-9f378b17d06d Co-authored-by: hustcc <7856674+hustcc@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The publish job was failing at
npm publish --provenance --access publicwithE404after the package had already built and been packed successfully. This change set aligns the release path with npm trusted publishing expectations and removes metadata drift that npm was auto-correcting during publish.Publish auth path
Package metadata normalization
repositoryinmap/package.jsonto the object form npm expects.Release behavior
mapworkspace package (amapcn).npm publish --provenance --access publicas the release command; the change is in how the package and workflow are prepared for that publish.{ "repository": { "type": "git", "url": "git+https://github.com/hustcc/amapcn.git" } }