Repository navigation
fix(release): publish local tarballs and allow verified retries - #10
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.
Merge Verdict
[APPROVE] Merge with rebase after CI passes.
Summary
The first 0.2.0 release passed every verification but npm interpreted
artifacts/ranui-preview-0.2.0.tgzas GitHub shorthand and attempted an SSH Git fetch. Publish the absolute local tarball path instead.Add a manual release trigger so the verified release can be retried from the selected workflow ref without rewriting the existing version tag. Both triggers retain the stable package/version check, artifact verification and npm-environment OIDC publishing.
Risk Analysis
Low: workflow-only change; package files and runtime code are unchanged. Manual publishing checks out the selected immutable workflow SHA, and its input must match the package's stable version.
Design Decisions
Keep
v0.2.0and its existing release intact. Recover through the corrected workflow on main, rebuild/reverify, and compare the stored archive with the original verified archive before accepting publication.Code Concerns
No remaining findings from the focused workflow review.
Verification
The failed run identifies the exact incorrect Git URL. Publishing the original verified archive by absolute path with
npm publish --dry-run --ignore-scripts --access public --tag latestpasses. Workflow formatting and whitespace checks pass. The unchanged runtime already passed the 42-case three-engine suite and installed-tarball validation.