Update Humanizer version and improve module layout

[cdhunt]

I still use this frequently and it hasn't been touched in years and Humanizer is working on a 3.0.0 release with tons of fixes and improvements.

If I'm going to crack open this project again I plan to reorganize the source and refactor the build automation to more modern practices.

@dfinke, Do you have a preference for build platform? Are there secrets in the repo for publishing to PSGallery?

[dfinke]

Cool! I prefer GitHub. No creds for gallery.

Let me know and we can chat about coordinating that, should be simple. Wow, 2019 for the last publuish of this.

Yeah, would like to see the updated CI/CD.

[WeihanLi]

is it possible to reference the NuGet package, and maybe we could query the package updates via a scheduled CI job

[dfinke]

@cdhunt thoughts?

[cdhunt]

Yes, can definitely pull in the versioned nuget.

[dfinke]

I like the idea of automation there. Uncomfortable there is not a gate for it.

[cdhunt]

In my PR I have the versioned pinned in a csproj file and new Humanizer releases are pretty infrequent.

[cdhunt]

PowerShell now ships with Humanizer 2.14.1 which basically means this module will likely be pinned to whatever is shipped with Pwsh.

[dfinke]

Cool. What's the deal with Humanizer shipping in PS?

[cdhunt]

I've been running this branch locally and it started to throw an error trying to load the dll. I finally tracked it down, but it only shows up in metadata in the public source.

https://github.com/search?q=repo%3APowerShell%2FPowerShell%20humanizer&type=code