From ece2e9f51e6aa4a8255cdfafe4a5854a26d48cfe Mon Sep 17 00:00:00 2001 From: Josh Johanning Date: Tue, 17 Mar 2026 14:46:25 -0500 Subject: [PATCH] docs: update Node.js runtime instructions in Copilot guidelines --- config/copilot/copilot-instructions-actions.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/config/copilot/copilot-instructions-actions.md b/config/copilot/copilot-instructions-actions.md index 5ace6ba..0aa8acf 100644 --- a/config/copilot/copilot-instructions-actions.md +++ b/config/copilot/copilot-instructions-actions.md @@ -59,8 +59,8 @@ const { functionToTest } = await import('../src/index.js'); ### Node Runtime -- Use `node24` (or the latest supported runtime) for `runs.using` in `action.yml` -- Keep the `runs.using` value up to date when GitHub deprecates older Node runtimes +- Use the same Node.js runtime version configured in this repo's `action.yml` (currently `node20`) for `runs.using` +- When updating Node.js support, update `runs.using` in `action.yml`, the `engines.node` range in `package.json`, and CI/test matrices together to stay consistent ### Input Handling @@ -106,7 +106,6 @@ const { functionToTest } = await import('../src/index.js'); ### Dependency and Version Changes - When bumping versions or changing dependencies, run `npm install` first to sync the `package-lock.json`, then run `npm run all` -- Always commit `package-lock.json` -- it must be checked in to the repository - Do not skip these steps -- a mismatched `package-lock.json` or failing checks will break CI ## Documentation Standards