🔧 update: adjust Node.js version strategy and update documentation - #7
Conversation
🚀 Development BuildDevelopment version ready for integration testing 📦 Package Information
📥 Installation InstructionsNPM Registrynpm install github-labels-template@0.9.2-dev.27a173a
npm install github-labels-template@dev # Use dist-tagGitHub Packagesnpm install @warengonzaga/github-labels-template@0.9.2-dev.27a173a
npm install @warengonzaga/github-labels-template@dev # Use dist-tag✨ Auto-scoped as 🔒 Security Audit✅ No vulnerabilities found This package was built automatically by the Package Build Flow action. |
🚀 Development BuildDevelopment version ready for integration testing 📦 Package Information
📥 Installation Instructions🔒 Security Audit✅ No vulnerabilities found This package was built automatically by the Package Build Flow action. |
There was a problem hiding this comment.
Pull request overview
This PR updates the project’s Node.js support policy to align with Node.js LTS (Node 22+), and adjusts CI + packaging scripts so builds/tests run against the supported runtime range.
Changes:
- Document Node.js v22+ as the runtime requirement (with v22/v24 called out) in README and CONTRIBUTING.
- Update CI workflow to test with a Node.js version matrix (22, 24) instead of a single version.
- Adjust
package.jsonbuild/pack lifecycle scripts and relax the Node engine constraint to>=22.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| README.md | Updates prerequisites and testing/runtime notes to reflect Node.js v22+ support. |
| package.json | Updates build command, adds packaging lifecycle hooks, and changes Node engine to >=22. |
| CONTRIBUTING.md | Updates contributor prerequisites to match the new Node.js support guidance. |
| .github/workflows/package.yml | Switches CI to a Node.js version matrix (22/24). |
…glet dependencies
🚀 Development BuildDevelopment version ready for integration testing 📦 Package Information
📥 Installation InstructionsGitHub Packagesnpm install @warengonzaga/github-labels-template@0.9.2-dev.83d2945
npm install @warengonzaga/github-labels-template@dev # Use dist-tag✨ Auto-scoped as 🔒 Security Audit✅ No vulnerabilities found This package was built automatically by the Package Build Flow action. |
🚀 Development BuildDevelopment version ready for integration testing 📦 Package Information
📥 Installation InstructionsNPM Registrynpm install github-labels-template@0.9.2-dev.83d2945
npm install github-labels-template@dev # Use dist-tag🔒 Security Audit✅ No vulnerabilities found This package was built automatically by the Package Build Flow action. |
🚀 Development BuildDevelopment version ready for integration testing 📦 Package Information
📥 Installation InstructionsNPM Registrynpm install github-labels-template@0.9.2-dev.c3aead4
npm install github-labels-template@dev # Use dist-tagGitHub Packagesnpm install @warengonzaga/github-labels-template@0.9.2-dev.c3aead4
npm install @warengonzaga/github-labels-template@dev # Use dist-tag✨ Auto-scoped as 🔒 Security Audit✅ No vulnerabilities found This package was built automatically by the Package Build Flow action. |
This pull request updates the project's Node.js version requirements to support LTS versions (v22 and v24) instead of only the latest version, and adjusts documentation, workflow, and packaging scripts accordingly. These changes improve compatibility and align the project with recommended Node.js LTS releases.
Node.js version support and documentation:
README.md,CONTRIBUTING.md, andpackage.jsonto broaden compatibility and clarify recommendations. [1] [2] [3] [4]CI workflow improvements:
.github/workflows/package.ymlto use a matrix strategy for testing against Node.js versions 22 and 24, instead of only version 25, ensuring CI coverage for supported LTS versions. [1] [2]Packaging and build scripts:
package.jsonscripts to addprepareandprepackhooks for building before packaging, and removed the--packages externalflag from the build command for improved compatibility. Also updated the engines field to reflect the new Node.js version requirement.