Open KonnorRogers opened 10 months ago
+1
But I guess it only really makes sense for the next set of betas, since the current betas are already published as latest and would further add to the confusion.
Yea. It would be for Turbo 9+, since I'm not sure there's a way to "yank" a tag but keep the release.
It doesn't necessarily need to be Turbo 9, it could also be implemented for something like the 8.1 betas
@hotwired/turbo-rails always publishes as
--tag="latest"
, when releasing beta builds, it'd be nice if you could do:npm publish --tag="beta"
so the default NPM behavior doesn't install breaking beta versions for new applications.
https://www.npmjs.com/package/@hotwired/turbo-rails?activeTab=versions
Latest breaking build using Bun + Rails new causes an infinite recursion issue.
https://github.com/hotwired/turbo/pull/1077#issuecomment-1828057688
EDIT: feel free to close as #wontfix but figured it's worth mentioning