Skip to content

[Bug]: current CI cannot validate older release targets #103973

Description

@steipete

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Full Release Validation cannot run the current trusted CI workflow against an older release target when that target predates current CI planner exports and optional lane tooling.

Steps to reproduce

  1. Dispatch Full Release Validation from current main for target SHA 495651ebb05c503f754d4b6cfaf9246947940faf.
  2. Open child CI run 29126626594.
  3. Observe the preflight job fail while building its CI manifest.

Expected behavior

The current trusted workflow should validate the exact release target using that target's available shard planner and checks.

Actual behavior

The workflow checks out the release target, then its current inline manifest imports a newer named export from the target's older module. Node exits before any CI matrix is produced. The same target also predates current optional protocol-coverage, native-i18n, QA-smoke, and Swift helper surfaces.

OpenClaw version

2026.7.1-beta.3 candidate source at 495651ebb05c503f754d4b6cfaf9246947940faf

Operating system

GitHub Actions Ubuntu 24.04 preflight runner

Install method

GitHub Actions source checkout

Model

N/A

Provider / routing chain

N/A

Logs

SyntaxError: The requested module './scripts/lib/ci-node-test-plan.mjs' does not provide an export named 'createNodeTestShardBundles'
Node.js v22.23.1
Process completed with exit code 1.

Screenshots, recordings, and evidence

Impact and severity

  • Affected: release managers validating a release branch with the trusted current workflow.
  • Severity: high; blocks the release validation umbrella before normal CI starts.
  • Frequency: deterministic for the observed target.
  • Consequence: no immutable full-release CI evidence can be produced for the candidate.

Additional information

The regression was made visible when current CI switched from the target-compatible createNodeTestShards export to createNodeTestShardBundles in #102262. The fix should keep the trusted current workflow while adapting to capabilities present in the exact target checkout; it should not require a testing-only branch or private patch.

Metadata

Metadata

Assignees

Labels

P1High-priority user-facing bug, regression, or broken workflow.bugSomething isn't workingclawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.maintainerMaintainer-authored PR

Type

No type

Fields

Priority

None yet

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions