Skip to content

chore(release): v0.37.1 - #1202

Merged
arantespp merged 1 commit into
mainfrom
release/v0.37.1
Sep 3, 2026
Merged

chore(release): v0.37.1#1202
arantespp merged 1 commit into
mainfrom
release/v0.37.1

Conversation

@arantespp

Copy link
Copy Markdown
Member

Summary

Version-and-changelog only bump of 0.37.00.37.1, cut with pnpm lerna version --yes --no-push.

@soat/sdk and @soat/cli publish to npm; app, postgresdb, server and website are private and bump in lockstep.

Contents

One commit since v0.37.0:

Type Change
Fix read the AI meter alone for a cost quota's pricing blackout (#1201)

A cost_usd quota's blackout verdict counted every usage event whatever its meter type, so a window holding only unpriced compute_execution events refused every generation with 409 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_unpriced gains 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 main keeps a subject starting with chore(release):. Every job in main.yml re-checks that prefix on head_commit.message; a default merge commit is titled Merge 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.yml skips the build, smoke and tutorials jobs on a chore(release): title, since these commits were already validated on main. #1201 passed the full suite there, including both live-stack suites.

After merging, confirm the main.yml run actually started for the merge commit rather than being skipped.

Process notes

  • Tags were fetched first, and the version lerna reported as current (0.37.0) matched git describe before the run — no dry-run writes had leaked into the tree.
  • No --dry-run this time. The only commit is a fix with no BREAKING CHANGE footer, so the patch bump was unambiguous and skipping the preview avoids the double-bump trap entirely.
  • Local main had diverged: it still carried the unpushed, amended v0.37.0 release commit whose content was squash-merged upstream. Reset to origin/main before cutting, verified by checking that commit was its only local-only one.
  • Engines were relaxed for lerna and restored in an amend; the commit carries no engines change. The orphaned local tag was deleted, since push-release-tag creates the real one from the merge commit.

🤖 Generated with Claude Code

https://claude.ai/code/session_01DRwsGecUbNX8PcAzZ5L2ov


Generated by Claude Code

@arantespp
arantespp merged commit 9a9a02f into main Sep 3, 2026
8 checks passed
@arantespp
arantespp deleted the release/v0.37.1 branch September 3, 2026 15:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants