chore(release): version packages - #131
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
12 times, most recently
from
April 30, 2026 14:00
b317d66 to
01542f2
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
June 23, 2026 06:59
01542f2 to
d196a7e
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
June 23, 2026 07:06
d196a7e to
8ec5d37
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
tailwindcss-obfuscator@3.2.0
Minor Changes
#143
d7ebffeThanks @josedacosta! - New extractor optionscanObjectStrings(defaultfalse) — opt-in pass that walks Tailwind class strings stored in object property values, factory args, and lookup tables that the standard JSX /cn()/cva()/tv()walkers don't reach. Heuristic-gated to avoid false positives: a string is picked up only if it contains ≥2 whitespace-separated tokens AND every token validates as a Tailwind class. Single-word strings ("flex","red","info") are NEVER auto-extracted — wrap them incn(…)or add tosafelist.Fixes the « broken design with obfuscator » class of bugs where status-color tables, badge variants by level, etc. produced inconsistent obfuscation across siblings of the same lookup table.
Patch Changes
#130
c5c1684Thanks @josedacosta! - Documentation: corrected the v4 feature-status pages (research/tailwind-v4-features-analysis,research/tailwind-v4-summary,research/v4-implementation-checklist). Most v4 utilities and variants previously labelled « ❌ MISSING » have actually shipped since v2.0.x — the docs were stale. The pages now accurately reflect that wildcard variants, 3D transforms, inset shadows, radial/conic gradients, field-sizing/color-scheme/font-stretch utilities, CSS-variable parens shorthand, arbitrary underscores and the v4 important-suffix syntax are all supported. No code change.#133
d000dcaThanks @josedacosta! - Documentation: removed the stale « tv() currently broken » card on the Limitations page. The fix shipped in PR fix: extract tv() (tailwind-variants) base + variants + compoundVariants (#61) #63 (issue fix: tv() (tailwind-variants) extractor misses base + variants + compoundVariants classes #61 closed) on 2026-04-29 and is verified end-to-end on every release byapps/test-tailwind-variants/. The card now correctly says supported, with a single noted caveat (multi-elementslotAPI not yet in test matrix).#134
b246940Thanks @josedacosta! - CI: added a weekly version-watch cron (Monday 08:00 UTC) that surveils every package this project supports for SemVer-major bumps OR explicit breaking-change keywords in upstream release notes. Anti-overkill: patches and minors are intentionally not surfaced (routine bumps are out of scope). Notification path is SMTP email whenSMTP_*secrets are configured, GitHub-issue fallback otherwise. Adjustable via.github/version-watch-config.json.#140
aaaac48Thanks @josedacosta! - Test apps: addedapps/test-eleventy/exercising Eleventy (11ty) v3 + Tailwind v4 + thetailwindcss-obfuscator/internalsCLI-mode pipeline. Eleventy emits multi-page HTML output from Nunjucks templates; the post-build pass walks every_site/**/*.htmlpage and rewrites_site/styles.cssin lockstep. 78 classes extracted at 100 % CSS obfuscation, 0 % residual. Adds_siteto theverify-obfuscation.mjsbuild-dir search list so the new app (and any future Eleventy/Jekyll app) is auto-detected.#142
92d943eThanks @josedacosta! - Test apps: addedapps/test-lit/exercising Lit (web components) v3 + Vite + Tailwind v4. Confirms the JSX/AST extractor handlesclass="..."attributes embedded inside Lit'shtml\`tagged template literals (Babel parses the template's quasis and the existing JSXAttribute/HTML regex catches the class strings). 52 classes extracted at 100 % obfuscation, 0 % residual. No package code change needed; the only app-specific config was extending thecontentglob to include*/.ts` (Lit lives in .ts files, not .tsx).#135
759009aThanks @josedacosta! - Test apps: addedapps/test-preact/exercising Preact + Vite + Tailwind v4. Verifies the JSX extractor correctly handles Preact'sclassattribute (vs React'sclassName) and signal-based reactive class bindings. 50 classes extracted at 100 % obfuscation coverage with 0 % residual on first build, no code change to the package needed.#139
142690fThanks @josedacosta! - Test apps: addedapps/test-vite-react-v5/to close the « claimed but untested Vite v5 » gap. The README advertises the supported Vite range as v4 → v8, but until now CI only exercised v6, v7, v8. The new app pins Vite v5.4 as the floor of the matrix. 105 classes extracted at 100 % obfuscation, no code change to the package needed.#132
8515f6bThanks @josedacosta! - Test coverage: added 39 new unit tests covering previously-uncovered modules —core/tailwind-validator.ts(was 0%),core/config.tsconfig-file loader (was 21%), andutils/logger.tsformatters / sink wiring (was 27%). Total test count rises from 432 to 471. No code change.