Skip to content

Create logic to publish two versions of @webref/css #1572

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Jun 10, 2025
Merged

Create logic to publish two versions of @webref/css #1572

merged 7 commits into from
Jun 10, 2025

Conversation

tidoust
Copy link
Member

@tidoust tidoust commented Jun 6, 2025

Goal is to continue to publish the CSS extracts per spec as version 6 and to publish the consolidated CSS as version 7 of the @webref/css package.

The versions are handled as two different packages in the code, but the actual package name is the same (defined in respective package.json files).

Note: Draft PR for now as I still need to add an -alpha suffix to the new version and update the code that bumps the package version accordingly as it does not currently expect that.

tidoust added 4 commits June 6, 2025 20:09
Goal is to continue to publish the CSS extracts per spec as version 6 and to
publish the consolidated CSS as version 7 of the `@webref/css` package.

The versions are handled as two different packages in the code, but the
actual package name is the same (defined in respective `package.json` files).
@tidoust tidoust marked this pull request as ready for review June 7, 2025 09:36
@tidoust
Copy link
Member Author

tidoust commented Jun 7, 2025

Code should now properly support pre-release version flags. Proposal is to release a 7.0.0-alpha version. I also adjusted the pre-release PR script so that it installs and computes a diff with the right version of the released package.

I tried to document the guarantees and to point people at "How to upgrade" instructions in the documentation.

@tidoust tidoust requested a review from dontcallmedom June 7, 2025 09:37
@tidoust
Copy link
Member Author

tidoust commented Jun 7, 2025

Note: I couldn't really test the release logic, coz' it's tied to npm releases. I wouldn't be surprised if there were details to adjust. Nothing like testing in production, right? \o/

@tidoust tidoust merged commit 4f33ac9 into main Jun 10, 2025
1 check passed
@tidoust tidoust deleted the css6 branch June 10, 2025 09:31
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