Release 2.0.0 - drop SharePoint 2016/2019 support (SE-only) - #13
Merged
Merged
Conversation
…r module only SharePoint Server 2016 and 2019 reached end of support on 14 July 2026, so the toolkit now targets Subscription Edition only. Remove the installed-build detection and the Microsoft.SharePoint.PowerShell PSSnapin branch from the entry script; load the SharePointServer module only (idempotent), guarded by a clear 'SharePoint installed' check via Get-SPSInstalledProductVersion (which throws when SharePoint is absent). Neutralize the version-specific help examples (CONTOSO-PROD-SP2019 -> CONTOSO-PROD-SPSE) and drop the now-unused Add-PSSnapin/Get-PSSnapin stubs from the module Pester tests. Refs #12
State Subscription Edition as the only supported version in the README and the Troubleshooting wiki page, and remove the description of the legacy Microsoft.SharePoint.PowerShell snap-in / 2016-vs-2019 loading branch. Add a migration note pointing users still on SharePoint Server 2016 or 2019 (end of support 14 July 2026) to the previous major release (v1.4.0). Refs #12
Bump the SPSCleanDependencies.Common module manifest to 2.0.0 (major, breaking: SharePoint 2016/2019 support dropped, Subscription Edition only). Prepend the 2.0.0 section to CHANGELOG.md (Removed / Changed / Migration) keeping the full history, and overwrite RELEASE-NOTES.md with the 2.0.0 block used as the GitHub Release body. Refs #12
Pester Test Results100 tests 100 ✅ 1s ⏱️ Results for commit ffd3db3. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #12
Summary
SharePoint Server 2016 and 2019 both reached end of support on 14 July 2026. This release makes SPSCleanDependencies target SharePoint Server Subscription Edition only.
Breaking change → major version bump 1.4.0 → 2.0.0.
What changed
Code (
refactor)Microsoft.SharePoint.PowerShellPSSnapin loading path (Get-PSSnapin/Add-PSSnapin) fromSPSCleanDependencies.ps1.SharePointServermodule only (idempotent), guarded by a clear "SharePoint installed" check viaGet-SPSInstalledProductVersion(throws when SharePoint is absent).CONTOSO-PROD-SP2019→CONTOSO-PROD-SPSE) and dropped the now-unusedAdd-PSSnapin/Get-PSSnapinstubs from the module Pester tests.Docs (
docs)wiki/Troubleshooting.mdnow state Subscription Edition as the only supported version, with a migration note.Version (
release)ModuleVersion→2.0.0; CHANGELOG 2.0.0 section (Removed / Changed / Migration); RELEASE-NOTES overwritten with the 2.0.0 block.Validation
Migration
Users still running SharePoint Server 2016 or 2019 should stay on the previous major release (v1.4.0).