Skip to content
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.

Sign up for GitHub

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

Jump to bottom

No outdated packages found #13

Open
do-you-dare opened this issue Feb 7, 2022 · 0 comments
Open

No outdated packages found #13

do-you-dare opened this issue Feb 7, 2022 · 0 comments

Comments

@do-you-dare
Copy link
Contributor

After updating a project to ruby 3.1 and trying to run gisdatigo, it didn't update any gems nor printed any gems that failed to be updated. Som of the latest versions of bundler seems to have started using the pretty columns output for outdated gems as default (see rubygems/bundler#4474). Using bundle outdated --parseable seems to be a viable solution here.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@do-you-dare