Skip to content

Fix local release testing: publish with --tag for prerelease versions (#57552)#57552

Closed
zeyap wants to merge 1 commit into
mainfrom
fix-e2e-publish-prerelease-tag
Closed

Fix local release testing: publish with --tag for prerelease versions (#57552)#57552
zeyap wants to merge 1 commit into
mainfrom
fix-e2e-publish-prerelease-tag

Conversation

@zeyap

@zeyap zeyap commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Summary:
scripts/e2e/init-project-e2e.js publishes in-repo packages to the local Verdaccio proxy with npm publish, but omits --tag. npm ≥ 11 (bundled with Node 24+) refuses to publish a prerelease version (e.g. 0.87.0-rc.0) without an explicit tag:

npm error You must specify a tag using --tag when publishing a prerelease version.

This breaks yarn test-release-local immediately at the publish step on any machine using npm ≥ 11.

Fix

Pass an explicit --tag react-native-e2e. This is a throwaway local registry and the install step pins the exact version, so the dist-tag value is not significant for resolution.

Changelog

[Internal] - Fix test-release-local publishing on npm ≥ 11

Test Plan: yarn test-release-local -t RNTestProject -p iOS now gets past the publish step on npm 11 (previously failed immediately at npm publish).

Reviewed By: christophpurrer

Differential Revision: D111995913

Pulled By: zeyap

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jul 14, 2026
@meta-codesync

meta-codesync Bot commented Jul 14, 2026

Copy link
Copy Markdown

@zeyap has imported this pull request. If you are a Meta employee, you can view this in D111995913.

@zeyap zeyap closed this Jul 15, 2026
@zeyap zeyap reopened this Jul 15, 2026
…#57552)

Summary:
`scripts/e2e/init-project-e2e.js` publishes in-repo packages to the local Verdaccio proxy with `npm publish`, but omits `--tag`. **npm ≥ 11** (bundled with Node 24+) refuses to publish a prerelease version (e.g. `0.87.0-rc.0`) without an explicit tag:

```
npm error You must specify a tag using --tag when publishing a prerelease version.
```

This breaks `yarn test-release-local` immediately at the publish step on any machine using npm ≥ 11.

## Fix

Pass an explicit `--tag react-native-e2e`. This is a throwaway local registry and the install step pins the **exact** version, so the dist-tag value is not significant for resolution.

## Changelog

[Internal] - Fix `test-release-local` publishing on npm ≥ 11


Test Plan: `yarn test-release-local -t RNTestProject -p iOS` now gets past the publish step on npm 11 (previously failed immediately at `npm publish`).

Reviewed By: christophpurrer

Differential Revision: D111995913

Pulled By: zeyap
@meta-codesync meta-codesync Bot changed the title Fix local release testing: publish with --tag for prerelease versions Fix local release testing: publish with --tag for prerelease versions (#57552) Jul 15, 2026
@meta-codesync meta-codesync Bot force-pushed the fix-e2e-publish-prerelease-tag branch from bed83bd to 719a78c Compare July 15, 2026 07:15
@meta-codesync

meta-codesync Bot commented Jul 15, 2026

Copy link
Copy Markdown

@zeyap has exported this pull request. If you are a Meta employee, you can view the originating Diff in D111995913.

@meta-codesync meta-codesync Bot closed this in 2dfdcbf Jul 15, 2026
@meta-codesync meta-codesync Bot added the Merged This PR has been merged. label Jul 15, 2026
@meta-codesync

meta-codesync Bot commented Jul 15, 2026

Copy link
Copy Markdown

@zeyap merged this pull request in 2dfdcbf.

react-native-bot pushed a commit that referenced this pull request Jul 15, 2026
…#57552)

Summary:
`scripts/e2e/init-project-e2e.js` publishes in-repo packages to the local Verdaccio proxy with `npm publish`, but omits `--tag`. **npm ≥ 11** (bundled with Node 24+) refuses to publish a prerelease version (e.g. `0.87.0-rc.0`) without an explicit tag:

```
npm error You must specify a tag using --tag when publishing a prerelease version.
```

This breaks `yarn test-release-local` immediately at the publish step on any machine using npm ≥ 11.

## Fix

Pass an explicit `--tag react-native-e2e`. This is a throwaway local registry and the install step pins the **exact** version, so the dist-tag value is not significant for resolution.

## Changelog

[Internal] - Fix `test-release-local` publishing on npm ≥ 11

Pull Request resolved: #57552

Test Plan: `yarn test-release-local -t RNTestProject -p iOS` now gets past the publish step on npm 11 (previously failed immediately at `npm publish`).

Reviewed By: christophpurrer

Differential Revision: D111995913

Pulled By: zeyap

fbshipit-source-id: 107a96d5c4317129228f783ad52bffe1578d1138
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Merged This PR has been merged. meta-exported p: Facebook Partner: Facebook Partner

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant