Clean up `semantic-release` dependency
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 140
- Forks
- 100
- Avg merge
- 1h 3m
- Merged PRs (30d)
- 30
Description
package.json has 20.x
https://github.com/openedx/paragon/blob/839964c84490b78d3e0c2403c51600f45bd49df0/package.json#L162
release.yml has @22
I think this means we can just remove it from package.json and rely on the npx installed version in the release workflow, but it'd be good to verify that with some dry runs.
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
Compare the semantic-release declarations in package.json and .github/workflows/release.yml, then use dry runs to verify whether the workflow's npx-installed version is sufficient. Done means package.json no longer carries a redundant dependency and the release workflow still behaves as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd, release
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100