@style-contract/binary-win32-arm64 0.6.0 → 0.7.0

package/README.md

@@ -88,7 +88,32 @@ Supported rules:
 - `empty-rule`
 - `module-to-module-import`
 
-All enabled rules are errors except `naming-convention-global`, `dynamic-reference`, `empty-rule`, and `module-to-module-import`, which are warnings. `unused-dependent-class` is disabled by default; when enabled, it verifies that classes declared in same-element compound selectors are used together with a complete prerequisite class path in one JSX `className` expression. `empty-rule` reports selector blocks that contain only whitespace or comments; empty `:export` and structural at-rule blocks are not reported. `module-to-module-import` reports `@use`, `@forward`, and `@import` dependencies from one `.module.css` or `.module.scss` file to another. Imports from ordinary non-module stylesheets remain allowed. The warning exists because Sass merges the imported module's classes into the importing module's generated class map, which can expose unexpected classes and compound through transitive import chains.
+All enabled rules are errors except `naming-convention-global`, `dynamic-reference`, `empty-rule`, and `module-to-module-import`, which are warnings. `unused-dependent-class` is disabled by default; when enabled, it verifies that classes declared in same-element compound selectors are used together with a complete prerequisite class path in one JSX `className` expression or `clsx(...)` call. `empty-rule` reports selector blocks that contain only whitespace or comments; empty `:export` and structural at-rule blocks are not reported. `module-to-module-import` reports `@use`, `@forward`, and `@import` dependencies from one `.module.css` or `.module.scss` file to another. Imports from ordinary non-module stylesheets remain allowed. The warning exists because Sass merges the imported module's classes into the importing module's generated class map, which can expose unexpected classes and compound through transitive import chains.
+
+### Targeted suppressions
+
+When a deliberate abstraction cannot be followed statically, use a targeted suppression comment. Directives work in TypeScript, CSS, and SCSS and accept canonical rule names separated by spaces or commas. Omit the rules to suppress every rule.
+
+```scss
+/* @sc-ignore unused-dependent-class */
+&.highlighted { color: yellow; }
+```
+
+```ts
+// @sc-ignore dynamic-reference
+return styles[name];
+```
+
+`@sc-ignore` applies to the next physical line. Use a nested block when several lines need the same suppression:
+
+```scss
+/* @sc-ignore-start unused-dependent-class */
+.root.active { color: red; }
+.root.selected { color: blue; }
+/* @sc-ignore-end */
+```
+
+Blocks apply after the start marker through the line before the matching end marker. End markers close the nearest open block. Invalid rule names and unmatched markers are errors. Suppressing `unused-dependent-class` on a declaration makes that declaration participate in usage analysis and navigation as an ordinary class.
 
 Previous `no-*` rule IDs remain accepted as configuration aliases, and the legacy `naming-convention` override remains available as an alias for both convention rules. For example:
 
@@ -124,5 +149,5 @@ cargo build --release
 
 Releases are published from version tags. Before the first release, create or claim the `@style-contract` organization on npm, grant the publisher access to it, and add an npm automation token to the GitHub repository as the `NPM_TOKEN` Actions secret.
 
-Keep the version in `package.json`, `Cargo.toml`, `Cargo.lock`, and every platform package dependency identical. The release verifier enforces this. Push a tag matching that version, such as `v0.6.0`; the release workflow builds and publishes all eight platform packages before publishing `style-contract`.
+Keep the version in `package.json`, `Cargo.toml`, `Cargo.lock`, and every platform package dependency identical. The release verifier enforces this. Push a tag matching that version, such as `v0.7.0`; the release workflow builds and publishes all eight platform packages before publishing `style-contract`.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@style-contract/binary-win32-arm64",
-  "version": "0.6.0",
+  "version": "0.7.0",
   "description": "Precompiled StyleContract binary for win32/arm64",
   "repository": {
     "type": "git",