purescript-contrib / purescript-contrib/setup-purescript
Don't use the versions file for tools installed via NPM
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 46
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
The versions file exists to avoid rate limits imposed by GitHub when getting the latest release for various tools via the GitHub API. However, if a user specifies they want the latest tool and the tool is installed via NPM, then we should skip the versions file and just NPM install the latest -- we don't get rate limited on that.
Contributor guide
No contributing guide indexed for this repository
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
Start with the versions file and the logic that reads it for tool versions. Verify how the workflow identifies tools installed via NPM, then make the latest-tool path install the latest NPM version without consulting the versions file while preserving the existing behavior for other tools.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100