Repository navigation
[doc] ship security reporting and support policy (ENG-11) - #38
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #38 +/- ##
=======================================
Coverage 87.99% 87.99%
=======================================
Files 23 23
Lines 1166 1166
=======================================
Hits 1026 1026
Misses 108 108
Partials 32 32 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Release archives contained no security contact or supported execution boundary, and the general contact section directed every report to public issues. Add a private reporting policy, document latest-release security support and the controlled-script boundary, and ship it with every new archive.
Refs STAR-28 (ENG-11), CLI delivery portion. The exact archive-member check now requires the policy for candidates while preserving the immutable v0.1.2 rollback baseline. Organization-wide adoption remains separate.
Validation: full build, race twice, vet and format; exact Go 1.26.8 Docker build/race; actual six-target snapshot build and native macOS install/upgrade/rollback rehearsal. The new archive contract rejects an otherwise valid candidate missing the policy and still accepts the original baseline. CI repeats installation, e2e and rollback on all six native targets.