Skip to content

wdk-op-policy's provenance note describes the state the fix removed #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
BTCBoyd merged 1 commit into from
Aug 9, 2026
Merged

wdk-op-policy's provenance note describes the state the fix removed #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 13 additions & 5 deletions packages/wdk-op-policy/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,11 +14,19 @@
>
> **Versions.** Published `0.4.1`.
>
> **Provenance.** Versions `0.1.0` and `0.4.1` resolve in
> [`observer-protocol/wdk-op-policy`](https://github.com/observer-protocol/wdk-op-policy)
> (archived, read-only). **`0.2.0`, `0.3.0`, `0.3.1`, `0.3.2` and `0.4.0` resolve only in a private
> repository and cannot be fetched from outside the organisation.** The next release onward resolves
> here.
> **Provenance. Every published version resolves publicly.** All seven, `0.1.0` through `0.4.1`,
> resolve in [`observer-protocol/wdk-op-policy`](https://github.com/observer-protocol/wdk-op-policy),
> and each is reachable from a tag named for its version. `0.1.0` and `0.4.1` sit on `main`; `0.2.0`,
> `0.3.0`, `0.3.1`, `0.3.2` and `0.4.0` sit on the unmerged `provenance/pre-monorepo` branch, a
> divergent lineage rather than an ancestor of `main`, which is why they are tagged. The next release
> onward resolves here.
>
> *Correction 2026-08-09: this block previously said those five versions "resolve only in a private
> repository and cannot be fetched from outside the organisation", and described the repository as
> "(archived, read-only)". Both were false when read. The five were made publicly resolvable on
> 2026-08-08 and that work is what this sentence was describing, so the fix left the description of
> the old state in place at the URL a consumer checking provenance lands on. The repository is not
> archived: `archived=false`, measured 2026-08-09.*
> The Observer Protocol API's rail registry no longer carries a pin. **Ruled 2026-08-05:** the
> field was named `version` and read as "these versions are known to work together", while
> nothing enforced or checked it — the running server never reads it. It is now
Expand Down
Loading