Import action for PowerShell modules doesn't play well with ScriptsToProcess

[RamblingCookieMonster]

ScriptsToProcess and other directives in a module manifest that run in the user's current scope will be loaded somewhere you can't get to.

Will add more details later, but https://github.com/cloudbase/powershell-yaml/blob/master/powershell-yaml.psd1#L49 is a good example.

For reference, we import modules here.

I think Gael already found this, but can't find the issue...

EDIT: Actually, powershell-yaml loads assemblies in ScriptsToProcess, and again in the psm1. Ignore me. Will close this if I validate it's not a problem
EDIT2: Nope. GitHub source != published module. They must have added that after the last publish. PowerShell Gallery code doesn't load the assemblies again in the psm1

[github-actions]

This issue has had no activity for 60 days. It will be closed in 30 days unless there is new activity or a maintainer removes the stale label.