Skip to content

Releases: bart-turczynski/cc-cream

v0.5.0

04 Jun 17:37

Choose a tag to compare

What's Changed

Full Changelog: v0.4.0...v0.5.0

v0.4.0

04 Jun 17:02

Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.3.6...v0.4.0

v0.3.6

04 Jun 12:59

Choose a tag to compare

What's Changed

Full Changelog: v0.3.4...v0.3.6

v0.3.4

31 May 16:57

Choose a tag to compare

Full Changelog: v0.3.3...v0.3.4

v0.3.3

30 May 20:49

Choose a tag to compare

Full Changelog: v0.3.2...v0.3.3

v0.3.2

30 May 19:19

Choose a tag to compare

What's Changed

Full Changelog: v0.3.1...v0.3.2

v0.3.1

30 May 16:43

Choose a tag to compare

What's Changed

Full Changelog: v0.3.0...v0.3.1

v0.3.0

30 May 16:07

Choose a tag to compare

What's Changed

  • v5: install/uninstall UX hardening, ghost-bar self-defense, one-command releases by @bart-turczynski in #12
  • Harden release script: stage only bump files, ignore untracked by @bart-turczynski in #13
  • Make release version-bump surgical (preserve manifest formatting) by @bart-turczynski in #14

Full Changelog: v0.2.0...v0.3.0

v0.2.0 — internal hardening

30 May 10:48
466fac7

Choose a tag to compare

Internal hardening + diagnosability (v4). See CHANGELOG for detail.

Added

  • cc-cream-setup --check-config — lint your cc-cream.json for unknown / out-of-range keys.
  • CC_CREAM_DEBUG=1 — opt-in diagnostics to ~/.claude/cc-cream-debug.log explaining why segments are hidden (stdout untouched, zero tokens).

Changed (breaking)

  • The plugin status line no longer self-resolves its version via a shell glob (ls|grep|sort -V|tail). It now bakes the current version's absolute path, and the SessionStart hook re-pins it after /plugin update. Plugin users: the bar re-wires itself on the next session; if you set it up manually, re-run /cc-cream:setup.

Internal

  • Shared src/settings.js for installer + hook; pure segment rendering (no filesystem access in segments.js); schema-table config normalization.

🤖 Generated with Claude Code

v0.1.18 — security hardening

29 May 21:43

Choose a tag to compare

Security hardening for the status-line engine and installer.

Security

  • Strip terminal control bytes (ESC/BEL/DEL, C0/C1) from status-line text, so escape sequences in model.display_name, session_name, or effort.level can't reach the terminal.
  • Reject __proto__/constructor/prototype as session_id keys.

Fixed

  • Atomic writes to settings.json and the state file (temp + rename), so an interrupted write can't truncate user config.
  • Quote the node binary path in the plugin auto-update command.

Changed

  • Cap the session-state map at 50 entries (LRU by timestamp).

See CHANGELOG for details. Published to npm via OIDC trusted publishing.