Repository navigation
chore: sync main after release v0.16.2 - #549
Merged
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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.
Summary
Immediately synchronize released main commit
0f2173d03a63c73b9cf4a4d9978136cc5dec2909back into develop after the legitimatev0.16.2tag, using a normal merge and normal PR controls.This synchronization carries only final release metadata and the completed changelog from #548. It introduces no feature work, preserves both documentation commits, and leaves
Unreleasedempty with one section each for 0.16.2 and 0.16.1.Verification
The merged tree matches released main. Required final-candidate full local suite and exact-head staging already passed before tagging. This PR must pass its current full develop-target CI before normal merge. After merge,
git log --oneline origin/develop..origin/mainmust print nothing.Production publication is tracked in https://github.com/Azure/agentops/actions/runs/42309502860. Issue #499 stays open until actual publication is verified. Consumers must regenerate copied workflow YAML and configure and validate the documented protected controls and exclusive status identities. Publishing code does not configure those controls.