AtlassianPS.Standards

0.5.0

Shared analyzer settings and standards utilities for AtlassianPS modules.

Minimum PowerShell version

5.1

Installation Options

Copy and Paste the following command to install this package using PowerShellGet More Info

Install-Module -Name AtlassianPS.Standards

Copy and Paste the following command to install this package using Microsoft.PowerShell.PSResourceGet More Info

Install-PSResource -Name AtlassianPS.Standards

You can deploy this package directly to Azure Automation. Note that deploying packages with dependencies will deploy all the dependencies to Azure Automation. Learn More

Manually download the .nupkg file to your system's default download location. Note that the file won't be unpacked, and won't include any dependencies. Learn More

Owners

Copyright

(c) 2026 AtlassianPS contributors.

Package Details

Author(s)

  • AtlassianPS

Tags

AtlassianPS PSScriptAnalyzer Standards

Functions

Copy-ModuleArtifacts Get-ReleaseNotesFromChangelog Import-DotEnvFile Initialize-BuildEnvironment Initialize-ModuleTestEnvironment Install-DependencyRequirement Invoke-Lint Invoke-ModuleTests Join-ModuleSource New-ModulePackage Remove-OrphanedExternalHelp Resolve-ModuleSource Resolve-ProjectRoot Set-ModuleManifestVersion Sync-ScriptAnalyzerSettings Test-ModulePackage Update-DependencyReference Update-ExternalHelp Update-ModuleManifestExports Write-BuildInfo

Dependencies

Release Notes

### Added

- Support explicit alpha and beta releases through the shared CI and protected publication route, with exact candidate acquisition and package verification.
- Package alpha/beta releases from a selected repository branch, using one resolved commit for validation and the release tag.
* feat: support shared alpha and beta release candidates (#78, @lipkau)

### Changed

- Release planning stops a major release, stable or prerelease, unless a manual dispatch supplies `major_authorization` as `owner/repository vMAJOR`.
- `Test-ModulePackage -ExpectedVersion` compares the full version, including the prerelease label, and requires the package to match the built module file for file.
- `Install-DependencyRequirement` treats a requirement with only `ModuleVersion` as a minimum, no longer an exact pin.
- Release planning stops when the planned version is not above the latest stable version on PSGallery, and publication stops before tagging when a newer stable version, or a later alpha or beta of the same base, is already published.
- Release planning needs the module on PSGallery, so publish a new module's first version by hand.

### Fixed

- Honor both numeric dependency range bounds and exclude installed prereleases from normal stable provisioning.
- Publishing a module whose manifest uses a wildcard `MaximumVersion`, such as `1.*`, no longer fails while it installs the dependencies.
- A stable release can be published after an alpha or beta with a higher version.

FileList

Version History

Version Downloads Last updated
0.5.0 (current version) 66 11/21/2026
0.4.1 686 10/19/2026
0.4.0 732 9/13/2026
0.3.5 10 9/11/2026
0.3.4 282 8/25/2026
0.3.3 42 8/25/2026
0.3.2 5 8/25/2026
0.3.1 63 8/25/2026
0.3.0 92 8/25/2026
0.2.0 9 8/25/2026
0.1.19 121 8/24/2026
0.1.18 223 8/24/2026
0.1.17 42 8/24/2026
0.1.16 82 8/21/2026
0.1.15 63 8/21/2026
0.1.14 31 8/19/2026
0.1.13 7 8/18/2026
0.1.11 1,255 5/28/2026
0.1.10 152 5/26/2026
0.1.6 1,957 5/19/2026
0.1.2 85 5/18/2026
0.1.1 11 5/13/2026
Show more