Skip to content

Releases: Avnsx/win11_release_guard

v0.3.3

12 Jun 02:03

Choose a tag to compare

win11_release_guard 0.3.3

v0.3.2

10 Jun 00:28

Choose a tag to compare

win11_release_guard 0.3.2

v0.3.1

08 Jun 02:09

Choose a tag to compare

Release of win11_release_guard version 0.3.1

➡️ View the full Changelog here: https://avnsx.github.io/win11_release_guard/wiki/changelog/#v0.3.1

Version 0.3.1 documents and hardens the current win11_release_guard worktree: package/runtime version identity, signed public policy feed handling, static GitHub Pages output, strict JSON trust boundaries, tagged source releases, and the PyPI Trusted Publishing lane. Windows release semantics are unchanged: existing broad-fleet devices target Windows 11 25H2; 26H1 remains excluded for existing-device targeting; local build evidence outranks display labels; WUA remains optional secondary evidence; policy schema_version and public api_version are not program versions.

v0.3.0

05 Jun 05:17

Choose a tag to compare

win11_release_guard 0.3.0

Release v0.3.0 publishes the hardened signed-policy, Pages, wiki, GitHub Release, and PyPI packaging lanes for win11_release_guard.

Highlights

  • Package/runtime version: 0.3.0.
  • Package name: win11_release_guard; PyPI canonical project URL: https://pypi.org/project/win11-release-guard/.
  • License metadata: GPL-3.0-only, with LICENSE.txt included in source and wheel metadata.
  • GitHub Release asset: win11_release_guard-source.zip, generated by the release workflow clean-archive lane.
  • PyPI publishing: separate .github/workflows/pypi-publish.yml lane using Trusted Publishing / GitHub OIDC and environment pypi; no PyPI API token or Twine credentials.
  • Pages publishing: workflow-generated static site, signed policy JSON, detached Ed25519 signature, manifest, and /api/v1 aliases.
  • Runtime trust model: signed public JSON policy remains primary; WUA is optional secondary evidence only.
  • Windows targeting semantics: existing broad-fleet devices target Windows 11 25H2; 26H1 is excluded for existing-device feature-update targeting.
  • Local detection: build-number evidence remains authoritative over ProductName/Caption display labels.
  • Hardening: strict JSON loading, signature/key lifecycle rules, cache/freshness semantics, source diagnostics dashboard, clean archive exclusions, action pinning audit, and secret-material scanning.

Verification and Docs

Runtime clients use the signed public JSON feed and detached Ed25519 signature. GitHub Release assets are distribution artifacts, not policy trust roots.