chore(release): bump version to v1.28.3 - #534
Conversation
🤖 CodeAnt AI — Review Status
|
|
ⓘ Qodo reviews are paused because your trial has ended. Ask your workspace admin to add credits to resume reviews. Manage billing |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
|
Important Review skippedNo new commits to review since the last review. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (7)
Included review availability: 0 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 1 review per hour. 📝 WalkthroughWalkthroughThe project version was incremented to 1.28.3 across application metadata and service worker caches. Release documentation now identifies the 1.28.3 release candidate and records expanded onboarding regression coverage. ChangesVersion 1.28.3 release preparation
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This PR synchronizes the v1.28.3 release metadata and references fixes already merged to main; no actionable merge-blocking risk remains beyond normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1 files. (6 skipped: 6 unsupported.) ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThis release-prep PR bumps the project to v1.28.3 across package, service-worker, Tauri, and documentation metadata, while adding a changelog entry that summarizes the two already-merged onboarding/E2E fixes. No new functional application code is introduced; reviewers should verify version consistency, generated metadata, cache invalidation, and that the changelog accurately scopes issue #532 as still open. Flow diagram for v1.28.3 version propagationflowchart LR
Package[package.json v1.28.3] --> SyncSW[sync-sw-version.mjs]
Package --> SyncTauri[sync-tauri-version.mjs]
SyncSW --> ServiceWorker[public/sw.js]
SyncSW --> CacheNames[Versioned service-worker caches]
SyncTauri --> TauriManifest[src-tauri/tauri.conf.json]
SyncTauri --> Cargo[src-tauri/Cargo.toml and Cargo.lock]
Package --> Docs[AGENTS.md and CHANGELOG.md]
File-Level Changes
Possibly linked issues
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
There was a problem hiding this comment.
Version bump to v1.28.3 is correctly synchronized across all configuration files. The CHANGELOG documents two significant fixes: the onboarding bootstrap race condition that could skip the welcome portal (issue #527) and E2E test precondition improvements (issue #532). All version references are consistent and the changes follow the project's release management conventions.
You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4bac3f655b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
🏁 CodeAnt Quality Gate ResultsCommit: ✅ Overall Status: PASSEDQuality Gate Details
|
Matches the same release-candidate marker pattern used for v1.28.2's own release-prep PR (#524) -- the badge becomes inert once the v1.28.3 tag actually exists.
|
@coderabbitai review |
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Summary
Patch release (v1.28.2 → v1.28.3) containing two fixes already merged to
main:isPortalActiveinit +isInitialLoadguard).export.spec.ts's E2E precondition assumed WelcomePortal unconditionally;ensureWelcomePortalEntry()now deterministically reaches the portal regardless of startup shape, including its own internal-reload race and non-English locale handling. Issue E2E WelcomePortal entry remains nondeterministic across startup states #532's root cause (how a persisted project can appear before any test action runs) stays open — this PR does not close it.This is a release metadata / version synchronization PR —
package.json,src-tauri/{Cargo.toml,Cargo.lock,tauri.conf.json},public/sw.js,AGENTS.mdversion strings, plus CHANGELOG/README release truth (release-candidate marker + badge, matching the v1.28.2/#524 precedent). No new functional application logic.Two review findings on this PR: the README release badge (fixed — now advertises v1.28.3 with the matching
release-candidatemarker) and a CodeAnt finding onpublic/sw.js's cache-generation/precache-failure interaction, which is the same risk class already tracked as its own issue (#525) since the v1.28.2 release-prep — acknowledged and left there, not folded into this release-prep PR.Test plan
pnpm run ci:prepush— local admission PASSnode scripts/dependency-state.mjs reconcile— lockfile in syncnode scripts/sync-sw-version.mjs/sync-tauri-version.mjs— propagated topublic/sw.js,src-tauri/Cargo.toml,src-tauri/tauri.conf.json,src-tauri/Cargo.lock,AGENTS.mdnode scripts/sync-readme-metrics.mjs— README metrics already in sync (this script does not own the release badge itself, which was fixed separately)Release sequence after merge
main.mainCI, including real GitHub Pages deploy evidence (not just the aggregator).v1.28.3tag on that exactmaincommit.latest.json, updater signatures, Docker/GHCR publish, tag-triggered CI/CodeQL).release-candidatemarkers, record real release-gate evidence inAUDIT.md.Summary by CodeRabbit
Release
Documentation