Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
Author
|
Superseded by #4767, which uses a branch on dotnet/SqlClient rather than a fork. |
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.
Description
SqlClientNextVersioncurrently requires manual updates after releases or changes to the milestone plan. This adds milestone-closure and weekly reconciliation automation to propose version-bump PRs against the owning branch (mainorrelease/X.Y).The automation selects the next open milestone in the series, creates a patch milestone after a closure if needed, and skips stale events and legacy branches. Weekly runs can move
mainto the next unbranched series after a release branch is cut, or update an existing automation PR when a preview is discarded. It does not overwrite unrelated PR changes. Documentation covers the lifecycle. No public API or runtime behavior changes.Generated PRs use
GITHUB_TOKEN, so ordinarypull_requestchecks do not automatically trigger; a follow-up commit using a non-default token is needed before merging.Issues
N/A
Testing
19 targeted Bats scenarios passed, covering branch routing, version selection, weekly reconciliation, duplicate/retry behavior, legacy branches, and failures. Bash syntax, workflow YAML parsing, and
git diff --checkpassed. No live milestone or PR was created as a test.Guidelines
Reviewed the repository contribution and versioning guidance; updated package-version instructions and script-test documentation.