bdo-cli 0.46.0 → 0.47.0

package/CHANGELOG.md

@@ -5,6 +5,50 @@ All notable changes to Bushido (bdo) will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.47.0] (2026-10-17)
+
+### Features
+
+- **`BDO_QUIET=1` silences bdo's advisory notes on stderr** — the
+  reduced-view hint after `bdo read`, the daily "no hook installed / hook
+  outdated" reminder, and the "--raw has no effect" note. Output, errors, the
+  wrapped command's stderr, warnings that bdo misbehaved and the
+  `[full output: …]` pointer are unaffected. A suppressed hook reminder is not
+  spent: it still shows on the next run without `BDO_QUIET`.
+
+### Fixed
+
+- **Unit tests no longer race on, or write to, the real tracking DB.** A test
+  rewrote the process-wide `BDO_DB_PATH` while other tests opened trackers in
+  parallel, and several tests recorded rows into the user's own `history.db`
+  (visible in `bdo gain`). Each test thread now gets a throwaway DB.
+
+### Security
+
+- **npm publishing moved to Trusted Publishing (OIDC).** The release
+  workflow no longer uses a long-lived `NPM_TOKEN` secret: npm verifies a
+  short-lived token GitHub issues to the `publish-npm` job, and the package
+  gets npm provenance. The hardening check fails if a stored npm token comes
+  back (e.g. after `dist generate`).
+
+## [0.46.1] (2026-10-17)
+
+### Security
+
+- **rustls 0.23.45 → 0.23.46** (via `ureq`), fixing RUSTSEC-2026-0346
+  (`Debug` impls for client session values expose TLS secrets, medium),
+  RUSTSEC-2026-0347, RUSTSEC-2026-0348 and RUSTSEC-2026-0349 (including an
+  unauthenticated ServerHello downgrading later connections to classical key
+  exchange, low). Caught by the daily scheduled `cargo audit` run. No code
+  changes.
+
+- **CI actions pinned to commit SHAs.** `ci.yml` used mutable refs
+  (`actions/checkout@v6`, `dtolnay/rust-toolchain@1.91`), so whoever controls
+  those tags or branches could change what runs on every PR. They are now
+  pinned like `release.yml`, every checkout drops its credentials
+  (`persist-credentials: false`), and the hardening check runs against
+  `ci.yml` too, so an unpinned action fails CI.
+
 ## [0.46.0] (2026-10-04)
 
 ### Features

package/README.md

@@ -97,7 +97,7 @@ Each has a `.sha256` sidecar — verify before extracting.
 ### Verify Installation
 
 ```bash
-bdo --version   # Should show "bdo 0.46.0"
+bdo --version   # Should show "bdo 0.47.0"
 bdo gain        # Should show token savings stats
 ```
 
@@ -427,6 +427,15 @@ just runs raw. Raw runs are still tracked, at 0% savings.
 The older per-command switches — `bdo read -l none`, `BDO_NO_TOML=1`,
 `bdo proxy <cmd>` — keep working.
 
+### Quiet mode (`BDO_QUIET=1`)
+
+`BDO_QUIET=1` silences bdo's own advisory notes on stderr: the
+"reduced view — full raw content: …" hint after `bdo read`, the daily
+"no hook installed / hook outdated" reminder, and the "--raw has no effect"
+note. Command output, errors, the wrapped command's own stderr, warnings that
+bdo itself misbehaved (a filter panic, a failed hook integrity check) and the
+`[full output: …]` pointer are unaffected.
+
 ## Examples
 
 **Directory listing:**

package/package.json

@@ -1,6 +1,6 @@
 {
   "artifactDownloadUrls": [
-    "https://github.com/tedorigawa001/TokenReductionTool-BDO/releases/download/v0.46.0"
+    "https://github.com/tedorigawa001/TokenReductionTool-BDO/releases/download/v0.47.0"
   ],
   "author": "Patrick Szymkowiak",
   "bin": {
@@ -91,7 +91,7 @@
       "zipExt": ".tar.xz"
     }
   },
-  "version": "0.46.0",
+  "version": "0.47.0",
   "volta": {
     "node": "18.14.1",
     "npm": "9.5.0"