Skip to content

npm is ahead of the repo: published packages are 1.0.1, repo is 1.0.0 #6

Open

Description

@arnelirobles

Current behaviour

The registry is ahead of the repo. Every packages/*/package.json is at version 1.0.0, but the published utility packages are already at 1.0.1 on npm, so the next publish from a clone fails on "you cannot publish over the previously published versions".

In-repo versions are all 1.0.0. Registry versions:

npm view nano-clsx version              # 1.0.1
npm view nano-slug version              # 1.0.1
npm view nano-safe-storage version      # 1.0.1
npm view nano-human-bytes version       # 1.0.1
npm view tiny-debounce-throttle version # 1.0.1
npm view click-outside-lite version     # 1.0.1
npm view deep-merge-lite version        # 1.0.1
npm view deep-clean-obj version         # 1.0.1
npm view resilient-fetcher version      # 1.0.1

There are no changelogs, and .changeset holds only config.json (no changeset files), so the version bump that produced 1.0.1 was published but never committed back.

Confirm:

for f in packages/*/package.json; do node -e "const p=require('./$f'); console.log(p.name, p.version)"; done
npm view nano-clsx version
ls .changeset

Why it matters

The repo no longer reflects what is published. A fresh clone that runs the release will try to publish 1.0.0 over 1.0.1 and be rejected, and there is no changelog trail of what changed in 1.0.1.

Fix shape

Commit a version sync: bump the nine published packages to 1.0.1 in-repo (or run changesets properly so the bump and changelogs land in git), and commit the changelogs.

How you know it worked

Each package.json version matches npm view <name> version.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions