docs: post-release v1.28.3 sync (README/CHANGELOG/AUDIT) - #535
Conversation
Removes the now-stale release-candidate markers from README.md and CHANGELOG.md now that v1.28.3 is genuinely tagged and published, and records real release-gate evidence in AUDIT.md: main CI/CD run 33113772841 (with real GitHub Pages Deployments API evidence), CodeQL SAST run 33113772797 (0 open alerts), tag-triggered Tauri workflow 33115805027 (all 5 jobs), tag-triggered CI/CD run 33115805002 (E2E passed, no repeat of the v1.28.2 tag-run flake), and the Docker workflow 33115804967 (ghcr.io/qnbs/worldscript-studio pushed with a real digest, tagged 1.28.3/1.28/latest). All 15 GitHub Release assets uploaded successfully.
🤖 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 |
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. |
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThis documentation-only sync replaces stale v1.28.3 candidate markers with published-release truth and extends the audit trail with verified CI/CD, security, deployment, container, and release-asset evidence; no functional code is changed. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
🏁 CodeAnt Quality Gate ResultsCommit: ✅ Overall Status: PASSEDQuality Gate Details
|
There was a problem hiding this comment.
Review Summary
This PR updates documentation for version 1.2.0, including audit logs, changelog, and README improvements. All changes are documentation-only and properly formatted. No blocking issues identified.
Changes Reviewed:
- AUDIT.md: Version bump and audit trail for v1.2.0
- CHANGELOG.md: Properly categorized changes following semantic versioning
- README.md: Enhanced documentation with new feature examples and improved installation instructions
The documentation changes are clear, well-organized, and ready to merge.
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.
Warning Review limit reachedNext included review available in 22 minutes. View limit detailsLimit details: You’ve used the included review currently available. Your 101 included PR review attempts over the past 7 days set your current allowance at 1 review per hour. Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
💤 Files with no reviewable changes (1)
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 release audit now records v1.28.3 validation results and corrected onboarding E2E references. The changelog documents the sync, and obsolete v1.28.3 release-candidate markers were removed from the changelog and README. ChangesRelease Documentation
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk:⚪ Minimal · up to This PR only synchronizes release documentation and audit records for v1.28.3, with no functional code changes. 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 0 files. (2 skipped: 2 unsupported.) ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
…IT.md - 14 release assets, not 15 -- verified directly against the GitHub Release API rather than a manual recount. - PR #533 fixed the E2E harness/precondition gap associated with #532, not #532 itself -- the prior wording implied the root cause was closed, contradicting the correctly-stated "root cause stays open" a few words earlier. - Re-verified 0 open code-scanning alerts directly via the code-scanning/alerts API rather than inferring it from a green CodeQL run alone.
qnbs
commented
Aug 27, 2026
@coderabbitai review |
|
- Cite PR #530 and PR #533 explicitly next to the issues they fix, matching AUDIT.md's already-precise wording. - Make the #532 root-cause-open statement unambiguous: PR #533 fixed the E2E test-harness symptom, not issue #532 itself -- the prior parenthetical read ambiguously next to "see issue #532".
qnbs
commented
Aug 27, 2026
@coderabbitai review |
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:0962dc0552
ℹ️ 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".
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
… entry The release-prep commit only touches src-tauri/, not crates/, so the changed-path detector correctly gates core-rust off -- it was skipped, not passed. Verified directly via the run's job list (conclusion: skipped). The prior wording listed it among jobs that "passed", overstating the release's validation evidence.
qnbs
commented
Aug 27, 2026
@coderabbitai review |
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:3deb5f2fa8
ℹ️ 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".
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
…te entry - The tag-triggered CI/CD run's PR Size Governance and Deploy to GitHub Pages jobs are legitimately skipped for a tag push (restricted to pull_request and refs/heads/main respectively) -- reworded from "passed all jobs" to "passed all applicable jobs" with the skips recorded explicitly. Verified via the run's job list. - Separated the #527 and #532 narratives: #527 was found via v1.28.2's own tag-run flake, not via #532's E2E harness gap (a distinct, later finding from PR #530's post-merge main run). The prior wording's "the E2E test-harness precondition gap that surfaced it in CI" read as if #532 surfaced #527, conflating two unrelated fixes.
qnbs
commented
Aug 27, 2026
@coderabbitai review |
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Uh oh!
There was an error while loading. Please reload this page.
Two corrections from review, verified before fixing: 1. My v1.28.4 AUDIT.md edit replaced the entire v1.28.3 "Release gate" paragraph instead of inserting the new one above it, deleting real historical evidence (main CI/CodeQL run IDs, tag-triggered Tauri/ CI/Docker runs, asset list) that a repo-wide search confirmed no longer appeared anywhere. The v1.28.3 sync itself preserved v1.28.2's record the same way (PR #535). Restored the v1.28.3 paragraph unchanged, with v1.28.4's new record inserted above it. 2. TODO.md and AUDIT.md both implied CodeQL SAST reran on the v1.28.4 tag push alongside CI/Tauri/Docker. Verified against .github/workflows/codeql.yml: it triggers only on push/branches:[main], with no tags trigger at all -- it never runs again on a tag push. Corrected both to state the main-push CodeQL run is the only applicable evidence, distinct from the tag-triggered CI/Tauri/Docker runs.
* docs: post-release v1.28.4 sync (README/CHANGELOG/TODO/AUDIT) Removed the now-stale release-candidate markers from README.md and CHANGELOG.md now that the v1.28.4 tag and GitHub Release are published from main commit 21221d4, and recorded real release-gate evidence in AUDIT.md: - Post-merge main CI/CD run 33973305518 and CodeQL run 33973305597, both green; GitHub Pages deployment 6282574436 verified state:success for this exact commit. - Tag-triggered Tauri desktop build 33974750122, CI/CD 33974750136, and Docker 33974750117 (image digest sha256:f605598f...) all green. - All 14 expected release assets published (Linux rpm/deb/AppImage, Windows msi/exe, macOS dmg/app.tar.gz, all with .sig files except the dmg, plus latest.json), matching the v1.28.3 asset shape. TODO.md's release-cut item is now marked done, matching the actual published state. * fix(docs): preserve v1.28.3 audit history, correct CodeQL tag scope Two corrections from review, verified before fixing: 1. My v1.28.4 AUDIT.md edit replaced the entire v1.28.3 "Release gate" paragraph instead of inserting the new one above it, deleting real historical evidence (main CI/CodeQL run IDs, tag-triggered Tauri/ CI/Docker runs, asset list) that a repo-wide search confirmed no longer appeared anywhere. The v1.28.3 sync itself preserved v1.28.2's record the same way (PR #535). Restored the v1.28.3 paragraph unchanged, with v1.28.4's new record inserted above it. 2. TODO.md and AUDIT.md both implied CodeQL SAST reran on the v1.28.4 tag push alongside CI/Tauri/Docker. Verified against .github/workflows/codeql.yml: it triggers only on push/branches:[main], with no tags trigger at all -- it never runs again on a tag push. Corrected both to state the main-push CodeQL run is the only applicable evidence, distinct from the tag-triggered CI/Tauri/Docker runs.
User description
Summary
Mirrors PR #528's pattern for v1.28.2. Now that
v1.28.3is genuinely tagged and published:release-candidate: v1.28.3markers from README.md and CHANGELOG.md.No functional code changes.
Test plan
pnpm run ci:prepush— local admission PASS (docs:checkconfirms "latest v1.28.3")Summary by Sourcery
Finalize the documentation sync for the published v1.28.3 release.
Enhancements:
Documentation:
CodeAnt-AI Description
Synchronize documentation with the published v1.28.3 release
What Changed
Impact
✅ Accurate v1.28.3 release status✅ Verifiable release and deployment evidence✅ Clearer documentation of published assets and quality checks💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.
Summary by CodeRabbit