[RELEASE] 13.1.2#4665
Merged
Merged
Conversation
This is a bugfix release for TYPO3 13 LTS, primarily restoring Solr write functionality after a regression introduced by an upstream PSR-7 library update. Highlights since 13.1.1: * [BUGFIX] Pin `guzzlehttp/psr7` to `<2.10.0` — `guzzlehttp/psr7` 2.10.0 changed `Utils::modifyRequest()` to mutate the original `RequestInterface` via `withHeader()` instead of rebuilding a Guzzle `Request`. Combined with Guzzle's `PrepareBodyMiddleware` passing `Content-Length` as an `int`, this broke all Solr write requests through Solarium's `Psr18Adapter` in spec-compliant PSR-7 implementations like `TYPO3\CMS\Core\Http\Message` (TYPO3-Solr#4660 / @dkd-kaehm) * [BUGFIX] Prevent c:0 variant and content leakage on fe_group-restricted pages (TYPO3-Solr#4641 / @dkd-kaehm) * Plus 10 additional bugfixes and maintenance updates — see release notes for details. Please read the release notes: * https://docs.typo3.org/p/apache-solr-for-typo3/solr/13.1/en-us/Releases/solr-release-13-1.html * https://github.com/TYPO3-Solr/ext-solr/releases/tag/13.1.2 --- How to Get Involved There are many ways to get involved with Apache Solr for TYPO3: * Submit bug reports and feature requests on GitHub * Ask or help or answer questions in our Slack channel * Provide patches through pull requests or review and comment on existing pull requests * Go to www.typo3-solr.com or call dkd to sponsor the ongoing development of Apache Solr for TYPO3 Support us by becoming an EB partner: https://shop.dkd.de/Produkte/Apache-Solr-fuer-TYPO3/ or call: +49 (0)69 - 2475218 0 Relates: TYPO3-Solr#4660
This file contains hidden or 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
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.
This is a bugfix release for TYPO3 13 LTS, primarily restoring Solr write functionality after a regression introduced by an upstream PSR-7 library update.
Highlights since 13.1.1:
guzzlehttp/psr7to<2.10.0—guzzlehttp/psr72.10.0 changedUtils::modifyRequest()to mutate the originalRequestInterfaceviawithHeader()instead of rebuilding a GuzzleRequest. Combined with Guzzle'sPrepareBodyMiddlewarepassingContent-Lengthas anint, this broke all Solr write requests through Solarium'sPsr18Adapterin spec-compliant PSR-7 implementations likeTYPO3\CMS\Core\Http\Message([BUG] Solr writes fail with "Invalid header value for Content-Length" after guzzlehttp/psr7 2.10.0 #4660 / @dkd-kaehm)Please read the release notes:
How to Get Involved
There are many ways to get involved with Apache Solr for TYPO3:
Support us by becoming an EB partner:
https://shop.dkd.de/Produkte/Apache-Solr-fuer-TYPO3/
or call:
+49 (0)69 - 2475218 0
Relates: #4660