fix: use Node.js 24 for npm OIDC trusted publishing#25
Merged
ichoosetoaccept merged 1 commit intomainfrom Dec 25, 2025
Merged
Conversation
github-actions bot
pushed a commit
that referenced
this pull request
Dec 25, 2025
## [0.2.2](v0.2.1...v0.2.2) (2025-12-25) ### Bug Fixes * use Node.js 24 for npm OIDC trusted publishing ([#25](#25)) ([5bcb716](5bcb716))
|
🎉 This PR is included in version 0.2.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
github-actions bot
pushed a commit
that referenced
this pull request
Apr 1, 2026
# [2.1.0](v2.0.19...v2.1.0) (2026-04-01) ### Bug Fixes * add knip config, pre-commit hook, fix Zod compatibility, and remove unused code ([#38](#38)) ([a34d956](a34d956)) * change default HOST from 0.0.0.0 to 127.0.0.1 ([zereight#289](https://github.com/detailobsessed/efficient-gitlab-mcp/issues/289)) ([4225366](4225366)) * **ci:** add Node.js 22 setup for semantic-release ([#13](#13)) ([941a64b](941a64b)) * **ci:** add permissions and secrets inherit for reusable workflow ([#15](#15)) ([2a41bfc](2a41bfc)) * **ci:** checkout release tag in npm-publish workflow ([#21](#21)) ([8094cd1](8094cd1)) * **ci:** remove persist-credentials false for semantic-release ([#14](#14)) ([e9d9db1](e9d9db1)) * correct bin format in package.json ([#26](#26)) ([91a1e98](91a1e98)) * create_or_update_file now properly updates existing files ([#2](#2)) ([6f97958](6f97958)) * use Node.js 24 for npm OIDC trusted publishing ([#25](#25)) ([5bcb716](5bcb716)) * use ubuntu-latest for npm publish (OIDC requires GitHub-hosted runners) ([#24](#24)) ([28155bc](28155bc)) * use workflow_run trigger for npm-publish (GITHUB_TOKEN releases don't emit events) ([#39](#39)) ([b544db2](b544db2)) ### Features * add 405 response for GET /mcp endpoint when STREAMABLE_HTTP is enabled. https://modelcontextprotocol.io/specification/2025-06-18/basic/transports#listening-for-messages-from-the-server ([zereight#295](https://github.com/detailobsessed/efficient-gitlab-mcp/issues/295)) ([6a03064](6a03064)) * add GitLab search tools (global, project, group) ([#6](#6)) ([3e2e279](3e2e279)) * add GitLab tool modules with 52 tools and comprehensive tests ([#1](#1)) ([14bc851](14bc851)) * add HTTP transport security features ([#9](#9)) ([0eed0d6](0eed0d6)) * add MCP protocol logging for agent observability ([#10](#10)) ([85c4c50](85c4c50)) * add MCP Registry support with mcpName and server.json ([#30](#30)) ([19dd31e](19dd31e)) * add npm version badge to README ([#23](#23)) ([1c2cc84](1c2cc84))
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes npm OIDC trusted publishing by upgrading to Node.js 24.
Problem
npm trusted publishing with OIDC requires npm >=11.5.1, which is bundled with Node.js 24. We were using Node.js 22, causing this error:
Solution
Change
node-versionfrom22to24in the npm-publish workflow.References