Open the version bump as a pull request

Conversation 0 Commits 2 Files Changed 4

+75 -33

2 Commits

Author	SHA1	Message	Date
thatguygriffandClaude Opus 5	43dc10e1dc	Set the working version to 1.2.2 CI / Typecheck, test, build (pull_request) Successful in 14s Details Publish / Build and push (pull_request) Successful in 20s Details Publish / Move the working version on (pull_request) Skipped Details 1.2.1 shipped, so the tree was left on a version that is published and immutable, which is the thing the bump job exists to prevent. It failed before it got that far. Done by hand here, once: the job only fires on a tag, so no re-run of it will do this retroactively. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01XBT25ZDzm453A8XViSRqRB	2026-08-27 20:35:36 -03:00
thatguygriffandClaude Opus 5	b94c43a10c	Open the version bump as a pull request The bump job has never once worked. Its first step died in two seconds on `set: Illegal option -o pipefail` -- it is the only job here that runs in a container, and a container job is handed `sh -e {0}` rather than the bash the runner gives its own jobs. Dash has no `pipefail`, and no `10#` either, so the arithmetic on the line after would have gone the same way. It now asks for bash, which node:22 carries. That would have got the job as far as its last step, which pushed straight to main. Nothing had ever exercised that, and it needs the token to be allowed past whatever protects the branch -- hence the second token, VERSION_BUMP_TOKEN, standing by for where it is not. unsupervised-scheduler has been bumping its version on every release for a while by pushing a branch and opening a pull request with the ordinary task token, so that is what this does now. The second token is no longer needed, and neither is `[skip ci]`: main is never pushed, so there is no build of the just-published image to suppress. The pull request puts the changed package.json through a build before it lands. scheduler builds the request body with jq because its CI image carries jq. This one is node:22, where node is the thing that certainly is there. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01XBT25ZDzm453A8XViSRqRB	2026-08-27 20:35:33 -03:00

Author

SHA1

Message

Date

thatguygriffandClaude Opus 5

43dc10e1dc

Set the working version to 1.2.2

CI / Typecheck, test, build (pull_request) Successful in 14s

Details

Publish / Build and push (pull_request) Successful in 20s

Details

Publish / Move the working version on (pull_request) Skipped

Details

1.2.1 shipped, so the tree was left on a version that is published and
immutable, which is the thing the bump job exists to prevent. It failed before
it got that far. Done by hand here, once: the job only fires on a tag, so no
re-run of it will do this retroactively.

Co-Authored-By: Claude Opus 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01XBT25ZDzm453A8XViSRqRB

2026-08-27 20:35:36 -03:00

thatguygriffandClaude Opus 5

b94c43a10c

Open the version bump as a pull request

The bump job has never once worked. Its first step died in two seconds on
`set: Illegal option -o pipefail` -- it is the only job here that runs in a
container, and a container job is handed `sh -e {0}` rather than the bash the
runner gives its own jobs. Dash has no `pipefail`, and no `10#` either, so the
arithmetic on the line after would have gone the same way. It now asks for
bash, which node:22 carries.

That would have got the job as far as its last step, which pushed straight to
main. Nothing had ever exercised that, and it needs the token to be allowed
past whatever protects the branch -- hence the second token, VERSION_BUMP_TOKEN,
standing by for where it is not. unsupervised-scheduler has been bumping its
version on every release for a while by pushing a branch and opening a pull
request with the ordinary task token, so that is what this does now. The second
token is no longer needed, and neither is `[skip ci]`: main is never pushed, so
there is no build of the just-published image to suppress. The pull request
puts the changed package.json through a build before it lands.

scheduler builds the request body with jq because its CI image carries jq. This
one is node:22, where node is the thing that certainly is there.

Co-Authored-By: Claude Opus 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01XBT25ZDzm453A8XViSRqRB

2026-08-27 20:35:33 -03:00

Open the version bump as a pull request #6