v0.1.21: Require Node 24 and harden CI installs (npm/rollup optional deps)

Summary

This release is primarily about build and CI reliability. It moves the package and CI pipelines to Node.js 24, and updates GitHub Actions workflows to use a clean, forced install to work around npm/rollup optional-dependency issues.

There are no functional/runtime code changes to the GitHub tools API in this release.

Breaking change

Node.js 24 is now required

• package.json now declares:
  • engines.node: ">=24.0.0"
• CI workflows now run on Node 24.

Impact:

• Consumers and contributors running Node 22 (or earlier) will need to upgrade to Node 24+ to install/use this package.

CI / build changes

Work around npm/rollup optional dependency install failures

GitHub Actions workflows (test.yml, npm-publish.yml) now:

• Explicitly set the registry to the public npm registry (https://registry.npmjs.org/)
• Remove node_modules and any lockfile before installing
• Use npm install --force instead of npm ci

This is a mitigation for known npm issues where platform-specific optional dependencies (notably rollup native bindings) can fail to resolve correctly in CI environments.

Impact for contributors:

• Don’t expect CI parity with npm ci anymore; the workflows intentionally run a clean npm install --force.
• If you relied on repo-provided npm config, note that .npmrc was removed (see below).

Repository npm config cleanup

• The repository .npmrc was removed.
• The repo now treats package-lock.json as environment-specific (workflow comments and .gitignore updates indicate it’s not meant to be committed/used by CI).

Dependencies

• Bumped @eldrforge/git-tools to ^0.1.22.

Version

• Package version: 0.1.20 → 0.1.21