build-and-release

To reproduce Azure Pipelines build-and-release behavior locally, run pipeline-templates versionnumber scripts and install-forpipeline stamping to replicate version stamping, linting, signing, and publishing. It applies build.yml rules for local CI validation across Windows and Linux.

Version stamping for PowerShell module releases derives VersionString, PrereleaseSuffix, and ReleaseTag using pipeline templates. It enforces tag formats like v<major>.<minor>.<patch> and stamps manifests via install-forpipeline.ps1 for consistent release tagging.

Yes, the build-and-release process supports both Windows and Linux build templates. It handles local CI replication, release validation, and troubleshooting across both operating systems for tag and non-tag builds.

The signing and publishing workflow for PowerShell Gallery artifacts involves catalog signing on Windows, publishing the module, creating GitHub release artifacts, and conditionally publishing Docker Hub images. These steps follow the artifact rules defined in build.yml.

CI release validation fails during strict linting when install-forpipeline.ps1 encounters manifest stamping errors or code style violations. The build-and-release process enforces strict linting after installing into the target PSModulePath to ensure release readiness.