[skip changelog] Add workflow to check for problems with certificates #1071
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.
If the certificates fail verification, a notification will be posted on the #team_tooling Slack channel.
If the certificates expire in less than 30 days, a notification will be posted on the #team_tooling Slack channel.
Please check if the PR fulfills these requirements
before creating one)
our contributing guidelines
Feature
It's possible that the macOS code signing certificate could expire before the maintainers notice that it needs to be renewed.
A scheduled CI workflow checks the CI certificate for validity and pending expiration. If the certificate is found to be invalid or will expire in less than 30 days, a notification is posted to a Slack channel.


(above notification is from a simulated pending certificate expiration, it would normally only occur if there was <30 days)
The workflow is configured in a way that allows it to support checking additional certificates.
No.
Demonstration workflow runs: