Skip to content

fix: recover exact publish artifact - #37

Merged
tensornull merged 1 commit into
mainfrom
agent/recover-publish-runtime-artifact
Jul 29, 2026
Merged

fix: recover exact publish artifact#37
tensornull merged 1 commit into
mainfrom
agent/recover-publish-runtime-artifact

Conversation

@tensornull

Copy link
Copy Markdown
Contributor

What changed

  • Keep Release Please result evidence under runner.temp so release checks do not format runtime artifacts.
  • Add a one-cycle, exact-source recovery trigger for the already-created immutable v0.1.1 Release after the observed downstream gate failure.
  • Validate the recovery actor, source run, release commit, direct first parent, exact repair file set, artifact identity, and rerun state.

Root cause

Publish run 30469240186 verified the immutable Release and result artifact, then failed before packing because release-please-result/result.json was inside the Prettier workspace. No live smoke, OIDC, npm, or version/tag mutation occurred.

Verification

  • npm test (386 tests)
  • npm run format:check
  • npm run lint
  • npm run typecheck
  • npm run actionlint (1.7.12)
  • npm run check:self-contained
  • npm run check:public-preview
  • npm run test:secrets
  • git diff --check

The recovery constants are temporary and are documented for removal in the post-release evidence PR.

@tensornull
tensornull merged commit 22c313d into main Jul 29, 2026
9 checks passed
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