Restore Puma & SQLite dependency to correct state#6082
Restore Puma & SQLite dependency to correct state#6082tvdeyen merged 2 commits intosolidusio:mainfrom
Conversation
The issue with capybara that originally caused the change to the main branch of the puma repo has been fixed and solidus should return on the Puma release cycle.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6082 +/- ##
==========================================
+ Coverage 89.33% 89.58% +0.24%
==========================================
Files 730 801 +71
Lines 16462 18275 +1813
==========================================
+ Hits 14706 16371 +1665
- Misses 1756 1904 +148 ☔ View full report in Codecov by Sentry. |
It would be great if you 4 adhere to same standard that you ask from my two guys and document things properly. |
…recent versions Not required anymore. solidusio#5727
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
💔 Some backports could not be created
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
💔 Some backports could not be created
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
Summary
Fixes two dependency pinnings:
Due to changes in Puma Capybara failed. The solution was to pin Puma to the development branch. Given that the issue has been resolved, I restored the gemfile to a stable puma release.
original reason to pin sqlite:
Issue has been solved in the meantime.
Fixes #6081
Checklist
Check out our PR guidelines for more details.
The following are mandatory for all PRs:
The following are not always needed: