nodejs / nodejs/core-validate-commit
Use the shared travis config with auto-updates for node releases
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 55
- Forks
- 62
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 1
Description
tl;dr: I'd like to open a PR to replace the node_js section in the .travis.yml with an imported https://github.com/nodejs/ci-config-travis/blob/master/lts/gte-8.yml
Background: Package Maintenance WG has built a repository of shared Travis CI imports. The imports will be automatically updated as new Node.js versions get released.
Judging by what's inside the current .travis.yml here, and the missing engines in the package.json, I suspect that the lts upgrade policy is the right fit (it adds new versions as soon as they are released, never removes LTS versions, removes non-LTS versions when they reach EOL).
Is that OK?
Contributor guide
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.
Research direction
The change is in .travis.yml; inspect the existing node_js section and compare it with the linked lts/gte-8.yml shared import. Check package.json for its current engine declarations, then validate that Travis accepts the imported configuration and that the resulting Node.js release policy matches the project’s needs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- ci-cd
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100