fix(release): unblock v0.1.0 npm publish — handle component-prefixed tag + Node 24 opt-in

[IgorShevchik]

Unblocks the v0.1.0 publish to npm. Three small interrelated fixes — all touch the release pipeline; no src/ changes.

The story

PR #20 (release v0.1.0) merged → release-please.yml ran → tag b24rabbitmq-v0.1.0 and GitHub Release "b24rabbitmq: v0.1.0" created → npm-publish.yml triggered on release: published → publish failed at the sanity check because the tag carries a component prefix the strip logic didn't handle. As a bonus, that same workflow run surfaced a Node.js 20 deprecation warning on googleapis/release-please-action@v4 — and the same warning applies to every JavaScript action we pin in the other workflows.

Fix #1 — npm-publish sanity check handles both tag formats

-RAW="${GITHUB_REF#refs/tags/}"
-TAG="${RAW#v}"
+strip_tag() {
+  local raw="$1"
+  raw="${raw#b24rabbitmq-}"
+  raw="${raw#v}"
+  echo "$raw"
+}
+RAW="${GITHUB_REF#refs/tags/}"
+TAG=$(strip_tag "$RAW")

Same helper used on both the release-event path and the workflow_dispatch fallback. Dry-tested locally for b24rabbitmq-v0.1.0 (legacy), v0.1.1 (future), 0.1.0, b24rabbitmq-0.1.0 — all normalise to the bare semver 0.1.0 / 0.1.1.

Fix #2 — release-please stops adding the component prefix

   "release-type": "node",
   "include-v-in-tag": true,
+  "include-component-in-tag": false,
   "bump-minor-pre-major": true,

Single-package repo; the component prefix only adds noise. Future release PRs propose tag v0.1.1 (clean). The strip helper still works for both formats, so this PR doesn't have to land before v0.1.0 ships — but it's the right long-term shape.

Fix #3 — Node 24 opt-in across all three workflows

env:
  FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: 'true'

Added at the workflow level to release-please.yml, npm-publish.yml, and ci.yml. JavaScript actions (googleapis/release-please-action@v4, actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4) still run on Node 20 internally; the runner deprecation notice mandates Node 24 from 2026-06-02 and removes Node 20 from runners 2026-09-16. The FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 flag is the documented forward-compat option — opts the whole workflow into Node 24 without touching any individual action pin. Removable once every action ships a Node 24 native release.

Post-merge plan (to actually get v0.1.0 onto npm)

1. Merge this PR.
2. Trigger npm-publish.yml via workflow_dispatch on main — HEAD on main is the tagged commit b24rabbitmq-v0.1.0, git describe --tags --exact-match HEAD returns that tag, strip helper normalises to 0.1.0, matches package.json, OIDC publish proceeds.
3. Verify https://www.npmjs.com/package/@bitrix24/b24rabbitmq shows 0.1.0 with a green provenance badge.

After this is in npm, the next release will be the first one running through the corrected pipeline end-to-end — clean tag, no manual dispatch.

Gates

Gate	Result
pnpm lint	green
pnpm typecheck	green
pnpm test	66/66
pnpm test:coverage	100/100/100/100
pnpm build	green
pnpm docs:build	green
Tag-strip dry-run (4 inputs)	all normalise to bare semver

Behavioural change

None in src/. Public exports unchanged. No bundle size delta.

---

Generated by Claude Code