Requirement
Per Scale Computing's official Software Support Guide, support covers the two most recent
Standard Production releases, plus any Early/Limited Production release within 12 months of its
release (unless superseded). Nothing is currently EOL — this is about the actively-maintained
window, not removing anything that's actually end-of-life.
As of 2026-08-07, that window is 9.5 and 9.6. This window shifts as new releases ship — please
reconfirm the current two Standard Production releases when picking this up rather than relying on
this snapshot. Required/blocking CI coverage should track whichever versions are current at that
time.
Versions older than the window (currently 9.1–9.4)
Move from required/blocking to best-effort: no longer required to gate CI/merge/release, but avoid
unnecessary breakage where practical. A non-blocking job, a reduced-frequency check, or a single
canary version are all reasonable approaches — your call, just note which one in the PR/response.
Note
This doesn't affect existing users on older HyperCore versions — Ansible Galaxy keeps every
published collection release pinnable, so they can keep using whichever version was already
validated for their setup.
Requirement
Per Scale Computing's official Software Support Guide, support covers the two most recent
Standard Production releases, plus any Early/Limited Production release within 12 months of its
release (unless superseded). Nothing is currently EOL — this is about the actively-maintained
window, not removing anything that's actually end-of-life.
As of 2026-08-07, that window is 9.5 and 9.6. This window shifts as new releases ship — please
reconfirm the current two Standard Production releases when picking this up rather than relying on
this snapshot. Required/blocking CI coverage should track whichever versions are current at that
time.
Versions older than the window (currently 9.1–9.4)
Move from required/blocking to best-effort: no longer required to gate CI/merge/release, but avoid
unnecessary breakage where practical. A non-blocking job, a reduced-frequency check, or a single
canary version are all reasonable approaches — your call, just note which one in the PR/response.
Note
This doesn't affect existing users on older HyperCore versions — Ansible Galaxy keeps every
published collection release pinnable, so they can keep using whichever version was already
validated for their setup.