-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add get-fogversion #10
Comments
|
darksidemilk
added a commit
that referenced
this issue
Aug 18, 2024
darksidemilk
added a commit
that referenced
this issue
Aug 18, 2024
…10 will need to make a branch for using it to adjust the core objects dynamically
darksidemilk
added a commit
that referenced
this issue
Aug 18, 2024
Merged
darksidemilk
added a commit
that referenced
this issue
Aug 18, 2024
Created Get-FogVersion and implmented check for 1.6 version so correct dynamic parameters are used for 1.5.x vs 1.6 Also added a separate build test script for running a build test on each push. * Add get-fogversion #10 - Updated dynamic params to be contextual to the version * doc updates * Cleaned up a couple things * Added separate build script for use with testing builds on each push * Increment version, update release notes * trailing slash for import test * try psscript root * try importing with manifest * fix build test script path syntax * fix test for if module imported * don't error when testing import, wait for check for loaded module * Add built test badge to show if current master branch is passing build test
darksidemilk
added a commit
that referenced
this issue
Aug 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
working-1.6 now returns the version in the /fog/system/info path.
Can use this to parse a version of 1.6 and above and when that version isn't there can know it is version <=1.5.x and can adjust the dynamic core objects so removed options aren't displaying in 1.6 and options that didn't exist in 1.5 don't show either.
The text was updated successfully, but these errors were encountered: