v1.0.5

What's Changed

• fix(teams): align inherited member metadata by @heeyeon01 in #96
• release/v1.0.5 by @jh-lee-cryptolab in #97

Full Changelog: v1.0.4...v1.0.5

v1.0.4

What's Changed

• fix: allow deleting admin member state by @heeyeon01 in #94
• Release v1.0.4 by @jh-lee-cryptolab in #95

Full Changelog: v1.0.3...v1.0.4

v1.0.3

What's Changed

• Release v1.0.3: default teams to tree·detail view, post-install browser open, tab title by @jh-lee-cryptolab in #93

Full Changelog: v1.0.2...v1.0.3

v1.0.2

What's Changed

• fix(updater): handle systemd cross-mount publishing by @heeyeon01 in #91
• Release v1.0.2: console API username contract fix, workspace reconnect, installer/updater fixes by @jh-lee-cryptolab in #92

Full Changelog: v1.0.1...v1.0.2

v1.0.1

What's Changed

• docs: prepare v1.0.0 release badge by @esifea in #89
• refactor(workspace): move lifecycle actions to modal top-right as TextButtons by @geuna0204 in #90

Full Changelog: v1.0.0...v1.0.1

v1.0.0

First production release of Rune Console.

v0.4.0

⚠ BREAKING CHANGES

No in-place upgrade from v0.3.x — the server must be reinstalled. Your FHE keys and encrypted indexes carry over unchanged; what breaks is the deployment and config format, and there is no automated config migrator.

• Vault rewritten in Go as the single binary runevault (#61, #68). Python/Docker deployments cannot be upgraded in place — reinstall via install.sh. On-disk keys (<keys.path>/<key-id>/{Enc,Sec,Eval}Key.json) are read natively by envector-go-sdk, so no key migration is needed.
• Configuration consolidated into runevault.conf (YAML) — the env-var fallback (VAULT_TLS_DISABLE, VAULT_TEAM_SECRET, VAULT_AUDIT_LOG, …) is removed with no migration helper. Tokens/roles remain file-based via tokens.roles_file / tokens.tokens_file indirection.
• Admin transport moved from HTTP to a Unix domain socket — 127.0.0.1:8081 → /opt/rune-vault/admin.sock (mode 0600). Update any admin tooling.

---

What's New

Single Go binary runevault (#68)

• Entire vault reimplemented in Go; no Python runtime, no pyenvector dependency
• Built on github.com/CryptoLabInc/envector-go-sdk
• Daemon lifecycle delegated to the OS service manager (systemd / launchd) instead of Docker

Production installer (install.sh)

• --target local|aws|gcp|oci, SHA256SUMS checksum verification, systemd/launchd service registration, and an --uninstall flow
• Dev installer scripts/install-dev.sh for local/CSP testing without GitHub releases
• runevault group lets members run the CLI without sudo

Multi-CSP provisioning

• Terraform-based provisioning for AWS, GCP, and OCI: preflight CLI/auth checks, cloud-init bootstrap, CA-cert SCP polling
• CSP uninstall flow wrapping terraform destroy

New CLI subcommands

• runevault status — daemon + admin-socket health
• runevault logs — audit log tail
• EnsureVault startup hook activates keys and ensures the index on first run

Release & distribution

• Multi-platform release pipeline (linux/darwin × amd64/arm64) with a SHA256SUMS checksum manifest
• Cloud VM images bumped to Ubuntu 24.04 LTS

Removed

• Python sources, docker-compose.yml, Dockerfile, and the GHCR-published Docker image
• pyenvector runtime dependency
• Env-var configuration fallback (VAULT_TLS_DISABLE, VAULT_TEAM_SECRET, VAULT_AUDIT_LOG, …)

Upgrade Guide

1. Reinstall via install.sh --target <local|aws|gcp|oci> — no in-place upgrade from the Python deployment.
2. Reuse your existing keys: point keys.path in runevault.conf at your current vault-keys directory. Keys and encrypted indexes (1024d) are preserved — do not regenerate.
3. Recreate configuration in runevault.conf (env vars are gone); reference your token/role files via tokens.roles_file / tokens.tokens_file.
4. Update admin tooling to use the Unix domain socket instead of the old HTTP admin port.
5. Verify with runevault status.

Full Changelog: v0.3.0...v0.4.0

v0.3.0

⚠ BREAKING CHANGES

This release is NOT compatible with v0.2.x. Existing encrypted indexes must be re-created.

• Embedding dimension changed from 768 to 1024: Default embedding model switched from bge-base-en-v1.5 (768d, English-only) to Qwen3-Embedding-0.6B (1024d, multilingual). All previously encrypted vector data is incompatible with this version. There is no automatic migration — indexes must be rebuilt from source with the new model.

---

What's New

Multilingual Embedding Support (#53)

• Replaced bge-base-en-v1.5 (English-only, 768d) with Qwen3-Embedding-0.6B (100+ languages, 1024d)
• EMBEDDING_DIM updated across vault_core.py, docker-compose.yml, all deployment scripts, and install.sh

Upgrade Guide

1. Re-create all encrypted indexes with Qwen3-Embedding-0.6B (1024d)
2. Update EMBEDDING_DIM to 1024 in any custom deployment configs
3. Pull the new Docker image: docker pull ghcr.io/cryptolabinc/rune-admin:v0.3.0

Full Changelog: v0.2.2...v0.3.0

v0.2.1

What's Changed

• [FIX] Restore install dir ownership in deploy_local() by @heeyeon01 in #40
• feat(vault): add token rotation command (#24) by @jh-lee-cryptolab in #41

Full Changelog: v0.2.0...v0.2.1

v0.2.0

What's Changed

• feat: implement per-user token auth for Vault (#18) in #36
• feat: per-user token auth for Vault in #38

Full Changelog: v0.1.3...v0.2.0