Skip to content

ci: enable stable fork validation - #1

Merged
Kaliratech merged 1 commit into
mainfrom
chore/enable-fork-ci
Aug 24, 2026
Merged

Kaliratech merged 1 commit into
mainfrom
chore/enable-fork-ci

Conversation

@Kaliratech

Copy link
Copy Markdown
Owner

Summary

  • keep the fork's build and test workflow and add a real manual trigger
  • update validation to Node 22 with dependency caching and bounded concurrency
  • remove npm and MCP Registry publication workflows because this fork does not own the upstream package or registry identity
  • serialise Vitest files because parallel worker teardown races the signal-resilience subprocess group

Verification

  • npm run build: pass
  • npm test: 23 files, 258 tests, 0 failures
  • tests/signal-resilience.test.ts passes alone
  • the full suite passes with file-level serialisation
  • repository Actions enabled; workflow registry now active

The branch is current with upstream main before this change.

@Kaliratech
Kaliratech merged commit f16e3e3 into main Aug 24, 2026
1 check passed
@Kaliratech
Kaliratech deleted the chore/enable-fork-ci branch August 24, 2026 12:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant