Release 3.0.0 - drop SharePoint 2016/2019 support (SE-only) - #61
Merged
Conversation
…r module only SharePoint Server 2016 and 2019 both reached end of support on 14 July 2026. Only Subscription Edition remains supported on-premises. This commit removes the version-detection + PSSnapin path from the SharePoint command surface loaders and the AppFabric-based branch of the Distributed Cache check: - Import-SPSSharePointCommand always imports the SharePointServer module (no more Add-PSSnapin Microsoft.SharePoint.PowerShell branch). - Invoke-SPSCommand's remote baseScript imports the SharePointServer module instead of adding the snap-in. - Get-SPSInstalledProductVersion is kept as a plain 'SharePoint installed?' check and no longer documents the 2013/2016/2019 vs SE build heuristic. - Get-AppFabricStatus drops the Use-CacheCluster / Get-CacheHost / Get-AFCacheHostConfiguration path and its is-SE gate; only the SE cluster code (Get-SPCacheClusterInfo + local Use-SPCacheCluster + Get-SPCacheHostConfig) remains. - Test-SPSWeatherReadiness comment updated accordingly. Refs #60
- README.md: SPSWeather is now compatible with SharePoint Server Subscription Edition only. Added a migration note pointing SP2016/2019 users to v2.3.7. - wiki/Home.md: same compatibility statement and migration note. - wiki/Usage.md: scheduled task note now references the SharePointServer module instead of the Microsoft.SharePoint.PowerShell snap-in. Refs #60
- ModuleVersion 3.0.0. - CHANGELOG.md: new [3.0.0] section (Removed / Changed / Migration). - RELEASE-NOTES.md: rewritten to the 3.0.0 entry only (consumed by release.yml on tag). - Bumped the Pester version guard. Refs #60
Pester Test Results 1 files 15 suites 3s ⏱️ Results for commit 22b7804. |
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 #60.
Breaking change: SPSWeather now targets SharePoint Server Subscription Edition only. SharePoint Server 2016 and 2019 both reached end of support on 14 July 2026.
Removed
Microsoft.SharePoint.PowerShellPSSnapin loader path fromImport-SPSSharePointCommandand fromInvoke-SPSCommand's remote baseScript. SPSWeather always loads theSharePointServermodule now.Get-AppFabricStatus(Use-CacheCluster/Get-CacheHost/Get-AFCacheHostConfiguration). Only the SE cluster path (Get-SPCacheClusterInfo+ localUse-SPCacheCluster+Get-SPCacheHostConfig) remains.Changed
Get-SPSInstalledProductVersionis now a plain "SharePoint installed?" check (no 2013/2016/2019 vs SE build heuristic).README.md,wiki/Home.md,wiki/Usage.md) states the Subscription Edition requirement and points 2016/2019 customers at the previous major release (v2.3.7).ModuleVersionbumped to3.0.0.Validation
Not a cache host.Migration
Customers still running SharePoint Server 2016 or 2019 must stay on SPSWeather v2.3.7 and are encouraged to migrate their farm to Subscription Edition.