No Git tag created for `@actions/artifact@2.1.1`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.9k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
@actions/artifact v2.1.1 has been uploaded to npm for a week (see https://www.npmjs.com/package/@actions/artifact/v/2.1.1), but there's no corresponding Git tag pushed.
To Reproduce
Check https://github.com/actions/toolkit/tags.
Expected behavior
A tag named @actions/artifact@2.1.1 created for perhaps commit https://github.com/actions/toolkit/commit/c4f4f5ae0716be0a39c150667d784df112a36168.
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
Check the @actions/artifact@2.1.1 package version against the GitHub toolkit tags page and inspect the referenced commit c4f4f5ae0716be0a39c150667d784df112a36168. Done means the corresponding @actions/artifact@2.1.1 Git tag exists at the intended commit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, typescript
- Domain
- release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100