@changesets/should-skip-package versions and release history

Inspect a published release before upgrading or adding a dependency. Each version reference keeps its metadata and provider measurements pinned to that exact npm version.

Published versions14
Stable versions4
Prereleases10
Releases published in the last 90 days2
Deprecated releases0
Latest npm dist-tag1.0.0

All available releases

VersionPublishedRuntime dependenciesTypesStatus
1.0.02026-08-11T12:11:15.660Z1Not declaredlatest
1.0.0-next.92026-08-03T13:45:23.355Z1Not declarednext
1.0.0-next.82026-07-25T08:10:40.579Z1Not declared
1.0.0-next.72026-07-17T12:03:23.746Z1Not declared
1.0.0-next.62026-07-01T07:58:27.717Z1Not declared
1.0.0-next.52026-05-28T11:32:37.294Z1Not declared
1.0.0-next.42026-05-13T16:27:37.860Z1Not declared
1.0.0-next.32026-05-07T14:36:32.300Z1Not declared
1.0.0-next.22026-05-04T06:50:46.655Z1Not declared
1.0.0-next.12025-10-30T13:15:04.251Z2Not declared
1.0.0-next.02025-04-21T12:26:02.435Z2Not declared
0.1.22025-02-17T10:25:35.957Z2Bundled
0.1.12024-09-04T10:25:06.632Z2Bundled
0.1.02024-05-28T12:37:43.381Z3Bundled

Choosing a version

The latest tag is selected by the publisher and is not a guarantee of compatibility. Prerelease and deprecated status remain visible. Check your Node.js range and peer requirements on the exact version page, then review the maintainer’s release notes before upgrading.

Removed or unpublished versions may be absent. Historical download charts cover all package versions and do not show adoption of an individual release.

npm release-history source — retrieved 2026-10-29T07:59:57.990Z