@trackunit/migrations 0.2.39-alpha-a3b7922eaab.0 → 0.2.39

package/CHANGELOG.md

@@ -1,3 +1,7 @@
+## 0.2.39 (2026-08-07)
+
+This was a version bump only for migrations to align it with other projects, there were no code changes.
+
 ## 0.2.38 (2026-08-06)
 
 This was a version bump only for migrations to align it with other projects, there were no code changes.

package/README.md

@@ -69,6 +69,10 @@ flowchart LR
   rccMig --> pending
 ```
 
+## Writing classname-aware migrations
+
+If a migration needs to detect or rewrite Tailwind/classname strings in source files (e.g. renaming or removing a utility class), don't reimplement detection logic — import `@trackunit/css-classname-utils` (`libs/css/classname-utils`) directly. It has no `eslint`/`@typescript-eslint/utils` runtime dependency, so it's safe to use outside an ESLint rule context, and it's already the basis for the equivalent ESLint rules in `plugin-trackunit`. See the ["Shared classname utilities" section](../../docs/tech/TAILWIND-ARCHITECTURE.md#shared-classname-utilities) of the Tailwind architecture doc for what it exposes, notably `replaceClassToken()` for word-boundary-safe token replace/remove.
+
 ## Usage
 
 ### Step 1: Discover and collect migrations

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trackunit/migrations",
-  "version": "0.2.39-alpha-a3b7922eaab.0",
+  "version": "0.2.39",
   "repository": "https://github.com/Trackunit/manager",
   "license": "SEE LICENSE IN LICENSE.txt",
   "engines": {