chore: release v0.17.0 - #633
github-actions[bot] wants to merge 5 commits into
Conversation
adae36c to
caa61ee
Compare
d90abdf to
aa2eb5f
Compare
f8a02be to
05c98dc
Compare
a0f1644 to
7734a0f
Compare
zmanian
left a comment
There was a problem hiding this comment.
Clean automated release PR. Version bump 0.16.1 -> 0.17.0 is correct for the breaking API changes detected by cargo-semver-checks. Changelog is comprehensive (~50 PRs referenced).
Minor: Duplicate "Added" section at the bottom -- the Bedrock entry appears twice (once in main Added section as #713, again as standalone "Added" block). Known release-plz artifact. Cosmetic only.
12b763e to
701d198
Compare
zmanian
left a comment
There was a problem hiding this comment.
Release PR Review: v0.17.0
Version bump: OK
- 0.16.1 -> 0.17.0 is correct. Minor version bump is appropriate given the extensive breaking API changes detected by cargo-semver-checks (~60+ breaking field additions, removed structs, changed method signatures, new trait methods without defaults).
Changed files: OK
Only 3 files changed (CHANGELOG.md, Cargo.toml, Cargo.lock) -- pure release bookkeeping. No code changes to review.
Changelog: comprehensive
- ~50 PRs referenced spanning features (Bedrock, image support, timezone awareness, MCP transports, declarative provider registry, prompt caching), fixes (Windows compat, libSQL timestamps, IME composition, config overwrites), and infrastructure (300+ new tests, guardrails, dead code removal).
- All referenced PRs (#688, #713, #717, #721, #724, #725, #726, #734, #740, etc.) are confirmed merged to main.
Known cosmetic issue (carried forward from dismissed review)
Duplicate "Added" section at the bottom of the changelog -- the Bedrock entry (#713) appears in the main "Added" section and again as a standalone block. This is a known release-plz artifact and is cosmetic only.
One thing to note
The release branch is 1 commit behind main: PR #754 ("fix: prevent irreversible context loss when compaction archive write fails") was merged after the release branch was cut. This is a data-loss prevention fix. Consider whether to rebase the release branch to include it in v0.17.0, or ship as-is and include it in a v0.17.1 patch.
CI
No CI checks are reported on the release branch. Verify that CI has passed on main at the merge base before merging.
Approving -- this is a clean automated release PR. The only decision point is whether to pick up #754 before shipping.
e091b7b to
957e6f9
Compare
…-check] (#787) GitHub Actions step-level `if:` doesn't have access to `secrets` context. Replace `if: secrets.X != ''` with `continue-on-error: true` and let the Set token step handle the fallback. Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
957e6f9 to
f89c41d
Compare
…cks [skip-regression-check] (#794) - Remove continue-on-error from staging-ci.yml app token steps (secrets are configured) - Skip test.yml and code_style.yml on PRs targeting staging (staging-ci.yml already runs tests before promoting, promotion PR gets full CI on main) - Allow ironclaw-ci[bot] in Claude Code review for bot-created promotion PRs Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
f89c41d to
4530f0e
Compare
…egression-check] (#802) - Remove branches:[main] filter from code_style.yml so it runs on all PRs - Gate clippy-windows with `if: github.base_ref == 'main'` (skip on staging PRs) - Update rollup job to allow skipped clippy-windows - Simplify claude-review.yml to only trigger on labeled event (avoids duplicate runs) Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
4530f0e to
516b7f2
Compare
…709) * feat: persist worker events to DB and fix activity tab rendering In-process Worker (used by Scheduler::dispatch_job) now persists events via save_job_event at key execution points: plan creation, LLM responses, tool_use, tool_result, and job completion/failure/stuck. Event data shapes match the container worker format so the gateway activity tab renders them correctly. Frontend: tool_result errors now show a red X icon with danger styling instead of a silent empty output. The result event falls back to the error field when message is absent. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * feat: wire RoutineEngine into gateway for direct manual trigger firing Replace the message-channel hack in routines_trigger_handler with a direct call to RoutineEngine::fire_manual(), ensuring FullJob routines dispatch correctly when triggered from the web UI. Inject the engine into GatewayState from Agent::run after construction. Also persists user_id in save_job for both PG and libSQL backends, removes the source='sandbox' filter so all jobs are visible, and exposes job_id on RoutineRunInfo for the frontend job link. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: remove stale gateway_state argument from Agent::new test call sites The gateway_state parameter was removed from Agent::new during rebase (replaced by post-construction set_routine_engine_slot), but three test call sites still passed the extra None argument. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: address PR review — restore sandbox source filter, remove blank lines - Revert removal of `source = 'sandbox'` filter in all SandboxStore queries (8 sites across PG and libSQL). Sandbox-specific APIs should stay scoped to sandbox jobs; unified job listing for the Jobs tab should use a separate query path. - Remove extra blank lines in agent_loop.rs and worker.rs that caused formatting CI failure. [skip-regression-check] Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: address review — regenerate Cargo.lock, add user_id regression test - Regenerate Cargo.lock from main's lockfile to eliminate dependency version downgrades (anyhow, syn, etc.) that were churn from rebase. - Add regression test verifying user_id round-trips through save_job and get_job in the libSQL backend. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * style: remove trailing blank line in libsql jobs.rs [skip-regression-check] Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * test: add Postgres-side regression test for user_id persistence in save_job Mirrors the existing libSQL test (test_save_job_persists_user_id) for the Postgres backend. Gated behind #[cfg(feature = "postgres")] + #[ignore] since it requires a running PostgreSQL instance (integration tier). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
516b7f2 to
a9f7298
Compare
🤖 New release
ironclaw: 0.16.1 -> 0.17.0 (⚠ API breaking changes)⚠
ironclawbreaking changesChangelog
This PR was generated with release-plz.