[release] v0.110.0 - #5742
Merged
Merged
Conversation
Planning docs (context, plan, status, research index) plus the accepted research inputs: the RFC, the change-set interface spec, and the runner lifecycle architecture.
Both spikes are green. The decisions log records what was accepted from each spike and the seven product calls still open.
change-set, commit-transaction, read-config (engine-spike); execution-authorization, workspace-import, adapter-matrix (runner-spike). The value_from schema conflict is arbitrated; twelve product calls open.
…lls deduped to six
…orded Strict canonical serializer, multi-source atomicity, honest TOCTOU model, descendant confinement, harmless-forgery acknowledgement design, canonical generation payload, text-file import into text fields with diff approval, four-layer executable permission split.
…witch, S7c0 foundation slice, accepted Daytona risk
…ions, six open calls
…es, refactor plan, decision context
…ctions; inline marker validated; harness included
… errors, path normalization, selector forgiveness, optional free-text on all tools
…ditions; message derived server-side; invalid_operation split; v3 spike results
…ass match tolerance, uncommittable build kit
…irectives, .agenta-imports rename, folder policy dissolved by @ag.file, v3 assets, codex upstream check
… single-flag kill switch; open-issues log added
… rename costs nothing
…; cross-contract banners updated @ag.file marker, .agenta-imports root, list selector key with wrapper forgiveness, per-class match tolerance with length-preserving folds, derived commit message, split error codes with next-steps, platform-tool rejection, uniform reopen note, v3 instructions folded in as normative.
…tching (§18.2 with measured corruption examples)
…ssage/description); dao lock conditions
… absolute-path row struck, stale budget notes removed
… s7e credential handoff brief
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
dosubot
Bot
added
the
size:XS
feat(sdk): deliver the approval manifest to the live approval card
Contributor
Author
Railway Preview Environment
Updated at 2026-08-07T17:48:59.489Z |
…-removal refactor (keep the Badge idiom from release, keep the defaultOpen/sectionOpenState feature from the lane, drop the stale antd imports)
…-web feat(frontend): show the frozen content and diff on commit approvals
…-mount fix(runner): steered sessions keep their workspace mount (pre-existing)
…migration feat(api): agent behavior leaves the public API: handler-mode ops, one error envelope, routes deleted
chore(clients): regenerate both API clients from the branch spec
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
…e benchmark's run identity is now derived from non-secret values only (base+project context hash replaces the API-key fingerprint; the record only needs to say which deployment context produced a run); the runner test asserts the fence shape with startsWith/endsWith instead of a regex CodeQL reads as HTML filtering; the web test parses rendered HTML with the test environment's DOM instead of regex tag-stripping, which is also more correct. No product code changes.
fix(ci): clear the CodeQL highs (test and benchmark code only)
mmabrouk
force-pushed
the
release/v0.110.0
branch
from
August 7, 2026 14:22
20e8d2c to
d6b3e53
Compare
… gitleaks hook only guards commits a human types; commits created by tooling and pushed by other plumbing bypass it entirely, which is how four conflicted commits carrying full tree copies reached a release branch unscanned. This job scans the pushed range server-side with the repo's existing .gitleaks.toml, so origin does not matter.
…mit shape. The stream projector that turns a successful commit_revision tool output into the data-committed-revision part gated on the legacy 'count' field; the migrated handler answers {status: committed, ...} with no count, so the projector silently dropped the part, commits stored fine, and the playground never switched to the new version (live incident, session b024a6b0). The gate now accepts either shape. The suite stayed green through the regression because every fixture pinned the legacy shape; a test now pins the live handler shape. Live-verified: the round trip streams the part with correct ids and the playground signal fires.
fix(sdk): playground auto-refresh after an agent commit (regression from the migration)
…it shape when ordered operations are on
…ntent fix(sdk): the build-an-agent skill stops teaching the deprecated commit shape when ordered operations are on
…write deliberate high-entropy marker strings (QA-CWD-*, QA-APPROVE-*) into committed run records to prove storage round trips; the new server-side scan's first branch run flagged three of them as generic API keys. Test artifacts, not credentials; verified by reproducing the scan and reading each finding.
ci: server-side secret scan on every push and pull request
mmabrouk
approved these changes
Aug 7, 2026
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
3 participants
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.
New version v0.110.0 in