Back to Signal Feed
ProductionTracked since May 19, 2026

Fix slack-channel sync config so upstream tests are preserved in MCP CI

This PR fixes a deterministic CI regression by updating the slack-channel sync block in `sources.yaml` to stop excluding `*.test.ts` and `*.spec.ts` and to explicitly include `features/**`, so vendored `jeremylongshore/claude-code-slack-channel` now keeps its upstream test files while still syncing correctly.

jeremylongshore/claude-code-plugins-plus-skillsjeremylongshore/claude-code-slack-channelsources.yamlbun test

What Happened

  • This PR fixes a deterministic CI regression by updating the slack-channel sync block in `sources.yaml` to stop excluding `*.test.ts` and `*.spec.ts` and to explicitly include `features/**`, so vendored `jeremylongshore/claude-code-slack-channel` now keeps its upstream test files while still syncing correctly.
  • This PR fixes a deterministic CI regression by updating the slack-channel sync block in `sources.yaml` to stop excluding `*.test.ts` and `*.spec.ts` and to explicitly include `features/**`, so vendored `jeremylongshore/claude-code-slack-channel` now keeps its upstream test files while still syncing correctly.
  • 1 evidence item attached for review.

What is Different

Before

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

Now

Corrected a sync-template behavior bug in the slack-channel MCP plugin mirror by aligning synced file patterns with its test script: test files were dropped from the mirror even though `package.json` still ran `bun test`, producing deterministic CI red; the config change restores the intended test coverage execution path.

Why Track This

Why It Matters

Developers and CI operators will now get actual slack-channel plugin test results instead of a fake failure caused by missing test files, so regressions in MCP plugin logic are less likely to be hidden and can be caught during normal CI runs. The root cause was a sync-rule mismatch in `sources.yaml` (`exclude` dropped tests while `bun test` remained), and the fix now includes `features/**` while removing `*.test.ts`/`*.spec.ts` from excludes; continue monitoring whether other MCP plugin sync mirrors have similar rule drift and whether remaining short-circuit logic still hides failures in later plugin iterations.

Impact

Developers and CI operators will now get actual slack-channel plugin test results instead of a fake failure caused by missing test files, so regressions in MCP plugin logic are less likely to be hidden and can be caught during normal CI runs. The root cause was a sync-rule mismatch in `sources.yaml` (`exclude` dropped tests while `bun test` remained), and the fix now includes `features/**` while removing `*.test.ts`/`*.spec.ts` from excludes; continue monitoring whether other MCP plugin sync mirrors have similar rule drift and whether remaining short-circuit logic still hides failures in later plugin iterations.

What To Watch Next

  • Watch whether jeremylongshore/claude-code-plugins-plus-skills becomes a repeated pattern.
  • Track follow-up changes around AI Coding Agents.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: ci_short_circuit_hides_later_plugin_failures, other_plugin_sync_exclude_drift.
Open Topic TimelineOpen Technical EventOpen Original Sourceci_short_circuit_hides_later_plugin_failures / other_plugin_sync_exclude_drift / no_tests_found_false_positive_regression

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)

The failure was caused by `sources.yaml` excluding test globs while syncing upstream `bun test` into the mirror, which triggered a hard `No tests found!` exit; the patch removes those excludes and adds `features/**` to `include`.