GitVaulty 4.2.0

• Restore full recipient registry v3 support across the CLI, VS Code extension, and JetBrains
  plugin while preserving v3 on every normal write.
• Add gitvaulty registry upgrade --check and an explicit, verified v3-to-v4 migration that
  replaces public identities, signs group policies, and re-encrypts affected ciphertext.
• Show a non-blocking registry upgrade notice once per clone. Unknown future registry versions
  continue to fail closed.

GitVaulty 4.1.1

• Republish the 4.1.0 empty-placeholder editing feature after making its VS Code extension-host
  validation portable across Windows and Unix line endings; there are no user-facing behavior
  changes in this patch.

GitVaulty 4.1.0

• Initialize an unregistered zero-byte *.gitvaulty placeholder when it is opened for editing
  through gitvaulty edit or VS Code, using the repository's default group access.
• Preserve existing authorization and corruption errors for non-empty unregistered ciphertext and
  empty files that are already registered.

GitVaulty 4.0.0

• Select specific files with positional paths, such as gitvaulty materialize .env config/secrets.yaml.
• Reassign -f and --force to explicitly replace modified, untracked regular plaintext with the
  encrypted source.
• Continue rejecting tracked plaintext, symlinks, directories, unsafe paths, and unauthorized files
  even when force is requested.
• Remove the materialize --file <path> interface. Update scripts to use positional paths.

GitVaulty 3.0.3

• Prevent VS Code from reporting a false reload-before-save error after it successfully updates an
  encrypted file.

GitVaulty 3.0.2

• Publish the VS Code extension as stable by removing its Marketplace Preview designation.

GitVaulty 3.0.1

• Add stable GitVaulty support for compatible JetBrains IDEs through JetBrains Marketplace.
• Publish the CLI, native editor runtimes, VS Code extension, and JetBrains plugin from one shared
  vX.Y.Z release tag.
• Automate signed JetBrains plugin publication and attach verified editor runtimes to each GitHub
  release.

GitVaulty 3.0.0

GitVaulty 3.0.0 makes the GitVaulty-namespaced key-file variable the only supported master-identity file override.

Highlights

• GITVAULTY_AGE_KEY_FILE is now the only supported master-identity file override.
• SOPS_AGE_KEY_FILE is intentionally ignored during GitVaulty identity resolution.
• GitVaulty continues scrubbing SOPS_AGE_KEY_FILE before invoking SOPS or wrapped commands, preventing child processes from loading an unintended private key.
• The major-release CLI demo contract was reviewed. It already uses GITVAULTY_AGE_KEY_FILE exclusively, so the reviewed 2.0 recording remains current.

Required 2.x upgrade step

Rename the environment variable while keeping the same identity file:

export GITVAULTY_AGE_KEY_FILE=/secure/identity

The identity bytes, public recipient, signing key, repository policies, and encrypted files do not change. Existing ciphertext does not need to be re-encrypted.

GitVaulty 2.0.0

GitVaulty 2.0.0 makes the extensionless global master identity path canonical and includes the latest registration and documentation improvements.

Highlights

• GitVaulty now reads and writes the default master identity at ~/.config/gitvaulty/identity on Unix-like systems and %APPDATA%\gitvaulty\identity on Windows.
• The former identity.txt default is intentionally not read, moved, or used as a fallback.
• gitvaulty user register now prompts with the suggested system username when no username is supplied.
• The access-control demo was regenerated and visually reviewed against the major-release scenario contract; the scenario remains current.

Required 1.x upgrade step

Before running 2.0.0, users with only the former default file should rename it:

mv ~/.config/gitvaulty/identity.txt ~/.config/gitvaulty/identity

If the extensionless identity already exists, do not overwrite it. Preserve both files until access is verified. Renaming the same valid master identity does not change its public recipient or signing key, so existing encrypted files do not need to be re-encrypted.

GitVaulty for JetBrains 0.1.1

Refreshes the signed native runtime and validates automated delivery to JetBrains Marketplace. There is no intentional editor behavior change; the release includes digest-verified runtimes for macOS, Linux, and Windows.