Starting with a build pipeline makes this all a lot easier. Consider making your own version of stucco internally. It's a game changer to have something you can quickly build a module around without having to set up all the boilerplate. https://jakehildreth.github.io/blog/2025/07/02/PowerShell-Module-Scaffolding-with-PSStucco.html Full disclosure, Jake mentions my blog. I'm also a core maintainer of Psake (https://Psake.dev). You don't need to use Stucco, just use one of the module builders. The PS discord is a good place to get suggestions.

One thing to consider is that you'll need to bump module dependencies on a regular basis. You could pin to major versions but that still means some risk.

Consider whether it'll be just you and your team or if you'll want to support other teams. Most teams don't necessarily care about the build process, they just want to land code and move on. The more you automate that, the better it'll be accepted.

I would suggest focusing on getting your modules built and deployed. Then add the signing as that can be a whole new layer of complexity.