We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When publishing an RC release, CI npm publishing tags the rc release as latest when it should only tag it with the version.
latest
Solution: Remove the latest tag push from CI for RC releases, but maintain the version publishing.
See .github/workflows/release.yml
.github/workflows/release.yml
- name: Release on NPM @latest if: env.TEST_RUN != 'true' run: npm publish --tag latest --access public
Helpful: if: steps.is-full-release.outputs.is-full-release != 'true'
if: steps.is-full-release.outputs.is-full-release != 'true'
The text was updated successfully, but these errors were encountered:
Only publish the npm package api-augment to latest on full releases (#…
8f328ec
…1777) # Goal The goal of this PR is to update CI publishing of Api-Augment on RC releases. Closes #1776
728beab
wilwade
Successfully merging a pull request may close this issue.
When publishing an RC release, CI npm publishing tags the rc release as
latestwhen it should only tag it with the version.Solution: Remove the latest tag push from CI for RC releases, but maintain the version publishing.
See
.github/workflows/release.ymlHelpful:
if: steps.is-full-release.outputs.is-full-release != 'true'The text was updated successfully, but these errors were encountered: