Incorrect module version when deploying with PSGalleryModule through CI

[ramblingcookiemonster]

Incorrect module version when deploying with PSGalleryModule through CI

[RamblingCookieMonster]

Hi Erwan!

Yep, you can kill that piece if you'd like, it's set here in the psake build task. I kept forgetting to bump things, ended up just having it automatically bump based on existing gallery version.

Cheers!

[equelin]

Hi Warren !
Thx for your reply! So I just have to remove those lines, right?
I'm not sure to understand where those functions comes from? (Get-NextPSGalleryVersion, Update-Metadata)

[RamblingCookieMonster]

Ahh, so those are part of BuildHelpers - basically a bunch of little functions that might come in handy for a PowerShell-oriented build.

If you just kill that whole Try/Catch, it won't mess with the version in the PSD1. Also, note the Set-ModuleFunctions bit right above - that imports your module during the build, reads exported functions, sets these in the psd1 - might not be desired (personally I leave psd1 FunctionsToExport = '*', and let this update in the build, so I don't need to add new public functions manually, but... I might just be lazy).

Side note: Update-Metadata is exposed through BuildHelpers, but is really from Joel Bennett's awesome Configuration module - for whatever reason, publishing with that as a RequiredModule failed things in AppVeyor, so it's just hard coded into the BuildHelpers module now.

Cheers!

[equelin]

Thanks for your explanations Warren !