This repository has been archived by the owner on Jun 13, 2023. It is now read-only.
[ruby] Upgrade blacklight to version 7.19.1 #204
Merged
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.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ blacklight (7.19.0 → 7.19.1) · Repo
Commits
See the full diff on Github. The new version differs by 10 commits:
Release v7.19.1
Merge pull request #2459 from projectblacklight/bs5
Merge pull request #2460 from projectblacklight/polymorph-route
Symbolize the route argument to fix 'Please use symbols for polymorphic route arguments.' error introduced in Rails 6.1.3.2 security patch
Symbolize the route argument to fix 'Please use symbols for polymorphic route arguments.' error introduced in Rails 6.1.3.2 security patch
Support bootstrap 4 + 5
Merge pull request #2457 from projectblacklight/solrbuilder
Deep merge hashes from the search field parameters to allow e.g. json parameters to be sent as expected
Use a separate processor step for search field parameters
Update default_solr_parameters step to assign default values, not overwrite what's already there
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands