chore: sync staging and main - #2337
Merged
Merged
Conversation
…5626 chore: promote staging to staging-promote/2f2ad260-23866616993 (2026-04-01 22:10 UTC)
…6993 chore: promote staging to staging-promote/510fe19a-23863770631 (2026-04-01 19:23 UTC)
…0631 chore: promote staging to staging-promote/eb3fa0e6-23858863254 (2026-04-01 18:14 UTC)
…3254 chore: promote staging to staging-promote/58b01f15-23856539614 (2026-04-01 16:18 UTC)
…9614 chore: promote staging to staging-promote/27a2fab1-23853914907 (2026-04-01 15:27 UTC)
…4907 chore: promote staging to staging-promote/73759253-23837266309 (2026-04-01 14:31 UTC)
…6309 chore: promote staging to staging-promote/684a9d30-23835295614 (2026-04-01 07:30 UTC)
…5614 chore: promote staging to staging-promote/f441d788-23825523544 (2026-04-01 06:31 UTC)
…3544 chore: promote staging to staging-promote/b6b3ffa1-23819569437 (2026-04-01 00:16 UTC)
…9437 chore: promote staging to staging-promote/78e448df-23807837438 (2026-03-31 21:10 UTC)
…7438 chore: promote staging to staging-promote/27fa292b-23782121704 (2026-03-31 16:20 UTC)
…1704 chore: promote staging to staging-promote/42623ed1-23780941831 (2026-03-31 05:32 UTC)
* Add DB MIGRATION PR label * Broaden DB MIGRATION label coverage * chore(ci): address DB MIGRATION label review feedback
* Fix Telegram UTF-16 message splitting * fix: bump telegram channel registry version
…1770 chore: promote staging to staging-promote/bb2c3e1d-24154330911 (2026-04-08 21:41 UTC)
…0911 chore: promote staging to staging-promote/315c4cf8-24151502580 (2026-04-08 19:29 UTC)
…2580 chore: promote staging to staging-promote/8aa09412-24146405548 (2026-04-08 18:23 UTC)
…5548 chore: promote staging to staging-promote/482ee57c-24140982267 (2026-04-08 16:25 UTC)
…2267 chore: promote staging to staging-promote/3df1bf38-24132614443 (2026-04-08 14:32 UTC)
…4443 chore: promote staging to staging-promote/10d970d4-24125728989 (2026-04-08 11:19 UTC)
…8989 chore: promote staging to staging-promote/fdb093fb-24118285581 (2026-04-08 08:28 UTC)
…5581 chore: promote staging to staging-promote/288fe49a-24110798843 (2026-04-08 04:48 UTC)
…channels Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…1831 chore: promote staging to main (2026-03-31 04:47 UTC)
…6540 chore: promote staging to staging-promote/2b6f22f1-23922129343 (2026-04-03 03:01 UTC)
…9343 chore: promote staging to staging-promote/d789a5d2-23919737307 (2026-04-02 21:09 UTC)
…7307 chore: promote staging to staging-promote/3974163e-23917811640 (2026-04-02 20:09 UTC)
…1640 chore: promote staging to staging-promote/a6835808-23915112005 (2026-04-02 19:20 UTC)
…2005 chore: promote staging to staging-promote/5c35b58f-23910362543 (2026-04-02 18:14 UTC)
This was referenced Apr 16, 2026
theredspoon
pushed a commit
to theredspoon/ironclaw
that referenced
this pull request
Jun 21, 2026
* [codex] Label migration PRs with DB MIGRATION (nearai#1967) * Add DB MIGRATION PR label * Broaden DB MIGRATION label coverage * chore(ci): address DB MIGRATION label review feedback * Fix Telegram UTF-16 message splitting (nearai#1961) * Fix Telegram UTF-16 message splitting * fix: bump telegram channel registry version * chore: bump registry versions for github tool, whatsapp and telegram channels Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * revert: undo 2 main-only commits to unblock staging-promote merge (nearai#2297) Reverts: - 618df18 Fix Telegram UTF-16 message splitting (nearai#1961) - d16a9cd [codex] Label migration PRs with DB MIGRATION (nearai#1967) Keeps 0ed8bce (registry version bumps) intact. These changes were made directly on main and conflict with staging-promote. Both already exist in staging and will flow back to main via the promote merge. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * chore: release (nearai#2075) Co-authored-by: ironclaw-ci[bot] <266877842+ironclaw-ci[bot]@users.noreply.github.com> * fix(ci): unblock v0.25.0 release — fix tag filter and publish config (nearai#2306) The release pipeline broke when ironclaw_engine was added (Apr 2) with a monty git dependency that blocks crates.io publishing. Additionally, sub-crate tags (ironclaw_tui-v0.1.0) were triggering cargo-dist builds and stealing the "Latest" badge from the main release. - Narrow release.yml tag pattern to `ironclaw-v*` so only the main binary release tags trigger cargo-dist (not sub-crate tags) - Configure release-plz to skip crates.io publish for ironclaw (publish = false) while still creating git tags for cargo-dist - Mark ironclaw_engine, ironclaw_tui, ironclaw_gateway as non-publishable (release = false) in release-plz.toml - Add publish = false to tui and gateway Cargo.toml - Remove version fields from non-publishable path deps in root Cargo.toml Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * chore: update WASM artifact SHA256 checksums [skip ci] (nearai#2308) Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> --------- Co-authored-by: firat.sertgoz <firat.sertgoz@near.ai> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: ironclaw-ci[bot] <266877842+ironclaw-ci[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
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
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.
Summary
Sync staging with latest main -> mostly checksum/versions updates + some minor CI checks that were merged directly to main
Change Type
Linked Issue
Validation
cargo fmt --all -- --checkcargo clippy --all --benches --tests --examples --all-features -- -D warningscargo buildcargo test --features integrationif database-backed or integration behavior changedreview-prorpr-shepherd --fixwas run before requesting reviewSecurity Impact
Database Impact
Blast Radius
Rollback Plan
Review Follow-Through
Review track: