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.

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

[v4.2] Restrict sqlite3 gem to '~> 1.3', like ActiveRecord #5746

Merged
merged 2 commits into from
May 8, 2024

Conversation

github-actions[bot]
Copy link

@github-actions github-actions bot commented May 8, 2024

Backport

This will backport the following commits from main to v4.2:

Questions ?

Please refer to the Backport tool documentation

@github-actions github-actions bot requested a review from a team as a code owner May 8, 2024 10:40
@github-actions github-actions bot added the changelog:repository Changes to the repository not within any gem label May 8, 2024
@github-actions github-actions bot force-pushed the backport/v4.2/pr-5727 branch 2 times, most recently from 225f261 to bb5cc24 Compare May 8, 2024 10:41
@tvdeyen tvdeyen changed the title [v4.2] Restrict sqlite3 gem to '~> 1.3', like ActiveRecord [v4.2] Restrict sqlite3 gem to '~> 1.3', like ActiveRecord May 8, 2024
They just released sqlite3 2.0.0, but ActiveRecord's sqlite3 adapter
doesn't know about this yet, leading to conflicting sqlite3 gems in
specs.

This is probably a temporary fix until ActiveRecord learns the news.

(cherry picked from commit 4319e17)
The task itself is fine, as it inherits from
Rails' app generator, which has the sqlite3 restriction:
https://github.com/rails/rails/blob/main/railties/lib/rails/generators/database.rb#L19.

(cherry picked from commit e85fd4c)
@tvdeyen tvdeyen merged commit a1d1635 into v4.2 May 8, 2024
2 checks passed
@tvdeyen tvdeyen deleted the backport/v4.2/pr-5727 branch May 8, 2024 12:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog:repository Changes to the repository not within any gem
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants