Skip to content

chore(release): 2.1.4 #476

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
HeyItsGilbert merged 1 commit into from
Sep 13, 2026
Merged

chore(release): 2.1.4 #476

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,18 @@

## [Unreleased]

## [2.1.4] - 2026-09-13

### Fixed

- Explicit empty text defaults in JSON manifests now remain empty rather
than being treated as absent, while blank prompt input is accepted only
when a default is declared
([#474](https://github.com/PowerShellOrg/Plaster/pull/474),
closes [#473](https://github.com/PowerShellOrg/Plaster/issues/473))
- Pester 6.1.0 compatibility for mocks and empty `-ForEach` data sets
([#475](https://github.com/PowerShellOrg/Plaster/pull/475))

## [2.1.3] - 2026-06-18

### Fixed
Expand All @@ -24,7 +36,7 @@

### Fixed

- `AddContent` path separators normalised to forward slash on PS5.1 —

Check warning on line 39 in CHANGELOG.md

View workflow job for this annotation

GitHub Actions / Continuous Integration / Run Linters 

Unknown word (normalised) Suggestions: (normalized, normalize, normalizer, normalcies, normalizes)
`Get-ChildItem -Name` returns backslash-separated paths on Windows
PS5.1, causing cross-platform inconsistencies in source/destination
attributes
Expand All @@ -35,7 +47,7 @@
closes [#460](https://github.com/PowerShellOrg/Plaster/issues/460))
- `New-PlasterManifest` emitted `xmlns` inline on PS5.1 — .NET XML
serializer ignores `XmlWriterSettings.NewLineOnAttributes` for
namespace declarations; output is post-processed to normalise

Check warning on line 50 in CHANGELOG.md

View workflow job for this annotation

GitHub Actions / Continuous Integration / Run Linters 

Unknown word (normalise) Suggestions: (normalize, normalcies, normalizes, normale, normals)
formatting
([#464](https://github.com/PowerShellOrg/Plaster/pull/464),
closes [#461](https://github.com/PowerShellOrg/Plaster/issues/461))
Expand Down Expand Up @@ -206,7 +218,7 @@
Studio Code
- Fixed Test-PlasterManifest on non-Windows running .NET Core 2.0 which failed
with path using \ instead of /. Thanks to
[@elmundio87](https://github.com/elmundio87) via PR

Check warning on line 221 in CHANGELOG.md

View workflow job for this annotation

GitHub Actions / Continuous Integration / Run Linters 

Unknown word (elmundio) Suggestions: (edmund, edmund's)
[#282](https://github.com/PowerShell/Plaster/pull/282)

## [1.0.1] 2016-12-16
Expand Down
2 changes: 1 addition & 1 deletion Plaster/Plaster.psd1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
GUID = 'cfce3c5e-402f-412a-a83a-7b7ee9832ff4'

# Version number of this module.
ModuleVersion = '2.1.3'
ModuleVersion = '2.1.4'

# Supported PSEditions
CompatiblePSEditions = @('Desktop', 'Core')
Expand Down
Loading