You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when release-please publishes to npm, it moves the "latest" tag along with it. We should consider still doing the publish, but not moving the "latest" tag automatically. This gives us the opportunity to test the production pacakage without risking breaking production runs of telemetry against real projects.
The text was updated successfully, but these errors were encountered:
mattrosno
changed the title
consider release-please deploys not moving the "latest" tag on npm
Consider release-please deploys not moving the "latest" tag on npm
May 15, 2024
Summary
Currently, when release-please publishes to npm, it moves the "latest" tag along with it. We should consider still doing the publish, but not moving the "latest" tag automatically. This gives us the opportunity to test the production pacakage without risking breaking production runs of telemetry against real projects.
The text was updated successfully, but these errors were encountered: