Repository navigation
Conversation
A versioned source now has three parts next to Run: ListVersions (every version, oldest first), ReadAt (the source at one version) and Extract (the changes between two snapshots, with previous_version set). Run keeps working and is built from them. core/versions lists versions from GitHub releases, tags and commits, PyPI, npm and the Web Archive at a date, with one version ordering. openapi: every adapter whose LatestTag was releases/latest or the newest commit on its spec can list all of them (Stripe, Datadog, Vercel, Flagsmith, Supabase, Neon, Convex, PlanetScale); the rest list their newest. changelog, migrationguide and removedmembers no longer pin a tag: releases come from PyPI and each is read at its tag; the pinned releases stay as the goldens' cases. Every golden is byte-identical. Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: adssib <[email protected]>
This was referenced Nov 20, 2026
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.
Stacked on #208. Refs #179 (I19.8), part of #171.
What this changes
Additive interface in
core/plugin(versions.go), next toPlugin{Name, Run}, which keeps working unchanged:Extractstores nothing (no baselines);Runadds its own, so a backfill of old pairs never moves the normal baseline.Shared version sources in
core/versions:GitHubReleases(drafts and prereleases out),GitHubTags(by pattern),GitHubCommits(the commits that changed a file, dated),PyPIReleases(final, not yanked),NPMReleases(final, not deprecated),WaybackAt(the Web Archive's capture of a page nearest a date), plusCompare/Final/Major/Pairs. Each takes a getter (env.Getorgithub.Get) and pages through GitHub lists (max 1,000 entries). Unit tests for each.Implemented for:
RunandReplayare nowReadAt+Extract.adapter.Lister(optional) lists every version: Stripe, Datadog, Vercel (canaries out), Flagsmith from GitHub releases; Supabase, Neon, Convex, PlanetScale from the commits that changed the spec. GitHub, GitLab, Elasticsearch, Sentry, Algolia and Appwrite list their newest only, for now.Filehas aTagPrefix; releases come from PyPI, each read atTagPrefix + version, andExtractis that release's section.File.At(release)pins one;Textual0860/Urllib3200are nowTextual.At("0.86.0")/Urllib3.At("2.0.0"), the goldens' cases. Registered sources are unpinned.X.0.0) has a guide to read (MIGRATION.md atvX.0.0), every other pair has no events.sdkguide.Anthropicis unpinned;AnthropicV1 = Anthropic.At(1).Guide.Tagis gone: the tag is derived (TagPrefix+ release,vby default,posthog-vfor PostHog); New Relic's guide lives in a docs repo with no tags, so it keeps that repo's commit asDocsRef. Releases from PyPI; only the release a guide documents has events.Living pages (retirements, feed, eol, catalog, apichangelog) keep
Runonly: patch-it's hosted ingestion service reads them as dated versions of a page.Golden proof
Every golden is byte-identical (36 files, sha256 compared with
main). The pinned cases still produce them throughRun, and the new tests check that the pair into the pinned release gives the same fingerprints withprevious_versionset:openapi: three consecutive pairs, each with only its own change and the rightversion/previous_version.changelog: urllib3 1.26.15 → 2.0.0 == the 2.0.0 golden's events,previous_version1.26.15.migrationguide: 0.75.0 → 1.0.0 has the three removed parameters, 1.0.0 → 1.0.1 none; the unpinnedRunreproduces the golden byte for byte (CompareGolden).removedmembers: 1.26.4 → 2.0.0 == the NumPy golden's events; 2.0.0 → 2.0.1 none.Checklist
WatchesandURLsnow describe every release (no pinned URL); I read themtestdata/README.md: rows for the three small PyPI-shaped files the listing tests use (written for the test, labelled as such, read by no golden)providers/textual.md,urllib3.md,anthropic.mdupdated (no longer "pinned to that release")env.Get/core/kit/(openapi adapters throughgithub.Get, as before)make checkpasses locallyWhat patch-it's hosted ingestion service must change later (not in this PR)
Runreads the newest release from PyPI instead of the pinned one. Expect new events (and, for a release whose changelog has no section under its exact version, a run error naming it) until the worker drivesListVersions→ReadAt→Extractper consecutive pair.ReadAteach version of a pair it hasn't done,Extract, store events;Runcan stay for living pages.Calls I made (please check)
Extractfor changelog reads onlyto's section: correct for consecutive pairs (what the worker diffs), not for a jump across several releases.Releaseper guide: each guide documents one release (NumPy's 2.0 guide, PostHog's 7→8 guide); a later major needs its own guide entry (or I19.4's merged kind).Ref.Related PRs
plugins.jsonrelease asset)apps/plugins-repo.md)🤖 Generated with Claude Code