Update NextVersion.md (#1129)

* Update next version

* Update next version

docs/changehistory/NextVersion.md

@@ -71,7 +71,7 @@ This change might break consumers that rely on importing APIs directly from unsu
 
 - Main barrel file, i.e. `@itwin/appui-react`
 - `package.json` subpath, i.e. `@itwin/appui-react/package.json`
-- All SCSS files, i.e. `@itwin/core-react/lib/core-react/_typography.scss`. Since SCSS files are exported using the `sass` custom condition, consumers should ensure that [Node.js package importer](https://sass-lang.com/documentation/js-api/classes/nodepackageimporter/) is enabled. SCSS exports are available to facilitate the AppUI 5.0 adoption and will be removed in the next major version.
+- All SCSS files, i.e. `@itwin/core-react/lib/core-react/_typography.scss`. SCSS exports are available to facilitate the AppUI 5.0 adoption and will be removed in the next major version.
 
 To fix the import issue, consumers should update their import paths to use the supported export paths. For example:
 
@@ -110,7 +110,8 @@ If the currently used API is not exported from the barrel file and there is no r
 
 Support for CommonJS modules has been removed from all AppUI packages. [#1081](https://github.com/iTwin/appui/pull/1081)
 
-To facilitate the migration, the `exports` field has been updated to support legacy `cjs` and `esm` import paths in SCSS files. For example, `@import "@itwin/core-react/lib/cjs/core-react/base/base.scss"` will continue to work correctly by resolving to `@import "@itwin/core-react/lib/core-react/base/base.scss"`. However, consumers should avoid importing deprecated SCSS partial files, as these will be removed in the next major version.
+To facilitate the migration, the `exports` field has been updated to support legacy `cjs` and `esm` import paths in SCSS files. For example, `@import "@itwin/core-react/lib/cjs/core-react/base/base.scss"` will continue to work correctly by resolving to `@import "@itwin/core-react/lib/core-react/base/base.scss"`. Additionally, SCSS files are still delivered in `cjs` and `esm` directories to support a wider range of bundlers [#1125](https://github.com/iTwin/appui/pull/1125).
+However, consumers should avoid importing SCSS partial files, as these are deprecated and will be removed in the next major version.
 
 Additionally, file extensions are provided in import declarations, which are [mandatory for ES modules](https://nodejs.org/api/esm.html#mandatory-file-extensions). [#1056](https://github.com/iTwin/appui/pull/1056)
 
@@ -143,7 +144,6 @@ AppUI packages now specify `@itwin/itwinui-react` as a [peer dependency](https:/
 
 ### Changes
 
-- Updated `MessageManager.addMessage` and `MessageManager.outputMessage` to ignore already active messages displayed to the user. This API is used by various tools indirectly via `IModelApp.notifications.outputMessage` when `AppNotificationManager` is set up. This change should prevent the same message from being displayed multiple times unnecessarily. [#1042](https://github.com/iTwin/appui/pull/1042)
 - Popout widgets are now displayed in a flow layout to match the layout of floating, stage panel, and popout widgets when `reparentPopoutWidgets` is enabled. [#1049](https://github.com/iTwin/appui/pull/1049)
 - Use React portal instead of creating a separate element tree for each child window. [#1062](https://github.com/iTwin/appui/pull/1062)
 - Removed incorrect usage of the internal `IModelApp.renderSystem.options.displaySolarShadows` check from `useSolarDataProvider`. The `wantShadows` property of the viewport display style is used instead. [#1066](https://github.com/iTwin/appui/pull/1066)