ci: automate releases with release-please and OIDC publishing - #17

Merged

pnocera merged 22 commits into

mainfrom

chore/release-automation

Jul 17, 2026

Commits on Jul 17, 2026

ci: automate releases with release-please and OIDC publishing

pnocera
and
claude
committed
82f939b
docs: correct the release runbook's failure and recovery paths
pnocera
committed
c3c75a4
docs: make the manual release procedures fail closed
pnocera
committed
7396a5d
fix(release): check out the release tag by fully qualified ref
pnocera
committed
3d991f8
fix(release): bind the published worktree to the triggering merge
pnocera
committed
84ac766
fix(release): bind the release to the Release PR that produced it
pnocera
committed
66b2db8
fix(release): make the npm-publish environment the boundary; split the jobs
pnocera
committed
abdca1a
fix(release): serialize the release state machine with queue: max
pnocera
committed
c950f63
fix: report the package's real version, not a 1.0.0 literal
pnocera
committed
227cce1
test: assert the version at the surfaces that announce it
pnocera
committed
b4b6984
test: assert the outbound User-Agent on the wire, not in axios defaults
pnocera
committed
d7561e0
test: cover the default version path, not just the override branch
pnocera
committed
93c202a
test: assert the package default at initialize and GET /, and stop leaking config
pnocera
committed
3e48100
test: make the teardown postcondition and env restore actually check
pnocera
committed
84e2783
test: prove the singleton is absent instead of interrogating an error
pnocera
committed
f39b707
docs: stop the local recovery from dragging npm `latest` backwards
pnocera
committed
a24919a
docs: make local recovery mode-explicit and check the published version set
pnocera
committed
0359a72
docs: make backfill prove it is one, and pin npm before the pack preview
pnocera
committed
5e50b3e
docs: let npm enforce the tag policy instead of a homegrown state machine
pnocera
committed
de499ad
docs: arm npm's tag guard properly, and stop claiming it is atomic
pnocera
committed
b49fb8d
docs: do not treat a failed npm config read as proof of a clean config
pnocera
committed
e942a46
docs: match the npm config with bash, not a matcher that can fail
pnocera
committed
4c695d4

Navigation Menu

ci: automate releases with release-please and OIDC publishing - #17

ci: automate releases with release-please and OIDC publishing#17
pnocera merged 22 commits into
mainfrom
chore/release-automation

Commits on Jul 17, 2026

ci: automate releases with release-please and OIDC publishing

docs: correct the release runbook's failure and recovery paths

docs: make the manual release procedures fail closed

fix(release): check out the release tag by fully qualified ref

fix(release): bind the published worktree to the triggering merge

fix(release): bind the release to the Release PR that produced it

fix(release): make the npm-publish environment the boundary; split the jobs

fix(release): serialize the release state machine with queue: max

fix: report the package's real version, not a 1.0.0 literal

test: assert the version at the surfaces that announce it

test: assert the outbound User-Agent on the wire, not in axios defaults

test: cover the default version path, not just the override branch

test: assert the package default at initialize and GET /, and stop leaking config

test: make the teardown postcondition and env restore actually check

test: prove the singleton is absent instead of interrogating an error

docs: stop the local recovery from dragging npm `latest` backwards

docs: make local recovery mode-explicit and check the published version set

docs: make backfill prove it is one, and pin npm before the pack preview

docs: let npm enforce the tag policy instead of a homegrown state machine

docs: arm npm's tag guard properly, and stop claiming it is atomic

docs: do not treat a failed npm config read as proof of a clean config

docs: match the npm config with bash, not a matcher that can fail