Skip to content

Pog v0.13.0

Latest
Latest
Compare
Choose a tag to compare
@MatejKafka MatejKafka released this 27 Jun 02:03
· 14 commits to main since this release
v0.13.0
4eb5f3c

Full Changelog: v0.12.0...v0.13.0

  • Add support for pog.user.psd1 config files as a general mechanism for package-specific config.
  • Add a package config option to disable updates through Update-Pog. To prevent updates to a specific package, create a pog.user.psd1 file in the package directory next to pog.psd1 and set the content to @{ Frozen = $true }.
  • Get-GitHubRelease now returns SHA-256 digests for each asset, which GitHub recently started providing for new releases.
  • New-PogRepositoryPackage now supports creating generators, and multiple versions of a package.
  • All public cmdlets (both the public API and container cmdlets) should now have documentation available through man.
  • Publish two GitHub Actions for installing Pog to a pipeline and generating a remote repository from a local one.
  • Package generators can now easily Nuget package versions using a new Get-NugetRelease cmdlet.
  • Add a Pog.Utils module that exposes some useful internal cmdlets for public usage, such as the GitHub API cmdlets provided to generators. Run gmo Pog.Utils -ListAvailable | % ExportedCommands for a list of available commands.
  • Improved cmdlet testing system, resulting in quite a lot of added integration tests.
  • Improved information and progress messages for many cmdlets.

Installation

  1. Ensure you have enabled developer mode. Pog currently needs it for symbolic links (hopefully I can get rid of that in a future release).
  2. Download and unpack the archive to your preferred directory for portable applications.
  3. Run ./Pog/setup.cmd (or ./Pog/setup.ps1, if you're in PowerShell).
Assets 3
Loading