Skip to content

v0.2.3 — profile isolation and native handlers

Choose a tag to compare

View all tags
@web3blind web3blind released this 19 Sep 15:44
v0.2.3
f922a0f

Profile isolation and native handler fixes

  • Read VK credentials, ACL/config values, connection enablement, standalone-send credentials and redaction tokens through the active Hermes profile secret scope. Missing scoped values no longer borrow process-global default-profile values.
  • Keep scoped YAML values on the current profile configuration instead of exporting them into the process environment. Accept dictionary and object config forms while preserving an existing canonical token.
  • Wire native handler factories registered by other plugins during successful VK connection.

Requires Hermes >=0.21.3; the tested released baseline remains GitHub v2026.9.14. Existing v0.2.2 registration guards and optional target-parser handling are retained. No private configuration or credentials are included.

Verification

  • 348 plugin tests passed on v2026.9.14 and upstream main d7b836ab1c0cddaafc109ed24c9a83b6191cdc88 via scripts/run_tests.sh.
  • New disposable-profile integration tests use external plugin discovery for dotenv, canonical YAML and legacy YAML, verify no token/ACL borrowing and unchanged process environment, and revisit profiles to detect contamination.
  • Native-handler regression exercises real PluginContext registration and base wiring through connect with controlled VK transport.
  • GitHub CI main/release jobs passed: https://github.com/web3blind/hermes-vk-platform/actions/runs/35452621418
  • Fresh published-source admission validation passed, including security scan: safe. Syntax/diff checks passed; no unreviewed secret findings (two explicitly synthetic fixture lines are allowlisted).

Offline checks only: no live VK E2E, production installation changes, profile changes or gateway restart.

Assets 2
Loading