Skip to content

Conversation

@f-f
Copy link
Member

@f-f f-f commented Jan 27, 2026

Fixes the release script, the CI (well, hopefully) and docs so that we are ready for Friday's release.

git tag "${NEW_TAG}"
# npm version:
# 1. Updates package.json
# 2. Runs the "version" script (syncs version to spago.yaml files)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this guaranteed not to use a v prefix? Otherwise it looks like the scripts could get into a mismatch with a v prefixed version number and a non-prefixed one. Should we add --tag-version-prefix "" so the tag format is explicitly just numeric, regardless of what the npm config setting is where this is run?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking about it because I think npm defaults to v being included when you use npm version, for example the genesis of this thread:
https://stackoverflow.com/questions/37788907/have-npm-version-not-prepend-v-to-the-git-tag

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, great catch!! I completely forgot about this.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants