docs(repo): add 2 release-recovery durable lessons (v0.6.2→v0.6.3)#149
Merged
Merged
Conversation
From the 2026-05-28 release-recovery (session-88b46e). Triggering the first release of the session surfaced two pre-existing bugs that had silently broken npm publishing: - conventions/vendored-artifact-bump-must-revendor-in-same-pr.md — PR #137 bumped web-tree-sitter 0.26.8→0.26.9 without re-running the vendor script. Passed all CI (the prepublishOnly guard isn't a CI step) and aborted the dependency-ordered publish at release time. Re-vendor vendored-artifact deps in the same PR; ideally promote the guard into CI so the bump fails red, not the release. - conventions/npm-trusted-publisher-matches-entry-workflow-not-reusable.md — npm OIDC matches the entry workflow (release-please.yml), not the reusable workflow that runs npm publish (release.yml). Registering the wrong one 404s the token exchange; only manual workflow_dispatch runs ever published, so npm lagged the git tags for a full release cycle. INDEX.md updated with both pointers.
Merged
theagenticguy
pushed a commit
that referenced
this pull request
May 29, 2026
🤖 Automated release via release-please --- <details><summary>root: 0.6.4</summary> ## [0.6.4](root-v0.6.3...root-v0.6.4) (2026-05-28) ### Documentation * **repo:** add 2 release-recovery durable lessons (v0.6.2→v0.6.3) ([#149](#149)) ([6a59d38](6a59d38)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@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
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.
Summary
Docs-only Compound follow-on to the v0.6.2 → v0.6.3 release recovery. Two durable ERPAVal lessons capturing the pre-existing bugs that triggering the release surfaced.
vendored-artifact-bump-must-revendor-in-same-pr— PR build(deps): consolidate weekly Dependabot bumps (2026-05-28) #137 bumpedweb-tree-sitter0.26.8→0.26.9 without re-running the vendor script. It passed all CI (theprepublishOnlyguard isn't a CI step) and aborted the dependency-ordered publish at release time. Re-vendor vendored-artifact deps in the same PR; ideally promote the guard into CI so the bump fails red, not the release.npm-trusted-publisher-matches-entry-workflow-not-reusable— npm OIDC matches the entry workflow (release-please.yml), not the reusable one that runsnpm publish(release.yml). Registering the wrong one 404s the token exchange; only manualworkflow_dispatchruns ever published, so npm lagged the git tags for a full release cycle. Config is web-UI-only, passkey-gated, one entry per package (17 here).Test plan
docs(repo):accepted