Technical lifecycle intelligence

The breaking change is rarely the line in the changelog.

SchemaTrace turns API, SDK, authentication and runtime changes into evidence-bounded implementation records: what changed, who is affected, when enforcement starts and what remains unknown.

For platform teams, engineering leaders, security teams and technical vendors

Live source-linked publication · indexing enabled

STATUSLive research publicationCORPUS243 governed recordsOPERATING MODELFive lanes · central filter · evidence boundaries

Latest change files

API, runtime and authentication changes with operational consequences

Search all records →

ST-2026-153Field deprecated

AtlassianAPI endpoints & versionsRemoval after · 31 Jul 2027

Jira workflow webhook workflowId becomes an unusable placeholder

From 19 July 2026, workflowId in two Jira workflow-post-function webhook payloads is a placeholder and will be removed after 31 July 2027.

Previous stateWebhook consumers could treat workflowId as identifying a Jira workflow.Current stateworkflowId returns an invalid placeholder in Connect Workflow Post Function and Trigger a webhook payloads; workflowName or workflowEntityId must be used.

ST-2026-092Deprecated or maintenance

Amazon Web ServicesSDKs, clients & toolchainsNext lifecycle milestone · 2027-07-15

AWS CLI v1 enters maintenance mode

AWS CLI v1 entered maintenance mode on 5 August 2026; it now receives only critical bug and security fixes, while new-service, API-update and new-region support has ended. End of support remains 15 July 2027.

Previous stateThrough 4 August 2026, AWS CLI v1 remained in General Availability, with regular releases that included new-service support, API updates for existing services, and bug and security fixes.Current stateAWS CLI v1 entered maintenance mode on 5 August 2026. During maintenance, AWS limits releases to critical bug fixes and security issues, does not provide API updates for new or existing services, and does not add support for new regions. AWS lists 15 July 2027 as end of support.

ST-2026-113Retirement scheduled

AtlassianAPI endpoints & versionsEndpoints stop working after · 30 Jun 2027

Atlassian retires Get users and Get groups organisation-directory endpoints

Atlassian deprecated the GET organisation-directory users and groups endpoints; they stop working after 30 June 2027 and are replaced by the v2 POST search endpoints.

Previous stateIntegrations could enumerate directory users and groups through GET /v2/orgs/{orgId}/directories/{directoryId}/users and GET /v2/orgs/{orgId}/directories/{directoryId}/groups.Current stateThe GET endpoints are deprecated and must be replaced with POST /v2/orgs/{orgId}/directories/{directoryId}/users/search and POST /v2/orgs/{orgId}/directories/{directoryId}/groups/search before they stop working after 30 June 2027.

ST-2026-018Expiry rollout

AtlassianAuthentication & identityLatest legacy-key expiry boundary · 1 May 2027

Atlassian SCIM API keys move from indefinite lifetime to scheduled expiry

Atlassian states that newly created or regenerated SCIM API keys expire after one year, while older keys generated before 1 January 2025 are being assigned expiries between 1 May 2026 and 1 May 2027.

Previous stateSCIM provisioning keys could have an indefinite lifetime, including keys already used by identity providers to provision and de-provision Atlassian managed accounts.Current stateNew or regenerated SCIM keys expire after one year, and Atlassian is assigning the pre-2025 key cohort expiration dates across a May 2026 to May 2027 window.

ST-2026-088Retirement scheduled

XeroAPI endpoints & versionsVersion 3.0 retirement · 30 Apr 2027

Xero starts the 12-month retirement of Practice Manager Public API v3.0

Xero deprecated the Practice Manager Public API v3.0 and directs integrations to v3.1 before the stated 30 April 2027 retirement date.

Previous statePractice Manager integrations could remain on Public API v3.0 while Xero continued to add compatibility fields intended to support later migration.Current stateVersion 3.0 is deprecated under a 12-month migration period and new investment, including JSON responses, field selection and further enhancements, is focused on Practice Manager 3.1.

Daily research system

Five lanes built for this publication.

Read the operating method →

LaneResearch scopePrimary audienceAdmission rule

01API endpoints & versionsEndpoint retirement, version transitions, protocols and response-contract changesAPI owners and integration teamsA concrete compatibility or migration consequence

02SDKs, clients & toolchainsLanguage support, compiler floors, client libraries and package lifecycleApplication and developer-platform teamsOfficial support or compatibility boundary

03Authentication & identityOAuth, API keys, tokens, service accounts, certificates, IAM and MFASecurity and identity ownersChanged authentication or permission requirement

04Runtimes & developer platformsKubernetes, ingress, CI/CD, registries, build systems and execution runtimesPlatform engineering and SRERuntime availability, default or support change

05Enforcement & amendmentsBrownouts, grace periods, deadline extensions, shutdowns and correctionsProgramme and risk ownersDated action or material lifecycle update

Enforcement calendar

Enforcement, retirement and transition dates

2027-07-31
AtlassianRemoval after · 31 Jul 2027
Open file
2027-07-15
Amazon Web ServicesNext lifecycle milestone · 2027-07-15
Open file
2027-06-30
AtlassianEndpoints stop working after · 30 Jun 2027
Open file
2027-05-01
AtlassianLatest legacy-key expiry boundary · 1 May 2027
Open file

Open the full enforcement calendar →

Why this exists

Implementation teams need the boundary, not the headline.

A deprecation notice can hide five separate migrations: endpoints, authentication, permissions, agents and network policy. SchemaTrace keeps those obligations together without pretending every deadline or affected version is known.

See the evidence doctrine →