-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
Support updating libraries to the latest version #376
Comments
I was thinking if maybe |
I'm not sure that "bump" conveys the meaning in all languages/cultures -- I think "update" is clear and simple (even tho' I would never use this feature). |
I wouldn't use this either - not often at least - I do check release notes and change logs for breaking changes and run the tests after each library update (or a couple if they are small). |
@tengstrand hi! Just tried this out and it's a real timesaver for a mid-to-big workspace. Thanks a lot! 🙏 Still, it was not able to update the (root) development project |
Thanks for reporting this @marksto. Happy to hear that you like it, except for the bug of course! I'm working on a fix already and will post here when it's done. |
Issue #376 * Set :latest-version in :lib-deps for outdated libraries. * Fixed issues in 'libs :update' + support subset of libraries to be updated.
I have pushed a fix to Now it's possible to update a subset of libraries, by giving the If executed from a shell, then outdated libraries will be suggested when giving If you want to experiment with this feature from the shell, e.g. by changing a library to an older version, then you need to execute |
Today we can execute
poly libs :outdated
to show outdated libraries, e.g.:This is helpful, but the tool doesn't update the files for us. That we have to do manually.
Here we suggest that
poly libs :update
should update all the libraries to the latest version in alldeps.edn
files. This can be implemented by using theantq.api/upgrade-deps!
function.It should be possible to leave the library version for bricks and projects untouched, by adding a
:keep-lib-versions
key to:bricks
or:projects
inworkspace.edn
:The text was updated successfully, but these errors were encountered: