docs: post-release v1.28.4 sync (README/CHANGELOG/TODO/AUDIT) - #616
Conversation
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.
🤖 CodeAnt AI — Review Status
|
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 post-release documentation sync makes v1.28.4 status unconditionally truthful across the README, changelog, TODO, and audit record, using verified CI/CD, deployment, container, and release-asset evidence from commit 21221d4. Validation reported by the PR is clean documentation metrics and lint. Flow diagram for v1.28.4 release-truth synchronizationflowchart LR
Commit["Validated main commit 21221d43"] --> Gates["Verified release gates"]
Gates --> Evidence["CI/CD, CodeQL, Pages, Tauri, Docker green"]
Evidence --> Assets["14 release assets published"]
Assets --> Docs["README, CHANGELOG, TODO, AUDIT synchronized"]
Docs --> Truth["v1.28.4 status unconditionally truthful"]
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
 |
| Overall Grade | Security Reliability Complexity Hygiene |
Code Review Summary
| Analyzer | Status | Updated (UTC) | Details |
|---|---|---|---|
| Docker |  | Sep 5, 2026 4:13p.m. | Review ↗ |
| Python | | Sep 5, 2026 4:13p.m. | Review ↗ |
| Rust | | Sep 5, 2026 4:13p.m. | Review ↗ |
| Shell | | Sep 5, 2026 4:13p.m. | Review ↗ |
Important
AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
🏁 CodeAnt Quality Gate ResultsCommit: ✅ Overall Status: PASSEDQuality Gate Details
|
There was a problem hiding this comment.
This PR correctly removes stale release-candidate markers and documents the v1.28.4 release completion across AUDIT.md, CHANGELOG.md, and README.md. All changes are documentation-only, follow the documented truth-sync process, and maintain consistency across files. The changes are working as intended - no defects found that would block 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 43 minutes. View limit detailsLimit details: You’ve used the included review currently available. Your 83 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: Essentials 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: Essentials Run ID: 📒 Files selected for processing (4)
💤 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 documentation now reflects v1.28.4. Audit evidence, changelog status, README release markers, and sprint tracking were updated. Changesv1.28.4 Release Documentation
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk:⚪ Minimal · up to This documentation-only update reconciles the published v1.28.4 release records with no remaining merge-readiness risk. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:4ad0acc54c
ℹ️ 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.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
There was a problem hiding this comment.
No application code in the PR — skipped Code Health checks.
See analysis details in CodeScene
Quality Gate Profile:The Bare Minimum
Install CodeScene MCP: safeguard and uplift AI-generated code. Catch issues early with our IDE extension and CLI tool.
Uh oh!
There was an error while loading. Please reload this page.
User description
Summary
Post-release truth sync for
v1.28.4, now that the tag and GitHub Release are actually published from main commit21221d43. Matches the established v1.28.2/v1.28.3 pattern (PR #528, #535).Changes
<!-- release-candidate: v1.28.4 -->markers fromREADME.mdandCHANGELOG.md— the version badge and dated CHANGELOG entry are now unconditionally truthful since the tag exists.AUDIT.mdupdated with real, verified release-gate evidence:33973305518and CodeQL run33973305597, both green.6282574436verifiedstate: successfor commit21221d43.Tauri desktop build(33974750122),CI / CD(33974750136), andDocker(33974750117, image digestsha256:f605598f...) all green..sigfiles,latest.json), matching the v1.28.3 asset shape.TODO.md's release-cut item flipped from in-progress to done.Validation
node scripts/check-doc-metrics.mjs— OK,latest v1.28.4.pnpm run lint— clean.Summary by Sourcery
Finalize the documentation and release tracking for the published v1.28.4 release.
Enhancements:
Documentation:
Chores:
CodeAnt-AI Description
Align release documentation with the published v1.28.4 release
What Changed
Impact
✅ Accurate v1.28.4 release status✅ Verifiable release and deployment evidence✅ Clearer release-readiness tracking💡 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 cubic
Syncs the release docs to the published v1.28.4 tag and GitHub Release, replacing the pending release-candidate state with verified evidence.
release-candidatemarkers fromREADME.mdandCHANGELOG.mdand adds a changelog entry for the sync.AUDIT.md: main CI/CD, CodeQL, GitHub Pages deploy, tag-triggered Tauri/CI/Docker runs, and published release assets.v1.28.4release-cut item as done inTODO.md.AUDIT.mdthat the initial edit had overwritten.TODO.mdandAUDIT.mdto state that CodeQL runs only on main pushes, not tag pushes.Written for commit a9cd179. Summary will update on new commits.
Summary by CodeRabbit
Documentation
Chores