Latest nightly release

This pre-release is automatically updated after each successful CI run on the main branch. You probably want to use one of the stable releases below instead.

Pog v0.14.0

Full Changelog: v0.13.0...v0.14.0

• When package installation fails, the manifest is rolled back to the previous version to keep it in sync.
• Use .NET HttpClient for downloading everything instead of BITS to improve reliability and startup time.
• Add support for declaring non-portable paths in a package manifest.
• Find-Pog now supports wildcards.
• More efficient hash retrieval for GitHub assets in manifest generators.
• More informative error messages in various parts of Pog.
• A lot of bug fixes, minor improvements, and significant internal refactors.

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).

Pog v0.13.0

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).

Pog v0.12.0

Full Changelog: v0.11.0...v0.12.0

• Exported commands and shortcuts are now automatically kept in sync. It is no longer necessary to call Export-Pog after updating to a new version, as long as no new exports were added since the last version.
• Package repository is now unified with package generator repository – each generated package stores the generator at .pog/generator.psd1 (see 038f946 for rationale).
• Added new package generator cmdlets to make generating packages from GitHub releases much easier.
• When overwriting an export, print the package that owned the previous export.
• Use a Pog-specific User-Agent for all network requests by default.
• Added Get-PogRepository cmdlet.
• Release .zip is now generated from the CI.
• Lot of bugfixes and error message improvements.

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).

Pog v0.11.0

Full Changelog: v0.10.0...v0.11.0

• Added a very basic Update-Pog command which lists and updates all outdated packages.
• Added an automated update script for Pog itself (see README).
• Renamed multiple commands to make the names more consistent (noun for most commands is now either Pog or PogRepository).
• Install-Pog and Uninstall-Pog should now be a bit more resistant to tampering from Windows Defender.
• Export-Command and Export-Shortcut now correctly handle name casing changes.
• Lots of internal fixes and improvements.

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.

Pog v0.10.0

Full Changelog: v0.9.2...v0.10.0

• Import-Pog can now show a diff against the previous imported version (-Diff).
• Uninstall-Pog now detects if the package directory is in use before attempting to remove it.
• Added support for using multiple package repositories in a stack (configure using Set-PogRepository).
• Lots of minor bugfixes and improvements.

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.

Pog v0.9.2

Full Changelog: v0.9.1...v0.9.2

• Make OpenedFilesView optional. This speeds up the first-time setup and avoids a 3rd party dependency by default.
• Minor UI improvements.

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.

Pog v0.9.1

Full Changelog: v0.9.0...v0.9.1

• Add support for running Pog from DOS drives created with subst.
• Add documentation for creating packages.
• Improve documentation 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.

Pog v0.9.0

Full Changelog: v0.8.3...v0.9.0

• Add a shell.ps1 script to make it easier to use Pog without adding it to PATH and PSModulePath.
• When re-running setup.ps1 on a new machine, it prompts to automatically re-enable all packages.
• Simplify uninstallation by adding support for Disable-Pog Pog.
• Better error messages when Enable-Pog fails.

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.

Pog v0.8.3

Full Changelog: v0.8.2...v0.8.3

• Add filtering for remote package version autocomplete. (huh, guess I forgot about that one)

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.