Repository navigation
Conversation
CircleCI removes support for version 2.0 configs on 2026-09-21. Affected pipelines fail to compile after that date, so this is a required change rather than a cleanup. Verified with `circleci config validate --next`, which previews the new compiler: this config fails it before the change and passes after. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
CircleCI removes support for
version: 2.0configs on 2026-09-21. Pipelines still on 2.0 will fail to compile after that date, so this is required, not cleanup.mantleis worth prioritising alongsidepipeline_shared: it ships from git master to p.core and the services rather than as a released version, so a broken build here stays quiet until something downstream trips over it.What changed
One line —
version: 2→version: 2.1. Nothing else. (version: 2is the 2.0 schema; the new compiler reports it as end-of-life.) Thedefaults: &defaultsanchor and<<: *defaultsmerge keys are plain YAML and remain valid in 2.1, so no other migration was needed.Verification
circleci config validate --next— CircleCI's own preview of the September compiler — fails before this change (Config version 2 has reached end of life) and passes after.circleci config processoutput before and after: identical except for the legacy variable below.The 2.0 compiler injects a legacy
CIRCLE_COMPARE_URLenv var into the job; the 2.1 compiler does not. Grepped every repo in the org for it: zero references. With that line filtered out the compiled configs are identical.Scope
Part of an 8-repo sweep for the same deadline: pipeline_sync, pipeline_email, pipeline_events, pipeline_google, pipeline_dogfood, pipeline_shared, mantle, mailchimp. (pipeline_integrations was already migrated on 2026-09-01.)
The other three announced breaking changes — undeclared parameters, the regex engine update, and the deprecated
pipeline.trigger_parameters.*values — affect none of our configs; I checked all of them.🤖 Generated with Claude Code
Note on the implicit
buildjobThis config has
jobs:but noworkflows:key, so it relies on CircleCI running the job namedbuildimplicitly. That behaviour is intact under 2.1 — confirmed by the passing check on this PR, not assumed.