chore(release): prepare v0.7.1 stable publication - #173
Merged
Conversation
Eclipseic1848
marked this pull request as ready for review
September 3, 2026 18:51
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
Validation
npm run build:python-worker: passed.npm run check: passed (320 Biome files, TypeScript checks, 22 module contracts, five golden examples, 14 bilingual documentation pairs, 466 Markdown/MDX files).PYTHONPATH: 29 passed; Python golden example tests: 2 passed.npm run docs:build: passed; existing bundle-size warning only.npm run security:audit: passed; production dependencies have no known vulnerabilities, existing development-only risks remain recorded through 2026-09-30.git diff --check: passed.Release boundary
This PR does not publish packages or create a tag. After both required Engineering checks pass and this PR is merged, the v0.7.1 candidate and publication workflows will run against the exact protected-main commit. GitHub Release, npm, and PyPI publication are explicitly authorized by the maintainer.
CI regression follow-up