chore(manifest): refresh published versions to flow 1.32.0 and launcher 1.13.1 - #367
Merged
Conversation
…er 1.13.1 openadapt-flow 1.32.0 published to PyPI today from the qualified main SHA 02e68bf, carrying the structured push-result contract (#369). openadapt 1.13.1 published today at 01:12 UTC, after the last daily claims check ran, so the launcher entry was about to fail that check tonight. Both refreshes touch the four surfaces the registry binds together: public/status.json (versions, tag, release commit, qualified source commit, and the exact PyPI filename, URL, and SHA-256 for each artifact), public/llms.txt, public/llms-full.txt, and data/published-version-claims.json. The acknowledged benchmark release lag advances 77 -> 78 for v1.32.0. review_by stays 2026-10-31, for the same reason the prior re-acknowledgement recorded: restating the count is not a decision to keep waiting, so the acknowledgement must still expire on its original date. Every artifact fact comes from the PyPI JSON API and the GitHub tag objects, not from hand-editing. `node scripts/check_published_version_claims.mjs` passes with the network checks enabled, which verifies each release commit against its tag and each qualified source commit against that commit's first parent. `node --test tests/*.test.js` passes 193 tests. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
✅ Deploy Preview for cosmic-klepon-3c693c ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
1 participant
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.
Release aftercare for
openadapt-flow1.32.0, plus a launcher entry that wasabout to go stale on its own.
What changed
openadapt-flowopenadapt(launcher)openadapt-flow1.32.0 was published today from the qualifiedmainSHA02e68bf, and carries the structured push-result contract (#369).The launcher move is not part of that release.
openadapt1.13.1 waspublished today at 01:12 UTC, after the last daily claims check ran on
2026-08-19. The networked check already fails on it, so tonight's scheduled run
would have gone red:
Both are the same manifest refresh, so they land together.
Surfaces
All four surfaces the registry binds:
public/status.json- version, tag, release commit, qualified source commit,and the exact PyPI filename, URL, and SHA-256 for each artifact.
public/llms.txtandpublic/llms-full.txt- the published-version line.data/published-version-claims.json- the claim, its evidence line, and theacknowledged lag.
Every artifact fact is read from the PyPI JSON API and the GitHub tag objects.
Nothing here is hand-typed.
The acknowledged lag
headline-benchmark-engine-buildadvances 77 -> 78 for v1.32.0, which is whatthe checker independently observes:
review_bystays 2026-10-31, following the precedent already recorded inthe note: restating the count is not a decision to keep waiting, so the
acknowledgement must still expire on its original date.
Verification
node scripts/check_published_version_claims.mjs(network enabled) -> exit 0,"Published version claims are consistent (5 claims)." This verifies each
release commit against its tag object and each
qualified_source_commitagainst that commit's first parent.
node scripts/check_published_version_claims.mjs --offline-> exit 0.node --test tests/*.test.js-> 193 passed, 0 failed.🤖 Generated with Claude Code