Repository navigation
ci: activate 14-day pinned candidate observation - #46
Merged
Merged
Conversation
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
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.
Authorization and initial evidence
Owner approved 14 consecutive days and explicitly requested starting. Initial run https://github.com/zackpratamaa/safe-change/actions/runs/39656102889 completed successfully on Ubuntu, Windows, and macOS, testing frozen source
5e99b4f12b27890df22ea5bb4e4e0151c68b89ecrather than controller revision.Changes
blocked; record real UTC start date and initial source-bound run. End date remains null, independent audit not started, human GA approval false.Limits
Periodic regression observation, not one continuous 336-hour process, a completed soak, or production stability proof. Exact workload timestamps are retained in artifacts; conservative earliest evaluation 2026-11-05T00:00:00Z does not promise success. Different release SHAs still require source-bound validation.
Conflict remediation
Replaces #45 with a clean branch based on main after #44. Workflow bytes are unchanged from the successfully executed initial observation. No job cancelled and no failed result hidden. No application, version, license, tag or release changes.
Validation
Initial observation is successful. This clean PR's own hosted checks must pass before merge.