Latest version of @storybook/addons is not tagged with ”latest”, but with ”tag-for-publishing-older-releases”

[marek-saji]

Summary

Last version tagged with latest is 7.6.17 while currently highest version without any version suffixes in 7.6.20. This one is tagged with tag-for-publishing-older-releases.

https://www.npmjs.com/package/@storybook/addons?activeTab=versions
https://yarnpkg.com/package?q=%40storybook%2Faddons&name=%40storybook%2Faddons

• If >7.6.17 are not stable, shouldn’t they have a version suffix?
• If they are stable, shouldn’t they be tagged with latest? It’s confusing that tag-for-publishing-older-releases tags versions newer than latest.

Additional information

No response

Create a reproduction

No response

[JReinhold]

you are correct, 7.6.20 should be tagged with latest. It's a fault in our tagging logic that it isn't. The general problem is that when we do patches to older majors/minors, we can't tag them with latest, because there is already a higher minor that should be latest. eg. if we release v7.7.7 but 8.1.0 already exists, we don't want to tag v7.7.7 with latest, just because it was released more recently than 8.1.0.

It's a unique problem with @storybook/addons, because we stopped publishing that package in Storybook 8, so it should have gotten the latest tag.