A change to status checks was originally scheduled for April 28, 2025. The scope of the change has been revised based on user feedback.
What is changing?
We are updating some CircleCI job statuses to better align with how we report terminal job states to VCS status checks.
Starting June 2, 2025 jobs that are currently marked as skipped will be changed to failed in CircleCI in the following situations:
- Project is abusive
- User is sanctioned
- SSH key is missing
- Server license is expired
- Parallelism limit is exceeded
Note: Status checks will not be impacted, as these jobs are already reported as failures to GitHub.
Why are we making this change?
In these cases, the failed status more accurately reflects that the job was not successful due to blocking conditions—not because of optional skips or conditional logic. This change also improves consistency across job reporting as these jobs already appear as failures in GitHub.
This is a modification of the plans announced in April for Skipped Status Will Now Return Success which will remain paused.
When will this take effect?
June 2, 2025