-
Notifications
You must be signed in to change notification settings - Fork 6
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
RequiredVersion of ConsoleGuiTools is outdated. #17
Comments
I am having the same issue. Microsoft.PowerShell.ConsoleGuiTools is now at version 0.7.6.0 as of 2023-10-27. This latest version includes the command I request allowing newer versions of Microsoft.PowerShell.ConsoleGuiTools as well. (i.e. replace the exact-version specifier |
Sorry about this folks. I'm confused about In order to build/test locally, I have a build script that looks at a local PS repo for ConsoleGuiTools and if found updates F7History.ps1 to force use of it (updating Can you point me at docs that show how to effectively use |
No worries! Here's the doc: Looking at your implementation, I think you could simply swap |
I had to disable my CI/CD unit tests (which are pretty lame anyway) because of Pester v5 and me being confused. I'll fix those asap. Can y'all verify this was done correctly? If so I'll close this issue. |
Pretty sure v1.4.1 which was just published fixes this. |
I can confirm that the issue is resolved. I am able to import and successfully use version 0.7.6.0 of the module Microsoft.PowerShell.ConsoleGuiTools simultaneously with version 1.4.1 of the module F7History. Thank you! |
F7History.psd1 has a hardcoded dependency on v0.7.4 of ConsoleGuiTools, which is now at v0.7.5.35
I suggest using "ModuleVersion" instead of "RequiredVersion" to make a softer minimum version dependency.
The text was updated successfully, but these errors were encountered: