Skip to content

Chameleon

v2.22.3 Bugfix

This release fixes issues for SREs watching stability and regressions.

✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

ai-coding-assistant archetype ast-analysis claude-code claude-plugin code-conventions
+12 more
code-review code-style developer-tools javascript linter mcp mcp-server prompt-engineering python ruby rails typescript

Summary

AI summary

Fixed chameleon silently no‑ops inside linked git worktrees by resolving profiles and trust through the main worktree.

Full changelog

Fixed

  • chameleon no longer silently no-ops inside a linked git worktree. A
    worktree's .chameleon/ is gitignored and lives only at the main worktree, so
    profile and trust lookups (keyed on the worktree's own path) missed entirely:
    no archetype injection, no idiom enforcement, no trust, with no signal that
    anything was off. Profile and trust now resolve through the worktree's .git
    gitdir: pointer to the main worktree, so a worktree inherits the main
    checkout's committed profile and trust grant with no extra /chameleon-trust
    and regardless of where the worktree lives on disk (under the repo, a sibling,
    or a fully custom path). The worktree stays the identity/archetype root, so
    repo_id and path-relative archetype matching are unaffected. Strictly
    additive: a new resolve_profile_root helper returns the input root unchanged
    for every non-worktree layout, so standalone repos and monorepo workspaces
    behave byte-identically.

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track Chameleon

Get notified when new releases ship.

Sign up free

About Chameleon

All releases →

Related context

Earlier breaking changes

  • v3.0.0 MCP surface folded from 48 tools to 19; remaining 32 operator tools become actions on three dispatchers.

Beta — feedback welcome: [email protected]