PowerCraft.Release.psd1
|
@{ RootModule = 'PowerCraft.Release.psm1' ModuleVersion = '1.0.0' CompatiblePSEditions = @('Core') GUID = 'f3a1b2c4-d5e6-4f78-9a0b-1c2d3e4f5a6b' Author = 'The Code Kitchen' CompanyName = 'The Code Kitchen' Copyright = '(c) 2026 The Code Kitchen. All rights reserved.' Description = 'Universal release automation for PowerShell modules, .NET projects, Node.js packages, and Python projects. Provides version detection, bumping, validation, and publishing across ecosystems.' PowerShellVersion = '7.0' FunctionsToExport = @( 'Get-PCProjectVersion' 'Set-PCProjectVersion' 'Get-PCNextVersion' 'Test-PCReleaseReady' 'Publish-PCRelease' 'Install-PCReleaseWorkflow' ) CmdletsToExport = @() VariablesToExport = @() AliasesToExport = @() PrivateData = @{ PSData = @{ Tags = @('Release', 'Versioning', 'SemVer', 'CI-CD', 'Automation', 'PowerCraft') LicenseUri = 'https://github.com/The-Code-Kitchen/PowerCraft.Release/blob/main/LICENSE' ProjectUri = 'https://github.com/The-Code-Kitchen/PowerCraft.Release' ReleaseNotes = @' ## 1.0.0 (2026-06-26) ### Added - Multi-technology template engine with {{TOKEN}} resolution - Templates/powershell/ and Templates/shared/ folder structure - Resolve-TemplateTokens: generic token replacement engine - Get-SecretBootstrapBlock: auto-generates CI secrets step when PowerCraft.Secrets detected - Read-PCReleaseConfig: optional .powercraft/release.json per-repo overrides - {{MODULE_NAME}}, {{RUNNER}}, {{DEFAULT_BRANCH}}, {{SECRETS_BOOTSTRAP}} tokens in CI template - dependency-check.yml only installed when RequiredModules present - Version stamp header on all generated workflows - Disabled template support via config ### Fixed - ci.yml {{MODULE_NAME}} token was never resolved (copied as-is) ### Changed - Install-PCReleaseWorkflow now uses Get-ProjectType for technology detection - Templates restructured into technology-specific subfolders '@ } } } |