> For the complete documentation index, see [llms.txt](https://docs.charted.com/ap-automation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.charted.com/ap-automation/upgrade-process.md). # Upgrade Process Stay up to date with the latest software updates Charted automatically deploys application updates into your production account, so you're always running the latest version of our software. Updates may include new features, enhancements, bug fixes, and security patches. No action is needed within your account to complete an update unless we notify you otherwise. For a list of what's included in each release, refer to our [release highlights](/ap-automation/release-notes.md) and [release notes](/ap-automation/release-notes.md). ### Release schedule We release new versions of our software on a regular cadence, typically once every two weeks. Regular scheduled releases are never planned for the first two weeks of a quarter. Each release is identified by the year and the release number for that year (e.g. 2026.15). Occasionally, we may include a minor patch to a release after notification is sent. When a release reaches your production account, you'll always receive the most recent version, including all minor patches available at that time. Releases are designed to required zero downtime and do not require users to take any action until notified in advance. To maximize internal support coverage, releases are scheduled to start after 8am ET unless the release has been identified to require downtime for users actively using the system. The specific timing per account can vary depending on NetSuite system load, by typically all customer updates are completed by end of day ET. ### Pre-release notifications Customers may optionally choose to receive advanced notification of a release coming soon via email. This is useful for customers who would like to test out new features and changes in Sandbox ahead of the scheduled push to production. The notification includes the release number, a link to the release notes, and the planned date the release will be applied to production accounts. These notifications are typically sent one week ahead of the planned push to production. To sign up, join our [mailing list](https://lp.charted.com/sign-up-to-receive-squareworks-software-updates) and select **"Also, sign me up for pre-release software updates".** To test a new version, work with your NetSuite administrator to update your sandbox account to the latest version of our SuiteApp or bundle. ### Testing in your own account Charted does not have access to your NetSuite account and therefore cannot rule out compatibility issues with your data or other customizations. Our regression testing covers a generic installation of our software, so it's best practice to perform your own internal testing as well. ### NetSuite upgrades NetSuite releases two major upgrades annually, and Charted ensures our software remains compatible with your version of NetSuite. Prior to NetSuite's first production account upgrade, Charted performs complete regression testing based on a generic installation of our software. If any changes are required, they will be automatically released via our normal release process ahead of your planned NetSuite upgrade window. {% hint style="warning" %} **DO NOT UNINSTALL BUNDLES OR SUITEAPPS**\ Doing so will lose data that cannot be recovered from your NetSuite account! {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.charted.com/ap-automation/upgrade-process.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.