Adding release hygiene workflows#23621
Conversation
|
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Have you signed the CLA already but the status is still pending? Recheck it. |
Go Test Coverage: 63.2%See the workflow run for the full per-package breakdown and downloadable HTML report. |
Codecov ReportCaution This repository is currently using the Sentry GitHub App to receive Codecov PR comments. This integration will be deprecated on July 8, 2026. Please install the Codecov GitHub App to continue receiving coverage reports on your pull requests. Additional details and impacted files@@ Coverage Diff @@
## main #23621 +/- ##
==========================================
- Coverage 65.55% 61.00% -4.56%
==========================================
Files 944 778 -166
Lines 114480 88427 -26053
==========================================
- Hits 75049 53945 -21104
+ Misses 32434 29558 -2876
+ Partials 6997 4924 -2073 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Description
Adding release hygiene workflows that introduce two GitHub Actions workflows supporting release engineering hygiene checks. Non-blocking initially; results posted internally.
Please find the expected behavior in the below doc:
https://ibm.sharepoint.com/:w:/r/sites/hermes/_layouts/15/doc2.aspx?sourcedoc=%7B2A3ECECB-1C1A-4D8B-A769-07E70225D76C%7D&file=HCPINF-HashiGuard%20Server%20Side.docx&action=default&mobileredirect=true
These checks have been implemented as per this RFC: https://ibm.sharepoint.com/:w:/r/sites/hermes/_layouts/15/doc2.aspx?sourcedoc=%7B3744C6A5-9537-4EB9-B788-90ABF654B2E9%7D&file=IPS-HashiGuard%20-%20Unified%20CE-ENT%20Codebase%20Protection%20and%20Release%20Orchestration.docx&action=default&mobileredirect=true
Testing & Reproduction steps
Links
PR Checklist
PCI review checklist
I have documented a clear reason for, and description of, the change I am making.
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.