Back to Signal Feed
CodeTracked since May 19, 2026

Fix slack-channel sync rules to stop dropping MCP tests from CI mirror

The PR fixes a deterministic CI breakage by correcting the vendoring sync config for the slack-channel plugin: test files were excluded while `bun test` was still kept, causing `No tests found!` failures. The change updates `sources.yaml` so upstream `features/**` test suites are included and runnable in the mirror.

sources.yamlslack-channelbun testtest (mcp-plugins)

What Happened

  • The PR fixes a deterministic CI breakage by correcting the vendoring sync config for the slack-channel plugin: test files were excluded while `bun test` was still kept, causing `No tests found!` failures. The change updates `sources.yaml` so upstream `features/**` test suites are included and runnable in the mirror.
  • The PR fixes a deterministic CI breakage by correcting the vendoring sync config for the slack-channel plugin: test files were excluded while `bun test` was still kept, causing `No tests found!` failures. The change updates `sources.yaml` so upstream `features/**` test suites are included and runnable in the mirror.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Updated the slack-channel upstream sync mapping by removing `*.test.ts`/`*.spec.ts` from `exclude` and adding `features/**` to `include` in `sources.yaml`, so synced test files such as `server.test.ts`, `features/gate-properties.test.ts`, and `features/runner.test.ts` are restored in the vendored mirror and actually executed in CI.

Why Track This

Why It Matters

CI maintainers for MCP plugins now get real test validation for slack-channel instead of a repeatable false failure, so policy/journal/supervisor regressions are more likely to be detected before merge. The prior configuration kept `package.json`’s `bun test` script but removed the referenced tests, which produced a deterministic `No tests found!` exit and let the job short-circuit, hiding later plugin checks; continue monitoring whether other vendored plugins have similar sync-rule drift and whether CI still masks failures before a collect-all-failures mode is fully enforced.

Impact

CI maintainers for MCP plugins now get real test validation for slack-channel instead of a repeatable false failure, so policy/journal/supervisor regressions are more likely to be detected before merge. The prior configuration kept `package.json`’s `bun test` script but removed the referenced tests, which produced a deterministic `No tests found!` exit and let the job short-circuit, hiding later plugin checks; continue monitoring whether other vendored plugins have similar sync-rule drift and whether CI still masks failures before a collect-all-failures mode is fully enforced.

What To Watch Next

  • Watch whether sources.yaml becomes a repeated pattern.
  • Track follow-up changes around LLMOps.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: ci_short_circuit_masking, upstream_sync_rule_drift.
Open Topic TimelineOpen Technical EventOpen Original Sourceci_short_circuit_masking / upstream_sync_rule_drift / missing_tests_in_vendored_plugins

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

jeremylongshore/claude-code-plugins-plus-skills PR #745: fix(sync): stop stripping upstream tests from slack-channel mirror (claude-7tig.1)

This change turns a long-standing false-positive CI failure into real plugin coverage by fixing mismatched upstream sync include/exclude patterns.