-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(manager/gleam): enable update-lockfile #31002
feat(manager/gleam): enable update-lockfile #31002
Conversation
f7c20f2
to
2611eda
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it seems there is a command merged upstream and this PR now needs an update too.
Yes! Great news, Gleam v1.6.0 landed this feature as a result of gleam-lang/gleam#3602. Gleam v1.6.1 (released today) includes a hotfix that stabilizes this new feature - so we should be good to proceed! I have a staged changeset on my development branch that I will test tonight. If everything looks good, I'll update this PR and ping it for a fresh review. |
2611eda
to
c71a474
Compare
I never know when to trust GH's notifications! Forgive me if this is already in your queue @viceice |
I'm wondering if there's something wrong with this PR, or if everyone is just very busy this time of year? If something is not up to standards, please let me know so I can address it. 🚀 |
🎉 This PR is included in version 39.53.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ups, forgot to send my review
Thanks everyone for your help on this PR, and for your patience. It was a long journey, but we made it! Super eager to get this out into the wild! 🚀 |
Changes
Enables lockfile updates
This should not be merged until #31000 is accepted.#31000 has been merged, we can proceed with this PR.
Context
Supersedes #30811
The Gleam manager does not allow
rangeStrategy=update-lockfile
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: