Skip to content

docs: publish v4 support dates and the Echo Support offer - #3193

Merged
vishr merged 1 commit into
masterfrom
docs/v4-support-dates
Oct 29, 2026
Merged

vishr merged 1 commit into
masterfrom
docs/v4-support-dates

Conversation

@vishr

@vishr vishr commented Oct 29, 2026

Copy link
Copy Markdown
Member

Publishes the v4 support policy and the paid support offer.

  • v4: bug fixes until 2026-12-31 (unchanged); free, public, security-only fixes until 2027-12-31 for the latest v4 release; the plan after 2027 will be published by 2027-06-30. v4 requires Go 1.26 or later; v5 supports the three most recent Go releases.
  • SECURITY.md: version table with bug and security dates, what security fixes cover and how they ship, and the IPExtractor configuration v4 needs for GHSA-99jh-6h7p-pp36 and GHSA-246p-cpwv-v3jq.
  • README / ROADMAP / funding.json: same dates; no more "LTS".
  • .github/SUPPORT.md: paid support is Echo Support ($4,900/year, invoiced by LabStack LLC, v4 or v5, with or without Echo Pro) with its terms; GitHub Sponsors tiers are sponsorship, not a support contract.

Security fixes stay public for everyone; paid support buys no earlier or private fixes.

v4 bug fixes end on 2026-12-31 as announced. Security-only fixes continue,
free and public, until 2027-12-31 for the latest v4 release; the plan
after 2027 will be published by 2027-06-30.

- SECURITY.md: version table with bug and security dates, what security
  fixes cover and how they ship, the IPExtractor configuration needed
  for two advisories, and that paid support buys no private fixes.
- README and ROADMAP: same dates, drop "LTS", and align the Go policy
  on the three most recent releases (matches CI).
- SUPPORT.md: paid support is Echo Support ($4,900/year, invoiced),
  replacing the GitHub Sponsors Support tier text.
- funding.json: v4 is a maintenance line, not long-term support.
@vishr
vishr merged commit 4deac5d into master Oct 29, 2026
11 checks passed
@vishr
vishr deleted the docs/v4-support-dates branch October 29, 2026 04:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant