Review an open-source app update by reading the upstream release notes, recording the current version, and testing the workflows that matter to your users. The correct steps depend on the project and version you operate, so treat this article as a checklist rather than a provider maintenance schedule.
Identify the change
Record the version currently in use and the release you are considering. Read the project's changelog and upgrade notes from the upstream source. Separate security fixes, database changes, removed features, client compatibility notes, and any manual migration steps. Check whether your browser extension, mobile client, webhook consumer, or API script has a matching requirement.
Prepare a reversible check
- List the sign-in, read, write, notification, and export actions that must keep working.
- Use an export or backup function when the application version documents one, and protect the resulting copy.
- Record integrations, scheduled jobs, and configuration values that an update might affect.
- Tell users about a maintenance window in your own operations calendar when a workflow depends on it.
Keep a short change record with the release identifier, the checks you ran, and any integration that needs a later review. If the upstream notes call for a manual migration, follow those instructions and keep the change reversible where the project allows it.
Verify the application afterward
Sign in with a test account, exercise one representative read and write action, run the documented export or recovery check, and trigger a safe notification or integration test. Compare the result with the acceptance list written before the update. Report a reproducible regression with the app version, relevant timestamps, and the smallest useful diagnostic excerpt.
Keep service scope explicit
This generic checklist does not define provider maintenance responsibilities or product features. Confirm any account-specific scope in the current contract and service documentation, and use the upstream project documentation for version-specific tasks. Retain the record so later operators can distinguish an upstream change from a local configuration issue.
Ask about a specific release
For a question tied to your account or app version, use the support ticket form. The upstream pledge guide explains the separate contribution wording, and the products page is the plan entry point.