Skip to content

Rename legacy manufact branding to madmcp (service name, JSON info re… #122

Rename legacy manufact branding to madmcp (service name, JSON info re…

Rename legacy manufact branding to madmcp (service name, JSON info re… #122

Triggered via push July 25, 2026 20:29
Status Failure
Total duration 21s
Artifacts

ci.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 7 warnings
test
Process completed with exit code 1.
test/version-sync.test.js > version sync > keeps server.js's reported version in sync with package.json (found drifted 2026-07-25: package.json said 2.0.0, server.js said 2.1.0): test/version-sync.test.js#L22
AssertionError: Could not find the 'manufact-mcp-server vX.Y.Z listening' startup log in server.js -- update this test's regex if that message changed.: expected null not to be null ❯ test/version-sync.test.js:22:165
test
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test: connectors/notion/tools.js#L14
'findTagOverlapCandidates' is defined but never used
test: connectors/github/tools.js#L7
'z' is defined but never used
test: connectors/github/resource.js#L8
'toBase64' is defined but never used
test: connectors/github/resource.js#L8
'fromBase64' is defined but never used
test: connectors/github/prs.js#L7
'DEFAULT_OWNER' is defined but never used
test
package-lock.json is out of sync with package.json -- falling back to npm install so CI can still run. Trigger the 'Generate lockfile' workflow (workflow_dispatch) to regenerate and commit an up-to-date lockfile.