Repository navigation
fix(release): bump every sdk npm package in lockstep, incl. @nself/cli-api - #914
Conversation
ca3d4f0 to
1970113
Compare
1970113 to
5aabcbe
Compare
|
Rebased onto origin/main and resolved the merge conflict in scripts/release/fixtures/cases4.sh. Kept both sides' intent: the TMPDIR fix from main (GNU mktemp needs a live TMPDIR) and the dynamic sdk/*/package.json discovery from this branch (so ts-cli-api and any future SDK packages are included without hardcoding). Syntax check passes, no conflict markers remain. Force-pushed to fix/sdk-lockstep-ts-cli-api. |
…i-api (1.4.15) bump-version.sh listed sdk/ts and sdk/ts-sdk by hand and skipped sdk/ts-cli-api, so the v1.4.15 release left it at 1.4.14 and SDK Version Sync has been red on main since. The bumper and the three lockstep checks now glob sdk/*/package.json, so a new package is covered from the day it exists. The release fixture tests run the real bumper over one fixture per sdk package and fail when any is left behind. sdk/ts-cli-api is brought to 1.4.15 to complete the already released 1.4.15. No tag, release or npm publish.
5aabcbe to
e25b3d4
Compare
|
Rebased onto origin/main and resolved the merge conflict in cmd/commands/canon_engine_test.go by keeping both sides' intent (t.Cleanup for test isolation plus the fixture restoration logic). Tests pass: go test ./cmd/commands/ -run 'TestCanonEngine|TestHubUnknownSubcommand|TestHelpOnlyParentsComplete'. Force-pushed to fix/sdk-lockstep-ts-cli-api. |
bump-version.sh listed sdk/ts and sdk/ts-sdk by hand and skipped sdk/ts-cli-api, so the v1.4.15 release left it at 1.4.14 and SDK Version Sync has been red on main since (run 39381525318).