mirror of https://github.com/raandree/NTFSSecurity
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1.4 KiB
1.4 KiB
| status | date | last-verified | owner | source |
|---|---|---|---|---|
| accepted | 2026-10-04 | 2026-10-04 | shared | maintainer decisions in work package 4 |
Decision 10: One version for the manifest, assemblies, and changelog
- Choice:
ModuleVersioninNTFSSecurity.psd1andAssemblyVersionandAssemblyFileVersionofNTFSSecurity,Security2, andPrivilegeControl(asx.y.z.0) carry the same version (Tests\Manifest.Tests.ps1). The vendoredProcessPrivilegesand the unshippedLogkeep their own versions.CHANGELOG.mddescribes that version (Tests\Release.Tests.ps1throughGet-ReleaseInfo.ps1): a release has a dated section## [x.y.z] - yyyy-MM-dd; a prerelease has its label inPrivateData.PSData.Prereleaseand its notes under## [Unreleased], with no section forx.y.zyet (changelog Option A, amended 2026-10-04 for the 5.0.0 prerelease). - Rationale: Before, the manifest said 4.2.5, the release 4.2.6, and the assemblies 4.2.1.0, 3.2.3.0, and 1.0.0.0; releases bumped the version only in the published copy. One version, set in the repository before the release, identifies a build.
- Consequence: A version bump changes the manifest and three assemblies in
one commit. The final release renames
[Unreleased]to the dated version section and removes the prerelease label. - Context: 5.0.0 is major because the minimum PowerShell version rose to
5.1.
Remove-Item2 -PassThurstays as a deprecated alias of-PassThru.