« Changelog History


Sculpin v3.0.0 Release Notes

Release Date: 2019-04-10 // about 5 years ago

  • ➕ Added

    • 🆕 New --output-dir flag allows users to override the default output directory (output_dev, output_prod) with their own custom target.
      • Also works with SCULPIN_OUTPUT_DIR environment variable.
    • 🆕 New --source-dir flag allows users to override the default source directory (source) with their own custom target.
      • Also works with SCULPIN_SOURCE_DIR environment variable.
    • 🆕 New content:create command allows users to quickly and easily create new content types. It will generate appropriate templates, including pagination.
    • New init command allows users to spin up an EXTREMELY bare-bones Sculpin site, automatically creating YAML configuration files and some placeholder source/ files.

    🔄 Changed

    • BC BREAK: Many classes have been made final to reduce complexity. If there is a valid use case to extend one of the classes, please do a pull request to remove the final keyword and explain why you need to extend the class.
    • 🚚 BC BREAK: #367 moved to PHP 7.2 as the new minimum PHP version for Sculpin.
    • BC BREAK: #392 changed the signature of the getAdditionalSculpinBundles() method to specify an array return type. If you have a custom SculpinKernel.php file you will need to
    • #385 bumped minimum Symfony packages version to 4.1
      • See the "Fixed" section for a BC Break related to the Symfony YAML component.

    🗄 Deprecated

    • Nothing.

    ✂ Removed

    • 👍 #332 dropped php 5 support.
    • 🚚 #335 removed embedded composer and related commands: install, update, self-update and dump-autoload

    🛠 Fixed

    • BC BREAK: Pagination file names can now use the ".twig" extension, and when using this mode, "Page 2" will render as "blog/page/2/index.html" instead of "blog/page/2.html"
      • To preserve search engine indexes and/or bookmarks, consider creating redirect mappings to send visitors to the new destinations.
    • ⬆️ BC BREAK: Upgrading the Symfony YAML component has resulted in some changes to YAML Front Matter processing.
      • Most notably, values with a colon, such as page titles, now require quoting. E.g., title: My Journey: Back From Whence I Came must now be title: "My Journey: Back From Whence I Came"
      • These instances should be clearly called out the first time you call the generate command, so it should require minimal effort to locate and fix.