fix: upgrade github-comment-specific for semantic-release 25 - #1160
Conversation
github-comment-specific 1.0.7 requires p-filter without declaring it, relying on the CJS p-filter@2 that @semantic-release/github@8 hoisted to the top level. semantic-release 25 hoists ESM-only p-filter@4 instead, so the plugin's require() returns a namespace object and the success step throws 'TypeError: _b.apply is not a function' after publishing. Version 2.0.7 is built against @semantic-release/github@12 and no longer depends on p-filter. Ticket: AI-744 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
🎉 This PR is included in version @api-ts/express-wrapper@2.0.2 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @api-ts/typed-express-router@2.0.2 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @api-ts/io-ts-http@3.2.3 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @api-ts/openapi-generator@6.1.3 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @api-ts/superagent-wrapper@1.3.6 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
2 participants
Problem
Release run 29865224942 published all six packages successfully (trusted publishing + provenance now work end-to-end), but the workflow failed afterward in the
successhook of@semantic-release-extras/github-comment-specific:Version 1.0.7 calls
require("p-filter")without declaring it — a phantom dependency satisfied by the CJSp-filter@2that@semantic-release/github@8used to hoist. The semantic-release 25 upgrade hoists ESM-onlyp-filter@4instead, sorequire()returns a module namespace object and the call throws. Side effect: release-notification comments for that run were skipped (published packages were unaffected).Fix
Upgrade the plugin to 2.0.7, which targets
@semantic-release/github@12/@octokit/rest@22(the semantic-release 25 stack) and no longer uses p-filter. Verified locally that the plugin imports cleanly and exposes all five hooks.Note: multi-semantic-release filters commits per package directory, so this root-only
fix:commit may not cut new package versions by itself — but the release workflow should now complete green, and the next package-touching release will exercise the comment hooks.Ticket: AI-744
🤖 Generated with Claude Code