Clarify SDK version support policy with concrete example

[Copilot]

Addresses feedback on #925 requesting clarification of the version support policy. The phrase "most recent 2 releases (major, minor)" was ambiguous about whether it meant major or minor versions.

Changes

• Updated support policy text to explicitly state "2 most recent minor versions"
• Added concrete example: 2.1.0 and 2.0.0 are supported, 1.9.0 is not

This clarifies that support follows the 2 most recent minor releases within the current major version, not the 2 most recent major versions.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• bitbucket.org
  • Triggering command: /usr/local/bin/node /home/REDACTED/work/devcycle-docs/devcycle-docs/node_modules/.store/@docusaurus-core-virtual-915c38c41e/package/bin/docusaurus.mjs build (dns block)
• gitlab.com
  • Triggering command: /usr/local/bin/node /home/REDACTED/work/devcycle-docs/devcycle-docs/node_modules/.store/@docusaurus-core-virtual-915c38c41e/package/bin/docusaurus.mjs build (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[cloudflare-workers-and-pages]

Deploying devcycle-docs with    Cloudflare Pages

Latest commit:	0b5897d
Status:	✅  Deploy successful!
Preview URL:	https://531f444a.devcycle-docs.pages.dev
Branch Preview URL:	https://copilot-sub-pr-925.devcycle-docs.pages.dev

View logs

[Copilot]

Pull Request Overview

This PR clarifies the SDK support policy documentation by providing a more precise explanation of version support with a concrete example.

Key Changes:

• Updated the support timeline description to explicitly state "2 most recent minor versions" with a practical example showing versions 2.1.0, 2.0.0, and 1.9.0

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The support policy statement is ambiguous. The example shows supporting minor versions within the same major version (2.1.0 and 2.0.0), but then excludes 1.9.0 from a different major version. This doesn't clarify whether '2 most recent minor versions' means across all versions or within each major version. Consider rephrasing to: 'We actively support the 2 most recent minor versions within the current major version of each SDK. For example, if the latest versions are 2.1.0 and 2.0.0, both are supported, but 2.9.0 from a previous iteration would not be.' Alternatively, if cross-major support is intended, use: 'We actively support the 2 most recent releases of each SDK. For example, if versions 2.1.0 and 2.0.0 are the latest, both are supported. Version 1.9.0 from the previous major release is not supported.'

Suggested change

	We actively support the 2 most recent minor versions of each SDK. For example, if the latest versions are 2.1.0 and 2.0.0, both are supported, but 1.9.0 is not. Support includes:
	We actively support the 2 most recent minor versions within the current major version of each SDK. For example, if the latest versions are 2.1.0 and 2.0.0, both are supported, but 2.9.0 from a previous iteration would not be. Support includes: