Skip to content

fix(mod/versioning): use fixed version for deps when possible#41

Open
parthpower wants to merge 1 commit intoTekunogosu:omegafrom
parthpower:issue-40-dep-versioning
Open

fix(mod/versioning): use fixed version for deps when possible#41
parthpower wants to merge 1 commit intoTekunogosu:omegafrom
parthpower:issue-40-dep-versioning

Conversation

@parthpower
Copy link

should partially fix #40

this technically breaks VS's mod dep definition which says "this version is minimum version required for mod" and not "version is semver version constraint" but it maybe better to use semver constraints for these deps anyways?

should partially fix Tekunogosu#40

this technically breaks VS's mod dep definition which says "this version is minimum version required for mod" and not "version is semver version constraint" but it maybe better to use semver constraints for these deps anyways?
@Tekunogosu
Copy link
Owner

Heya, thanks for the PR. This doesn't actually fix the issue at hand. The problem lies in the fact that when a mod requires a specific version of a mod its suppose to "pin" that mod version, but its not happening that way. This is a known issue and is on my radar, I just have not had time to put into rustique as of late.

I'll keep it open if you would like to try to fix it, but know that it will eventually be fixed.

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.

mod dependency should be pinned version

2 participants