releaselisted

# Release Gerillass The repository and the npm package are separate things. Fixing `main` changes nothing for anyone using the library — the fix reaches users only when a new version is published. Never stop at the git tag. Take the target version from the user. If they did not name one, propose one and confirm before touching anything: - **patch** for dependency, security and bugfix work. This is what almost every release here has been, including dependency restructuring (see 1.2.6, 1.3.3). - **minor** for a new mixin or function. - `2.0.0` is **reserved** for the `@use`/`@forward` module migration. Do not spend it on anything else. ## 1. Verify the tree before anything else ```bash npm test # must pass: specs, smoke test and the manifest suite yarn audit # must be zero across all severities node tools/audit.js # the SILENT bucket must be empty node tools/check-docs.js # the docs must not claim a count the repo lacks node tools/check-wiki.js # names what the wiki page has to cover git status --short # know exactly what is going out ``` The library must no longer trip the two deprecations the module migration was about. This must print nothing: ```bash npx sass --load-path=scss test/smoke.scss 2>&1 >/dev/null | grep -E 'DEPRECATION.*(import|global-builtin)' ``` A plain `grep DEPRECATION` will still find something, and that is expected: Sass is deprecating its own `if()`, which the library calls in 21 place