Manually bump tapioca / regenerate rbi #1514
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Dependabot does not do this because it resolves with Ruby 3.0 from the gemspec and tapioca now only supports 3.1 This unblocks prism 1.0 which is required for the ruby-lsp to update to the latest version. Currently it runs into Shopify/ruby-lsp#2630, causing a restart loop. To make sure this does the right thing on older rubies, I added a step to print the resolved lockfile on CI
|
Thanks for noticing that! |
|
It was quite hard not to, the persistent notifications from my IDE about this were quite noticable. I think this dependabot issue is about cases like this: dependabot/dependabot-core#4987, though the situation is a bit different with the lockfile being used for both library and application (the demo). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dependabot does not do this because it resolves with Ruby 3.0 from the gemspec and tapioca now only supports 3.1
This unblocks prism 1.0 which is required for the ruby-lsp to update to the latest version. Currently it runs into Shopify/ruby-lsp#2630, causing a restart loop.
To make sure this does the right thing on older rubies, I added a step to print the resolved lockfile on CI