what stackpulse tracks
pnpm releases from GitHub
StackPulse watches pnpm release notes and keeps the original source link close to every summary.
Fast, disk space efficient package manager StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches pnpm release notes and keeps the original source link close to every summary.
upgrade risk
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Migration steps and recommended actions are only shown when the upstream release notes support them.
This release stores registries, accounts, and tokens in the database, enabling replicas to share registry configuration and administrators to manage it without a config deploy. It restricts publishing to package owners and admins by default, adds 90-day default token expiry, and includes security fixes for web login links and private upstream credentials. Upgrading from alpha.19 requires a fresh store and database; existing data is not migrated, and many configuration keys and commands have changed or been removed.
Operators upgrading from alpha.19 must rebuild state and adapt configuration, while registry administrators, package publishers, and token users are affected by the new database-backed management and access defaults.
Before upgrading, back up the hosted store and databases, prepare an empty store and database, and follow the alpha.19 migration and configuration-renaming steps in the release notes.
This release adds PostgreSQL and MySQL metadata storage, deduplicates identical hosted archives, and introduces `pnpr gc` to reclaim unreferenced archives while the registry remains available. It also includes a URL-credential logging fix and changes authentication, account, team, publishing, and registry behavior. Alpha.18 data is not migrated, and the release notes describe substantial upgrade steps.
Operators upgrading from alpha.18 must plan a database and storage transition and may need to recreate accounts, tokens, and published packages; registry users are also affected by stricter authentication and publishing validation.
Before upgrading, back up the alpha.18 databases and follow the release's upgrade steps, including configuring fresh storage and replacing the old database configuration.
This prerelease changes package and hosted-storage layouts, removes legacy commands, flag aliases, environment variables, and snake_case configuration keys, and updates batch-publish endpoints. It fixes two security issues, improves libsql/Turso authentication database reliability, and includes publishing, installation, and authentication fixes.
pnpr operators must account for the incompatible storage layout, removed commands and aliases, camelCase configuration, and changed batch-publish endpoint; users of libsql or Turso auth databases and metrics endpoints also see relevant fixes and behavior changes.
Before upgrading, republish packages into an empty store and update configuration, TTL settings, and batch-publish clients as described in the release notes.
pnpr 0.1.0-alpha.16 introduces significant changes to storage layout and configuration validation, replacing deprecated fields with `artifacts.orgs` and requiring migration of existing stores. New features include ecosystem-specific URL prefixes, tar registries, npm audit endpoints, and Prometheus metrics.
Users of pnpr with existing storage layouts or configurations using deprecated fields will need to migrate to the new layout and update their configurations.
Back up existing stores and run `pnpr upgrade-storage` to migrate to the new layout, and update configurations to use the new `artifacts.orgs` and `registries` settings.