Allow pinning WordPress core to the latest patch of a chosen minor branch
A
Amaury BALMER
Context
For some projects, we need to keep WordPress core on a specific minor branch (e.g., 6.4.x or 6.5.x) for compatibility and controlled rollout reasons.
Problem
Today, the update behavior forces WordPress core to the latest available version (latest major/minor), rather than allowing us to stay within a selected minor branch and only apply patch releases.
Request
Add an option to choose the WordPress core update policy per site (or per group), such as:
• Latest version (current behavior)
• Latest patch of a selected minor branch (e.g., stay on 6.4.x and automatically update to 6.4.4, 6.4.5, etc.)
Expected behavior
• If a site is pinned to 6.4.x, the system auto-updates only within 6.4.*.
• It should not upgrade to 6.5.0+ unless the policy is changed.
• UI should clearly display the chosen policy and the target branch.
Benefit
This enables safer, more controlled core updates for enterprise contexts:
• better compatibility management (plugins/themes),
• staged rollout across fleets,
• reduced risk of unexpected major/minor upgrades.
Rune Rasmussen
Would basically in regards to automation also be covered by https://wp-umbrella.canny.io/features-request/p/smarter-automated-updates-with-version-level-control-patch-minor-major - so feel free to vote everyone.
A
Amaury BALMER
Rune Rasmussen Yes, it's the same logic. I thought your request was more "plugins" oriented.
Rune Rasmussen
Amaury BALMER you're probably right, and anyhow mine is regarding automated updates, and core isn't yet part of that (but I mentioned it also for future support). Anyhow I realise now that this is probably more about manual updates of core then, kind of similar to my other request here, but again I was more plugin orientated indeed: https://wp-umbrella.canny.io/features-request/p/update-to-older-versions-of-plugins-not-just-latest