Skip to content

RELEASES.md

Latest commit

 

History

History
142 lines (120 loc) · 7.37 KB

RELEASES.md

File metadata and controls

142 lines (120 loc) · 7.37 KB
Raw

OpenSquilla Releases

Version Tag Date Notes
0.5.0rc2 v0.5.0rc2 2026-07-06 Preview: provider/router recovery, Web UI upload refresh, desktop/session fixes, and CI contract repair
0.5.0rc1 v0.5.0rc1 2026-07-04 Preview: Model Ensemble routing, Control UI, managed execution, OpenTUI, and portable retirement
0.4.1 v0.4.1 2026-06-30 Desktop reliability, six-language client support, telemetry accuracy, router packaging, and mainline governance
0.4.0 v0.4.0 2026-06-27 Control UI refresh, manual MetaSkills, coding mode, search expansion, and runtime hardening
0.3.0 v0.3.0 2026-05-31 MetaSkills, Health Doctor, tool compression, and docs release
0.2.1 v0.2.1 2026-05-21 0.2 maintenance release
0.2.0 v0.2.0 2026-05-20 0.2 release
0.2.0rc1 v0.2.0rc1 2026-05-19 Second public preview
0.1.0rc1 v0.1.0rc1 2026-05-12 First public preview

0.5.x preview releases publish Electron desktop installers, updater metadata, the versioned Python wheel, and SHA256SUMS:

  • OpenSquilla-<version>-mac-arm64.dmg
  • OpenSquilla-<version>-mac-arm64.zip
  • OpenSquilla-<version>-win-x64.exe
  • latest-mac.yml
  • latest.yml
  • *.blockmap
  • opensquilla-<version>-py3-none-any.whl
  • SHA256SUMS

0.5.x preview releases are GitHub pre-releases and must not be marked as Latest. They do not publish Windows portable zips, Windows portable latest aliases, public wheelhouse zips, macOS portable zips, or Linux portable zips. Existing 0.4.x release pages keep their legacy Windows portable downloads for historical compatibility, but new 0.5.x releases only publish Electron desktop installers plus the Python wheel.

The Windows desktop installer is currently unsigned; release notes and download sections must link to docs/code-signing-policy.md until a signing workflow is approved and enabled. Windows browser downloads may carry Mark-of-the-Web, and SmartScreen, Smart App Control, enterprise policy, and unsigned binary reputation must be checked on a real Windows machine before broad promotion.

GitHub source archives remain available for code review and developer reference; source installs should use git clone plus Git LFS. Python wheel filenames must remain versioned because installers validate the version segment inside the wheel filename.

Release docs must describe the unified non-user-initiated network observability switch. OPENSQUILLA_PRIVACY_DISABLE_NETWORK_OBSERVABILITY=true or:

[privacy]
disable_network_observability = true

disables automatic install telemetry, passive update checks, and desktop startup auto-update checks. The legacy compatibility environment variables OPENSQUILLA_TELEMETRY_DISABLED=true and OPENSQUILLA_UPDATE_CHECK_DISABLED=true remain honored. Manual user-initiated release, download, or update checks may still contact GitHub after user intent.

Preview README install commands must use tag-pinned URLs such as:

  • https://github.com/opensquilla/opensquilla/releases/download/v0.5.0rc2/OpenSquilla-0.5.0-rc2-mac-arm64.dmg
  • https://github.com/opensquilla/opensquilla/releases/download/v0.5.0rc2/OpenSquilla-0.5.0-rc2-win-x64.exe
  • https://github.com/opensquilla/opensquilla/releases/download/v0.5.0rc2/opensquilla-0.5.0rc2-py3-none-any.whl

Release SOP

  1. Verify git status is clean before starting release prep.

  2. Confirm the latest origin/main SHA is the intended release baseline and that its required CI run completed successfully.

  3. Prepare a release PR from origin/main: update version metadata, CHANGELOG.md, RELEASES.md, CONTRIBUTORS.md, release notes, README download sections, install scripts, workflow asset contracts, and release tests.

  4. Confirm release notes and README download sections link to PRIVACY.md, THIRD_PARTY_NOTICES.md, and docs/code-signing-policy.md; do not claim Windows code signing before it is enabled. Confirm privacy wording documents the unified network observability switch and legacy opt-out environment variables.

  5. Bump pyproject.toml, uv.lock, desktop/electron/package.json, desktop/electron/package-lock.json, install.sh, and install.ps1 to the release version.

  6. Run the focused release contract tests locally, then open and merge the release PR only after review and CI pass.

  7. Fetch origin main --tags, verify the merged origin/main SHA and CI one more time, then create the annotated tag on that exact SHA:

    git tag -a v0.5.0rc2 <verified-sha> -m "OpenSquilla 0.5.0 Preview 2"
git push origin v0.5.0rc2

  8. Wait for .github/workflows/wheelhouse-release.yml, then review the draft GitHub Release. For v0.5.0rc2, confirm it is a pre-release, is not marked Latest, and contains only the Electron installers, updater metadata, versioned wheel, SHA256SUMS, plus GitHub's generated source archives. It must not contain OpenSquilla-*-portable.zip or OpenSquilla-windows-x64-portable.zip.

  9. Publish the GitHub Release only after maintainer confirmation, then run the post-publish tag URL checks:

    curl --fail --head --location https://github.com/opensquilla/opensquilla/releases/download/v0.5.0rc2/OpenSquilla-0.5.0-rc2-mac-arm64.dmg
curl --fail --head --location https://github.com/opensquilla/opensquilla/releases/download/v0.5.0rc2/OpenSquilla-0.5.0-rc2-win-x64.exe
curl --fail --head --location https://github.com/opensquilla/opensquilla/releases/download/v0.5.0rc2/opensquilla-0.5.0rc2-py3-none-any.whl
curl --fail --head --location https://github.com/opensquilla/opensquilla/releases/download/v0.5.0rc2/SHA256SUMS

  10. If a release tag is wrong before publication, stop and repair it explicitly: delete the local and remote tag, recreate it on the verified SHA, push it, and rerun Release Assets. If a draft release already exists for the wrong tag, delete the draft release before moving the tag so stale assets cannot survive the repair.

  11. For subsequent previews: bump the package version, docs, workflow contracts, and tag to the next preview version, for example 0.5.0rc2 / v0.5.0rc2. Preview GitHub Releases must remain pre-releases and use tag-pinned README URLs until a later stable release is intentionally promoted.

GitHub-only release checks

These checks cannot be fully proven by local artifact generation:

  • The tag exists on GitHub and matches pyproject.toml.
  • The release workflow can fetch hydrated Git LFS router assets.
  • The draft GitHub Release title is OpenSquilla 0.5.0 Preview 2.
  • The draft GitHub Release is marked Pre-release and is not marked Latest.
  • Preview GitHub Releases contain the Electron installers, updater metadata, versioned wheel, and SHA256SUMS after gh release upload --clobber.
  • Preview GitHub Releases do not contain Windows portable zips or portable latest aliases.
  • After a preview GitHub Release is published, the tag-pinned release asset URLs resolve.
  • Windows browser downloads may carry Mark-of-the-Web; SmartScreen, Smart App Control, enterprise policy, and unsigned binary reputation must be checked on a real Windows machine.

Why preview package versions use rc

Release assets are distributed as built artifacts, so the package filename, installer name, wheel name, and tag should describe the same preview build. PEP 440 accepts 0.5.0rc2, while the public GitHub Release title can use the friendlier name "OpenSquilla 0.5.0 Preview 2".