> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/api-reference/change-logs/upgrade-guide.md). # Current Upgrade Guidance Identify the API and SDK you use, review current integration boundaries, and plan compatibility checks before consulting historical release entries. Start here when maintaining an existing integration. Changelogs record what changed at a point in time; the current Developer Guide and public schema define the integration contract. A source update without publication metadata is not a numbered release or proof that every deployment has changed. ## 1. Identify Your Integration Record the API family, regional base, credential type, workspace or organization, SDK package and pinned version, channel, and selected service/configuration. See the [package snapshot](/api-reference/change-logs.md#current-sdk-packages) for the last verified package versions. Classic and Platform packages use different resources and credentials; do not replace one package with the other as a routine version bump. ## 2. Check Current Boundaries The following are compatibility checkpoints reviewed on September 6, 2026, not new product announcements: | If your integration uses… | Check or change… | Current implementation | | ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | | Managed channel provisioning through old workspace routes | Arrange managed provisioning separately, then use the public service-binding contract | [Use Cases and Bindings](https://docs.concurrence.com/developer-guide/platform-api/workspaces/use-cases) | | Shareable intake upload links or the retired external HMAC upload path | Use the supported authenticated dataset-intake workflow; confirm processing and queryability separately | [Customer Data Intake](https://docs.concurrence.com/developer-guide/platform-api/data-world-model/intake) | | Standalone ringless voicemail | Remove that retired workflow; ordinary outbound-call voicemail handling is a separate voice capability | [Voicemail](https://docs.concurrence.com/developer-guide/platform-api/conversations/voicemail) | | A text answer treated as complete at acknowledgement | Handle pending work and the supported background-delivery receipt protocol | [Serve an Agent From a Web App](https://docs.concurrence.com/developer-guide/platform-api/conversations/serve-agent-from-web-app) | | Scribe through generic text-session or login-session assumptions | Use its deployment base, provider access, session mode, and artifact lifecycle | [Scribe](https://docs.concurrence.com/developer-guide/platform-api/scribe) | | SMS delivery inferred from conversation creation or an opt-in send record | Inspect consent/suppression and delivery evidence independently | [SMS](https://docs.concurrence.com/developer-guide/platform-api/conversations/sms) | | Mutable workspace environment or region settings | Select the appropriate regional workspace and use the current workspace contract; retired fields do not move a deployment | [Workspaces](https://docs.concurrence.com/developer-guide/platform-api/workspaces) | Use the relevant endpoint's current schema for exact requests, responses, and deprecation metadata. Do not infer one deadline or replacement operation from a historical feature title. For the September 2026 SDK releases, review the [Classic 2.0.0 and Platform 0.108.0 compatibility changes](/api-reference/change-logs/sdk-ecosystem.md#september-2026-compatibility-releases). Classic generated fields and model identifiers changed; Platform fleet status no longer accepts a selector. For conversation context, reviewed September 14, 2026, coordinate the service's `accepted_context` with create callers and the selected Context Graph's `context_bindings`. Service updates use `PUT`; context keys and tool parameter names must match exactly. Review the [Platform changelog entry](/api-reference/change-logs/amigo-api.md#conversation-context-and-tool-bindings), particularly before relying on automatic `channel-id` in text sessions. ## 3. Validate the Change For the September 16 documentation review, migrate removed cost-to-serve reads to the [current usage and cost reports](https://docs.concurrence.com/developer-guide/platform-api/platform-api/cost-to-serve), preserving their different access requirements and unavailable-data handling. Treat voice `call_sid` values as opaque strings, including UUID-shaped values, and verify retained Realtime history separately from live events. Intake-source deletion still requires deployment confirmation. See the [source and contract update](/api-reference/change-logs/amigo-api.md#usage-cost-and-voice-contracts) for scope. Pin the intended package and record the previous version. Compile the affected client code, compare the applicable current operations, and rerun representative success, access-denial, pending-work, interrupted-request, and cleanup cases on a test deployment. The [First Verified Conversation](https://docs.concurrence.com/developer-guide/guides/first-verified-conversation) provides a pinned example and fixture checks for one Platform workflow. Passing those local checks does not establish compatibility for your full application or provisioned channel. Before production rollout, verify configuration selection and recovery, decide how ambiguous external outcomes are reconciled, and record the observations that would stop or reverse the rollout. A package downgrade or configuration rollback does not undo a target-system action. ## Find the Historical Detail * [Concurrence API](/api-reference/change-logs/amigo-api.md) retains recent entries, an archive index, and forwarding headings for older bookmarks. * [Web Platform](/api-reference/change-logs/web-platform.md) does the same for Developer Console and Admin Portal history. * [SDK Ecosystem](/api-reference/change-logs/sdk-ecosystem.md) tracks package-specific changes. * [Agent Forge CLI](/api-reference/change-logs/agent-forge.md) tracks CLI changes independently. When a historical entry and current behavior appear inconsistent, preserve the history and report the discrepancy with the version, operation, and observed evidence. Use [Troubleshooting](https://docs.concurrence.com/developer-guide/guides/troubleshooting) to identify the failing boundary. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.concurrence.com/api-reference/change-logs/upgrade-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.