Дата публикации: 11-06-2026 16:56:22

Note: Date changed from August 17 to September 21. We are adding warning messages to the UI, Build Notifications, and API endpoints. When pipelines run that contain deprecated features, a warning message will be returned. APIs impacted will include GET /api/v2/pipelin, GET /api/v2/pipeline/{pipeline-id}, GET /api/v2/project/{project-slug}/pipeline, GET /api/v2/project/{project-slug}/pipeline/mine, and GET /api/v2/project/{project-slug}/pipeline/{pipeline-number}.**
Note:** This post consolidates and replaces three earlier Discuss posts that covered each of these breaking changes separately, each with its own effective date. Those dates have since been aligned — all three changes now take effect on September 21, 2026. Please refer to this post as the single source of truth going forward.
On September 21, 2026, CircleCI is introducing three breaking changes to how configs are compiled. As part of a larger initiative to build next-generation config tooling, stricter and more predictable validation gives us the reliable foundation needed to support more flexible config in the future.
Pipelines affected by any of these changes will fail to compile after this date.
How to check if you’re affected
You can preview whether your config is affected today, before any of these changes are enabled.
Validate your config using either:
UI: Open the config editor and enable the “config next” toggle (bottom-right). It will re-validate your config automatically.
CLI: Install or update to the latest CircleCI CLI (see Installing the CircleCI local CLI), then run:
circleci config validate <path-to-config> --next
Review the errors — the output will surface any issues caused by the three breaking changes below.
Fix them — refer to the relevant section below for guidance on how to resolve each type of error. You can also use an AI agent to help resolve issues quickly.
Revalidate using the same UI toggle or CLI command to confirm all errors are resolved.
What’s changing
Expand each section to understand what’s changing and how to fix it.
1. Undeclared parameters will fail compilation (click for more details)
2. Regex engine updateNegative lookaheads (?!...)Negative lookbehinds (?<!...)Possessive quantifiers ?+, \*+, ++Backreferences \\1, \\2, etc. (click for more details)
3. End of support for version: 2.0HEREDOC syntax <<Illegal characters in job namesUnrecognized keys on job definitionsbranches: on job definitionsUnsupported keys on Docker image definitionsworking-directory vs working_directoryresource_class inside machine: executorPipeline parameter syntaxname: key on jobsCIRCLE_COMPARE_URL not available in v2.1 (click for more details)
Need help?
If you’re unsure whether your config is affected or need help with a specific fix, reply to this thread or open a support ticket.
10 posts - 8 participants
Read full topic

Основное содержимое страницы с новостью.

Схожие новости