Repository navigation
chore(release): v3.5.0 - #1537
Merged
Merged
Conversation
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 47 minutes. View limit details
No actionable comments were generated in the recent review.
 |
| Layer / File(s) | Summary |
|---|---|
Release entry and workspace versions CHANGELOG.md, Cargo.toml, crates/ox_content_napi/package.json, editors/zed/*, docs/content/getting-started.md |
The changelog adds the 3.5.0 release entry. Workspace, crate, editor, and Rust documentation dependency versions change from 3.4.3 to 3.5.0. |
npm package versions npm/ox-content-code-play/package.json, npm/ox-content-islands/package.json, npm/oxct/package.json, npm/theme-color/*/package.json, npm/theme/*/package.json, npm/unplugin-ox-content/package.json, npm/vite-plugin-ox-content*/package.json, npm/vscode-ox-content/package.json |
The listed npm package versions change from 3.4.3 to 3.5.0. |
Priority:
Estimated code review effort: 2 (Simple) | ~8 minutes
Change: Other
Suggested reviewers: kazupon
Merge Risk: 
a497a
-
This release metadata update is ready to merge with no identified functional or operational risk.
Pre-merge checks: 
-
Check name Status Explanation Resolution Description check The description identifies the v3.5.0 release process but does not follow the required template. It omits the Summary, Risk, Validation, and Release and docs checklist sections and their required deta… Add the required template sections. Document the release summary, risk level, user or production impact, rollback plan, automated checks, manual verification, considered edge cases, and applicable documentation, configuration, observability… -
Check name Status Explanation Title check The title clearly identifies the release version and matches the primary changes, which update the repository and packages to v3.5.0. Docstring Coverage No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat… Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request. Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (89 skipped: 89 unsupported.)
-
Full details: Description check
-
Explanation
The description identifies the v3.5.0 release process but does not follow the required template. It omits the Summary, Risk, Validation, and Release and docs checklist sections and their required details.
Resolution
Add the required template sections. Document the release summary, risk level, user or production impact, rollback plan, automated checks, manual verification, considered edge cases, and applicable documentation, configuration, observability, security, privacy, and dependency impacts. Mark items as not needed when applicable.
-
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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 @coderabbitai help to get the list of available commands.
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.
Release v3.5.0. Chromium remains the default OG renderer; Satori and Takumi (
@takumi-rs/core) are explicit browserless alternatives. TypeScript, Vue, Svelte, React, and Solid templates share the SSR pipeline, with component CSS and local public images preserved. Takumi package-family settings use@takumi-rs/*rather than enumerating platform packages.The exact release head
3f4fdc29passed CI and the full release validation. The merged commit and immutablev3.5.0tag are9f615ce9a5708aa3249d53d514e4bcd8f5f179ad.Core publication succeeded. Public verification covered all 91 npm packages (version, signature/provenance metadata, and tarball integrity), all 13 crates.io archives and their checksums, and all four native CLI archive checksums. A new project installed the published package and successfully built all 15 renderer/template combinations, verifying 1200×630 PNG output, OG/Twitter metadata, and ESM/CommonJS exports.
VS Code Marketplace publication was verified for all four platform targets. Open VSX publication failed with
No trusted publisher matches the presented token; the namespace's trusted publisher must be configured before retrying only that publisher job.