Release v1.0.14 - #148
Merged
Merged
Conversation
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.
Version bump only — eight files, one line each. No product change.
What this release carries
Everything merged since
v1.0.13:v1.0.13cannot be built from a fresh clone: its AppImage plugin is pinned to linuxdeploy's rollingcontinuoustag, which upstream rewrote on 2026-08-01, sojust updies on a checksum mismatch. Also seeds the Alertmanager config and adds a CI guard on the pinned digests.OPSWARDEN_BIND_ADDR, so a nativejust devcan coexist with the Compose stack./api/auth/*, closing the one gap found by a manual audit of every externally reachable surface. Plus the README collaboration limits VIGIL requires, and two dead endpoints removed.brace-expansionpast a freshly published mitigation bypass that had turnedmainred on its own.Why tag now
Two reasons beyond routine.
A juror cloning
v1.0.13gets a broken build. That tag predates #143, sogit checkout v1.0.13 && just upstill fails on the stale pin. Only a new tag makes the released artifact reproducible.The release pipeline itself is untested. #140 bumped
tauri-actionto v1.0.0 andattest-build-provenanceto v4 insiderelease.yml— a workflow that only runs on a tag, so no CI run has ever exercised those changes. This tag is what validates them.Blast radius
release.ymlonly: quality gate, E2E, desktop packages, server and web images with provenance attestations, GitHub Release. Production deployment staysworkflow_dispatch— nothing ships to prod from this tag.