-
-
Notifications
You must be signed in to change notification settings - Fork 80.7k
[Bug]: current CI cannot validate older release targets #103973
Copy link
Copy link
Closed
Labels
P1High-priority user-facing bug, regression, or broken workflow.High-priority user-facing bug, regression, or broken workflow.bugSomething isn't workingSomething isn't workingclawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.This 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.Very strong issue quality with high-confidence source-level or clear reproduction.maintainerMaintainer-authored PRMaintainer-authored PR
Description
Metadata
Metadata
Assignees
Labels
P1High-priority user-facing bug, regression, or broken workflow.High-priority user-facing bug, regression, or broken workflow.bugSomething isn't workingSomething isn't workingclawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.This 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.Very strong issue quality with high-confidence source-level or clear reproduction.maintainerMaintainer-authored PRMaintainer-authored PR
Type
Fields
Priority
None yet
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
mainfor target SHA495651ebb05c503f754d4b6cfaf9246947940faf.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
495651ebb05c503f754d4b6cfaf9246947940fafOperating system
GitHub Actions Ubuntu 24.04 preflight runner
Install method
GitHub Actions source checkout
Model
N/A
Provider / routing chain
N/A
Logs
Screenshots, recordings, and evidence
Impact and severity
Additional information
The regression was made visible when current CI switched from the target-compatible
createNodeTestShardsexport tocreateNodeTestShardBundlesin #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.