chore: synchronize main release ancestry#49
Merged
Conversation
Fixes the privacy scanner false negative tracked in #1. Validated by focused regression tests, full CI, dependency review, and independent Agent review.
First public Agent-native release with review-gated execution, verified Feishu Task mutations, safe Agent presentation, and tag-only provenance-aware release automation.
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.
Problem
The v0.1.0 squash release left main and develop with equivalent release trees but divergent ancestry, causing the reviewed v0.1.1 promotion PR to conflict.
Change
Verification
git diff 7ba833d..11c33b9is emptyMerge boundary
This PR must use a normal merge once, not squash, so the main parent remains in develop ancestry. Repository merge settings and develop linear-history protection will be restored immediately after the merge attempt. All required checks, PR requirements, force-push/deletion protections, and strict status checks remain active.
Closes #48