# Upgrading Pomerium Enterprise
When new version of Pomerium Enterprise are released, check back to this page before you upgrade.
# 0.17.0
# Before You Upgrade
- The new license-keyoption is required for starting Pomerium Enterprise. Please contact your account team if you have not been issued one yet.
# 0.16.0
# Before You Upgrade
- The - signing-keyhas been replaced with- authenticate-service-url. Instead of manually setting the signing key in the Enterprise Console to match the Authenticate Service, we specify the trusted URL of the Authenticate Service to pull the signing key from.- The - signing-keykey will continue to work for existing configurations, but device enrollment will not work until it is replaced by- authenticate-service-url.
# 0.15.0
# Before You Upgrade
- signing-keyis now a required option to improve request security from Pomerium Core. The value should match the one set in Pomerium Core. See the signing key reference page for more information on generating a key.
- audienceis now a required option to improve request security from Pomerium Core. The value should match the Enterprise Console's external URL hostname, as defined in the- fromfield in the Routes entry (not including the protocol).
# Helm Installations
- As of v0.15.0, All Helm charts have been consolidated to a single repository. Remove the - pomerium-enterpriserepo and upgrade from- pomerium:- helm repo remove pomerium-enterprise helm upgrade --install pomerium-console pomerium/pomerium-console --values=./pomerium-console-values.yaml
- As noted above, - signing-keymust be shared between Pomerium and Enterprise. See the Update Pomerium section of Install Pomerium Enterprise in Helm for more information.