Skip to content

fix(registry): use remix@ git tags for remix 1.6.5+#92

Merged
moshest merged 1 commit into
mainfrom
claude/remix-git-clone-failure-dHWRz
Jun 2, 2026
Merged

fix(registry): use remix@ git tags for remix 1.6.5+#92
moshest merged 1 commit into
mainfrom
claude/remix-git-clone-failure-dHWRz

Conversation

@moshest
Copy link
Copy Markdown
Member

@moshest moshest commented Jun 2, 2026

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.

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.
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Jun 2, 2026

⚠️ No Changeset found

Latest commit: fc4b6a4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@moshest moshest merged commit 3a74442 into main Jun 2, 2026
3 checks passed
@moshest moshest deleted the claude/remix-git-clone-failure-dHWRz branch June 2, 2026 15:51
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.

2 participants