`@v2` tag still points to v2.0.2, not v2.1.0
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 140
- Forks
- 19
- Avg merge
- 13h 19m
- Merged PRs (30d)
- 3
Description
On pnpm/setup@v2, CI actually pulls v2.0.2, not the latest v2.1.0
From log:
Download action repository 'pnpm/setup@v2' (SHA:84cb39b…)
On the tags page, v2 still points at the same commit as v2.0.2 (84cb39b), while v2.1.0 is 703c526 so publishing v2.1.0 didn't advance the v2 tag. Effect: @v2 users miss v2.1.0 and get Warning: Unexpected input(s) 'require-lockfile' because the input only exists in v2.1.0.
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
Start at the repository's tags page and compare the commit targets for v2, v2.0.2, and v2.1.0. Update the v2 tag to the v2.1.0 commit, 703c526, then verify that pnpm/setup@v2 resolves to the new commit and includes the require-lockfile input.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100