Overly frequent action major version updates #200765
Unanswered
MarcellPerger1
asked this question in
Actions
Replies: 1 comment
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
💬 Feature/Topic Area
Actions Checkout
Discussion Details
Major version updates to Github actions like
actions/checkout,actions/setup-node,actions/setup-pythonare IMO far too frequent, most of them semi-useless churn caused by constantly updating node versions.For example,
actions/checkouthas hadv5,v6, andv7version bumps released in the last year which seems rather excessive.And each major version update for each action requires me to go through the changelog, looks for breaking changes (which often aren't even highlighted), go through each of my projects, check that the breaking changes won't cause any problems for that project, update the version for that project.
And most of these turn out to be just trivial node version bumps which for 99% of people don't cause any problems and could either be:
No I can't just do
@latestbecause then breaking changes might break my workflows silently.All reactions