NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist
Packagist, #2522 most downloaded on Packagist
Interceptors for PHP's native phar:// stream handling
Latest stable
v4.0.0
Last release 2 years ago
no release in 18 months
Ships unpredictably
gaps range from 8 days to 3.2 years
Most releases are documented
notes for 21 of 27 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
27 releases · first in 2018
Drag across the ruler to compare, or tap a release to open it.
Breaking changes to the interfaces \TYPO3\PharStreamWrapper\Collectable and \TYPO3\PharStreamWrapper\Resolvable are described in PR https://github.com…
This is a maintenance release, supporting the PHP version range v7.1 - v8.4. The support for PHP v7.0 was dropped in favor of having ?nullables for PHP 8.4 compatibility.
Breaking changes to the interfaces \TYPO3\PharStreamWrapper\Collectable and \TYPO3\PharStreamWrapper\Resolvable are described in PR https://github.com/TYPO3/phar-stream-wrapper/pull/78.
Full Changelog: https://github.com/TYPO3/phar-stream-wrapper/compare/v3.1.8...v4.0.0
This is a maintenance release, supporting the PHP version range v7.1 - v8.4. The support for PHP v7.0 was dropped in favor of having ?nullables for PHP 8.4 compatibility.
Breaking changes to the interfaces \TYPO3\PharStreamWrapper\Collectable and \TYPO3\PharStreamWrapper\Resolvable are described in PR #78.
Full Changelog: v3.1.8...v4.0.0
Your coding agent can read these notes before it upgrades. Set up the MCP server →
This is a maintenance release, supporting the PHP version range v7.0 - v8.3.
This is a maintenance release, supporting the PHP version range v7.0 - v8.3.
Full Changelog: https://github.com/TYPO3/phar-stream-wrapper/compare/v3.1.7...v3.1.8
This is a maintenance release, supporting the PHP version range v7.0 - v8.3.
Full Changelog: v3.1.7...v3.1.8
#68: Stop processing when reading from stream via fgets fails
#68: Stop processing when reading from stream via fgets fails
PHP versions 8.0-RC1, 7.4.12, 7.3.24 introduced a different behavior for stream_wrapper_restore() and would throw a PHP notice which is mitigated with
PHP versions 8.0-RC1, 7.4.12, 7.3.24 introduced a different behavior for stream_wrapper_restore() and would throw a PHP notice which is mitigated with this phar stream wrapper release. Besides that, test cases are now executed via symfony/phpunit-bridge instead of phpunit/phpunit.
Nothing published for this version
Nothing published for this version
## Resolved Issues * #49: Ensure PHP 7.4 compatibility
## Resolved Issues * #34: Normalize resolved Windows path to Unix-style * #42: Avoid analysing non-phar files on alias resolving * #40: Add Windows te
ext-fileinfo)Releases v3.1.1 and v.2.1.1 aim to overcome drawbacks in Phar's alias resolving from Phar stub as well as solving performance aspects.
Releases v3.1.1 and v.2.1.1 aim to overcome drawbacks in Phar's alias resolving from Phar stub as well as solving performance aspects.
Releases v3.1.0 and v.2.1.0 aim to overcome drawbacks in Phar's alias resolving (either by Phar archives using Phar::setAlias() in meta-data or Phar::
Releases v3.1.0 and v.2.1.0 aim to overcome drawbacks in Phar's alias resolving (either by Phar archives using Phar::setAlias() in meta-data or Phar::mapPhar() in stub code).
Merged pull-requests
In case custom Assertable interceptors have been used, path resolving has to be adjusted in order to make use of alias resolving features.
$baseFile = Helper::determineBaseFile($path);
$invocation = Manager::instance()->resolve($path);
$baseName = $invocation->getBaseName(); // previously called $baseFile
There have been reports about flaws using stream_select() and according stream_cast() in PharStreamWrapper. Since it was not possible to reproduce the behavior in an isolated scenario and specific platform requiresments were not clear, these aspects have not been covered by these releses - see #8 and #19 for details.
Phar\Reader for stub & meta-data (incl. alias) and their model representationsResolver\PharInvocationResolver in order to resolve/handle alias namesInterceptor\ConjunctionInterceptor for combining multiple interceptorsInterceptor\PharMetaDataInterceptor for actually testing against insecure deserialization in meta-data of Phar archivessee https://github.com/TYPO3/phar-stream-wrapper/wiki/TYPO3-PSA-2018-001
see https://github.com/TYPO3/phar-stream-wrapper/wiki/TYPO3-PSA-2018-001
Basically no functional differences to v1.0.1 release. Since PHP 5.3 compatibility has been merged into this repository, the new v2 branch will be use
Basically no functional differences to v1.0.1 release. Since PHP 5.3 compatibility has been merged into this repository, the new v2 branch will be used for PHP 5.3 related sources and master still requires PHP 7.0. That's why v1.0.1 is re-released now as v3.0.0.
#68: Stop processing when reading from stream via fgets fails
#68: Stop processing when reading from stream via fgets fails
Albeit the v2 branch of typo3/phar-stream-wrapper is dedicated to PHP5, it seems to be used with PHP7 as well.
Albeit the v2 branch of typo3/phar-stream-wrapper is dedicated to PHP5, it seems to be used with PHP7 as well.
PHP versions 7.4.12, 7.3.24 introduced a different behavior for stream_wrapper_restore() and would throw a PHP notice which is mitigated with this phar stream wrapper release.
Nested serialized structures have not been handled correctly in https://github.com/dbrumann/polyfill-unserialize, which has been fixed in version 2.0.
Nested serialized structures have not been handled correctly in https://github.com/dbrumann/polyfill-unserialize, which has been fixed in version 2.0.0. It's still possible to use version ^1.0 of the polyfill explicitly in projects - otherwise new ^2.0 will be used.
Nothing published for this version
Nothing published for this version
Branch v2 is not considered to be dramatically changed in order to be compatible with future PHP versions anymore. Albeit this branch now should be wo
Branch v2 is not considered to be dramatically changed in order to be compatible with future PHP versions anymore. Albeit this branch now should be working for PHP 5.3, 5.4, 5.5, 5.6, 7.0, 7.1, 7.2, 7.3 and 7.4 we'd like to encourage projects to switch to the master branch and v3.1.3 or any later version - which is considered to be adjusted for future PHP versions as well.
tl;dr: No guarantee v2 branch will be maintained for upcoming PHP 7.4.x and PHP 8 versions
## Resolved Issues * #34: Normalize resolved Windows path to Unix-style * #42: Avoid analysing non-phar files on alias resolving * #40: Add Windows te
ext-fileinfo)Releases v3.1.1 and v.2.1.1 aim to overcome drawbacks in Phar's alias resolving from Phar stub as well as solving performance aspects.
Releases v3.1.1 and v.2.1.1 aim to overcome drawbacks in Phar's alias resolving from Phar stub as well as solving performance aspects.
Releases v3.1.0 and v.2.1.0 aim to overcome drawbacks in Phar's alias resolving (either by Phar archives using Phar::setAlias() in meta-data or Phar::
Releases v3.1.0 and v.2.1.0 aim to overcome drawbacks in Phar's alias resolving (either by Phar archives using Phar::setAlias() in meta-data or Phar::mapPhar() in stub code).
Merged pull-requests
In case custom Assertable interceptors have been used, path resolving has to be adjusted in order to make use of alias resolving features.
$baseFile = Helper::determineBaseFile($path);
$invocation = Manager::instance()->resolve($path);
$baseName = $invocation->getBaseName(); // previously called $baseFile
There have been reports about flaws using stream_select() and according stream_cast() in PharStreamWrapper. Since it was not possible to reproduce the behavior in an isolated scenario and specific platform requiresments were not clear, these aspects have not been covered by these releses - see #8 and #19 for details.
Phar\Reader for stub & meta-data (incl. alias) and their model representationsResolver\PharInvocationResolver in order to resolve/handle alias namesInterceptor\ConjunctionInterceptor for combining multiple interceptorsInterceptor\PharMetaDataInterceptor for actually testing against insecure deserialization in meta-data of Phar archivessee https://github.com/TYPO3/phar-stream-wrapper/wiki/TYPO3-PSA-2018-001
see https://github.com/TYPO3/phar-stream-wrapper/wiki/TYPO3-PSA-2018-001
Thanks to Alex Pott, Drupal for creating back-ports of all sources in order to provide compatibility with PHP v5.3.
Thanks to Alex Pott, Drupal for creating back-ports of all sources in order to provide compatibility with PHP v5.3.
Nothing published for this version
Thanks to Alex Pott, Drupal for creating back-ports of all sources in order to provide compatibility with PHP v5.3.
Thanks to Alex Pott, Drupal for creating back-ports of all sources in order to provide compatibility with PHP v5.3.
a93126f [TASK] Allow Manager::destroy() even if not being initialized
Nothing published for this version
One column per quarter.