Repository navigation
Release 2.0.0 - drop SharePoint 2016/2019 support (SE-only) - #29
Merged
Merged
Conversation
…r module only SharePoint 2016 and 2019 reached end of support on 14 July 2026; only Subscription Edition remains. Import-SPSSharePointCommand no longer detects the product version nor loads the Microsoft.SharePoint.PowerShell PSSnapin: it imports the SharePointServer module only (idempotent), keeping a clear 'SharePoint not installed' guard. Get-SPSInstalledProductVersion stays as that installed? guard (doc simplified). Test-SPSUserSyncReadiness drops the 2013/2016-2019/SE version label and reports the build. Comments in the two scripts updated accordingly. Refs #28
State compatibility with SharePoint Server Subscription Edition only, note that 2016/2019 reached end of support on 14 July 2026 (use v1.3.4 there), and replace the Microsoft.SharePoint.PowerShell snap-in wording with the SharePointServer module across the README and wiki. Refs #28
Drop SharePoint 2016/2019 support (end of support 14 July 2026); SPSUserSync is now Subscription Edition only. Bump ModuleVersion to 2.0.0, prepend the 2.0.0 CHANGELOG section (Removed / Changed BREAKING / Migration) and reset RELEASE-NOTES to the 2.0.0 block. Users on 2016/2019 stay on v1.3.4. Refs #28
Pester Test Results101 tests 101 ✅ 3s ⏱️ Results for commit d961c75. |
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
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.
Closes #28.
Why
SharePoint Server 2016 and 2019 both reached end of support on 14 July 2026. Only Subscription Edition (SE) remains supported. This drops the dual load path and makes SPSUserSync SE-only — a breaking change, hence the major bump
1.3.4→2.0.0.What
Refactor (SE-only command surface)
Import-SPSSharePointCommandno longer detects the product version nor loads the deprecatedMicrosoft.SharePoint.PowerShellPSSnapin. It imports theSharePointServermodule only (idempotent), keeping a clear "SharePoint not installed" guard and throw. Returns'SharePointServer'.Get-SPSInstalledProductVersionstays as the "installed?" guard (documentation simplified; behaviour unchanged).Test-SPSUserSyncReadiness.ps1drops the 2013 / 2016-2019 / SE version-label branch and reports the build number; snap-in wording → module.SPSyncUserInfoList.ps1/SPSyncUserProfile.ps1updated.Docs
SharePointServermodule instead of the snap-in.Release
ModuleVersion→2.0.0; CHANGELOG## [2.0.0](Removed / Changed BREAKING / Migration); RELEASE-NOTES reset to the 2.0.0 block.Migration
Environments still on SharePoint 2016/2019 must stay on the previous major release v1.3.4 (which keeps the PSSnapin path). No config change when moving to 2.0.0 on SE.
Validation
2.0.0.refactor/docs/chore(release).