generated: '2026-08-27' method: probed source: >- https://docs.simetrik.com/cli/changelog (HTTP 200) and its served markdown at https://docs.simetrik.com/cli/changelog.md (HTTP 200), plus the release manifest at https://cli.simetrik.com/cli/manifest.json (HTTP 200), all fetched 2026-08-27. url: https://docs.simetrik.com/cli/changelog scheme: semver current_version: 1.3.8 current_released: '2026-08-27' entry_count: 1 status: surface-published-but-empty note: >- Simetrik publishes a changelog SURFACE that currently carries no entries. The page is live and says it is "automatically generated on every release", but the served markdown contains only the heading and that sentence - no versions, no dates, no highlights. The docs home separately lists a platform-wide Changelog as "Coming soon". So there is a real, reachable changelog URL and zero published history behind it, which is a materially different fact from either "no changelog" or "a maintained changelog", and is recorded as such rather than being smoothed into either. The single dated release entry below is NOT read from the changelog - it is read from the provider's own release manifest, which is machine-readable and authoritative for versions and dates. entries: - version: 1.3.8 date: '2026-08-27' channel: stable released_at: '2026-08-27T01:35:53Z' source: https://cli.simetrik.com/cli/manifest.json method: probed breaking: unknown additions: unknown highlights: null highlights_note: >- The manifest carries version, timestamp, per-platform artifact names, sizes and sha256 digests - but no release notes. Nothing about what changed in 1.3.8 is published anywhere, so no highlights are recorded. artifacts: - platform: linux-x86_64 sha256: 0ca97c9541a21ca294dc9313b4da5bcf6535135b12834fd8800941822c74d1fb - platform: darwin-arm64 sha256: 96e5195a8adaa85e21a14f0a901837ff192c34ba28226234dd2bca66a30f7a1d - platform: windows-x86_64 sha256: cb16603593d5fc9999283764dfdb0f582c7848835d548c126392c48ec12731f3 companion: artifact: simetrik-skill.tar.gz skill_version: 1.3.21 sha256: 5c0bdf02e3fbdf12b7e6f0f2580049ebcfe75c65a8d2be7ccb999e8b18e93372 gap_for_provider: >- The release manifest already carries everything a changelog needs except prose. Wiring release notes into the existing /cli/changelog page would turn a live-but-empty surface into a real one at very low cost.