Skip to content

docs: support only the newest release, with the CRA fix commitment product-wide (#119) - #120

Merged
rubentalstra merged 2 commits into
mainfrom
docs/support-latest-release-only
Oct 19, 2026
Merged

rubentalstra merged 2 commits into
mainfrom
docs/support-latest-release-only

Conversation

@rubentalstra

Copy link
Copy Markdown
Contributor

What changed and why

The owner decided on 2026-10-19 that only the newest release of each product is supported. SECURITY.md now says that every earlier release stops receiving fixes when a new one is published, with no maintenance branches, no long-term-support line and no backports, and that upgrading is free. The Cyber Resilience Act commitment is stated product-wide: Cadasto B.V. keeps publishing security fixes for at least five years after each release (Regulation (EU) 2024/2847 Art 13(8)) and ships them only in the newest release (Art 13(10)).

The supported-versions table lists the ferrohealth-ui crate with the newest published release as its supported version and the newest release as where fixes ship. No API changes; a console needs no change. No other page in this repository stated a support period.

Closes #119

Licensing of contributions

  • I accept the terms in CONTRIBUTING.md § Licensing of contributions: I have the right to submit this work, I license it under the project licence of the version it lands in, and I grant the Licensor the relicensing right stated there.

…oduct-wide (#119)

Only the newest release is supported: an earlier release receives no fix,
backport or patch release, and upgrading is free. Cadasto B.V. commits to
keep publishing security fixes for at least five years after each release
(Regulation (EU) 2024/2847 Art 13(8)) and ships them only in the newest
release (Art 13(10)).
@rubentalstra rubentalstra added the documentation Docs-only work. Maps to a docs/ branch and a docs: commit. label Oct 19, 2026
@rubentalstra
rubentalstra added this pull request to the merge queue Oct 19, 2026
@rubentalstra
rubentalstra removed this pull request from the merge queue due to a manual request Oct 19, 2026
@rubentalstra
rubentalstra merged commit 606cbd8 into main Oct 19, 2026
10 checks passed
@rubentalstra
rubentalstra deleted the docs/support-latest-release-only branch October 19, 2026 17:35
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Docs-only work. Maps to a docs/ branch and a docs: commit.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: support only the newest release, with the CRA fix commitment product-wide

1 participant