Skip to content

Conversation

@Saadnajmi
Copy link
Collaborator

@Saadnajmi Saadnajmi commented Jan 14, 2026

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 Saadnajmi requested a review from a team as a code owner January 14, 2026 03:56
@Saadnajmi 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 Saadnajmi changed the title ci(0.79): demote 0.79 package from latest ci(0.79): demote release from latest Jan 14, 2026
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.
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