Skip to content

fix: restore versioned page links in catalog feed - #6

Merged
dhruvjainin merged 1 commit into
mainfrom
fix/catalog-versioned-page
Nov 2, 2026
Merged

dhruvjainin merged 1 commit into
mainfrom
fix/catalog-versioned-page

Conversation

@dhruvjainin

Copy link
Copy Markdown
Contributor

The catalog feed's page field changed from /packages/<slug>/<version>/ to /packages/<slug>/. The TulipFarm app validates that each entry's page matches the versioned path, so it rejected the whole feed and the Packages page showed "Could not load packages".

This emits the versioned path again. That URL already redirects (301) to the new unversioned page, so links keep working.

Adds a test that applies the app's link check to every built feed entry and verifies the redirect rule.

TulipFarm apps validate every catalog.json entry and reject the whole feed
unless page resolves to /packages/<name>/<version>/. #5 changed page to the
unversioned detail path, so the in-app Packages page has shown 'Could not
load packages' since 2026-11-01 05:33 UTC. Emit the versioned path again; it
301-redirects to the canonical page.
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying tulipfarm-packages with  Cloudflare Pages  Cloudflare Pages

Latest commit: c05dcf6
Status: ✅  Deploy successful!
Preview URL: https://57fe51aa.tulipfarm-packages.pages.dev
Branch Preview URL: https://fix-catalog-versioned-page.tulipfarm-packages.pages.dev

View logs

@dhruvjainin
dhruvjainin merged commit 9fbe126 into main Nov 2, 2026
2 checks passed
@dhruvjainin
dhruvjainin deleted the fix/catalog-versioned-page branch November 2, 2026 02:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant