cctally 1.3.0 → 1.4.0

package/CHANGELOG.md

@@ -5,6 +5,42 @@ based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+## [1.4.0] - 2026-05-09
+
+### Added
+- Shareable reports — all 8 reporting subcommands (`report`, `daily`,
+  `monthly`, `weekly`, `forecast`, `project`, `five-hour-blocks`, `session`)
+  now accept `--format md|html|svg` to emit shareable artifacts to a
+  filename like `cctally-<cmd>-<utcdate>.<ext>`. Flags: `--theme light|dark`,
+  `--no-branding`, `--reveal-projects` (project labels are anonymized to
+  `project-N` by default), `--output <path>` / `--output -` for stdout,
+  `--copy` (markdown only), `--open` (html/svg only). `session --format`
+  also accepts `--top-n N` to cap the chart's project breakdown.
+  See `docs/commands/share.md` and the per-command "Shareable output"
+  sections.
+
+### Fixed
+- Dashboard 5-hour row now shows the post-reset delta (`⚡ Δ +Xpp this
+  block`) when a 5h block spans a weekly reset, instead of suppressing
+  the number behind a `⚡ reset` line. The cross-reset flag now detects
+  natural weekly boundaries from `weekly_usage_snapshots.week_start_at`
+  in addition to Anthropic-shifted mid-week resets, and all interval
+  comparisons normalize through `unixepoch()` so the flag flips
+  correctly on non-UTC hosts (the prior lex-compare silently failed
+  for `+03:00` and other non-zero offsets, leaving the panel showing
+  a misleading `Δ −94pp this block`).
+- `record-usage`: self-heal `percent_milestones` and `five_hour_blocks` rows
+  that were silently dropped when an earlier invocation was killed between
+  snapshot insert and milestone insert (e.g. Claude Code self-update kill
+  window). On a dedup'd tick, re-runs the idempotent milestone helpers
+  against the latest snapshot — recovering missed rows at the next
+  status-line tick instead of waiting for the percent to advance.
+- Root `.gitignore` now anchors `/node_modules` and `/package-lock.json`,
+  preventing `npm install` next to the repo-root `package.json` (the
+  npm-publish sentinel) from leaving the working tree dirty and blocking
+  `cctally release`. `dashboard/web/node_modules` and the tracked
+  `dashboard/web/package-lock.json` are unaffected by the anchored entries.
+
 ## [1.3.0] - 2026-05-08
 
 ### Changed

package/README.md

@@ -9,6 +9,13 @@
   <strong>Track Claude Code subscription usage as a weekly $-per-1% trend. Local web dashboard, terminal UI, forecasts, and threshold alerts.</strong>
 </p>
 
+<p align="center">
+  <a href="https://www.npmjs.com/package/cctally"><img src="https://img.shields.io/npm/v/cctally.svg" alt="npm version"></a>
+  <a href="https://www.npmjs.com/package/cctally"><img src="https://img.shields.io/npm/dm/cctally.svg" alt="npm downloads"></a>
+  <a href="https://github.com/omrikais/cctally/blob/main/LICENSE"><img src="https://img.shields.io/github/license/omrikais/cctally.svg" alt="Apache-2.0 license"></a>
+  <a href="https://github.com/omrikais/cctally/stargazers"><img src="https://img.shields.io/github/stars/omrikais/cctally.svg" alt="GitHub stars"></a>
+</p>
+
 If you're using `ccusage` to watch Claude Code spend, `cctally` covers the same ground and adds the parts you reach for next: a live web dashboard, a forecast that tells you whether you're going to cap this week, threshold alerts when you cross a percent, and a persistent week-over-week trend of cost per percent of quota. All local, no account, no telemetry.
 
 <p align="center">