Repository navigation
v0.4.2 — all Dependabot alerts cleared, provenance-signed unattended releases
All seven packages are published at 0.4.2, and this is the first release
where every artifact carries SLSA provenance —
built and published by GitHub Actions with no credential in the loop.
🔒 Security: all 24 Dependabot alerts cleared
npm audit now reports 0 vulnerabilities at any severity, and all
Dependabot alerts on the repository are closed as fixed. Every alert was
reached through package-lock.json; none of them were in shipped code paths.
Transitive, no declared range touched — npm audit fix resolved these:
next 16.2.10 → 16.3.0 (9 alerts), postcss → 8.5.26 (4), sharp
0.34.5 → 0.35.3, plus js-yaml, fast-uri, nanoid and brace-expansion.
Angular needed a major bump. All five Angular advisories were scoped
<= 19.2.25 with no patched version declared — 19.2.25 is the last 19.x
release, so the fixes exist only in later majors and staying on 19 meant
staying vulnerable. The Angular adapter's devDependencies moved to
Angular 20.3, the smallest bump that clears them (pulling TypeScript
5.7 → 5.8, since compiler-cli peers >=5.8 <6.0, and jest-preset-angular
14.5 → 14.6, the last line supporting Angular 20 on jest 29).
Consumers are unaffected.
@opentagcloud/angularstill declares
peerDependencies: { "@angular/core": ">=17.0.0" }— Angular is only this
repo's build and test toolchain, not something the package imposes on you.
A subtlety worth recording: the root overrides block is load-bearing, not
decoration. npm fills a root peer slot for the adapter's >=17.0.0
independently of its devDependencies and had chosen 19.2.25 — leaving the
flagged version at the tree root while the workspace itself used 20.3.27
nested below. Dependabot scans the root, so without that pin the alerts would
have survived an otherwise-successful upgrade.
SvelteKit removed, which retired the last advisory. The final three alerts
were a single advisory (cookie < 0.7.0) reached only via @sveltejs/kit,
whose current release still depends on cookie ^0.6.0 — there was no version
to upgrade to. It turned out nothing used SvelteKit: no source file imported
@sveltejs/kit, $app/* or $env/*. The published package is built by
svelte-package from src/lib, the Pages site by scripts/build-pages.mjs,
and the Playwright suite serves its own fixtures. SvelteKit existed solely to
serve a one-page demo, which is now a plain Vite app — so a framework with a
server, router, SSR and prerendering left the tree along with the advisory.
🚀 Releases are now unattended, with provenance
Publishing used to mean relaying a dozen short-lived npm 2FA links. A release
is now a tag push:
git tag v0.4.3 && git push origin v0.4.3.github/workflows/release.yml runs the full verify pipeline (lint → build →
svelte-check → unit tests → Playwright) and publishes all seven packages in
dependency order, authenticating via npm trusted publishing (OIDC) — no
token stored anywhere, and provenance attestations
are generated automatically. Requires npm ≥ 11.5.1, so the workflow runs
Node 24 (Node 22 still bundles npm 10.9.x).
📖 Docs
The README's Releasing section was rewritten to cover trusted publishing, token
auth, and local publishing.
Looking for the font-legibility fix, the framework-first examples site, or the
npm installinstructions? Those shipped in
v0.4.1.
Install
npm install opentagcloud # Svelte 5 + vanilla mount() + <otc-tag-cloud>
npm install @opentagcloud/react # or /vue, /angular, /solid, /next, /coreFull changelog: v0.4.1...v0.4.2