ci: cross-package regression canary against latest published stack - #3
Merged
Conversation
Adds .github/workflows/canary.yml: a scheduled (daily 06:00 UTC) + manually dispatchable job that upgrades every @wasmagent/* and @openagentaudit/* dependency to its latest published version (ignoring the pinned lockfile), then runs ts-check and the end-to-end chain test. This makes the golden path a canary for the whole provable-agent stack — a bad core publish that breaks execute->verify->evidence->passport turns this job red within a day, independent of this repo pinned versions. The existing ci.yml still tests the pinned lockfile on every push/PR. Verified locally: the upgrade step pulls newer versions (otel-exporter 2.0.0->3.0.0 etc) and ts-check + chain test (4/4) stay green.
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
1 participant
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.
Implements the cross-package regression gate (execution-plan §4-1) as a canary rather than a hard pre-publish block.
The core packages (
@wasmagent/core,aep,compliance, …) live in thewasmagent-jsmonorepo; this repo already exercises them end-to-end via the chain test. This adds.github/workflows/canary.yml:@wasmagent/*and@openagentaudit/*dependency to@latest(ignoring the pinned lockfile), then runsts-check+ the end-to-end chain test.ci.yml.The existing
ci.ymlstill tests the frozen lockfile on every push/PR — this is the complementary latest-published signal.Verified locally on a throwaway copy: the upgrade step pulls newer versions (
@wasmagent/otel-exporter2.0.0→3.0.0,ag-ui/mcp-firewallbumps) and bothts-checkand the chain test (4/4) stay green.