Cloud and DevOps tooling generates a constant stream of change notices, most of which are additive and safe to ignore. The exceptions are narrow and specific: a supported version window closing, a runner image changing its default toolchain, a managed service deprecating an API version. Those are the entries with a date and a consequence attached.

Orchestration platforms in particular run a support window of only a few releases. Fall behind by more than that and the upgrade path stops being a single hop, which turns a routine maintenance task into a project. The value of tracking here is largely about not letting that gap open in the first place.

What this category tracks

Orchestration platform releases
Minor and patch releases for container orchestration platforms, with their supported version windows.
CI runner and image updates
Hosted runner image changes, including default toolchain versions and removal notices.
Cloud service changes
New regions, service tiers, API versions and generally available features from major cloud providers.
Deprecation deadlines
Dated cut-offs for API versions, instance families, runtimes and authentication methods.

What matters most here

Runner image changes are the most under-appreciated event in this category. A hosted CI image is updated on the provider's schedule, not yours, and a change to the default language runtime inside that image can break a pipeline that has not been touched in a year. These changes are announced, but in a changelog most teams do not read until after the build has gone red.

Where this data comes from

  • Platform release pages and published version support policies
  • CI provider runner image changelogs and announcement repositories
  • Cloud provider service announcement feeds
  • Published deprecation schedules and retirement notices

Every indexed entry links to its primary source. See our editorial and sourcing policy for what we verify and what we do not.

Common questions

Do you cover every cloud provider announcement?

No, and deliberately. The major providers publish hundreds of announcements a month, most of them regional availability notices. We index changes with a version, a deprecation date or a behavioural change attached, and leave the rest.

How far ahead are deprecation deadlines listed?

As soon as the provider publishes the date, which is often twelve months or more in advance. Sorting by oldest first within a filtered view brings the nearest deadlines to the top.

Tracked releases in Cloud & DevOps

The live release list for this category loads below.

Guides covering this area

More in Technology