Skip to content

Honor caller SDK pins in package updates - #130

Merged
woksin merged 1 commit into
mainfrom
ci/package-update-sdk-pin
Oct 1, 2026
Merged

woksin merged 1 commit into
mainfrom
ci/package-update-sdk-pin

Conversation

@woksin

@woksin woksin commented Oct 1, 2026 •

Copy link
Copy Markdown
Contributor

Changed

@woksin woksin self-assigned this Oct 1, 2026
@woksin

woksin commented Oct 1, 2026

Copy link
Copy Markdown
Contributor Author

The owner-confirmed passing updater tests for this exact SDK-pin branch are reused; no code inputs changed after preparation. Other unchanged preparation checks: cleanup-pr-artifacts suite 35/35, bootstrap-package-update-safety suite 5/5, changed YAML actionlint. git diff --check origin/main...HEAD passed again after fetching main. Workflows contains no application solution/build gate.

This PR stays separate from the bootstrap/report follow-up so the package rollout safety gate remains narrowly scoped. It installs the SDK selected by global.json without rewriting the caller's version or roll-forward policy. No live package updates, publication, schedule restoration, secrets, or merge are included. CI results still need review before any later merge.

@woksin
woksin merged commit c533e2d into main Oct 1, 2026
1 check passed
@woksin
woksin deleted the ci/package-update-sdk-pin branch October 1, 2026 17:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant