`@v2` tag still points to v2.0.2, not v2.1.0

Open Beginner friendly
#48 0 comments 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions
Domain
ci-cd, release

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.

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…)

Image

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.

Image
Dominant language
TypeScript
Stars
140
Forks
19
Avg merge
7d 9h
Merged PRs (30d)
8

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 pnpm/setup

All issues in pnpm/setup

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.