MetaMask / MetaMask/action-publish-release
Add a dry mode to the whole action
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 22
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
If there is a bug in this action, the bug won't reveal itself until after the release PR is merged. That seems too late in my opinion. It would be nice if we added a check to release PRs which ran this action in dry-run mode to ensure that everything up to running the actual commands to create a GitHub release and publish the NPM package work as designed.
Additionally, if we could prevent the issue that Maarten had with `@metamask/abi-utils` (where the release PR had to be recreated multiple times) then that would be great as well.
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
No files or tests are named. Start by tracing the action's release-PR workflow and the entry points that create a GitHub release or publish the NPM package; define which steps dry-run must validate and investigate the @metamask/abi-utils release-PR recreation problem. Done means release PRs can exercise those checks without running the actual publishing commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100