Adam Kreiss

To further detail the changes now that I have them implemented for our own use - I added a -Credentials parameter to Invoke-PSDepend that accepts a hashtable of named PSCredential...

@johnmccrae Sure - you can see the changes in `credentials` branch on my fork of the project: https://github.com/alphakilo45/PSDepend/commits/credentials Beware though, I haven't merged in any changes since creating the fork

Absolutely - I can get things merged later this week and submit a PR (unless @rlvandaveer gets around to it first).

I agree that we don't want credentials in the *.depend.psd1 files. The intention was was to provide a hash (keyName -> credential) of the credentials to your call to Invoke-PSDepend....

@pauby I think the piece that's missing is that you need to specify the key for the credentials in your dependency. For example from the PSDepend tests: ``` 'jenkins' =...

I went with a `UpgradeLowerVersion` parameter to avoid changing how the resource works by default (uninstall/install behavior). I would have expected upgrading packages to be the default behavior as well....

@pauby Only reason I can think of is when the build/pre-release tag is the only difference in the version number and that'll still be supported. I'll get the code updated.

Agreed - rebase didn't help so I need to find some time on keyboard to figure out what is causing that.

@pauby Looks like Pester released v5 recently and that is causing issues with the tests. I fixed the maxed version in AppVeyor at 4.10.1 (the last pre-5.0.0 version) and tests...

+1 - Could really use this fixed as well - if there anything in particular it's waiting on? Or just the next release?