Repository navigation
fix(release): prepare trusted publication of v1.0.1 - #28
Merged
Merged
Conversation
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
1 participant
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.
Release publishing currently looks for tarballs in the wrong locations and still configures npm token authentication. Fix the archive paths, publish through the production environment using npm trusted publishing and GITHUB_TOKEN for GitHub Packages, and explicitly set latest in both registries. Keep the registry matrix independent so failed publication jobs can be rerun separately.
Start release now gates the draft release on separate lint, formatting, and documentation jobs. Both release workflows compare the tag without its v prefix against package.json. Bump the package and lockfile to 1.0.1 and update contributor instructions. PR and edge workflows are unchanged.
Validation: build, lint, formatting, documentation build, npm pack, packed manifest inspection, and matching/mismatched version probes passed. Actionlint passed with only its outdated ubuntu-26.04 label check excluded. The production environment was created and the repository NPM_TOKEN secret was removed. Hosted release and OIDC publication will be verified after merge.