Repository navigation
Prepare inline-css 5.0.0-rc.1 - #159
Merged
Merged
Conversation
16 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements the 16-issue release scope proposed in #158 and stages
inline-css@5.0.0-rc.1with only its seven existing companion packages. No new npm package names are introduced.The release adds explicit, bounded stylesheet access; corrects CSS cascade, source-order and media handling; and prevents template placeholder and inherited-key corruption. It retains the CommonJS Promise API while requiring Node 22.12+, disabling automatic proxies, and rejecting selector removal when CSS is retained. Migration guidance covers these changes and the standalone package contracts.
Resource policy and template protection remain shared internal source. A Node-only build bundles the required files into each existing package before packing; generated files are not committed. Packed-consumer checks verify neither former helper package is installed or resolvable and aggregate loading limits remain shared across copies.
Validation:
Resource-limit defaults remain provisional pending representative production workloads and RC feedback. This PR enables the Linux/Windows CI matrix for Node 22.12, 22, 24 and 26. No npm packages have been published; RC publication and stable promotion remain separate steps.
The internal-helper revision passes CI on Linux and Windows for Node 22.12, 22, 24 and 26, including the eight-package packed-consumer checks.
Refs #158.