From fc4b6a42a58d32545f436f8b7be0a436e16a819d Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 2 Jun 2026 12:59:10 +0000 Subject: [PATCH] fix(registry): use remix@ git tags for remix 1.6.5+ The remix monorepo stopped publishing unified v{version} tags after v2.11.1 and tags each package instead (e.g. remix@2.17.5). Split the version ranges so 1.6.5+ resolves to the remix@{version} tag pattern, fixing the publish-all clone failure for remix@2.17.5. --- registry/npm/remix.yaml | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/registry/npm/remix.yaml b/registry/npm/remix.yaml index eafed0c..62820db 100644 --- a/registry/npm/remix.yaml +++ b/registry/npm/remix.yaml @@ -3,9 +3,19 @@ description: "Full stack web framework focused on web fundamentals and user expe repository: https://github.com/remix-run/remix versions: + # Early releases used a unified "v{version}" git tag. - min_version: "1.0.0" + max_version: "1.6.5" source: type: git url: https://github.com/remix-run/remix docs_path: docs tag_pattern: "v{version}" + # From 1.6.5 onward the monorepo tags each package, e.g. "remix@2.17.5". + # The unified "v{version}" tags stopped at v2.11.1. + - min_version: "1.6.5" + source: + type: git + url: https://github.com/remix-run/remix + docs_path: docs + tag_pattern: "remix@{version}"