Release v0.4.22: pin installer after Bitwarden launch lookup reuse - #102
Merged
Merged
Conversation
#101: Bitwarden harness launches were listing the full vault separately for every named or project-qualified reference. Reuse parsed lookup metadata within one manifest resolution. UUID-only and empty manifests skip listing, and every launch still fetches current secret values. Also includes #99: fail closed on glued Bitwarden refs from bash 0.3.0 refresh.
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 - no behaviour change beyond what #101 already merged. Same pin-file shape as v0.4.21:
Cargo.toml,Cargo.lock,install-remote.sh,AGENTS.md,README.md(and theva update vX.Y.Zexamples so they name this pin).Why cut a release
#101 shipped after v0.4.21 was tagged. An unpinned
curl … | bashstill installs a binary without the single-listing lookup optimization. Moving the pin is what makes the optimized Bitwarden harness launch available from a product install.Also includes #99 (fail closed on glued Bitwarden refs from bash 0.3.0 refresh).
Checks
Pin-only. CI on this PR is the gate. Tagging follows merge:
.github/workflows/release.ymlfires onv*.