As far as I understand, matches is available as a logic statement but not as an expression operator. Is that right? Any idea why not? Expressions are way more readable than collections of logic statements, and matches seems like it would fit pretty cleanly, eg:
when: |
a.var == 1 and b.var matches "c|d"
1 post - 1 participant
Read full topic
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | [Breaking Change] Regex Engine Update for Config | 0 | 13.49 | 28-05-2026 |
| 2 | Breaking Changes: Config Compilation Updates — September 21, 2026 | 0 | 14.42 | 11-06-2026 |
| 3 | Https://discuss.circleci.com/t/circleci-community-code-of-conduct/36564?u=milezdeep9 | 0 | 30 | 12-03-2026 |
| 4 | Customizing the OIDC sub claim to drop the user/ segment | 0 | 5.93 | 09-06-2026 |
| 5 | Native GitHub Actions YAML Workflow Support — Preview | 0 | 6.81 | 22-09-2026 |
| 6 | (Breaking Change) Undeclared Parameters Will Fail Config Compilation | 0 | 12.74 | 08-06-2026 |
| 7 | Intermittent CloudFront 403 when triggering pipelines via API v2 | 0 | 11.77 | 12-06-2026 |
| 8 | Intermittent pipeline inconsistencies when running parallel jobs with shared dependencies | 0 | 7.54 | 19-06-2026 |
| 9 | PocketCI - CircleCI in your pocket | 0 | 8.79 | 29-09-2026 |
| 10 | Guys i am in free tier of circle CI and i cant setup private repo? | 0 | 5.91 | 20-06-2026 |