`Changesets` force-published local version without consent

[ShookLyngs]

When the #157 was merged, the version of the rgbpp package was 0.1.0 locally. It was not intended to be published on NPM, but when I tried to publish a snap version of it, the changesets thought that it was an unpublished local version and force-published it anyway.

Here's the command log:

rgbpp-sdk % changeset publish --snapshot --tag snap
🦋  warn ===============================IMPORTANT!===============================
🦋  warn Packages will be released under the snap tag
🦋  warn ----------------------------------------------------------------------
🦋  info npm info @rgbpp-sdk/btc
🦋  info npm info @rgbpp-sdk/ckb
🦋  info npm info rgbpp
🦋  info npm info @rgbpp-sdk/service
🦋  warn Received 404 for npm info "rgbpp"
🦋  warn @rgbpp-sdk/btc is not being published because version 0.1.0 is already published on npm
🦋  warn @rgbpp-sdk/ckb is not being published because version 0.1.0 is already published on npm
🦋  info rgbpp is being published because our local version (0.1.0) has not been published on npm
🦋  warn @rgbpp-sdk/service is not being published because version 0.1.0 is already published on npm
🦋  info Publishing "rgbpp" at "0.1.0"
🦋  success packages published successfully:
🦋  rgbpp@0.1.0
🦋  Creating git tag...
🦋  New tag:  rgbpp@0.1.0