Repository navigation
fix(release): handle first publication and document verified 0.2 alpha - #158
Merged
Merged
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing (31)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Publishing a new package can create npm's
latesttag even when the requested channel isalpha. Record the exact first-version expectation only when pre-publication metadata returns 404; existing packages, the other channel, unchanged dependencies, and old baselines retain strict protection. Add regression coverage for malformed exceptions and tag drift.Update English and Chinese documentation for the eight published 0.2.0-alpha.0 packages, the four unchanged dependencies, managed toolchain setup, bounded bundler/SSR coverage, and deferred Octane. Document the original failed post-publication workflow, independently verified recovery, durable audit attachments, and manual deployment to the existing Cloudflare Pages project.
Validation: full release contract suite, release metadata/change policy, docs verification (71 Markdown pages and 10 Rust examples), and docs build passed locally. Published archives were verified against original GitHub artifacts and actual npm tarballs; Vue/React and managed-preset registry consumers passed. No package versions or runtime implementation change here. Managed registry acceptance reused its Rust cache.
CI strategy: one combined PR; retain Verify and Documentation checks. The unchanged experimental runtime integration matrix is intentionally not repeated for release scripts and documentation. After merge, identical-tree duplicate workflows may be cancelled; cancellations are not reported as test passes.
Summary by CodeRabbit