Chore: Sync Main/Staging - #1612
Conversation
…3042 chore: promote staging to staging-promote/ec04354c-23271447493 (2026-03-19 00:12 UTC)
…6242 chore: promote staging to staging-promote/b9e5acf6-23283208580 (2026-03-19 15:15 UTC)
…8580 chore: promote staging to staging-promote/3dcccc1e-23280048384 (2026-03-19 06:44 UTC)
…8384 chore: promote staging to staging-promote/ec04354c-23271447493 (2026-03-19 04:37 UTC)
…6661 chore: promote staging to staging-promote/ec04354c-23271447493 (2026-03-19 16:48 UTC)
…7493 chore: promote staging to main (2026-03-18 23:07 UTC)
Co-authored-by: ironclaw-ci[bot] <266877842+ironclaw-ci[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…4063 chore: promote staging to staging-promote/65062f3c-23317058602 (2026-03-19 23:06 UTC)
…8602 chore: promote staging to staging-promote/52ca9d65-23312673755 (2026-03-19 21:10 UTC)
…3755 chore: promote staging to staging-promote/71f41dd1-23309993684 (2026-03-19 19:18 UTC)
…3684 chore: promote staging to staging-promote/71f9012d-23307625134 (2026-03-19 18:14 UTC)
…5134 chore: promote staging to staging-promote/ec04354c-23271447493 (2026-03-19 17:20 UTC)
Co-authored-by: ironclaw-ci[bot] <266877842+ironclaw-ci[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…2672 chore: promote staging to staging-promote/c4ab3825-23321164063 (2026-03-20 02:56 UTC)
…7636 chore: promote staging to staging-promote/cba1bc37-23334371795 (2026-03-20 16:12 UTC)
…1795 chore: promote staging to staging-promote/c1762616-23332963145 (2026-03-20 08:09 UTC)
…3145 chore: promote staging to staging-promote/b952d229-23331469361 (2026-03-20 07:18 UTC)
…9361 chore: promote staging to staging-promote/806d4028-23330265305 (2026-03-20 06:16 UTC)
…5305 chore: promote staging to staging-promote/455f543b-23329172268 (2026-03-20 05:23 UTC)
…2351 chore: promote staging to staging-promote/3da9810e-23351687636 (2026-03-20 17:14 UTC)
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request performs a synchronization between the main and staging branches, integrating a comprehensive set of updates, new features, and bug fixes that have accumulated across versions Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
…6254 chore: promote staging to staging-promote/89394ebd-23395764012 (2026-03-22 05:25 UTC)
…4012 chore: promote staging to staging-promote/b97d82db-23390775365 (2026-03-22 04:36 UTC)
…5365 chore: promote staging to staging-promote/9d538136-23389762470 (2026-03-21 23:04 UTC)
…2470 chore: promote staging to staging-promote/8ad7d78a-23387609319 (2026-03-21 22:03 UTC)
…9319 chore: promote staging to staging-promote/62326090-23374571867 (2026-03-21 20:02 UTC)
…1867 chore: promote staging to staging-promote/9964d5da-23372765633 (2026-03-21 07:13 UTC)
…5633 chore: promote staging to staging-promote/0d1a5c21-23372030005 (2026-03-21 05:17 UTC)
…0005 chore: promote staging to staging-promote/e6277a39-23371263100 (2026-03-21 04:30 UTC)
…3100 chore: promote staging to staging-promote/6d847c60-23366109539 (2026-03-21 03:42 UTC)
…9539 chore: promote staging to staging-promote/9603fefd-23364438978 (2026-03-20 23:06 UTC)
…8978 chore: promote staging to staging-promote/d3b69e7b-23359661011 (2026-03-20 22:04 UTC)
…-version-bumps fix: bump registry versions for staging promotion 1451
…2268 chore: promote staging to staging-promote/89203225-23327092672 (2026-03-20 04:32 UTC)
Co-authored-by: ironclaw-ci[bot] <266877842+ironclaw-ci[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 15 out of 16 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "wasm32-wasip2": { | ||
| "sha256": "5fca74022264d1c8e78a0853766276f7ffa3cf0d8065b2f51ca10985acad4714", | ||
| "url": "https://github.com/nearai/ironclaw/releases/download/v0.19.0/channel-feishu-0.1.1-wasm32-wasip2.tar.gz" | ||
| "sha256": "52def36121a93cf0b06dd6d594dc9528745fae56ded7d632998700cc595be762", | ||
| "url": "https://github.com/nearai/ironclaw/releases/download/v0.21.0/channel-feishu-0.1.2-wasm32-wasip2.tar.gz" | ||
| } |
There was a problem hiding this comment.
The manifest advertises version 0.1.3 (line 5), but the artifact URL here still references channel-feishu-0.1.2. This version mismatch can break installs or lead to downloading the wrong binary; please align the artifact filename/tag (and sha256) with the manifest version (or adjust the manifest version to match the published artifact).
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 18 out of 19 changed files in this pull request and generated 15 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "display_name": "Telegram Tool", | ||
| "kind": "tool", | ||
| "version": "0.2.0", | ||
| "version": "0.2.1", |
There was a problem hiding this comment.
The tool manifest version is now 0.2.1, but the artifact URL still references tool-telegram-0.2.0-.... Please align the manifest version with the artifact version (and sha) so clients fetch the intended build.
| "version": "0.2.1", | |
| "version": "0.2.0", |
| "kind": "tool", | ||
| "version": "0.2.0", | ||
| "version": "0.2.1", | ||
| "wit_version": "0.3.0", |
There was a problem hiding this comment.
The tool manifest version is now 0.2.1, but the artifact URL still references google-calendar-0.2.0-.... Update the artifact URL/sha to the 0.2.1 artifact (or revert the manifest version) to keep the registry entry consistent.
| "display_name": "Google Docs", | ||
| "kind": "tool", | ||
| "version": "0.2.0", | ||
| "version": "0.2.1", |
There was a problem hiding this comment.
The tool manifest version is now 0.2.1, but the artifact URL still references google-docs-0.2.0-.... Please keep version consistent with the artifact filename/sha (either publish a 0.2.1 artifact or revert the manifest bump).
| "version": "0.2.1", | |
| "version": "0.2.0", |
| authors = ["NEAR AI <support@near.ai>"] | ||
| license = "MIT OR Apache-2.0" | ||
| homepage = "https://github.com/nearai/ironclaw" | ||
| repository = "https://github.com/nearai/ironclaw" |
There was a problem hiding this comment.
Removing publish = false makes this crate publishable to crates.io. Given release-plz automation in this repo, confirm this is intended; if not, restore publish = false (or another mechanism) to prevent accidental publishing/releases.
| repository = "https://github.com/nearai/ironclaw" | |
| repository = "https://github.com/nearai/ironclaw" | |
| publish = false |
|
|
||
| ## [Unreleased] | ||
|
|
||
| ## [0.22.0](https://github.com/nearai/ironclaw/compare/ironclaw-v0.21.0...ironclaw-v0.22.0) - 2026-03-25 |
There was a problem hiding this comment.
The 0.22.0 compare link uses ironclaw-v0.21.0...ironclaw-v0.22.0, while recent entries (e.g. 0.21.0) use v0.20.0...v0.21.0. If release tags are vX.Y.Z (as implied by registry artifact URLs), this link will be broken—please align it to the actual tag naming convention.
| ## [0.22.0](https://github.com/nearai/ironclaw/compare/ironclaw-v0.21.0...ironclaw-v0.22.0) - 2026-03-25 | |
| ## [0.22.0](https://github.com/nearai/ironclaw/compare/v0.21.0...v0.22.0) - 2026-03-25 |
| "display_name": "Web Search", | ||
| "kind": "tool", | ||
| "version": "0.2.1", | ||
| "version": "0.2.2", |
There was a problem hiding this comment.
The tool manifest version is now 0.2.2, but the artifact URL still references tool-web-search-0.2.1-.... Please keep the manifest version consistent with the artifact filename (and sha) so registry consumers don’t think they’ve upgraded while still downloading the old component.
| "version": "0.2.2", | |
| "version": "0.2.1", |
| "display_name": "Slack Tool", | ||
| "kind": "tool", | ||
| "version": "0.2.0", | ||
| "version": "0.2.1", |
There was a problem hiding this comment.
The tool manifest version is now 0.2.1, but the artifact URL still references tool-slack-0.2.0-.... Update the artifact URL/sha to the 0.2.1 build (or revert the manifest version) to avoid advertising a version that isn’t actually shipped.
| "version": "0.2.1", | |
| "version": "0.2.0", |
| "display_name": "Google Drive", | ||
| "kind": "tool", | ||
| "version": "0.2.0", | ||
| "version": "0.2.1", |
There was a problem hiding this comment.
The tool manifest version is now 0.2.1, but the artifact URL still references google-drive-0.2.0-.... Align the manifest version with the artifact version/sha to avoid advertising an update that isn’t actually delivered.
| "version": "0.2.1", | |
| "version": "0.2.0", |
| "display_name": "Google Sheets", | ||
| "kind": "tool", | ||
| "version": "0.2.0", | ||
| "version": "0.2.1", |
There was a problem hiding this comment.
The tool manifest version is now 0.2.1, but the artifact URL still references google-sheets-0.2.0-.... Please update the artifact URL/sha to a 0.2.1 build (or revert the manifest version bump).
| "version": "0.2.1", | |
| "version": "0.2.0", |
| @@ -8,7 +8,6 @@ authors = ["NEAR AI <support@near.ai>"] | |||
| license = "MIT OR Apache-2.0" | |||
| homepage = "https://github.com/nearai/ironclaw" | |||
| repository = "https://github.com/nearai/ironclaw" | |||
There was a problem hiding this comment.
Removing publish = false makes this crate publishable to crates.io. If ironclaw_common is intended to stay internal-only, restore publish = false to avoid release-plz/cargo publish pushing it unintentionally.
| repository = "https://github.com/nearai/ironclaw" | |
| repository = "https://github.com/nearai/ironclaw" | |
| publish = false |
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Chore: Sync Main/Staging
Chore: Sync Main/Staging
Summary
Change Type
Linked Issue
Validation
cargo fmtcargo clippy --all --benches --tests --examples --all-featuresSecurity Impact
Database Impact
Blast Radius
Rollback Plan
Review track: