// Prepare the DSInternals project for a new release by updating version numbers, release notes, and changelog.
| name | release-preparation |
| description | Prepare the DSInternals project for a new release by updating version numbers, release notes, and changelog. |
If releasing in a new calendar year, update the copyright information first.
C# project files - Update <Version> and <PackageReleaseNotes>:
C# project files - Update <Version> only (not packable):
C++/CLI interop library:
VERSION_MAJOR, VERSION_MINOR, VERSION_REVISION, VERSION_BUILD.[!NOTE] Only increment the version number if the respective assembly has changes or its dependencies have changed.
DSInternals.psd1 - Update ModuleVersion and ReleaseNotes in the PowerShell module manifest file.
[!NOTE]
ModuleVersionmust match the assembly version (e.g.,6.3for assembly6.3.0.0).
dsinternals-psmodule.nuspec - Update <releaseNotes> in the Chocolatey package specification.
CHANGELOG.md - Add new version section following Keep a Changelog format. Update comparison links at the bottom.
Release notes should be consistent across files:
Perform a systematic code review of all source files, focusing on security, performance, backwards compatibility, and design principles.
Ensure that C# and C++/CLI types are documented with XML comments and follow best practices for documentation.
Update copyright year references across the project at the beginning of each calendar year.