-
-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v2
not up to date
#95
Comments
I'll add to this: this repo does not have any major or minor tags, only full version tags. This is not the recommended way to handle these. Major Versions and minor versions should be tagged and have that tag move to the latest applicable tagged release along with the full major.minor.patch versions. So now, with This can't be done in a PR, it has to be done by someone with write permissions on the repo. |
The branch / tag situation has improved, however the v2 branch is at the v2.3.0 release level and does not contain the latest release v2.4.0.
It looks like releases are handled in a manual way. You might like to consider automating releases so that branches and tags are automatically updated. Using https://github.com/cycjimmy/semantic-release-action is one way to do this. |
I am sorry. I have merged |
Many thanks for correcting this! 👍🏻 Would you like to check? It looks like this issue can be closed now. |
Still the case for both I can help if possible.
|
This PR upgrades the `pnpm/action-setup` GitHub Action to v4.0.0. Trying to see if I can fix the Renovate warning stemming from pnpm/action-setup#95. Release Notes: - N/A
The
v2
ref is not pointing to the latest release, which does not contain the lateststandalone
config documented in the README: https://github.com/pnpm/action-setup/tree/v2The text was updated successfully, but these errors were encountered: