Skip to content

Conversation

@briceicle
Copy link
Contributor

Jira

Description

We updated our config schema to allow configuring a job to run when an upstream dependency is not run. not_run is now available as a state to use in the requires stanza, for example:

workflows:
  a:
    jobs:
      - deploy
      - release:
          requires:
            - deploy
      - notify:
          requires:
            - release: [success, failed, canceled, not_run]

Implementation details

  • Update the schema to include the new not_run requires state

This provides the ability configure a workflow job to run
when an upstream dependency is not run. `not_run` is now available as a state to use
in the requires stanza
@briceicle briceicle requested a review from a team November 21, 2025 20:31
@briceicle briceicle merged commit bd4f687 into main Nov 24, 2025
6 checks passed
@briceicle briceicle deleted the PIPE-5119 branch November 24, 2025 17:06
@henrahmagix
Copy link

Hi all, this feature looks really super useful for me and my team! It'll allow us to get rid of a buuuuuuuuuuunch of bash we have 😅 I've tried it out but it's not working as I thought it would - but also I can't find anything about it in the official documentation, so I'm guessing it isn't fully released? Is that right?

May I ask if there's a known-ish timeline for not_run to become publicly available? Thanks so much! 🙏

(the reason I'm asking here is because this pull-request is the exact change that made me aware of this job state: I have a yaml extension that checks https://www.schemastore.org/circleciconfig.json, which references https://raw.githubusercontent.com/CircleCI-Public/circleci-yaml-language-server/refs/heads/main/schema.json, which contains this change, so it popped up in my code editor as an allowable value for the requires enum ☺️)

@parkuman
Copy link
Contributor

parkuman commented Dec 9, 2025

Hi all, this feature looks really super useful for me and my team! It'll allow us to get rid of a buuuuuuuuuuunch of bash we have 😅 I've tried it out but it's not working as I thought it would - but also I can't find anything about it in the official documentation, so I'm guessing it isn't fully released? Is that right?

May I ask if there's a known-ish timeline for not_run to become publicly available? Thanks so much! 🙏

(the reason I'm asking here is because this pull-request is the exact change that made me aware of this job state: I have a yaml extension that checks https://www.schemastore.org/circleciconfig.json, which references https://raw.githubusercontent.com/CircleCI-Public/circleci-yaml-language-server/refs/heads/main/schema.json, which contains this change, so it popped up in my code editor as an allowable value for the requires enum ☺️)

Hi! Yes that's right. Unfortunately this feature isn't 100% implemented and functioning as of yet (this change to the schema was just one of the things on the todo list). The team is actively working on getting this feature out the door and you can expect a docs page explaining how all of it will fit together. I'll be sure to send that update here once it's out and ready for you to use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants