Repository navigation
chore(release): ship scheduled-task improvements in 0.0.78 - #89
Conversation
|
@coderabbitai full review Please review candidate c350030 for the 0.0.78 release and explicitly approve if there are no blocking findings. The PR bumps four package versions. The actual unreleased release diff also contains the already-merged scheduled-task changes from #87 and #88: a849bed...c350030 . Please include that small integration diff at a high level. Focused validation passed 24 web editor tests and 69 server scheduler/branch tests. No browser or live-service work is included. |
|
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 51 minutes. View limit details
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to The four package versions are updated consistently. No merge-blocking risk is identified in the reviewed changes. Pre-merge checks |
|
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
|
@coderabbitai approve Your completed review covered candidate c350030 and identified no actionable findings or merge-blocking risk. Please record the formal approval for that exact candidate. The independent GPT-6 Astra review also gave SOURCE GO on the complete unreleased integration diff from 0.0.77, including #87 and #88. All applicable CI checks passed. |
|
Tip For best results, initiate chat on the files or code changes.
No approval was submitted. An authorized reviewer must submit the formal GitHub approval. You are interacting with an AI system. |
|
|
@coderabbitai Please give an explicit written GO or NO-GO for merging your reviewed candidate c350030. The review covered the four aligned 0.0.78 versions in apps/server/package.json, apps/desktop/package.json, apps/web/package.json and packages/contracts/package.json and reported no actionable findings or merge-blocking risk. Repository configuration prevents submission of a formal GitHub approval, so please state explicitly in this comment whether you approve those exact reviewed changes for merge. Use the completed review as evidence and identify any remaining blockers. The full unreleased integration diff, including #87 and #88, also has independent GPT-6 Astra SOURCE GO for this exact SHA; all applicable CI checks passed. |
|
Tip For best results, initiate chat on the files or code changes. 🧩 Analysis chain🏁 Script executed: #!/bin/bash
set -euo pipefail
repo="RTVision/t3code"
sha="c3500306a57a4025bc88bcc49decd30915840d20"
gh api "repos/$repo/pulls/89" --jq '{head: .head.sha, state, mergeable, mergeable_state}'
gh api --paginate "repos/$repo/pulls/89/reviews" --jq '.[] | {user: .user.login, state, commit_id, body}'
gh api --paginate "repos/$repo/issues/89/comments" --jq '.[] | select(.user.login == "coderabbitai[bot]") | {body}'
gh api "repos/$repo/commits/$sha/check-runs?per_page=100" --jq '{total_count, checks: [.check_runs[] | {name, status, conclusion}]}'
gh api "repos/$repo/commits/$sha/status" --jq '{state, statuses: [.statuses[] | {context, state}]}'
gh api "repos/$repo/git/trees/$sha?recursive=1" --jq '.tree[] | select(.path == "apps/server/package.json" or .path == "apps/desktop/package.json" or .path == "apps/web/package.json" or .path == "packages/contracts/package.json") | .path'
for path in apps/server/package.json apps/desktop/package.json apps/web/package.json packages/contracts/package.json; do
printf '\n--- %s ---\n' "$path"
gh api "repos/$repo/contents/$path?ref=$sha" --jq '.content' | base64 --decode
doneLength of output: 26652
I verified the following evidence:
Remaining merge blockers: none identified. This recommendation covers the reviewed four-package version update. Your reported independent SOURCE GO covers the broader unreleased integration diff, including This comment is not a formal GitHub approval. Formal approval remains unavailable through CodeRabbit in this repository. This merge recommendation does not authorize publication or deployment; the stated release gates still apply. You are interacting with an AI system. |
The scheduled-task improvements in #87 and #88 merged after 0.0.77. Release 0.0.78 includes web/desktop effort and permission editing plus reliable base branches for MCP-created fresh-thread schedules. This PR aligns all four release manifests at 0.0.78.
Validation: 24 focused web tests and 69 focused server tests passed. Primary and independent GPT-6 Astra reviews gave GO on exact candidate
c3500306a57a4025bc88bcc49decd30915840d20and the full unreleased integration diff. CodeRabbit gave an explicit written GO for the four version manifests, with no blockers. All candidate checks and merged-head CI passed. The merged head is86800ebfafd5b91c63cd698d0d805d09dc582877.The release build passed. All 11 artifacts match their sizes and SHA256 digests; all 10 SHA256SUMS payloads passed. A clean Alpine 3.24.2 / Node 24.18.1 installation passed source-built native PTY execution, musl file search, and service preflight. The exact npm tarball is published to RTVision's registry with SHA512 integrity and downloaded bytes verified. Release 0.0.78 is published. Registry verification used uncached metadata because its normal npm endpoint briefly served stale data. No live service deployment or restart occurred.
Model and harness: GPT-6.1 Sol through Codex in T3 Code; independent review by GPT-6 Astra.