chore(release): 0.7.0 — bring develop onto main - #154
Merged
Conversation
Each token step ran on an iter.Pull coroutine of its own so a breakpoint or a clock wait inside its body could pause the token. Go's race runtime keeps a coroutine's TSan state after it ends, so a run of a million steps under -race grew to several gigabytes and the runtime test binary was killed for memory on CI. The steps of a run now share one body coroutine kept idle on the Context between steps and ended when the outermost run leaves; a paused step keeps its coroutine until it ends, so the next step makes another. Pausing, resuming, Release and the deadlock reported for an abandoned pause are unchanged. Co-Authored-By: jason.han <[email protected]>
Development merges into `develop`; `main` carries releases only and receives `release/x.y.z` and `hotfix/` pull requests. CircleCI's build-test workflow now runs on merges to both branches (the release workflow stays on tags), `make proto-breaking` compares against `origin/develop` by default, and CONTRIBUTING.md, AGENTS.md and docs/project/releasing.md describe the branch model and the release branch flow. Co-Authored-By: jason.han <[email protected]>
Co-Authored-By: jason.han <[email protected]>
Each token step ran on an iter.Pull coroutine of its own so a breakpoint or a clock wait inside its body could pause the token. Go's race runtime keeps a coroutine's TSan state after it ends, so a run of a million steps under -race grew to several gigabytes and the runtime test binary was killed for memory on CI. The steps of a run now share one body coroutine kept idle on the Context between steps and ended when the outermost run leaves; a paused step keeps its coroutine until it ends, so the next step makes another. Pausing, resuming, Release and the deadlock reported for an abandoned pause are unchanged. Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: jason.han <[email protected]>
* ci(branching): adopt develop as the integration branch Development merges into `develop`; `main` carries releases only and receives `release/x.y.z` and `hotfix/` pull requests. CircleCI's build-test workflow now runs on merges to both branches (the release workflow stays on tags), `make proto-breaking` compares against `origin/develop` by default, and CONTRIBUTING.md, AGENTS.md and docs/project/releasing.md describe the branch model and the release branch flow. Co-Authored-By: jason.han <[email protected]> * docs(releasing): compare release and hotfix branches against origin/main Co-Authored-By: jason.han <[email protected]> --------- Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: jason.han <[email protected]>
Co-Authored-By: jason.han <[email protected]>
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
HuiJun
approved these changes
Sep 9, 2026
6 tasks
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
1 participant
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.
What and why
Moves the integration state of
developontomainso thatv0.7.0can be tagged with everything the release should carry.mainalready holds the folded## 0.7.0 — 2026-09-09entry (#145) but not the changes merged todevelopsince:Go race testsjob onmainpass again (everymainpipeline since the shared simulation clock landed failed that job on memory).develop/mainbranch model: CircleCIbuild-teston both branches,BUF_BREAKING_REFdefaulting toorigin/develop, CONTRIBUTING / releasing / AGENTS updated.changes/unreleased/after merging tomain.The release branch is cut from
develop(which already hasmainmerged in, somaingains no unrelated commits) plus one commit that folds the three outstanding fragments into the existing## 0.7.0sections (Added / Changed / Performance) rather than opening a new version, since 0.7.0 has not been tagged yet.changes/unreleased/is back to its README only.How it was verified
python3 scripts/changelog.py checkandmake docs-checkpass.gofmt -l .prints nothing;go build ./...andgo vet ./...are clean.api/protois byte-identical betweenorigin/mainand this branch, so the wire-compatibility check against the released schema has nothing to compare.develop; theGo race testsjob onmainafter this merge is the authoritative check for the memory fix.After merging: tag
v0.7.0onmain, then mergemainback intodevelop(plain merge) asdocs/project/releasing.mddescribes.Checklist
make testandmake lintpass locally (the branch isdevelopplus a changelog fold;gofmt,go build,go vetandmake docs-checkre-run here)## 0.7.0entry, which is what a release branch does perdocs/project/releasing.mdmake docs-countsrun if a gate count moved — no gate count moved