Repository navigation
Releases: cbs-consulting/virtual-key-mapper
Releases · cbs-consulting/virtual-key-mapper
Release list
v0.1.2
- The local sign-in extension
cbs-consulting.vkm-hostis now called "Virtual Key Mapper: host
sign-in": the Marketplace still holds the old display name for the removedvkm-local. Messages
that ask you to install it name its ID.
v0.1.1
- The local sign-in extension is now
cbs-consulting.vkm-host(filevkm-host.vsix): the
Marketplace no longer listscbs-consulting.vkm-localand does not accept its name again.
Uninstallvkm-localand installvkm-host; the settings (vkm.localCommand,
vkm.localProfiles) stay the same.
v0.1.0
- First public version, under the name Virtual Key Mapper: the command is
vkm, the
packagevirtual-key-mapper, the repository file.vkmand the environment variables
VKM_*. The VS Code extensions arecbs-consulting.vkm(Copilot Chat) and
cbs-consulting.vkm-local(local sign-in for dev containers, SSH and WSL). - Licensed under the Apache License 2.0.
- Published on PyPI (
virtual-key-mapper) by a release workflow with one shared version; the
VS Code extensions (cbs-consulting.vkm,cbs-consulting.vkm-local) are attached to each
GitHub release and uploaded to the Visual Studio Marketplace by hand. - Labels: requests carry key/value labels such as
customer = "acme"andproject = "webshop", defined in the central rules document
(version"2.0") or the profile, with required labels, allowed values and per-label
sources. Each label is resolved on its own from--label KEY=VALUE,VKM_LABEL_<KEY>,
vkm repo bind --label, a.vkm[labels]table or a central rule. Gateway adapters
declare outputs; LiteLLM sendsx-litellm-tags(defaultKEY:VALUEper label,
overridable with${KEY}formats) and spend-log metadata with all labels and their
sources. Newvkm labels list|values;profile add/update --label/--output;
"Assign labels" and a status bar with all label values in VS Code. See
docs/labels.md.