Skip to content

ci(0.81): pass --access public to npm publish#3000

Merged
Saadnajmi merged 1 commit into
microsoft:0.81-stablefrom
Saadnajmi:0.81/fix-npm-publish-access-public-r2
Jun 26, 2026
Merged

ci(0.81): pass --access public to npm publish#3000
Saadnajmi merged 1 commit into
microsoft:0.81-stablefrom
Saadnajmi:0.81/fix-npm-publish-access-public-r2

Conversation

@Saadnajmi

@Saadnajmi Saadnajmi commented Jun 26, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • add --access public to scoped package publish commands in .ado/jobs/npm-publish.yml
  • apply the flag to both yarn and npm publish paths

Why

Azure publish failed while publishing @react-native-macos/virtualized-lists with:

  • YN0035 Not found
  • PUT https://registry.npmjs.org/@react-native-macos%2fvirtualized-lists

For scoped packages, publish needs explicit public access. This change aligns the pipeline command with npm scoped package publish requirements.

Test Plan

  • Re-run the Azure publish pipeline on this PR/branch and verify Publish packages succeeds for both:
    • @react-native-macos/virtualized-lists
    • react-native-macos

Fix Azure Pipelines publish step for scoped packages by explicitly setting public access for both yarn and npm publish paths.\n\nThis matches the previously landed publish fix and addresses 404 PUT failures when publishing @react-native-macos/virtualized-lists.\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@Saadnajmi Saadnajmi requested a review from a team as a code owner June 26, 2026 22:12
@Saadnajmi Saadnajmi merged commit 003c68c into microsoft:0.81-stable Jun 26, 2026
23 of 43 checks passed
@Saadnajmi Saadnajmi deleted the 0.81/fix-npm-publish-access-public-r2 branch June 26, 2026 23:06
Saadnajmi added a commit that referenced this pull request Jun 26, 2026
## Summary
- revert the generated `chore(release): publish 0.81.8` bump commit so
repo versions return to the last published baseline (`0.81.7`)
- keep a single Nx patch version plan to retry releasing `0.81.8`

## Why
`0.81.8` was tagged in git but did not fully publish to npm. Retrying
from `0.81.7` + a patch version plan is the same working pattern used in
the previous release-retry PR.

## Changes since v0.81.7
- chore(0.81): bump fmt to 12.1.0 to fix Xcode 26.4 (#2997)
- fix(0.81): Add value-initialization in RCTComponentData (#2999)
- ci(0.81): pass --access public to npm publish (#3000)

## Validation
- `yarn exec -- nx release --dry-run --verbose`
  - resolves current versions as `0.81.7`
- plans bump to `0.81.8` for both `react-native-macos` and
`@react-native-macos/virtualized-lists`

🤖 Generated with Copilot CLI

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants