From 21d00ce24c2cfc27f2d4003a91e52b426bb70ee1 Mon Sep 17 00:00:00 2001 From: purple Date: Sat, 22 Jun 2024 00:16:48 +0200 Subject: [PATCH] changelog `beta-F248`: update changelog --- docs/pages/about/changelog/beta-F248.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/pages/about/changelog/beta-F248.md b/docs/pages/about/changelog/beta-F248.md index c24e1a0..d0125e2 100644 --- a/docs/pages/about/changelog/beta-F248.md +++ b/docs/pages/about/changelog/beta-F248.md @@ -13,6 +13,8 @@ - Extension buttons have been redesigned once again and should now look more recognizable for each extension. - We've added new marketing material and updated Blueprint's default logo. This includes new versions of Blueprint's icon and full-res images of our stickers. - Add a choice for putting the application in maintenance mode when installing/upgrading Blueprint. +- No longer use folder placeholders for navigating to the Pterodactyl directory. ([#40](https://github.com/BlueprintFramework/framework/pull/40)) +- The extensions page now shows a " System" badge on system extensions (such as Blueprint).
@@ -25,9 +27,12 @@ - Extension information values could not contain the `&` character. Doing so would break some pages. (Reported by [@0x7d8](https://github.com/0x7d8)) - Extension-provided scripts were sometimes ran with root permissions, which was not intentional. - Fixed a typo in Blueprtint's installation log. ([#38](https://github.com/BlueprintFramework/framework/pull/38)) +- `SettingsContainer.tsx` was extended by the backups component, which was not intentional. (Reported by [@itsvic-dev](https://github.com/itsvic-dev/)) +- Ending extension identifiers with `.blueprint` in `-install` no longer results in a error. ([#41](https://github.com/BlueprintFramework/framework/pull/41))
#### Breaking Changes - Install, remove and export scripts may no longer be able to use colored logs. -- Export scripts need an additional flag ([`developerEscalateExportScript`](?page=documentation/flags)) to run with root-level perms, which might be needed in some cases. \ No newline at end of file +- Export scripts need an additional flag ([`developerEscalateExportScript`](?page=documentation/flags)) to run with root-level perms, which might be needed in some cases. +- You can no longer change Blueprint's `$FOLDER` variable by parsing `$_FOLDER` upon first run of the script. \ No newline at end of file