Repository navigation
Conversation
core/ holds what isn't one kind: the plugin contract and registry, fetch, kit and kittest, the event types, migrate, and the OpenAPI diff engine with normalize and hint. The spec adapters move to plugins/openapi/adapter, the deprecations-page reader to plugins/retirements/retire and the migration guide reader to plugins/migrationguide/sdkguide. The old import paths that patch-it's hosted ingestion service uses (plugin, event, fetch, migrate, kit, kit/kittest, retire, sdkguide) stay as deprecated packages that only forward to the new ones. The newest-release, newest-commit-on-a-path and commit-date lookups that nine adapters, apichangelog and catalog each decoded themselves are now one helper, core/github. Also regenerates docs/plugins.json and the README badge (out of date on main since the salesforce plugin) and gofmts vercel_test.go. Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: adssib <[email protected]>
This was referenced Nov 20, 2026
gofmt versions disagree on how to align the old map literal, so CI's gofmt failed on what a newer one wrote. Two lists need no alignment. Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: adssib <[email protected]>
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.
First of a stack of five (layout → providers and sources → no committed lists → versions → README). Refs #174 (I19.3, the shared GitHub lookup part), part of #171.
What this changes
Layout only; no plugin's behavior changes.
core/: what isn't one kind.core/plugin(contract and registry),core/fetch,core/kit+core/kit/kittest,core/event,core/migrate, and the OpenAPI diff engine with its helpers (core/diff,core/normalize,core/hint).plugins/<kind>/: each kind with its providers. The spec adapters move toplugins/openapi/adapter, the deprecations-page reader toplugins/retirements/retire, the migration-guide reader toplugins/migrationguide/sdkguide(theirtestdata/moves with them).core/github(LatestRelease,LatestCommit,Commit,Head,Headers). Stripe, Datadog, Vercel, Flagsmith, Supabase, Neon, Convex, PlanetScale, Appwrite, Algolia and Elasticsearch, plusapichangelogandcatalog, each had their own copy of decoding GitHub'sreleases/latest,commits?path=…&per_page=1orcommits/<ref>response; they now call it. It takes a getter (github.Get, or the plugin'senv.Get), so tests fake it the same way as before.plugin,event,fetch,migrate,kit,kit/kittest,retire,sdkguide(what patch-it's hosted ingestion service imports today) stay as deprecated packages that only forward to the new ones (type aliases, constants, function values). Code built against v0.2.0's API keeps compiling unchanged.main:docs/plugins.jsonand the README badge were out of date after the Salesforce plugin, andplugins/openapi/vercel_test.gowasn't gofmt'd.nethttpallowlist,todosdirs), CI comments, AGENTS.md layout, README layout table, writing-a-plugin.md and provider pages point at the new paths.Checklist
docs/plugins.md. Not applicable: no plugin added, removed or changed (the table is untouched;docs/plugins.jsonregenerated only to fix main)git commit -s, DCO)main)testdata/README.md: unchanged, moved with its packageproviders/<api>.md: paths updated onlyenv.Get/core/kit/(andcore/github, which goes throughfetch.Getorenv.Get)make checkpasses locallyGolden proof
find . -path '*/testdata/golden/*' -type f | xargs sha256sum: the 36 hashes are identical tomain's.Notes for the reviewer
replaceto the local checkout):go build ./... && go vet ./...pass. Its golden-replay test reads saved pages from the module by relative path; the two reader packages'testdata/moved (retire/testdata→plugins/retirements/retire/testdata,sdkguide/testdata→plugins/migrationguide/sdkguide/testdata), so that test needs its paths updated when it bumps to a release with this change.diff,normalize,hint,adapter) are not kept: v0.x, and keeping every one would double the package list. Easy to add if wanted.core/githubkeeps each adapter's URL variables (tests still point them at local servers); only the decoding moved.Calls I made (please check)
plugins/openapi/adapter,plugins/retirements/retire,plugins/migrationguide/sdkguide) rather than being merged into the kind's package: no identifier clashes, smaller diff. Merging kinds (I19.4–I19.6) is separate.var F = core.Ffor functions (and copies of exported values such askittest.Clock,retire.OpenAI): same behavior for callers; assigning to the old variable doesn't change the new one.Related PRs
plugins.jsonrelease asset)apps/plugins-repo.md)🤖 Generated with Claude Code