Skip to content

chore: promote staging to staging-promote/e0f393bf-23105705354 (2026-03-16 23:06 UTC)#1267

Merged
henrypark133 merged 4 commits intostaging-promote/e0f393bf-23105705354from
staging-promote/1f209db0-23170138026
Mar 16, 2026
Merged

chore: promote staging to staging-promote/e0f393bf-23105705354 (2026-03-16 23:06 UTC)#1267
henrypark133 merged 4 commits intostaging-promote/e0f393bf-23105705354from
staging-promote/1f209db0-23170138026

Conversation

@ironclaw-ci
Copy link
Contributor

@ironclaw-ci ironclaw-ci bot commented Mar 16, 2026

Auto-promotion from staging CI

Batch range: 63a23550d6b485de6eb3b9a8aefeee47de569ddd..1f209db0faa8169e2e83dff5b700e30db1aead9f
Promotion branch: staging-promote/1f209db0-23170138026
Base: staging-promote/e0f393bf-23105705354
Triggered by: Staging CI batch at 2026-03-16 23:06 UTC

Commits in this batch (15):

Current commits in this promotion (1)

Current base: staging-promote/e0f393bf-23105705354
Current head: staging-promote/1f209db0-23170138026
Current range: origin/staging-promote/e0f393bf-23105705354..origin/staging-promote/1f209db0-23170138026

Auto-updated by staging promotion metadata workflow

Waiting for gates:

  • Tests: pending
  • E2E: pending
  • Claude Code review: pending (will post comments on this PR)

Auto-created by staging-ci workflow

@github-actions github-actions bot added size: XS < 10 changed lines (excluding docs) risk: low Changes to docs, tests, or low-risk modules contributor: core 20+ merged PRs labels Mar 16, 2026
@claude
Copy link

claude bot commented Mar 16, 2026

Code review

Found 1 issue:

  1. [HIGH:100] Version-artifact URL mismatch in telegram channel — manifest declares version 0.2.4 but artifact URL still references 0.2.3 binary

    "version": "0.2.4",
    "wit_version": "0.3.0",
    "description": "Talk to your agent through a Telegram bot",
    "keywords": [
    "messaging",
    "bot",
    "chat",
    "telegram"
    ],
    "source": {
    "dir": "channels-src/telegram",
    "capabilities": "telegram.capabilities.json",
    "crate_name": "telegram-channel"
    },
    "artifacts": {
    "wasm32-wasip2": {
    "url": "https://github.com/nearai/ironclaw/releases/download/v0.18.0/telegram-0.2.3-wasm32-wasip2.tar.gz",
    "sha256": "b9a83d5a2d1285ce0ec116b354336a1f245f893291ccb01dffbcaccf89d72aed"

    The PR bumps the declared version to 0.2.4 but the artifact URL still downloads the 0.2.3 WASM binary:

    • Line 5: "version": "0.2.4"
    • Line 21: "url": "https://github.com/nearai/ironclaw/releases/download/v0.18.0/telegram-0.2.3-wasm32-wasip2.tar.gz"

    Impact: Users installing this channel will see version 0.2.4 in the registry but will actually run version 0.2.3 code. This creates silent version confusion where manifest metadata and runtime code are inconsistent, potentially masking bug fixes or security patches intended for 0.2.4. Per installer.rs, version-pinned release URLs use strict checksum validation with no fallback, so the mismatch will persist through installation.

    Fix: Update the artifact URL to telegram-0.2.4-wasm32-wasip2.tar.gz and update the sha256 checksum to match the released 0.2.4 artifact, or revert the version bump until the 0.2.4 release is available.

henrypark133 and others added 3 commits March 16, 2026 16:10
* fix staging CI coverage regressions

* ci: cover all e2e scenarios in staging

* ci: restrict staging PR checks and fix webhook assertions

* ci: keep code style checks on PRs

* ci: preserve e2e PR coverage

* test: stabilize staging e2e coverage

* fix: propagate postgres tls builder errors

* ci: isolate heavy integration tests

* fix: clean up heavy integration CI follow-up
* fix: misleading UI message

* review fixes

* review fixes

* enhance test
…1776

chore: promote staging to staging-promote/1f209db0-23170138026 (2026-03-16 23:13 UTC)
@github-actions github-actions bot added scope: agent Agent core (agent loop, router, scheduler) scope: channel/wasm WASM channel runtime scope: ci CI/CD workflows scope: dependencies Dependency updates labels Mar 16, 2026
@henrypark133 henrypark133 merged commit d3e392a into staging-promote/e0f393bf-23105705354 Mar 16, 2026
12 of 13 checks passed
@henrypark133 henrypark133 deleted the staging-promote/1f209db0-23170138026 branch March 16, 2026 23:43
@github-actions github-actions bot added size: L 200-499 changed lines risk: medium Business logic, config, or moderate-risk modules and removed size: XS < 10 changed lines (excluding docs) risk: low Changes to docs, tests, or low-risk modules labels Mar 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

contributor: core 20+ merged PRs risk: medium Business logic, config, or moderate-risk modules scope: agent Agent core (agent loop, router, scheduler) scope: channel/wasm WASM channel runtime scope: ci CI/CD workflows scope: dependencies Dependency updates size: L 200-499 changed lines staging-promotion

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants