v2.0.1

2.0.1 — Do not re-ingest the output destination

Fixed: previously generated artifacts are no longer used as source shapes

• On repeated runs with a recursive input glob, the CLI used to pick up its
  own previously generated sprites and stylesheets from the configured
  destination directory and process them as source shapes, producing shapes
  with identifiers derived from the output path (e.g. assets--OUT--stack-- svg--sprite). The destination tree (and the mode-specific output
  directories when the destination is the current directory) is now filtered
  out of the glob results.

v2.0.0

Breaking change — scoped package name

The CLI is now published as @svgforge/svgforge-cli (npm and GitHub Packages). The old unscoped svgforge-cli package on npm is deprecated and receives no more updates.

Migration from 1.x

Existing installs must switch manually:

npm uninstall --global svgforge-cli
npm install --global @svgforge/svgforge-cli@2.0.0

The CLI now depends on the scoped @svgforge/svgforge library (also renamed). The svgforge command itself stays unchanged.

---

What's Changed

• Feature/scoped package names by @joeda1 in #10

Full Changelog: v1.1.0...v2.0.0

v1.1.0

What's Changed

• ci: create GitHub release on publish by @joeda1 in #6
• chore: CLI 1.1.0 — bump to svgforge 1.1.0, GH_TOKEN fix by @joeda1 in #7
• chore: exclude svgforge 1.1.0 from the minimum release age policy by @joeda1 in #8
• chore: drop dev-only link override from the committed workspace by @joeda1 in #9

Full Changelog: v1.0.1...v1.1.0

v1.0.1

• Bump the svgforge dependency to ^1.0.1 (native promise-based helpers,
  deepMerge and escapeHtml utilities, no async/lodash dependencies)