OpenZeppelin / OpenZeppelin/compact-tools
Attempt publish before tagging in release workflow
Open
Beginner friendly
Nobody has claimed this yet.
github_actions
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 5
- Avg merge
- 15h 28m
- Merged PRs (30d)
- 31
Description
Creating a tag should happen after publishing to npm. If there's a publishing issue, the workflow will be blocked until the tag is deleted
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
Locate the release workflow that publishes the package to npm and creates the tag. Read the publish and tagging steps first, then verify the workflow publishes before tagging and that its failure behavior matches the issue; test the workflow or inspect its validation path to confirm the ordering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100