Repository navigation
Adopt the manifest contract across the extensions site - #406
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://codex-align-extension-manifests-extensions.fossbilling.workers.dev (commit 9baba5b)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
There was a problem hiding this comment.
All reported issues were addressed across 60 files
Reply with feedback, questions, or to request a fix.
Turn on auto-fix | Re-trigger cubic
There was a problem hiding this comment.
All reported issues were addressed across 17 files (changes from recent commits).
Reply with feedback, questions, or to request a fix.
Turn on auto-fix | Re-trigger cubic
There was a problem hiding this comment.
0 issues found across 2 files (changes from recent commits).
Requires human review: Adopts the manifest v1 API contract across forms, details, releases, and the generated client, and switches cache tags to 'extensions' in coordination with the API. Deployment must coordinate the cache-tag and manifest migration, and old pending revisions require resubmission.
Turn on auto-fix | Re-trigger cubic
The publisher currently converts `module` to `mod`, converts licenses to objects, drops author/PHP/module metadata, and reduces FOSSBilling requirements to a single minimum. Send manifest v1 fields directly, including optional homepage/icon paths and complete requirements on each release. Preserve historical release constraints and idempotent same-version replacement. Refuse API history without manifest requirements so publishing against an unmigrated API cannot silently discard Coordinated PRs: - [FOSSBilling/api #294](FOSSBilling/api#294) - [FOSSBilling/extensions #406](FOSSBilling/extensions#406)
The site currently builds and renders the old extension payload, so native manifest metadata would fail submission or disappear from views. Regenerate the checked-in OpenAPI client and update author/edit/moderator forms, public details, release tables, and revision comparisons for the manifest v1 contract. Preserve compound requirements and keep package attribution distinct from developer ownership, while retaining legacy audit-field display.
Resolve supported GitHub package-relative icons against their release tags, including the
FOSSBilling/modulespackage directory layout. Replace catalogue terminology throughout the site and share theextensionscache tag between route rules and both purge paths.Coordinated PRs: