CI: do not persist the checkout token, and test the minimum supported Node
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- git, github-actions, nodejs
- Domain
- build-system, ci-cd
Research direction
Start with .github/workflows/ci.yml and .github/workflows/deploy.yml, where both actions/checkout steps need persist-credentials: false. For the Node item, compare package.json engines, .nvmrc, and .github/dependabot.yml, then decide with a maintainer whether to add a Node 22 matrix leg or raise engines to 24. Done when both workflows pass with the checkout change and CI tests the version that engines declares.
Written by the indexing model from the issue text.
Description
Summary
Two small gaps in the GitHub Actions workflows: the checkout step leaves the job token in the local git config while dependency scripts run, and CI only tests Node 24 although the project says it supports Node 22.12 and later.
Checklist
- Do not persist the checkout token.
.github/workflows/ci.yml:18and.github/workflows/deploy.yml:24useactions/checkoutwithoutpersist-credentials: false, so the job'sGITHUB_TOKENstays in.git/configwhilenpm ci, lint, tests and the build run code fromnode_modules. The token is already least-privilege (contents: read, pluspages: readin the deploy build job), and nothing later in either job uses git with it, so addwith: { persist-credentials: false }to both checkout steps. This is defence in depth: it matters if job permissions are widened later. - Test the oldest supported Node.
package.json:7-9declares"node": ">=22.12"and Dependabot pins@types/nodeto the oldest supported major (.github/dependabot.yml:15-17), but.nvmrcand both workflows use Node 24 only (ci.yml:21). Either add a Node 22 leg toci.yml, or raiseenginesto>=24and move@types/nodeto 24.
Acceptance criteria
- Both checkout steps set
persist-credentials: false, and both workflows still pass. - CI runs the declared minimum Node version, or
enginesmatches what CI tests.
Getting started
- Relevant files:
.github/workflows/ci.yml,.github/workflows/deploy.yml,package.json,.nvmrc,.github/dependabot.yml - Related: #20, #23
Filed by repo-audit/full-audit at de2b25b. Severity: low. Effort: S. audit-key: ci|.github/workflows/ci.yml|actions/checkout persist-credentials
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 3
- Avg merge
- 8h 13m
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TMHSDigital/GH-Arcade
-
bug good first issue severity: low
Difficulty 1/5 Under an hour Newbie friendliness 88/100
TMHSDigital/GH-Arcade#105 ·
-
bug good first issue severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
TMHSDigital/GH-Arcade#104 ·
-
bug good first issue severity: medium
Difficulty 2/5 Under an hour Newbie friendliness 84/100
TMHSDigital/GH-Arcade#88 ·
-
accessibility enhancement severity: low
Difficulty 4/5 3-5 days Newbie friendliness 40/100
TMHSDigital/GH-Arcade#114 ·
-
enhancement severity: low
Difficulty 4/5 3-5 days Newbie friendliness 35/100
TMHSDigital/GH-Arcade#113 ·
All issues in TMHSDigital/GH-Arcade
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
steelbrain/node-ssh#487 ·
-
cli: `execCargoMetadata` decodes stdout per chunk, corrupting non-ASCII paths across pipe boundariesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 62/100
lingdojo/kana-dojo#34127 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
osmlab/name-suggestion-index#13104 ·
Maintainers usually reply within 1 day