Repository navigation
Release 0.6.13 monitoring freshness and frozen chronology - #11
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An unchanged successful source check now updates the activity dates shown by status, fleet and reports. A later unknown check preserves the prior conclusive/link verification only for the same placement identity. Adds
chronology pullfor compatible hosted versions andchronology exportfor saved pages, with explicit denied origins, history gaps, partial paging, exact identity and refusal to replace an input or existing output. Existing frozen version-two reports remain intact. The generated catalog, plugin manifests and REST/MCP client identity move to 0.6.13.Validation and custody:
0b770b46bf676c77e7e79ff1cce43de60c3547b2d12978a3c4da2a91804ca198. This is a prepared archive, not npm publication or a fresh customer installation.0.6.13 remains unreleased. The latest recorded npm readback is 0.6.11; hosted command availability and consumer adoption are separate receipts. The retained release workflow stays disabled with
if: ${{ false }}so this PR/tag cannot publish a second artifact. No supplier activation, recurring collection or message delivery is introduced by this package release.