Add failed login log message, including IP address, to enable use with fail2ban.#2232: Fix flag icon path in Peers Tab missing.#2085: Fix not showing torrents in sidebar for categories other than 'All' in classic mode.#2125: Fix plugin methods not being available when enabled until restart.#2046: Fix plugins not enabling properly until after refreshing page.#2212: Fix unable to scroll in proxy preferences page.#2120: Fix manually entered values not being saved in spinners.#2103: Fix sorting by name is case-sensitive.#1890: Fix columns in files and peers view could use some spacing.#2069: Fix login window layout problem when using larger than default font size.#2112: Fix world readable tmp directory in json_api.Add move completed option to add torrent dialog.#1397: Add support for -s STATE in info command.#2065: Fix crash with missing closing quote. Ensure console commands are executed in order.LP#1004793: Enable use of connect command in non-interactive mode.Fix showing exception error to user in Classic Mode with no libtorrent installed.#2260: Fix the Add Torrent dialog also bringing the main window to active workspace.#2228: Fix Apply-To-All in AddTorrent? Dialog copying file renames to other torrents.#2129: Fix empty filename able to be set in AddTorrent? dialog.#2130: Fix same name can be given to different files in Add Torrent dialog.#1946: Fix ReactorNotRestartable? error when set as startup application.#1474: Fix the on_show_prefs hook not being executed immediatly after enabling a plugin.#2147: Fix missing translations for plugin preferences page.Fix torrent names on libtorrent 0.16 on windows.#2146: Fix missing translations in View|Tabs submenu.#2086: Fix submenus and icons for appindicator.#2104: Fix no title set for the appindicator.#2171: Fix the Add Peer dialog not responding if empty or invalid values entered.Laravel and its other first-party packages follow Semantic Versioning. Major framework releases are released every year (~February), while minor and patch releases may be released as often as every week. Minor and patch releases should never contain breaking changes. When referencing the Laravel framework or its components from your application or package, you should always use a version constraint such as ^9.0, since major releases of Laravel do include breaking changes. However, we strive to always ensure you may update to a new major release in one day or less. Named arguments are not covered by Laravel's backwards compatibility guidelines. We may choose to rename function arguments when necessary in order to improve the Laravel codebase. Therefore, using named arguments when calling Laravel methods should be done cautiously and with the understanding that the parameter names may change in the future.įor all Laravel releases, bug fixes are provided for 18 months and security fixes are provided for 2 years. For all additional libraries, including Lumen, only the latest major release receives bug fixes. In addition, please review the database versions supported by Laravel. VersionĪs you may know, Laravel transitioned to yearly releases with the release of Laravel 8. Previously, major versions were released every 6 months. This transition is intended to ease the maintenance burden on the community and challenge our development team to ship amazing, powerful new features without introducing breaking changes. Therefore, we have shipped a variety of robust features to Laravel 8 without breaking backwards compatibility, such as parallel testing support, improved Breeze starter kits, HTTP client improvements, and even new Eloquent relationship types such as "has one of many". Therefore, this commitment to ship great new features during the current release will likely lead to future "major" releases being primarily used for "maintenance" tasks such as upgrading upstream dependencies, which can be seen in these release notes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |