Repository navigation
Merge main into development before the v0.2.0 promotion - #337
Merged
Merged
Conversation
release: promote development to main (73 commits since v0.1.0)
Release: promote development → main — the docs site stops serving the broken Quickstart
Promote development to main: refresh engine and published docs
Release: promote development to main after scoped external evidence
Release: promote development to main after conformance hardening
Brings the five earlier promotion merge commits (#220, #223, #265, #289, #297) into development so the promotion PR is up to date with main, as the new branch rule requires. No content change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017eKZATy4SSLSBFWZWZwFyZ
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.
The promotion PR #336 shows behind because
mainholds the five earlier promotion merge commits (#220, #223, #265, #289, #297), whichdevelopmentnever received. The new branch rule requires branches to be up to date. This mergesmainintodevelopmentwith no tree change (git diffis empty). Merge with a merge commit. #336 then becomes mergeable.🤖 Generated with Claude Code
https://claude.ai/code/session_017eKZATy4SSLSBFWZWZwFyZ
Generated by Claude Code