zf-apigility-skeleton 1.5.2

Added

• Nothing.

Changed

• Nothing.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• #168 fixes file permissions of the /var/www folder when using Vagrant,
  setting them to the www-data user.

Apigility 1.5.1

Added

• Nothing.

Changed

• Nothing.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• #165 updates the composer.lock by running composer install using a
  PHP 5.6 release. This was done as the 1.5.0 release was made using a PHP 7.1+
  binary, and thus installed versions of dependencies that were compatible with
  those release - but not with 5.6. Once a release is made with this patch,
  users on PHP 5.6 will be able to install the skeleton again.

  However, this means that PHP 7.1+ users will need to execute the following
  after an initial skeleton install in order to get newer versions of libraries
  compatible with 7.1:

  $ rm -Rf composer.lock vendor
  $ composer install

Apigility 1.5.0

Added

• #159 adds a development requirement on zendframework/zend-test, ensuring users
  have the ability to run existing unit tests, as well as write and execute new ones out of the box.

Changed

• #164 updates all dependencies to versions that will work with PHP 7.2, where possible.

• #154 modifies the config/autoload/.gitignore rules to omit *.local-development.php files.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• Nothing.

Apigility 1.4.2

Added

• Nothing.

Changes

• Nothing.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• #162 fixes a compatibility issue with PHP 7.2

Apigility 1.4.1

Added

• Nothing.

Changes

• #146 updates the Vagrant configuration to use bento/ubuntu-16.04 as its base.
• #147 updates the minimum supported versions of the following dependencies:
  • zend-component-installer: 0.5.0
  • zf-apigility-documentation: 1.2.3
  • zf-apigility-admin: 1.5.9
• #148 updates the public/index.php to allow intercepting calls to it for enabling and disabling development mode (e.g., php public/index.php development enable). These calls now proxy to the official zf-development-mode scripts. The change was made to allow backwards compatibility in existing toolsets such as Zend Studio, which would enable development mode when invoking the admin GUI.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• #136 fixes the shipped error view scripts to accommodate PHP 7 Throwable instances.
• #138 fixes the Docker configuration of the Apache virtual host such that it will work correctly.
• #145 adds a missing bootstrap directive to the shipped phpunit.xml.dist.

Apigility 1.4.0

This version bumps the minimum supported PHP version to 5.6.

It incorporates the following components and modules at the specified versions; these versions likely contain bugfixes, and, if noted, additional features. Additional Zend Framework components are also present, but not noted here.

• zendframework/zend-component-installer: 0.3.0
• zendframework/zend-developer-tools: 1.1.0
• zfcampus/zf-api-problem: 1.2.1
• zfcampus/zf-apigility: 1.3.0
  • Support in ZF\Apigility\Application for handling PHP 7 Throwables.
• zfcampus/zf-apigility-admin: 1.5.6
  • Extracts all factories defined in the Module class to their own classes.
  • Extracts all listeners defined in the Module class to their own classes.
  • Adds a patchList() stub to the REST resource class template, so that it is present by default.
  • Adds support for working with modules using PSR-4 directory format, and the ability to generate PSR-4-style modules.
  • Adds a vendor script, apigility-upgrade-to-1.5, for upgrading an existing Apigility application so that it may use Zend Framework component v3 releases.
  • Adds the ability to generate all configuration files using short array syntax and ::class notation.
  • Adds a new API endpoint for reporting the current Apigility skeleton version.
• zfcampus/zf-apigility-admin-ui: 1.3.7
  • Displays the current Apigility skeleton version as returned by the zf-apigility-admin API.
  • Uses full controller service names when interacting with the zf-apigility-admin API; this resolves some lingering UI issues due to version mismatch.
  • Adds a "field type" input to new field entries, allowing you to provide this information via the UI (previously the information could only be provided by manually updating configuration files). This allows communicating field type information to documentation systems such as Swagger.
  • Numerous UI fixes, particularly with regards to sidebar behavior.
• zfcampus/zf-apigility-documentation: 1.2.2
  • Adds support for displaying documentation of APIs in nested PHP namespaces.
  • Adds support for transforming Markdown documentation to HTML, and enables it by default.
  • Displays field types, if provided, by default.
• zfcampus/zf-apigility-provider: 1.2.0
  • Deprecates the Module class. You no longer need to list the ZF\Apigility\Provider module in your application module configuration.
• zfcampus/zf-asset-manager: 1.1.1
  • New in this version. Uses configuration from rwoverdijk/assetmanager to expose asset directories in the document root of your application. It acts as a Composer plugin, and copies configured asset directories under your public/ directory, adding an entry to that directory's .gitignore file to prevent checking those files into version control. Updates to modules are honored, and removal of a module will remove the files from your source tree.
• zfcampus/zf-composer-autoloading: 1.0.0
  • New in this version. Provides a vendor binary for adding an autoloading entry to your Composer configuration for the module you specify, and then updates autoloading rules locally.
• zfcampus/zf-configuration: 1.2.1
  • Adds a new configuration switch, zf-configuration.class_name_scalars, allowing you to configure whether or not generated configuration will use ::class notation.
• zfcampus/zf-console: 1.3.0
  • Adds the ability to substitute your own dispatcher via the ZF\Console\DispatcherInterface
  • Adds the ability to disable output of the application banner.
  • Adds the ability to compose a container-interop container with the dispatcher, which allows providing service names as console handlers.
  • The exception handler now catches PHP 7 Throwable instances as well.
• zfcampus/zf-content-negotiation: 1.2.2
• zfcampus/zf-content-validation: 1.3.4
  • Adds support for mapping input filters to GET requests. This feature is not yet supported in the admin UI, however.
• zfcampus/zf-deploy: 1.2.0
• zfcampus/zf-development-mode: 3.0.0
  • This new release now ships as a standalone vendor binary, instead of using the deprecated MVC <-> Console integration.
• zfcampus/zf-hal: 1.4.2
  • Adds an interface, concrete classes, and configuration for allowing alternate "self" and generic link generation strategies. As such, usage of the server url and url helpers with the Hal plugin is now deprecated.
  • Adds service factories for the two link extraction services, allowing the ability to provide alternate facilities if needed.
  • Adds a new method to the Hal plugin, resetEntityHashStack(); this can be used when rendering multiple responses or payloads within the same request cycle to allow re-use of the same entity instances.
• zfcampus/zf-mvc-auth: 1.4.2
• zfcampus/zf-oauth2: 1.4.0
  • Adds support for the ext/mongodb extension.
  • Adds token revocation suport.
• zfcampus/zf-rest: 1.3.1
• zfcampus/zf-rpc: 1.3.0
• zfcampus/zf-versioning: 1.2.0

Please read the migration documentation for more details on upgrading.

Apigility 1.3.3

Incorporates the following fix from zf-apigility-admin-ui:

• #100, which provides a fix for handling database table names that contain underscore-separated words.

Apigility 1.3.2

Incorporates the following fixes from zf-apigility-skeleton:

• 109: Added setenvif to apache vhost in order to pass authorization headers
• 112: Set always_populate_raw_post_data to -1
• 114: Set UTF8 fo LC_ALL in Vagrant environment
• 117: Authentication fix for fast-cgi
• Updates minimum versions of select dependencies: ZF2 2.5.3, zf-apigility-admin 1.4.1, and zf-apigility-admin-ui 1.4.2.

Additionally, the following modules have updates incorporated in this release:

• zf-development-mode updated to 2.1.2; brings in fixes for configuration cache settings when switching between development and production modes.
• zend-apigility-admin 1.4.1 fixes an issue in the RpcServiceModel to ensure that a correct pattern is generated when fetching a service by name.
• zend-apigility-admin-ui 1.2.2 fixes a number of issues discovered, including:
  • DB Autodiscovery was failing due to inability to properly select the DB adapter name.
  • Custom authentication adapters are now displayed.
  • The regex for validating custom content-types was fixed to ensure it only allows valid MIME type specifications.
  • Fixes validation for REST and RPC service names, raising a warning on invalid input.

Apigility 1.3.1

• zfcampus/zf-oauth2#112 fixes a parse error in the receive code template, and updates the cURL examples on that page to use the current request scheme.
• Fixes for AG2015-01, which patch a user spoofing vector in zf-oauth2.
• zfcampus/zf-mvc-auth#94 fixes HTTP authentication to ensure that omitting an Authorization header no longer results in a 401 status, and instead falls back to using the GuestIdentity as it did prior to 1.1.0.
• zfcampus/zf-apigility-admin#305 and zfcampus/zf-apigility-admin-ui#69 allow DB adapters that do not support metadata features to be used for DB-Connected REST services.
• #105 updates the Vagrant setup to ensure it includes PHP 5.6, allowing it to work with versions 1.3+.

Apigility 1.2.1

• zfcampus/zf-oauth2#112 fixes a parse error in the receive code template, and updates the cURL examples on that page to use the current request scheme.
• Fixes for AG2015-01, which patch a user spoofing vector in zf-oauth2.
• zfcampus/zf-mvc-auth#94 fixes HTTP authentication to ensure that omitting an Authorization header no longer results in a 401 status, and instead falls back to using the GuestIdentity as it did prior to 1.1.0.
• zfcampus/zf-apigility-admin#305 and zfcampus/zf-apigility-admin-ui#69 allow DB adapters that do not support metadata features to be used for DB-Connected REST services.