Repository navigation
The server is unchanged — nothing under src/ differs from 0.2.2. This release exists to get the corrected description onto the npm page, which renders it from the published tarball rather than from the repository.
Changed
- The one-line description now mentions restoring. It previously listed classify, archive, and compact, so a reader of the npm page or repository header could not tell the server can undo an archive.
md_restore_fileshas existed since 0.2.0.
Internal
- Trusted publishing works.
registry-urlonactions/setup-nodewas writing an.npmrccontaining_authToken=${NODE_AUTH_TOKEN}; with no token configured, npm read that empty value as configured credentials and never attempted the OIDC exchange. See actions/setup-node#1551. - The publish workflow now checks out the release tag explicitly, so a provenance attestation always points at the commit the release claims to ship rather than at a branch head.
- Added a diagnostics step to the publish workflow. npm reports every trusted-publishing misconfiguration as a
404orENEEDAUTH, indistinguishable from a missing package or a forgotten login (npm/cli#9088).
Full changelog: v0.2.2...v0.2.3