Releases: cedaro/satispress
Releases · cedaro/satispress
2.0.1
- Fixed the search functionality in the package selector sidebar. See [#223].
- Switched to using thunks instead of generators in the React data stores.
- Added psr/log to the built zip file for release. See [#215].
- Prevented notices in the console from core React components. See [#222]. Props @thefrosty
- Explicitly marked nullable types for PHP 8.4+ compatability. See [#221]. Props @andronocean
- Prevented PHP deprecation notices caused by string interploation. See [#220]. Props @hirasso
2.0.0
- SatisPress now requires PHP 8+.
- Updated Composer dependencies. The latest versions of PSR packages and the Pimple container may prevent conflicts with other plugins.
- Added return type hints for classes implementing
ArrayAccess. This prevents errors in PHP 8+. - Fixed a fatal error in the Envato integration. See #182. Props @BjornKraft
- Added
satispress_debug_modefilter to prevent exceptions from being thrown in the request handler. See #211. - Fixed output of
codetags in the admin. - Prevented errors when header names aren't strings. See #192.
- Fixed formatting of the authors array in
package.json. See #185. Props @NielsdeBlaauw - Added the package name to the information displayed on the Repository tab in the admin. See #191. Props @tyrann0us
- Fixed numerous WPCS warnings and errors after updating to WPCS 3.
1.0.4
- Allowed SatisPress dependencies to require
composer/installersversion 1 or 2. Props @LucasDemea - Removed
node_modulesfrom the list of directories to be automatically excluded for cases where a package depends on it existing. Props @tyrann0us
1.0.3
- Added a search field in the package selector sidebar. Props @DavidSingh3
- Added support for composer/installers 2.0+ for packages served by SatisPress. Props @tyrann0us
- Added support for PHP 8.
1.0.2
- Fixed a parse error in the Envato Market integration.
- Skipped releases without a SemVer compliant version string in the Composer repository transformer to prevent fatal errors. See #160. Props @DavidSingh3
- Removed the trace from
\SatisPress\Logger\format_exception()to prevent fatal errors.
1.0.1
- Fixed the validation logic in the hidden directory validator and updated the test. See #142. Props @patrick-leb for troubleshooting and help in resolving this issue.
- Fixed a fatal error in the Envato Market adapter. See #153
1.0.0
- Updated the admin interface to make it easier to manage the repository from a single screen.
- Introduced REST endpoints for managing SatisPress resources:
/satispress/v1/packages/satispress/v1/plugins/satispress/v1/themes
- Removed the meta capability check from the Composer repository transformer. This allowed packages or individual releases to be filtered from
packages.json, but prevented the transformer from being used in other scenarios. - Removed a type hint from the
upgrader_post_installto prevent fatal errors when aWP_Errorobject is passed as a parameter. See #152
0.7.2
- Fixed an incorrect variable name in the
HiddenDirectoryValidatorthat caused a fatal error. - Added a Health Check feature to display admin notices for common configuration issues.
- Fixed authentication integration tests to check for the correct exception type after preventing
AuthenticationExceptions from being thrown in a2415c7. - Moved validator tests to the integration test suite.
- Removed the
PclZipdevelopment dependency fromcomposer.json. WordPress uses a patched version and in cases where it was inadvertently installed, it could cause issues. See #149.
0.7.1
- There weren't any changes in this release. The version number was bumped to allow Composer to install updates from the previously botched release process.
0.7.0
- Introduced validators to prevent invalid artifacts from being cached when downloaded from the vendor.
- Introduced adapters for downloading artifacts from vendors that use a non-standard update process.
- Added a field to the SatisPress package list screen to copy the CLI command for requiring a package in
composer.json. - Fixed a bug with the logger not logging messages above the specified log level.