Publish the new workflow package

login-workflow/CHANGELOG.md

@@ -5,21 +5,18 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## v4.0.0 (Unreleased)
+## v5.0.0 (October 3, 2023)
 
 ### Added
 
--   A `ViewEulaSubscreen` component.
--   A `ContactSupportSubscreen` component.
--   A `BrandedCardContainer` component.
--   Confirm password field error state message in `ChangePasswordForm`.
--   Option to hide the Create Password screen during registration
--   A `ExistingAccountRegisterSuccessSubscreen` component.
--   A `RegistrationWorkflowContext` context, a `RegistrationWorkflowContextProvider` component and a `useRegistrationWorkflowContext` hook.
+-   Reusable screen components.
+-   Support for custom react auth workflow injection.
+-   Support for router customizability.
+-   Learn more about migrating from v4 => v5 your existing application by reading our [Migrating Guide](https://github.com/etn-ccis/blui-react-workflows/blob/master/login-workflow/README.md#migrating-from-v4--v5).
 
 ### Changed
 
--   Changed the verification code styles for the self registration workflow.
+-   Updated i18next and react-i18next packages to the latest.
 
 ## v3.1.1 (December 14, 2022)
 

login-workflow/docs/migration-guide-4-5.md

@@ -11,7 +11,7 @@ yarn upgrade @brightlayer-ui/react-auth-workflow@^5.0.0
 
 ## Managing Auth State
 
-In order to be more flexible / customizable, the workflow no longer manages the authentication status of the user internally. You will need to establish your own mechanism (such as using a ContextProvider or Redux) to track whether or not a user is authenticated to your application. For reference, you can look at how we set up the [AppContext](https://github.com/etn-ccis/blui-react-workflows/blob/dev/login-workflow/example/src/contexts/AppContextProvider.tsx) in the example project.
+In order to be more flexible / customizable, the workflow no longer manages the authentication status of the user internally. You will need to establish your own mechanism (such as using a ContextProvider or Redux) to track whether or not a user is authenticated to your application. For reference, you can look at how we set up the [AppContext](https://github.com/etn-ccis/blui-react-workflows/blob/master/login-workflow/example/src/contexts/AppContextProvider.tsx) in the example project.
 
 
 ## Managing Routing

login-workflow/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@brightlayer-ui/react-auth-workflow",
-    "version": "5.0.0-alpha.1",
+    "version": "5.0.0",
     "author": "Brightlayer UI <[email protected]> (https://github.com/brightlayer-ui)",
     "license": "BSD-3-Clause",
     "description": "Re-usable workflow components for Authentication and Registration within Eaton applications.",