🐻 Component Refresh (charming soft)

[simurai]

⚠️ Don't merge this into master just yet. It will most likely be released as Primer CSS 15.0.0.

This PR is only to test changes with a different package name (@primer/css-next) so it can be installed in parallel to @primer/css.

🔍 All PRs merged into next (so far).

How to use this branch

1. Make a PR and change the base branch to next
   • You might wanna branch off from next if your changes are related.
2. When the PR is approved, merge it
3. In dotcom run bin/npm install @primer/css-next@canary
   • Or e.g. bin/npm install @primer/css-next@0.0.0-4467910 if you want to rollback to a previous PR

How to release this branch

Once all the changes from next should be available in @primer/css, do the following:

1. Revert this commit 6d181f9 (renaming the package)
2. Create a new "release" branch, probably release-15.0.0.
3. Change the base branch for this PR to release-15.0.0 -> merge it.
4. Follow the usual RELEASING process.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/primer/primer-css/3tzazr8d1
✅ Preview: https://primer-css-git-next.primer.vercel.app

[simurai]

Only changing the package name 6d181f9 to publish this branch as @primer/css-next seemed to work fine. 👌

Except that publish @primer/css never finishes. Which is kinda expected? Should we fix this? Maybe in https://github.com/primer/publish?

On the other hand, might be ok to keep as is since everything else works and we will revert changing the name 6d181f9 again before releasing the changes to @primer/css.

/cc @emplums @BinaryMuse @colebemis