Skip to content

fix(ci): recover publication from verified release artifacts - #46

Merged
nichinichisou0609 merged 3 commits into
mainfrom
codex/recover-release-010
Oct 8, 2026
Merged

nichinichisou0609 merged 3 commits into
mainfrom
codex/recover-release-010

Conversation

@nichinichisou0609

Copy link
Copy Markdown
Contributor

Publishing a relative path such as release/package.tgz can be interpreted as a GitHub package spec by npm. Resolve the verified release tarball to an absolute path before publishing.

An explicit recovery mode can publish the original tarball from a completed tag-release run. It validates the repository, tag, source commit, workflow and artifact identities, the complete SHA256SUMS set, the browser manifest and matching ZIP/npm payloads. Default manual runs remain non-publishing preflights. Recovery does not rebuild artifacts or alter the source tag.

Validation: 24 packaging tests, 6 recovery test groups, actionlint, validation of the actual tagged release assets, and a real npm dry-run with the absolute package path all passed. Package sources are unchanged.

@nichinichisou0609
nichinichisou0609 merged commit a24918f into main Oct 8, 2026
8 checks passed
@nichinichisou0609
nichinichisou0609 deleted the codex/recover-release-010 branch October 8, 2026 05:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant