chore(release): v0.37.1 - #1202
Merged
Merged
Conversation
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
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
Version-and-changelog only bump of
0.37.0→0.37.1, cut withpnpm lerna version --yes --no-push.@soat/sdkand@soat/clipublish to npm;app,postgresdb,serverandwebsiteare private and bump in lockstep.Contents
One commit since
v0.37.0:A
cost_usdquota's blackout verdict counted every usage event whatever its meter type, so a window holding only unpricedcompute_executionevents refused every generation with409 QUOTA_UNENFORCEABLE— and could not recover, because the refusal blocked the very generation that would have landed the first priced event. Nothing in the request or response contract changes;on_unpricedgains a sentence naming which meter the verdict reads.This is the release naturali needs in order to move its runtime pin off
0.36.0, so its live e2e stops failing on every deploy.Merge instructions
Squash and merge, so the commit landing on
mainkeeps a subject starting withchore(release):. Every job inmain.ymlre-checks that prefix onhead_commit.message; a default merge commit is titledMerge pull request #NNN…, which would silently skip the tag push, the npm publish and the Docker image while the PR still shows green.Per
.claude/rules/release.md,pr.ymlskips the build, smoke and tutorials jobs on achore(release):title, since these commits were already validated onmain. #1201 passed the full suite there, including both live-stack suites.After merging, confirm the
main.ymlrun actually started for the merge commit rather than being skipped.Process notes
0.37.0) matchedgit describebefore the run — no dry-run writes had leaked into the tree.--dry-runthis time. The only commit is afixwith noBREAKING CHANGEfooter, so the patch bump was unambiguous and skipping the preview avoids the double-bump trap entirely.mainhad diverged: it still carried the unpushed, amendedv0.37.0release commit whose content was squash-merged upstream. Reset toorigin/mainbefore cutting, verified by checking that commit was its only local-only one.engineschange. The orphaned local tag was deleted, sincepush-release-tagcreates the real one from the merge commit.🤖 Generated with Claude Code
https://claude.ai/code/session_01DRwsGecUbNX8PcAzZ5L2ov
Generated by Claude Code