You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(ci): repair Windows-branch VM runtime and K3s installer pins #5734
As the maintainer validating OpenShell Windows PR #5327, I need its VM and Kubernetes CI dependencies to fetch reproducibly so the supervisor change can be reviewed and merged independently of CI pin repairs.
Description
Refresh the three stale VM-runtime artifact SHA-256 pins to the values already used on main. Fetch the K3s installer from the configured release tag and verify that exact script, preserving K3s 1.36.3+k3s1.
Context
The repairs were validated with #5327 at 9dbf1690105292a4bb6681fb7bfaf2ee3e577bc6. The operator requested splitting these two CI commits into a standalone PR and merging it before #5327, with the existing CI evidence attached and no additional CI rerun.
Definition of Done
Only the VM-runtime hash pins and K3s installer URL/checksum change.
Existing artifact and K3s versions are retained.
Attach the completed Branch Checks, native Windows, external Windows, and full E2E results with their tested commit identified.
Merge the standalone repair before the supervisor PR.
Merged the standalone pin repair in #5736 (f0db2ee8119a50980ddb5fa89a561a24677bed96), followed by #5327 (8a93cab12e04416af21d052a5c9007f17520bb8d). Verified the first commit changes only the two pin files; the second changes only the supervisor and policy documentation. Existing CI evidence is attached to #5736, with the tested source commit and operator-approved rerun waiver stated explicitly.
Activity
fix(ci): repair Windows VM runtime and K3s installer pins (#5736)