Release history

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased] - YYYY-MM-DD

About

We keep an Unreleased section at the top to track upcoming changes.

This serves two purposes:

  1. People can see what changes they might expect in upcoming releases.
  2. At release time, we can move the Unreleased section changes into a new release version section.

Added

Changed

Deprecated

Removed

Fixed

Security

About the release cycle

HydePHP consists of two primary components, Hyde/Hyde and Hyde/Framework. Development is made in the Hyde/Develop Monorepo. Major and Minor release versions are made in the Develop project. These releases are synced to the Hyde and Framework projects, and are what this changelog file tracks. Patch release versions are made in the Framework and Hyde projects independently. See https://github.com/hydephp/develop#releases for more information.

HydePHP v2.0 Release Notes

Overview

HydePHP v2.0 represents a major evolution of the framework, introducing significant improvements to the asset system, navigation API, and overall developer experience. This release modernizes the frontend tooling by replacing Laravel Mix with Vite, completely rewrites the navigation system for better flexibility, and introduces numerous performance optimizations throughout the framework.

This document will give you an overview of the changes. When you're ready to upgrade your site, take a look at the Upgrade Guide.

Major Features

🚀 Modern Frontend Tooling with Vite

We've replaced Laravel Mix with Vite for a faster, more modern development experience:

🎨 Enhanced Asset Management System

The new consolidated Asset API provides a more intuitive interface for handling media files:

🧭 Redesigned Navigation API

The navigation system has been completely rewritten for maximum flexibility:

📝 Improved Documentation Features

Documentation pages now benefit from several enhancements:

🎯 Better Developer Experience

Numerous quality-of-life improvements for developers:

Upgrading to v2.0

📖 For complete step-by-step upgrade instructions, see the Upgrade Guide.

Important: PHP 8.2+ is now required. Laravel Mix has been replaced with Vite, and Tailwind CSS has been upgraded to v4.

Breaking Changes

High Impact Changes

1. Tailwind CSS v4 Upgrade

We've upgraded from Tailwind CSS v3 to v4. Run the automated upgrade tool to migrate your custom classes:

1npx @tailwindcss/upgrade

Review the Tailwind v4 Upgrade Guide for detailed breaking changes.

2. ESM Module Migration

Frontend tooling now uses ESM modules instead of CommonJS. If you have custom JavaScript, update to ESM syntax:

Before:

1const module = require('module-name');
2module.exports = { /* ... */ };

After:

1import module from 'module-name';
2export default { /* ... */ };

3. Navigation Configuration Format

Update your navigation configuration to use the new array-based format:

Before:

1'navigation' => [
2    'custom_items' => [
3        'Custom Item' => '/custom-page',
4    ],
5],

After:

1'navigation' => [
2    'custom_items' => [
3        ['label' => 'Custom Item', 'destination' => '/custom-page'],
4    ],
5],

4. Features Configuration

Replace static method calls with enum values in your config/hyde.php:

Before:

1'features' => [
2    Features::htmlPages(),
3    Features::markdownPosts(),
4],

After:

1'features' => [
2    Feature::HtmlPages,
3    Feature::MarkdownPosts,
4],

General Impact Changes

Post Author System

The blog post author feature has been significantly improved:

Configuration changes:

 1// Before
 2'authors' => [
 3    Author::create('username', 'Display Name', 'https://example.com'),
 4],
 5 
 6// After
 7'authors' => [
 8    'username' => Author::create(
 9        name: 'Display Name',
10        website: 'https://example.com',
11        bio: 'Author bio',
12        avatar: 'avatar.png',
13        socials: ['twitter' => '@username']
14    ),
15],

Key changes:

The way this system now works is that you first define authors in the config, Hyde then loads this during the booting process, and you can then access them using the get method.

Medium Impact Changes

Asset API Updates

All asset methods now return MediaFile instances instead of strings. This instance can be cast to a string which will automatically resolve to a relative link at that time. You can also call helper methods on it. When using Blade templates, thanks to the Stringable implementation no change will happen.

1// Methods renamed for clarity
2Hyde::asset('image.png');        // Previously: Hyde::mediaLink()
3Asset::get('image.png');         // Previously: Asset::mediaLink()
4Asset::exists('image.png');      // Previously: Asset::hasMediaFile()
5HydeFront::cdnLink('app.css');   // Previously: Asset::cdnLink()

Configuration changes:

Routes Facade API

Methods renamed to follow Laravel conventions:

1// Before
2$route = Routes::get('route-name');        // Returns null if not found
3$route = Routes::getOrFail('route-name');  // Throws exception
4 
5// After
6$route = Routes::find('route-name');       // Returns null if not found
7$route = Routes::get('route-name');        // Throws exception

DataCollection API

Low Impact Changes

Includes Facade Return Types

Methods now return HtmlString objects:

1{{-- Before: Required unescaped output --}}
2{!! Includes::html('partial') !!}
3 
4{{-- After: Automatic rendering --}}
5{{ Includes::html('partial') }}

⚠️ Security Note: Output is no longer escaped by default. Use {{ e(Includes::html('foo')) }} for user-generated content.

Documentation Search Generation

The documentation search page is now generated as an InMemoryPage instead of a post-build task, meaning it appears in the dashboard and route list.

Sidebar Configuration

Documentation sidebar configuration has been reorganized:

New Features

Enhanced Blog Posts

Improved Build System

Developer Tools

Package Updates

Realtime Compiler

HydeFront

Performance Improvements

Dependency Updates

Removed Features

Deprecated Method Removals

Build Commands

Configuration Options

Components and Files

Support & Resources

For the complete changelog with all pull request references, see the full changelog.

1.8.0 - 2025-05-17

Added

Changed

Deprecated

Fixed

1.7.0 - 2024-07-05

Added

Changed

Deprecated

Removed

Fixed

Extra information

This release contains changes to how HydePHP behaves when a site URL is not set by the user.

These changes are made to reduce the chance of the default localhost value showing up in production environments.

Most notably, HydePHP now considers that default site URL localhost to mean that a site URL is not set, as the user has not set it. This means that things like automatic canonical URLs will not be added, as Hyde won't know how to make them without a site URL. The previous behaviour was that Hyde used localhost in canonical URLs, which is never useful in production environments.

For this reason, we felt it worth it to make this change in a minor release, as it has a such large benefit for sites.

You can read more about the details and design decisions of this change in the following pull request https://github.com/hydephp/develop/pull/1726.

1.6.0 - 2024-04-17

Added

Changed

Deprecated

Fixed

Upgrade Path

In order to prepare your project for HydePHP v2.0, you should update your config/hyde.php configuration file to use the new Feature enum for the features array.

You can see the changes to make in your Hyde project by looking at the following pull request https://github.com/hydephp/hyde/pull/250/files

Your new config array should look like this:

 1// Make sure to import the new Feature enum at the top of the file
 2use Hyde\Enums\Feature;
 3 
 4// Then replace your enabled features with the new Feature enum cases
 5'features' => [
 6    // Page Modules
 7    Feature::HtmlPages,
 8    Feature::MarkdownPosts,
 9    Feature::BladePages,
10    Feature::MarkdownPages,
11    Feature::DocumentationPages,
12 
13    // Frontend Features
14    Feature::Darkmode,
15    Feature::DocumentationSearch,
16 
17    // Integrations
18    Feature::Torchlight,
19],

If you need more help, you can see detailed upgrade instructions with screenshots in the pull request https://github.com/hydephp/develop/pull/1650

1.5.0 - 2024-02-13

Improved Patch Release Strategy

This release experiments some changes into how releases are handled to clarify the patch versioning of distributed packages compared to the monorepo source versioning.

In short: We are now experimenting with rolling patch releases, where patches are released as soon as they're ready, leading to faster rollout of bugfixes. This means that the patch version discrepancy between the monorepo and the distributed packages will be increased, but hopefully the end results will still be clearer, thanks to the second related change: Prefixing the subpackage changes in this changelog with the package name. If there is no prefix, the change applies to the core package or the monorepo.

All this to say, please keep in mind that when the monorepo gets a new minor version, the prefixed changes may already have been released as patches in their respective packages.

Added

Changed

Deprecated

Fixed

1.4.2 - 2023-12-22

Added

Changed

Fixed

1.4.0 - 2023-12-11

Added

Changed

Removed

Fixed

Internal

1.3.0 - 2023-10-30

Added

Changed

Fixed

v1.2.0 - 2023-06-22

Added

Changed

Removed

Fixed

v1.1.0 - 2023-03-22

About

This release is the first since the official release of HydePHP 1.0.0. It contains a number of bug fixes and improvements, but no breaking changes as the project has reached general availability and adheres to the semantic versioning backwards compatibility promise.

Added

Changed

Removed

Fixed

v1.0.0 - 2023-03-14

Changed

Security

v1.0.0-RC.8 - 2023-03-14

Changed

Removed

Fixed

v1.0.0-RC.7 - 2023-03-14

Added

Changed

v1.0.0-RC.6 - 2023-03-14

Removed

Fixed

v1.0.0-RC.5 - 2023-03-13

Added

Changed

Fixed

v1.0.0-RC.4 - 2023-03-12

Added

Changed

Removed

Fixed

v1.0.0-RC.3 - 2023-03-11

Changed

Deprecated

v1.0.0-RC.2 - 2023-03-10

Added

Changed

Deprecated

This release candidate version contains a few deprecations, these will be removed before the final 1.0.0 release.

Removed

Fixed

v1.0.0-RC.1 - 2023-03-07

About

Welcome to the first release candidate for HydePHP 1.0! If you are coming from a beta version, please know that there are is a very large amount of breaking changes regarding the internal structure, so it is highly reccomended that you read through the release notes below.

Added

Breaking changes

Abstract

This beta release contains a plethora of breaking changes compared earlier beta versions. So many in fact, it could actually be easier and faster to recreate your project from scratch than to upgrade a particularly complex project. Though it only took me like five minutes to upgrade a simple documentation site, see this diff to see what I did.

The good news however, is that as HydePHP approaches version 1.0, there will no longer be releases like these with breaking changes.

While I've got your attention: read this the section right after this, as you might not need to make any changes at all.

Do I need to make any changes to my project?

If any of these statements are true, you will probably need to make changes to your project, and it might be easiest to copy over your content to a new project.

In all cases, you will most definitely need to republish the configuration files and update the app/bootstrap.php file.

Upgrade guide

The easiest way to upgrade your project is to copy over your content (source files, etc.) to a new project.

Major breaking changes

These are changes that break backwards compatibility and that are likely to concern users using HydePHP to create sites.

Breaking internal changes

These are changes that break backwards compatibility but are unlikely to concern users using HydePHP to create sites. Instead, these changes will likely only concern those who write custom code and integrations using the HydePHP framework.

These types of changes are handled within the framework ecosystem to ensure they do not affect those using HydePHP to create sites. For example, if a namespace is changed, all internal references to that namespace are updated, so most users won't even notice it. If you however have written custom code that explicitly references the old namespace, you will need to update your code to use the new namespace.

v0.64.0-beta - 2022-10-18

Note from the maintainer

First of all, I'm really sorry for the just insane amount of breaking changes in this update. I believe they are necessary in order to make v1.0 a great and stable release. I hope you'll understand. Most of the changes are likely to not affect normal usage, with the exception of the front matter navigation key changes.

About

This release performs a large amount of refactors and naming changes in preparation for the 1.0 release. Many of these refactors are breaking as several classes are moved around to new namespaces, several are merged, methods renamed, interfaces updated, and more, so forth, etc.

In general, these changes should only affect those who have written custom code that interacts with the framework, though you may need to update your configuration files, and any Blade components you may have published.

What you can expect to break

This update requires the configuration file to be updated.

The most high impact change is change of sidebar front matter options, and related areas. Please try updating your site in a test environment first, to see if you need to update any of your front matter.

Added

Changed

Major breaking changes

A very large number the changes in this update are breaking, as such, not all are marked as breaking. The really major changes that require especially close attention are here listed, please scroll down to see the rest as well as the concrete changes of this high level overview.

Navigation schema changes

If you are using any of the following front matter properties, you will likely need to update them:

This change also bubbles to the HydePage accessors, though that will only affect you if you have written or published custom code that interacts with the framework.

General

Class and method renames

Namespace changes

Page-model specific

Documentation page front matter changes

Markdown post/pre-processor changes

If you have not written any custom Markdown processors or any custom codes that interacts with default ones, you can ignore this section. Note that list may not be exhaustive.

Removed

Fixed

v0.63.0-beta - 2022-09-01

About

This release contains breaking changes regarding the PostBuildTasks that may require your attention if you have created custom tasks.

Added

Changed

Deprecated

Fixed

v0.62.0-beta - 2022-08-27

About

This update deprecates two interfaces (contracts) and inlines them into their implementations. It also refactors the documentation page layout to use more Blade components which may cause you to need to republish any manually published components.

The following interfaces are affected: HydeKernelContract and AssetServiceContract. These interfaces were used to access the service container bindings. Instead, you would now type hint the implementation class instead of the contract. This change will only affect those who have written custom code that uses or type hints these interfaces, which is unlikely. If this does affect you, you can see this diff to see how to upgrade. https://github.com/hydephp/develop/pull/428/commits/68d2974d54345ec7c12fedb098f6030b2c2e85ee. In short, simply replace HydeKernelContract and AssetServiceContract with HydeKernel and AssetService.

Changed

Deprecated

Removed

Fixed

v0.61.0-beta - 2022-08-17

About

Creates a new foundation class, the FileCollection. Which like the other foundation collections, discovers all the files. Running this part of the autodiscovery will further enrich the Hyde Kernel, and allow greater insight into the application. The end user experience should not be affected by this.

Added

Changed

Fixed

Upgrade guide

Collection namespace change

You only need to do this if you have written custom code that uses the old namespace.

To upgrade the moved collection namespaces, simply replace the following namespace imports:

1-use Hyde\Framework\PageCollection;
2+use Hyde\Framework\Foundation\PageCollection;
3-use Hyde\Framework\RouteCollection;
4+use Hyde\Framework\Foundation\RouteCollection;

v0.60.0-beta - 2022-08-12

About

This release continues refactoring the internal codebase. As part of this, a large part of deprecated code has been removed and the package has been updated accordingly.

Added

Changed

Removed

Fixed

Upgrade Guide

MarkdownFileParser path change

This class now expects the supplied filepath to be relative to the root of the project. This will only affect you if you have written any custom code that uses this class. All internal Hyde code is already updated to use the new path format.

To upgrade, change any calls you may have like follows:

1-return (new MarkdownFileParser(Hyde::path('_posts/foo.md')))->get();
2+return (new MarkdownFileParser('_posts/foo.md'))->get();

v0.59.0-beta - 2022-08-11

About

This release refactors the internal routing system. Unless you have written custom code that directly uses these classes and methods, updating should be fairly smooth. If not, you may want to read through the following overview.

The route index has been decoupled from page index and is split into two new collection classes, PageCollection and RouteCollection. The PageCollection contains all the site's parsed pages, and the RouteCollection contains all the page routes.

The RoutingService class remains for compatibility with existing code, but now only forwards calls to the new RouteCollection. The RoutingServiceContract interface is now deprecated.

Added

Changed

Deprecated

Removed

Fixed

Upgrade notes

Route keys are now used in navigation config

Prior to this release, the navigation menu priorities were based on the page slug. This has been changed to the route key. A route key in Hyde is in short the compiled page's path, relative to the site's root. For example, _site/foo/bar.html has the route key foo/bar.

This change is breaking as the order of navigation items may be changed unless the configuration is updated. However, this is really easy. Just change docs to docs/index in the config/hyde.php file.

1'navigation' => [
2    'order' => [
3        'index' => 0,
4        'posts' => 10,
5-        'docs' => 100,
6+        'docs/index' => 100,
7    ],
8],

If you have used the config to hide the documentation page from the navigation menu, you also need to use the route key by changing 'exclude' => ['docs'] to 'exclude' => ['docs/index']. The same goes if you have used the config to change the navigation titles for the home and documentation pages.

v0.58.0-beta - 2022-08-08

About

This update contains breaking changes to the internal API regarding page models. This should only affect you directly if you've written any code that interacts with the internal page models, such as constructing them using non-built-in Hyde helpers.

The update makes large changes to how dynamic data is constructed. Instead of generating page data at runtime, now the data is generated when constructing a page object. This gives the major benefit of being able to see all dynamic data right away, without having to render the page.

The way metadata tags are handled internally is also refactored. The rendered result should not be affected.

Added

Changed

Deprecated

Removed

Fixed

Upgrade guide and extra information

Rename slugs to identifiers

Previously internally called slug(s), are now called identifier(s). In all honestly, this has 90% to do with the fact that I hate the word "slug". I considered using basename as an alternative, but that does not fit with nested pages. Here instead is the definition of an identifier in the context of HydePHP:

An identifier is a string that is in essence everything in the filepath between the source directory and the file extension.

So, for example, a page source file stored as _pages/foo/bar.md would have the identifier foo/bar. Each page type can only have one identifier of the same name. But since you could have a file with the same identifier in the _posts directory, we internally always need to specify what source model we are using.

The identifier property is closely related to the page model's route key property, which consists of the site output directory followed by the identifier.

Heavily refactor constructors of Markdown-based page models

Adds a new interface to the Markdown page model constructors, that expects instantiated FrontMatter and MarkdownDocument objects. Normally you would use the SourceFileParser to create the object.

This means that the constructor for all Markdown-based pages is completely changed. To use a format matching the old behaviour, you can use the MarkdownPageModel::make method.

Title property has been removed from page model constructors

The following syntax has been removed: new MarkdownPage(title: 'Foo Bar') Instead, you can add it with front matter: MarkdownPage::make(matter: ['title' => 'Foo Bar'])

Markdown pages now have front matter in an object instead of array

This means that instead of the following $post->matter['title'], you would use $post->matter('title'), which allows you to add a fallback like so: $post->matter('title', 'Untitled')

Author helper has been merged into the model

The deprecated Helpers\Author has been fully merged into Models\Author. Simply swap namespaces to upgrade.

1-use Hyde\Framework\Helpers\Author;
2+use Hyde\Framework\Models\Author;

v0.57.0-beta - 2022-08-03

About

This update refactors the internal page source model parsing. This will likely not affect you directly, however, if you have written custom code that interacts with any class relating to the PageParser contract, you'll want to take a closer look at the changes.

Added

Changed

Deprecated

Removed

v0.56.0-beta - 2022-08-03

About

This update makes changes to the internal Markdown services. If you have written code or integrations that uses any of these services, you may want to take a closer look. Otherwise, this should not affect you much.

Many Markdown related classes have been moved to a new namespace, and the classes themselves have been restructured. Again, this only affects those who in the past have used these classes outside of what Hyde normally provides.

Due to the nature of this refactor, where so much have been changed, not everything is documented here. See the attached pull request for the full Markdown change diff: https://github.com/hydephp/develop/pull/318

Added

Changed

Removed

v0.55.0-beta - 2022-08-01

About

This update removes the deprecated LegacyPageRouter class from the Hyde Realtime Compiler (HydeRC). Along with this release, the HydeRC is now on version 2.5, and requires Hyde version 0.48.0-beta or higher.

Changed

Removed

v0.54.0-beta - 2022-08-01

About

This release refactors and cleans up a large part of the internal code base. For most end users, this will not have any visible effect. If you have developed integrations that depend on methods you may want to take a closer look at the associated pull requests as it is not practical to list them all here.

Overview

Here is a short overview of the areas that are impacted. If you don't know what any of these mean, they don't affect you.

Added

Changed

Deprecated

Removed

Upgrade tips

When refactoring the Hyde::copy() helper change, you have two options (that you can combine). If one or more of your inputs are already qualified Hyde paths, use the native copy helper. If you don't want to overwrite existing files, make that check first.

v0.53.0-beta - 2022-07-30

About

This release refactors some internal code. If you have published any Blade views or created any custom integrations, you may want to take a closer look at the changes. Otherwise, this should not affect most existing sites.

Added

Changed

Deprecated

Removed

v0.52.0-beta - 2022-07-29

About

This update internally refactors how documentation sidebars are handled. If you have published Blade views relating to these, or built framework integrations you may want to take a closer look at the changed files.

Added

Changed

v0.51.0-beta - 2022-07-28

Added

Removed

v0.50.0-beta - 2022-07-26

About

This update makes breaking changes to the configuration. You will need to update your configuration to continue using the new changes. Each one has been documented in this changelog entry, which at the end has an upgrade guide.

Overview of major changes

As there are a lot of changes, here is first a quick overview of the major ones. See the full list after this section.

Note that the goal with this release is to make the framework more stable and developer friendly, but without it affecting the end user experience. For example, the visual experience as well as the interactions of the refactored documentation pages are minimal and most users won't notice any change. However, for developers, the changes are significant and will reduce a lot of complexity in the future.

Added

Changed

Removed

Fixed

Upgrade Guide

Here are some instructions for upgrading an existing project. You should also read the standard upgrade guide first for general advice, https://hydephp.com/docs/2.x/updating-hyde.

If you use Git, you may be able to automatically configure some of these by merging https://github.com/hydephp/hyde into your project. Alternatively, you can download the release and unzip it into your project directory, and using GitHub Desktop or VS Code (or whatever you use) to stage the new changes without affecting your project's configuration.

Core file changes

Here is an overview of the core files that have changed and that you will most likely need to update. Some of these have detailed instructions further down.

A large number of Blade views have also changed. You may want to update pretty much all of them. See the diff for a list of files that have changed.

Updating Composer

When updating an existing project, you may need to add laravel-zero/framework to your Hyde composer.json file.

1"require": {
2    "php": "^8.0",
3    "hyde/framework": "^0.50",
4    "laravel-zero/framework": "^9.1"
5},

Using the new site config

Site-specific config options have been moved from config/hyde.php to config/site.php. The Hyde config is now used to configure behaviour of the site, while the site config is used to customize the look and feel, the presentation, of the site.

The following configuration options have been moved. The actual usages remain the same, so you can upgrade by using copying over these options to the new file.

If you have published and Blade views or written custom code that uses the config options, you may need to update them. You can do this by republishing the Blade views, and/or using search and replace across your code. VSCode has a useful feature to make this a breeze: CMD/CTRL+Shift+F.

Using the new footer config

The footer configuration options have been merged. Prior to this update, the config option looked as follows:

1// filepath: config/hyde.php
2'footer' => [
3  'enabled' => true,
4  'markdown' => 'Markdown text...'
5],

Now, the config option looks as follows:

1// filepath: config/hyde.php
2 
3// To use Markdown text
4'footer' => 'Markdown text...',
5 
6// To disable it completely
7'footer' => false,

As you can see, the new config option is a string or the boolean false instead of an array. We use the same option for both the Markdown text and the footer disabled state.

Updating Blade Documentation Views

This release rewrites almost all of the documentation page components to use TailwindCSS. In most cases you won't need to do anything to update, however, if you have previously published the documentation views, you will need to update them.

Release Notes for HydeFront v2.x

HydeFront version 2.0 is a major release and has several breaking changes. It is not compatible with HydePHP versions lower than v0.50.0-beta. HydePHP versions equal to or later than v0.50.0-beta require HydeFront version 2.0 or higher.

Many files have been removed, as HydePHP now uses Alpine.js for interactions, and TailwindCSS for the documentation pages.

HydeFront v1.x will receive security fixes only.

v0.49.0-beta - 2022-07-15

Added

Changed

v0.48.0-beta - 2022-07-10 - Internal Pseudo-Router Service Refactoring

About

This release brings a massive refactor in the way the HydePHP auto-discovery process works. It does this by centralizing all discovery logic to the new pseudo-router module which discovers and maps all source files and output paths.

The update also refactors related code to use the router. Part of this is a major rewrite of the navigation menu generation. If you have set any custom navigation links you will need to update your configuration files as the syntax has changed to use the NavItem model instead of array keys.

You will also need to update navigation related Blade templates, if you have previously published them.

Added

Changed

Deprecated

Removed

v0.47.0-beta - 2022-07-05

Added

v0.46.0-beta - 2022-07-03

Added

Changed

Removed

Fixed

v0.45.0-beta - 2022-07-03

Added

Changed

Removed

Fixed

v0.44.0-beta - 2022-07-02 - Internal code restructuring

About

This release mainly makes internal changes to the Framework API. If you are an end user, most of the changes are not relevant. However, if you are a package developer, or if you have published Blade views or otherwise extended Hyde you may want to take a look as there are internal breaking changes.

Added

Changed

Deprecated

Removed

Fixed

v0.43.0-beta - 2022-06-25 - File-based Collections

Added

Removed

Fixed

v0.42.0-beta - 2022-06-24

Added

Changed

Fixed

v0.41.0-beta - 2022-06-24 - Add an Asset facade

About

This release refactors and improves the Asset Service, adding auto-configuration features and a new Asset facade.

Using the Asset facade in Blade views

Instead of the long syntax Hyde::assetManager() you can now use the Asset facade directly. See this example, which both do the exact same thing using the same underlying service:

1Hyde::assetManager()->hasMediaFile('app.css')
2Asset::hasMediaFile('app.css')

If you don't know what any of this means, good news! You don't have to worry about it. Hyde's got your back.

Added

Changed

Deprecated

v0.40.0-beta - 2022-06-22

Added

Changed

Deprecated

Removed

Security

v0.39.0-beta - 2022-06-20

Added

Changed

Removed

Fixed

v0.38.0-beta - 2022-06-18

About

This release refactors the test suite, compartmentalizing test code into the respective package directories. This does not affect the behavior of the library, but it does affect how package developers run the test suites.

Added

Changed

v0.37.2-beta - 2022-06-17

About

This release brings internal restructuring to the Hyde monorepo, adding a helper command to manage the new release cycle.

Added

Changed

v0.37.1-beta - 2022-06-16 - Update validation test

About

If there are no documentation pages there is no need for an index page, and the test can safely be skipped.

What's Changed

Full Changelog: https://github.com/hydephp/develop/compare/v0.36.0-beta...v0.37.1-beta

v0.37.0-beta - 2022-06-16 - Replace dependency with custom validator implementation

What's Changed

Full Changelog: https://github.com/hydephp/develop/compare/v0.36.0-beta...v0.37.0-beta.1

v0.36.0-beta - 2022-06-16 - Add package auto-discovery

What's Changed

Full Changelog: https://github.com/hydephp/develop/compare/v0.35.0-beta.1...v0.36.0-beta

v0.35.0-beta - 2022-06-14 - Initial Monorepo Release

What's Changed

Full Changelog: https://github.com/hydephp/develop/commits/v0.35.0-beta

Archive (pre v0.35.0)

In v0.35.0 the Hyde project source was moved into the HydePHP/Develop monorepo where the changelog is now handled. Releases in Hyde/Hyde and Hyde/Framework are synced one-to-one since this change.

Hyde/Hyde Archive (pre v0.35.0)

All notable changes to this project will be documented in this file. Dates are displayed in UTC.

Generated by auto-changelog.

v0.34.1-beta

11 June 2022

v0.34.0-beta

6 June 2022

v0.33.0-beta

4 June 2022

v0.32.3-beta

4 June 2022

v0.32.2-beta

4 June 2022

v0.32.1-beta

4 June 2022

v0.32.0-beta

4 June 2022

v0.31.0-beta

4 June 2022

v0.30.1-beta

31 May 2022

v0.30.0-beta

31 May 2022

v0.29.0-beta

30 May 2022

v0.28.1-beta

29 May 2022

v0.28.0-beta

23 May 2022

v0.27.1-beta

21 May 2022

v0.27.0-beta

19 May 2022

v0.26.0-beta

18 May 2022

v0.25.0-beta

17 May 2022

v0.24.1-beta

11 May 2022

v0.24.0-beta

11 May 2022

v0.23.0-beta

6 May 2022

v0.22.0-beta

4 May 2022

v0.21.0-beta

3 May 2022

v0.20.0-beta

3 May 2022

v0.19.0-beta

1 May 2022

v0.18.0-beta

29 April 2022

v0.17.1-beta

28 April 2022

v0.17.0-beta

28 April 2022

v0.16.1-beta

28 April 2022

v0.16.0-beta

27 April 2022

v0.15.0-beta

27 April 2022

v0.14.0-beta

21 April 2022

v0.13.0-beta

20 April 2022

v0.12.0-beta

19 April 2022

v0.11.0-beta

17 April 2022

v0.10.0-beta

12 April 2022

v0.9.0-alpha

7 April 2022

v0.8.0-alpha

3 April 2022

v0.7.3-alpha

1 April 2022

v0.7.2-alpha

1 April 2022

v0.7.1-alpha

1 April 2022

v0.7.0-alpha

1 April 2022

v0.6.0-alpha

30 March 2022

v0.5.0-alpha

25 March 2022

v0.4.1-alpha

25 March 2022

v0.4.0-alpha

24 March 2022

v0.3.3-alpha

23 March 2022

v0.3.2-alpha

23 March 2022

v0.3.1-alpha

23 March 2022

v0.3.0-alpha

22 March 2022

v0.2.1-alpha

21 March 2022

v0.2.0-alpha

21 March 2022

v0.1.1-pre.patch

19 March 2022

v0.1.1-pre

19 March 2022

v0.1.0-pre

18 March 2022

Hyde/Framework Archive (pre v0.35.0)

All notable changes to this project will be documented in this file. Dates are displayed in UTC.

Generated by auto-changelog.

v0.34.0

6 June 2022

v0.33.0-beta

4 June 2022

v0.32.1-beta

4 June 2022

v0.32.0-beta

4 June 2022

v0.31.1-beta

3 June 2022

v0.31.0-beta

2 June 2022

v0.30.1-beta

31 May 2022

v0.30.0-beta

31 May 2022

v0.29.5-beta

31 May 2022

v0.29.4-beta

30 May 2022

v0.29.3-beta

30 May 2022

v0.29.2-beta

30 May 2022

v0.29.1-beta

30 May 2022

v0.29.0-beta

30 May 2022

v0.28.1-beta

25 May 2022

v0.28.0-beta-pre

22 May 2022

v0.28.0-beta

23 May 2022

v0.27.12-beta

22 May 2022

v0.27.11-beta

21 May 2022

v0.27.10-beta

20 May 2022

v0.27.9-beta

20 May 2022

v0.27.8-beta

19 May 2022

v0.27.7-beta

19 May 2022

v0.27.6-beta

19 May 2022

v0.27.5-beta

19 May 2022

v0.27.4-beta

19 May 2022

v0.27.3-beta

19 May 2022

v0.27.2-beta

19 May 2022

v0.27.1-beta

18 May 2022

v0.27.0-beta

18 May 2022

v0.26.0-beta

18 May 2022

v0.25.0-beta

17 May 2022

v0.24.0-beta

11 May 2022

v0.23.5-beta

11 May 2022

v0.23.4-beta

11 May 2022

v0.23.3-beta

10 May 2022

v0.23.2-beta

7 May 2022

v0.23.1-beta

6 May 2022

v0.23.0-beta

6 May 2022

v0.22.0-beta

5 May 2022

v0.21.6-beta

4 May 2022

v0.21.5-beta

3 May 2022

v0.21.4-beta

3 May 2022

v0.21.3-beta

3 May 2022

v0.21.2-beta

3 May 2022

v0.21.1-beta

3 May 2022

v0.21.0-beta

3 May 2022

v0.20.0-beta

2 May 2022

v0.19.0-beta

1 May 2022

v0.18.0-beta

29 April 2022

v0.17.0-beta

28 April 2022

v0.16.1-beta

28 April 2022

v0.16.0-beta

27 April 2022

v0.15.0-beta

27 April 2022

v0.14.0-beta

21 April 2022

v0.13.0-beta

20 April 2022

v0.12.0-beta

19 April 2022

v0.11.0-beta

17 April 2022

v0.10.0-beta

12 April 2022

v0.9.0-beta

7 April 2022

v0.8.1-beta

3 April 2022

v0.8.0-beta

2 April 2022

v0.7.5-alpha

2 April 2022

v0.7.4-alpha

1 April 2022

v0.7.3-alpha

1 April 2022

v0.7.2-alpha

1 April 2022

v0.7.1-alpha

1 April 2022

v0.7.0-alpha

1 April 2022

v0.6.2-alpha

30 March 2022

v0.6.1-alpha

30 March 2022

v0.6.0-alpha

30 March 2022

v0.5.3-alpha

26 March 2022

v0.5.2-alpha

25 March 2022

v0.5.1-alpha

24 March 2022

v0.5.0-alpha

24 March 2022

v0.4.3-alpha

23 March 2022

v0.4.2-alpha

23 March 2022

v0.4.1-alpha

22 March 2022

v0.4.0-alpha

22 March 2022

v0.3.1-alpha

22 March 2022

v0.3.0-alpha

21 March 2022


Syntax highlighting by Torchlight.dev