Skip to content

Release v0.4.22: pin installer after Bitwarden launch lookup reuse #102

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
JacobStephens2 merged 1 commit into from
Sep 7, 2026
Merged

Release v0.4.22: pin installer after Bitwarden launch lookup reuse #102

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,13 +12,13 @@ Also hosted: https://vaultedagent.com/AGENTS.md

Glossary for domain terms (harness, manifest, backend, …): [CONTEXT.md](CONTEXT.md).

Current release pin (product install): **v0.4.21**
Current release pin (product install): **v0.4.22**

```bash
curl -fsSL https://vaultedagent.com/install.sh | bash
# pin:
VAULTED_AGENT_VERSION=v0.4.21 curl -fsSL https://vaultedagent.com/install.sh | bash
vaulted-agent version # expect 0.4.21 (git stamp may appear in parentheses)
VAULTED_AGENT_VERSION=v0.4.22 curl -fsSL https://vaultedagent.com/install.sh | bash
vaulted-agent version # expect 0.4.22 (git stamp may appear in parentheses)
```

## What you must not do
Expand Down Expand Up @@ -80,7 +80,7 @@ elevated launches always read the machine config dir).
| Auth mode | `va auth-mode` / `va auth-mode prompt` / `va auth-mode file` |
| Interactive install-time config | `va setup` |
| Store / rotate the manager token | `printf %s "$TOKEN" \| sudo va setup bitwarden --set-token` |
| Replace the installed launcher binary | `va update` (latest GitHub release) / `va update v0.4.21` |
| Replace the installed launcher binary | `va update` (latest GitHub release) / `va update v0.4.22` |
| Uninstall | `sudo va uninstall` |

Launcher flags **before** the harness name: `-p` / `--prompt-auth`,
Expand Down
2 changes: 1 addition & 1 deletion Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "vaulted-agent"
version = "0.4.21"
version = "0.4.22"
edition = "2021"
description = "Launch AI coding agents with vault-resolved secrets in-process"
license = "MIT"
Expand Down
2 changes: 1 addition & 1 deletion MIGRATION.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ refresh. `va update` (or a reinstall) is the way off that writer.
`va update` downloads a GitHub release asset for this OS/arch and overwrites
the running launcher (`current_exe`, usually `/usr/local/bin/vaulted-agent`).
Default target is `VAULTED_AGENT_VERSION`, else the latest GitHub release.
`va update v0.4.21` pins. `--check` and `--dry-run` write nothing.
`va update v0.4.22` pins. `--check` and `--dry-run` write nothing.

This is not `install.sh`. Harnesses, manifests, and token files stay put. If
the dest is not writable, it retries with `sudo install`. `va` and
Expand Down
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ auth**: paste the vault token at each launch so even the manager token need not
live on disk. Same scrub/resolve/exec path for one-shot tools via `va run`.

**macOS and Linux.** Product page: [vaultedagent.com](https://vaultedagent.com/) ·
Latest: [v0.4.21](https://github.com/JacobStephens2/vaulted-agent/releases/tag/v0.4.21)
Latest: [v0.4.22](https://github.com/JacobStephens2/vaulted-agent/releases/tag/v0.4.22)
(Rust runtime; Bash retired — see [MIGRATION.md](MIGRATION.md))

## Contents
Expand All @@ -37,7 +37,7 @@ curl -fsSL https://vaultedagent.com/install.sh | bash

Installs `vaulted-agent` and `va`, detects agents on PATH (`claude`, `codex`,
`grok`, `kimi`, `agy`) and `bash`, and can ask for a vault backend + auth mode. Pin:
`VAULTED_AGENT_VERSION=v0.4.21` (or `latest`).
`VAULTED_AGENT_VERSION=v0.4.22` (or `latest`).

### 2. Wire a vault

Expand Down Expand Up @@ -91,7 +91,7 @@ va refresh # build/update a refs file (Bitwarden or 1Password)
va edit-manifest # open a refs file in $EDITOR; check on save
va auth-mode prompt # or: file
va update # replace the installed binary from the latest GitHub release
va update v0.4.21 # pin; --check / --dry-run do not write
va update v0.4.22 # pin; --check / --dry-run do not write
sudo va uninstall
```

Expand Down Expand Up @@ -230,7 +230,7 @@ you $ va claude --resume <session-id>
blast-radius control, not containment.

Writeup: [One vault, three agents](https://stephens.page/blog/one-vault-three-agents-writing-the-pattern-down-found-five-bugs/) ·
Latest: [v0.4.21](https://github.com/JacobStephens2/vaulted-agent/releases/tag/v0.4.21)
Latest: [v0.4.22](https://github.com/JacobStephens2/vaulted-agent/releases/tag/v0.4.22)

## The honest claim

Expand Down
2 changes: 1 addition & 1 deletion install-remote.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ REPO="${VAULTED_AGENT_REPO:-JacobStephens2/vaulted-agent}"
# Default pin. Overridden by VAULTED_AGENT_VERSION=... or "latest".
# Bump this when cutting a release so unpinned one-liners stay intentional.
# Must match a published GitHub release tag (and Cargo.toml version).
DEFAULT_VERSION="v0.4.21"
DEFAULT_VERSION="v0.4.22"
VERSION="${VAULTED_AGENT_VERSION:-$DEFAULT_VERSION}"
GITHUB_API="${GITHUB_API:-https://api.github.com}"
GITHUB="${GITHUB:-https://github.com}"
Expand Down
Loading