Skip to content

Conversation

@maxisbey
Copy link
Contributor

@maxisbey maxisbey commented Feb 12, 2026

Recent commits (2182205, 4fc49c6, 1a8c14a) accidentally updated README.md with v2 content after it was intentionally reverted to v1 docs in #1971 (see #1970). This restores README.md to the v1 state. No content is lost — all three commits already applied their changes to README.v2.md.

Commits 2182205, 4fc49c6, and 1a8c14a accidentally updated README.md
with v2 content after it was intentionally reverted to v1 docs in 2137c8f.

Restore README.md to the v1 state. All three commits already applied their
changes to README.v2.md as well, so no content is lost.
Kludex
Kludex previously approved these changes Feb 12, 2026
README.md is frozen at v1 docs. The hook fails with a clear message
directing contributors to edit README.v2.md instead.
@maxisbey maxisbey dismissed stale reviews from felixweinberger and Kludex via 28a766f February 12, 2026 16:12
@maxisbey maxisbey force-pushed the fix/revert-readme-to-v1 branch from e81a431 to 28a766f Compare February 12, 2026 16:12
Co-authored-by: Marcelo Trylesinski <marcelotryle@gmail.com>
@maxisbey maxisbey merged commit 1e0b5c0 into main Feb 12, 2026
47 of 53 checks passed
@maxisbey maxisbey deleted the fix/revert-readme-to-v1 branch February 12, 2026 16:22
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.

3 participants