Skip to content

ci(0.79): demote release from latest - #2801

Merged
Saad Najmi (Saadnajmi) merged 7 commits into
microsoft:0.79-stablefrom
Saadnajmi:0.79-demote
Jan 17, 2026
Merged

Saad Najmi (Saadnajmi) merged 7 commits into
microsoft:0.79-stablefrom
Saadnajmi:0.79-demote

Conversation

@Saadnajmi

@Saadnajmi Saad Najmi (Saadnajmi) commented Jan 14, 2026 •

Copy link
Copy Markdown
Collaborator

Note: Needs #2800 to merge first

Summary:

Demote the 0.79 release in the NX config from latest to a new stable tag, now that 0.81 is (almost) out

@Saadnajmi
Saad Najmi (Saadnajmi) requested a review from a team as a code owner January 14, 2026 03:56
@Saadnajmi Saad Najmi (Saadnajmi) changed the title chore(0.79): demote NPM package from latest to 0.79-stable ci(0.79): demote 0.79 package from latest Jan 14, 2026
@Saadnajmi Saad Najmi (Saadnajmi) changed the title ci(0.79): demote 0.79 package from latest ci(0.79): demote release from latest Jan 14, 2026
Saad Najmi (Saadnajmi) added a commit that referenced this pull request Jan 16, 2026
## Summary:

One part of our publish process we have not yet automated is setting the
`v0.xx-stable` and `next` tags when a new release is promoted or
demoted. Let's automate this by specifying additional tags in our CI
that should be set when we publish a release. Now, a new `latest` or
patch to `latest` will also always set is `0.xx-stable` tag.

Note: Previously, if `0.xx` was tagged as `latest`, we would not have
had a `v0.xx-stable` tag. Now we will always have both `latest` and the
`0.xx-stable` tag.

## Test Plan:

I duplicated this change to
#2800 and
#2801 . We can look
at the dry run output for both to make sure release is behaving as
expected.
@Saadnajmi
Saad Najmi (Saadnajmi) merged commit eaec0c4 into microsoft:0.79-stable Jan 17, 2026
19 checks passed
@Saadnajmi
Saad Najmi (Saadnajmi) deleted the 0.79-demote branch January 17, 2026 06:42
Saad Najmi (Saadnajmi) added a commit that referenced this pull request Oct 15, 2026
react-native-macos@latest is 0.83 now, so tag 0.81 releases with 0.81-stable
instead, as #2801 did for 0.79. Until then, the prepublish check in the NPM
Publish (Dry Run) job fails on every 0.81-stable pull request, and would block
the next 0.81 release.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 33ac4470-c1d2-43c0-92ee-8407909f0f6a
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