From edcc4ffa042103a1ef2e94c9d4200acbb91fdf82 Mon Sep 17 00:00:00 2001 From: Scott K Logan Date: Thu, 25 Jun 2026 15:00:53 -0500 Subject: [PATCH] Fix handling of path-only dependencies This scenario is completely unsupported when crates.io is used, so we have some room to decide how to interpret a dependency specified only by path. If both a version and a path are present, a crate packaged for crates.io will carry the version number only, and pallet-patcher uses that version number for search and resolution as you might expect. This change interprets the version constraint as "any version", or "*", when there isn't any version number given in the dependency constraints at all. --- pallet_patcher/search.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pallet_patcher/search.py b/pallet_patcher/search.py index d26be45..f3dd11f 100644 --- a/pallet_patcher/search.py +++ b/pallet_patcher/search.py @@ -106,7 +106,7 @@ def compose(dependencies, search_paths, *, seeds=None): # core {'version': '1.0.0', # 'optional': True, 'package': 'rustc-std-workspace-core'} name = specifications.get('package', name) - version_spec = specifications.get('version', name) + version_spec = specifications.get('version', '*') else: version_spec = specifications