Skip to content

Fix errors when GUID is not used with MaximumVersion #44

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 2, 2024

Conversation

JustinGrote
Copy link
Owner

@JustinGrote JustinGrote commented Jan 2, 2024

ModuleFast will now check at install time if the manifest GUID does not match what was in the spec. We unfortunately cannot do this earlier in the process without fully downloading the modules, as Nuget v3 doesn't have a standard location to store the GUID for PowerShell modules in the metadata. There could potentially be a tag like "GUID:XXX-YYY-ZZZ" used for this purpose in the future.

A warning was also added against using GUID to match in general.

Closes #43.

@JustinGrote JustinGrote self-assigned this Jan 2, 2024
@JustinGrote JustinGrote merged commit 44c656f into main Jan 2, 2024
@JustinGrote JustinGrote deleted the JustinGrote/issue43 branch January 2, 2024 20:54
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.

Errors as soon GUID is not used with MaximumVersion (#Requires-Spec)
1 participant