Skip to content

Comments

fix: store versions per-repo to prevent fork collisions#17

Merged
DaniPopes merged 4 commits intomasterfrom
dani/fix-fork-version-collision
Jan 15, 2026
Merged

fix: store versions per-repo to prevent fork collisions#17
DaniPopes merged 4 commits intomasterfrom
dani/fix-fork-version-collision

Conversation

@DaniPopes
Copy link
Member

Previously, versions like 'nightly' from different repos (e.g., foundry-rs/foundry vs tempoxyz/tempo-foundry) would overwrite each other since they were stored under the same directory.

Now versions are stored under versions/{owner}/{repo}/{version}, so each fork has its own isolated version storage.

The list output now shows the repo alongside the version: foundryup: foundry-rs/foundry nightly

Fixes #9

Previously, versions like 'nightly' from different repos (e.g.,
foundry-rs/foundry vs tempoxyz/tempo-foundry) would overwrite each
other since they were stored under the same directory.

Now versions are stored under `versions/{owner}/{repo}/{version}`,
so each fork has its own isolated version storage.

The list output now shows the repo alongside the version:
`foundryup: foundry-rs/foundry nightly`

Fixes #9 (comment 3666667993)
On startup, foundryup now detects legacy version directories
(those stored directly under versions/ without a repo prefix)
and automatically migrates them to the new structure under
foundry-rs/foundry/.

This ensures backwards compatibility for users upgrading from
older versions of foundryup.
@DaniPopes DaniPopes enabled auto-merge (squash) January 15, 2026 17:55
@DaniPopes DaniPopes requested a review from onbjerg January 15, 2026 18:26
@DaniPopes DaniPopes merged commit eb988e5 into master Jan 15, 2026
8 checks passed
@DaniPopes DaniPopes deleted the dani/fix-fork-version-collision branch January 15, 2026 18:30
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.

Multi-version management

2 participants