# Update to a Newer Version of FusionAuth Learn how to update FusionAuth instances, FusionAuth Cloud deployments, and client libraries to a newer version. > For the index of this section of the site, see [llms.txt](https://fusionauth.io/docs/llms.txt) This section describes how to update any instance of FusionAuth to the latest version. [Update a Development Instance Learn how to update an instance of FusionAuth that isn't used for production purposes.](https://fusionauth.io/docs/update/dev-instance.md) [Update a Production Instance Learn how to plan, perform, and verify an update of a FusionAuth instance in a production environment.](https://fusionauth.io/docs/update/prod-instance.md) [Database Migrations Learn how FusionAuth migrates your database schema during an update, and how to run the migrations yourself.](https://fusionauth.io/docs/update/database-migrations.md) [Roll Back an Update Learn how to roll back FusionAuth to a previous version.](https://fusionauth.io/docs/update/rollback.md) [Early Access Program Learn about how to get your hands on new versions of FusionAuth before the official release.](https://fusionauth.io/docs/update/early-access-program.md) [Roadmap Learn more about the FusionAuth roadmap and planning process.](https://fusionauth.io/docs/update/roadmap.md) [Deprecation Policy Learn more about the FusionAuth deprecation policy.](https://fusionauth.io/docs/update/deprecation-policy.md) ## Stay Informed To find out about new releases, try one of the following options: * Bookmark the [release notes](https://fusionauth.io/docs/release-notes.md) and subscribe to the [release notes RSS feed](https://fusionauth.io/docs/releases.xml) * Sign up for release notifications: Form submission blocked by your browser. Please temporarily disable your ad blocker or privacy protection to submit. Thank you! Your submission has been received. ## FusionAuth Versioning FusionAuth releases come in three flavors: major, minor, and patch. You can tell what a release is from the rightmost non-zero number in the version: `..`. For example: * `1.0.0`: major release, may significantly change the API * `1.63.0`: minor release, may make small changes to the API * `1.45.1`: patch release, never changes the API The FusionAuth team provides detailed information about every change in every version, including tying the change back to a GitHub issue. To understand how a version update affects your systems, read the [release notes](https://fusionauth.io/docs/release-notes.md). ### Client Library Versioning FusionAuth represents releases with a version number: `..`. Major releases can add, change, or remove functionality from the API, minor releases can add to the API, but patch releases never change the API. Client library version numbers show you which API version a client library was built for. We recommend using a client library with the same `major` and `minor` numbers as your FusionAuth instance version. This ensures that your client library supports the same APIs as your FusionAuth instance. If you don't keep your client library in sync with your FusionAuth version: * you won't be able to access new API endpoints * you won't benefit from client library improvements (e.g. exponential backoff, improved HTTP connections, etc) * you could experience subtle bugs when existing API endpoints change behavior (e.g. changed argument order in an untyped language) Patch releases don't always exist for client libraries since many bugfixes and small changes don't impact client libraries. FusionAuth only creates patch releases for client libraries when we fix an issue in the library, so always update to the latest `patch` release for your `major` and `minor` version. Patch releases may also update dependencies, language engines, and operating systems, as we follow the deprecation and sunsetting policies of each platform. Consider a user whose FusionAuth instance runs version `1.61.1`. They should: * use Java client library version [1.61.2](https://github.com/FusionAuth/fusionauth-java-client/releases/tag/1.61.2), the latest patch release for `1.61.x` * use TypeScript client library version [1.61.0](https://www.npmjs.com/package/@fusionauth/typescript-client/v/1.61.0), the latest patch release for `1.61.x` This theoretical user also ought to update their FusionAuth instance to `1.61.2`, the latest patch for the `major` and `minor` instance version. ## Update a FusionAuth Cloud Deployment To update your FusionAuth Cloud deployment, see the [Update a Deployment Guide](https://fusionauth.io/docs/cloud/update-a-deployment.md). ## Update a Client Library Older FusionAuth client libraries should work properly with newer FusionAuth versions upon updating. However, once you use new features on that instance, FusionAuth might return enumeration values that older clients do not understand. This can cause client operations to fail. Note that newer FusionAuth client libraries *might not* be compatible with older FusionAuth versions. The [release notes](https://fusionauth.io/docs/release-notes.md) provide more information about API changes between versions. If you are using an OIDC-compatible library in your application to log your users in, it is unlikely that this integration would require modification, but test it in a non-production environment to make sure. ## Update FAQs How many versions can I skip? You can skip minor versions, as long as you read the release notes for every version you skip and test the update in a non-production environment. FusionAuth applies every database migration needed to reach the new version. See [Decide How Far to Jump](https://fusionauth.io/docs/update/prod-instance.md#decide-how-far-to-jump). How often should I update? We recommend staying within the last three minor versions, but we will not force an update. In addition, we typically don't backport bug fixes. If you run into an issue with a bug, you'll need to update to get the fix. We recommend you set up a regular cadence of reviewing and updating FusionAuth that fits your business needs, the same as you would with a framework or library your application depends on. How can I find out about new releases? We publish release notes for every release. You can find them here: [Release Notes](https://fusionauth.io/docs/release-notes.md). There are a variety of ways to be [notified of releases](https://fusionauth.io/docs/update.md#stay-informed), including an email list and RSS feed. Does FusionAuth support zero-downtime updates? At this time, FusionAuth does not support zero-downtime updates when there is a database change. While there are a variety of options that can minimize downtime, updates will cause downtime whenever a schema change is required. Please [review and upvote this issue](https://github.com/FusionAuth/fusionauth-issues/issues/1240) if zero-downtime updates are important to you. What kind of downtime can I expect? This depends on the amount of data in your system, the speed of your database, the schema changes in the release, and your [update strategy](https://fusionauth.io/docs/update/prod-instance.md#choose-an-update-strategy). Multi-node clusters can minimize downtime. For example, multi-node clusters in FusionAuth Cloud experience user-facing downtime on the order of seconds to minutes during updates. Testing an update in a non-production environment is the surest way to understand the amount of downtime. See [Downtime and Locking](https://fusionauth.io/docs/update/database-migrations.md#downtime-and-locking). What is runtime mode and how does it affect updates? The runtime mode, `development` or `production`, controls whether FusionAuth offers Maintenance Mode. Together with silent mode, it decides how database migrations are applied during an update. See [When FusionAuth Applies Migrations](https://fusionauth.io/docs/update/database-migrations.md#when-fusionauth-applies-migrations). What is Maintenance Mode? Maintenance Mode is an interactive setup page, available only in the `development` runtime mode, that configures the database and search engine and applies database migrations. Never use it in production. See [Maintenance Mode](https://fusionauth.io/docs/update/database-migrations.md#maintenance-mode). What is Silent Mode? [Silent Mode](https://fusionauth.io/docs/get-started/download-and-install/reference/silent-mode.md) makes FusionAuth apply database migrations automatically on startup, which suits automated deployments. As of version `1.19.0`, it works in both runtime modes. If a migration fails, FusionAuth displays an error message on the login page. See [Database Migrations](https://fusionauth.io/docs/update/database-migrations.md). Related [Update Update a Development Instance of FusionAuth Learn how to update an instance of FusionAuth that isn't used for production purposes. upgrade fusionauthversion upgrademigration](https://fusionauth.io/docs/update/dev-instance.md) [Update Roll Back a FusionAuth Update Learn how to roll back FusionAuth to a previous version. upgrade fusionauthversion upgrademigration](https://fusionauth.io/docs/update/rollback.md) [Update Update a Production Instance of FusionAuth Learn how to plan, perform, and verify an update of a FusionAuth instance in a production environment. upgrade fusionauthversion upgradeupdate fusionauth](https://fusionauth.io/docs/update/prod-instance.md) [Cloud Update a Deployment Learn how to update a deployment to a newer version of FusionAuth. update fusionauthversion upgradeversion update](https://fusionauth.io/docs/cloud/update-a-deployment.md)