Replies: 4 comments
-
I am experiencing the exact same issue at our organization. Every tags is always tagged as |
Beta Was this translation helpful? Give feedback.
-
Indeed, I've seen the same behavior. I noticed the announcement of the v2 of the npm registry perhaps this is related, I'm not sure. |
Beta Was this translation helpful? Give feedback.
-
Same for our organization. Even caused a small disruption when an incorrect version was used in production. |
Beta Was this translation helpful? Give feedback.
-
In case this helps someone else - I had an error that looked similar to this. I was publishing with However when I did a May not be the same problem, but then maybe someone will come across this thread who did have the same issue I did and this may help them. |
Beta Was this translation helpful? Give feedback.
-
An integration pipeline I used would tag a canary release every so often
npm publish --tag canary
for example. However starting yesterday it seems github "tags" all packages aslatest
and the--tag
flag is ignored?Looking through the recent changes from github it seems there was an update to the security around npm publish, could this be affecting it?
Beta Was this translation helpful? Give feedback.
All reactions