Files
n8n-mcp/package.runtime.json
Romuald Członkowski a9c4400a92 fix: sync package.runtime.json version in Docker builds (v2.33.1) (#534)
Docker images were built with stale package.runtime.json (v2.29.5)
while npm package was at v2.33.0. This was caused by the build-docker
job not syncing the version before building, while publish-npm did.

Changes:
- Add "Sync runtime version" step to release.yml build-docker job
- Add "Sync runtime version" step to docker-build.yml build job
- Add "Sync runtime version" step to docker-build.yml build-railway job
- Bump version to 2.33.1 to trigger release with fix

The sync uses a lightweight Node.js one-liner (no npm install needed)
to update package.runtime.json version from package.json before
Docker builds.

Conceived by Romuald Czlonkowski - www.aiadvisors.pl/en

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-12 10:25:58 +01:00

25 lines
559 B
JSON

{
"name": "n8n-mcp-runtime",
"version": "2.33.1",
"description": "n8n MCP Server Runtime Dependencies Only",
"private": true,
"dependencies": {
"@modelcontextprotocol/sdk": "1.20.1",
"@supabase/supabase-js": "^2.57.4",
"express": "^5.1.0",
"express-rate-limit": "^7.1.5",
"dotenv": "^16.5.0",
"lru-cache": "^11.2.1",
"sql.js": "^1.13.0",
"tslib": "^2.6.2",
"uuid": "^10.0.0",
"axios": "^1.7.7"
},
"engines": {
"node": ">=16.0.0"
},
"optionalDependencies": {
"better-sqlite3": "^11.10.0"
}
}