cctally 1.69.1 → 1.69.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +10 -0
- package/bin/_cctally_dashboard_sources.py +1049 -0
- package/bin/_cctally_source_analytics.py +2050 -0
- package/bin/_lib_dashboard_sources.py +511 -0
- package/bin/_lib_source_analytics.py +1375 -0
- package/package.json +5 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,16 @@ based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
|
|
|
5
5
|
|
|
6
6
|
## [Unreleased]
|
|
7
7
|
|
|
8
|
+
## [1.69.3] - 2026-07-17
|
|
9
|
+
|
|
10
|
+
### Fixed
|
|
11
|
+
- Dashboard: cleared the persistent `⚠ sync error` chip (`source-bundle: data_version must be a non-empty string`) that appeared once a provider — typically Codex — stayed degraded or unavailable across two or more consecutive sync ticks. The first failure records an unavailable provider generation; the next tick then tried to retain that already-unavailable generation as a `partial` state with an empty data version, which fails the source-state validator. `degrade_source_state` now stays `unavailable` (carrying the new warning) when there is no coherent prior generation to retain.
|
|
12
|
+
|
|
13
|
+
## [1.69.2] - 2026-07-17
|
|
14
|
+
|
|
15
|
+
### Fixed
|
|
16
|
+
- Completed the 1.69.0/1.69.1 packaging fix: the four source-aware runtime modules were added to the public mirror allowlist in 1.69.1 but were still missing from the npm `package.json` `files` list, so the npm tarball kept excluding them and installed commands crashed at import; they now ship in the npm package. Brew was unaffected — it archives the whole public tree.
|
|
17
|
+
|
|
8
18
|
## [1.69.1] - 2026-07-17
|
|
9
19
|
|
|
10
20
|
### Fixed
|