Mirrors/unleash.unleash
1
0
Fork 0
mirror of https://github.com/Unleash/unleash.git synced 2025-01-25 00:07:47 +01:00
Code Issues Projects Releases Wiki Activity

fix: add license key notice to upgrade instructions (#7440)

Browse Source 
Add missing notice about license keys when upgrading to v6
This commit is contained in:
Gastón Fournier 2024-06-25 11:47:54 +02:00 committed by GitHub
parent c3fa468a9d
commit a26bbf1a7e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
website/docs/using-unleash/deploy/upgrading-unleash.md
View File

@ -9,6 +9,13 @@ Generally, the intention is that `unleash-server` should always provide support
[Unleash v6](https://github.com/Unleash/unleash/issues/4380) was released on June 6th, 2024. **We expect this upgrade to be straightforward**, provided you have followed the previous migration guides on this page. We're removing some features that were deprecated in version 5 and marking some features as deprecated, but these will continue to be supported during version 6. Here's the list of the outstanding changes you need to take into account when migrating from v5 to v6:
### Self-hosted enterprise customers are now required to use a License Key
Before upgrading you should make sure to get a valid license key. More information in [this page](../deploy/license-keys.mdx).
- For Unleash hosted (Pro/Enterprise), license management is not necessary and is handled automatically.
- For Unleash Open Source, no license is necessary and these steps do not apply.
### Remove Passport libs from the official open source Docker distribution
*If you're not using the official open source image, you can safely ignore this change.*