Attempt publish before tagging in release workflow

Open Beginner friendly
#90 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, typescript
Domain
ci-cd, release

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.

Description

github_actions

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

Dominant language
TypeScript
Stars
4
Forks
5
Avg merge
15h 28m
Merged PRs (30d)
31

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenZeppelin/compact-tools

All issues in OpenZeppelin/compact-tools

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.