ci: add beta dist-tag workflow

[dreamwasp]

Overview

Add a GHA workflow to publish beta packages when the beta label is added. This should also skip the alpha publish on commit. I also renamed a couple of tasks from "alpha" to "pre-release".

I have a couple of open questions about using the beta dist-tag like if we want to block multiple PRs from using the label or how we should "gate" it but this is the MVP of "publish under beta dist-tag"

PR Checklist

• Related to designs:
• Related to JIRA ticket: [gmt-1607]
• Version plan added/updated (or not needed)
• I have run this code to verify it works
• This PR includes unit tests for the code change
• This PR includes testing instructions tests for the code change
• The alpha package of this PR is passing end-to-end tests in all relevant Codecademy repositories

Testing Instructions

Branch off of this branch and try adding the beta tag to your test PR
you can also try `yarn add @codecademy/gamut@beta in another repo if you want to test that the dist-tags works

PR Links and Envs

n/a

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 913d422

---

☁️ Nx Cloud last updated this comment at 2026-04-16 15:46:15 UTC

[codecademydev]

📬 Published Beta Packages (install with @beta):

Package	Version	npm	Diff
@codecademy/gamut	68.2.3-beta.pr3327.24465403529.0	npm	diff
@codecademy/gamut-icons	9.57.3-beta.pr3327.24465403529.0	npm	diff
@codecademy/gamut-illustrations	0.58.10-beta.pr3327.24465403529.0	npm	diff
@codecademy/gamut-kit	0.6.593-beta.pr3327.24465403529.0	npm	diff
@codecademy/gamut-patterns	0.10.29-beta.pr3327.24465403529.0	npm	diff
@codecademy/gamut-styles	17.13.2-beta.pr3327.24465403529.0	npm	diff
@codecademy/gamut-tests	5.3.4-beta.pr3327.24465403529.0	npm	diff
@codecademy/variance	0.26.2-beta.pr3327.24465403529.0	npm	diff
eslint-plugin-gamut	2.4.4-beta.pr3327.24465403529.0	npm	diff

[dreamwasp]

we can change this - i'd like to add some gating or something around beta publishes so that the @beta tags stays useful

[codecov]

⚠️ JUnit XML file not found

The CLI was unable to find any JUnit XML files to upload.
For more help, visit our troubleshooting guide.

[github-actions]

🚀 Styleguide deploy preview ready!

Preview URL: https://69e104f0f28cc61349e32075--gamut-preview.netlify.app
Deploy Logs: https://app.netlify.com/projects/gamut-preview/deploys/69e104f0f28cc61349e32075

[sh0ji]

I think I see now where we were misunderstanding each other. I've been under the impression that you could just run something like this to get the React 19 stuff out under a prerelease channel (beta is fine).

yarn nx release prerelease --preid beta
yarn nx release publish --tag beta

That would publish it as 68.2.3-beta.0 I think, allowing @BandanaKM to install it with yarn add @codecademy/gamut@beta.

I'm all for updating our workflows and CI too, but it never crossed my mind as a dependency of unblocking Bana. Is there some reason we can't do that today without any real code changes?