v2.1 release follow ups by jbw976 · Pull Request #6903 · crossplane/crossplane

jbw976 · 2025-11-05T22:15:59Z

Description of your changes

Updated, in a single PR, the following on main:

The releases table in the README.md, removing the now old unsupported release and adding the new one.

The baseBranches list in .github/renovate.json5, removing the now old unsupported release.

I have:

Read and followed Crossplane's contribution process.
Run earthly +reviewable to ensure this PR is ready for review.
~~Added or updated unit tests.~~
~~Added or updated e2e tests.~~
~~Linked a PR or a docs tracking issue to document this change.~~
~~Added backport release-x.y labels to auto-backport this PR.~~
~~Followed the API promotion workflow if this PR introduces, removes, or promotes an API.~~

Need help with this checklist? See the cheat sheet.

Signed-off-by: Jared Watts <jbw976@gmail.com>

coderabbitai · 2025-11-05T22:17:33Z

📝 Walkthrough

Walkthrough

The README.md was updated to reflect release schedule changes: v1.19 was removed, v2.1's release date was specified as November 5, 2025, and a new v2.4 release row was added with an expected release date of Early August 2026 and EOL in May 2027.

Changes

Cohort / File(s)	Change Summary
Release Schedule Documentation `README.md`	Removed v1.19 release entry; updated v2.1 release date from "Early Nov '25" to "Nov 5, 2025"; added new v2.4 release row with Early Aug '26 release and May 2027 EOL dates

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'v2.1 release follow ups' clearly describes the main change—updating release information following the v2.1 release—and is well under the 72-character limit.
Description check	✅ Passed	The description directly relates to the changeset, referencing the specific release issue and detailing the exact updates made to README.md and renovate.json5.
Breaking Changes	✅ Passed	PR only modifies README.md and .github/renovate.json5, which are not API or CLI code files under apis/ or cmd/ directories.
Feature Gate Requirement	✅ Passed	PR contains only administrative and documentation updates to README.md and renovate.json5; no new experimental features affecting apis/** or runtime behavior are introduced.

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 209df7d and cd7c8bc.

⛔ Files ignored due to path filters (1)

.github/renovate.json5 is excluded by none and included by none

📒 Files selected for processing (1)

README.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

**/*.md

⚙️ CodeRabbit configuration file

**/*.md: Ensure Markdown files are wrapped at 100 columns for consistency and
readability. Lines can be longer if it makes links more readable, but
otherwise should wrap at 100 characters. Check for proper heading
structure, clear language, and that documentation is helpful for users.

Files:

README.md

🔍 Remote MCP

Relevant Context for PR Review

Crossplane Release Maintenance Policy

Crossplane releases on a quarterly (13-week) cadence, with the most recent three releases under maintenance at any given time. When Crossplane cuts a new release, the fourth most recent release reaches end of life (EOL). Users can expect Crossplane to maintain any given release for nine months.

Release Context - v1.19 removal is justified: The PR removes v1.19 from the releases table and renovate.json5 configuration, which aligns with this policy. Since v2.1 is the release being followed up on, this would trigger the retirement of older v1.x versions that no longer fall within the "three most recent releases" window.

Renovate Configuration in Crossplane

The renovate.json5 file manages which release branches Renovate (a dependency update automation tool) should target. Renovate repositories for Crossplane extensions follow similar branching conventions to upstream Crossplane, where the release process assumes the workflow executing in branches with the release-* prefix. main is often included. Removing an old release from baseBranches prevents unnecessary dependency update automation for unmaintained versions.

Release Documentation and Maintenance

The updates align with Crossplane's standard release follow-up procedures. Release-specific updates on the release branch typically include documentation. Keeping the README.md releases table current is important for communicating to users which versions are actively maintained.

Checkpoints for Review

The PR checklist indicates:

✅ Contribution process followed and earthly +reviewable passed
⚠️ Note: Several checklist items remain unchecked (tests, docs, backport labels, API promotion workflow) - though these may not be applicable to documentation-only changes

🔇 Additional comments (1)

README.md (1)

25-32: Releases table update looks good—dates and EOL calculations are consistent.

The changes correctly reflect the v2.1 release happening on November 5, 2025, and reasonably add v2.4 to the forward-looking schedule. I noticed the pattern of precise dates for past releases (v1.20, v2.0, v2.1) and approximate dates for future releases (v2.2–v2.4), which makes sense for planning purposes.

A quick clarification: the PR objectives mention updating .github/renovate.json5 as well—is that change being handled separately, or should it also be included in this review?

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

jbw976 added 2 commits November 5, 2025 14:14

README: update releases table for v2.1 release

1001c2f

Signed-off-by: Jared Watts <jbw976@gmail.com>

build: remove v1.19 from renovate baseBranches

cd7c8bc

Signed-off-by: Jared Watts <jbw976@gmail.com>

jbw976 requested review from a team as code owners November 5, 2025 22:16

jbw976 requested review from bassam, bobh66, negz and phisco November 5, 2025 22:16

jbw976 mentioned this pull request Nov 5, 2025

Cut v2.1.0 Release on November 5, 2025 crossplane/release#51

Closed

56 tasks

negz approved these changes Nov 5, 2025

View reviewed changes

jbw976 merged commit 7a6e710 into crossplane:main Nov 5, 2025
24 checks passed

BrewTestBot mentioned this pull request Feb 18, 2026

crossplane 2.2.0 Homebrew/homebrew-core#268085

Merged

coderabbitai bot mentioned this pull request Feb 18, 2026

readme: Leave a note about v1.20 extended support #7153

Merged

2 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

v2.1 release follow ups#6903

v2.1 release follow ups#6903
jbw976 merged 2 commits intocrossplane:mainfrom
jbw976:2.1-rel-up

jbw976 commented Nov 5, 2025

Uh oh!

coderabbitai bot commented Nov 5, 2025

Walkthrough

Changes

Estimated code review effort

Relevant Context for PR Review

Crossplane Release Maintenance Policy

Renovate Configuration in Crossplane

Release Documentation and Maintenance

Checkpoints for Review

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

jbw976 commented Nov 5, 2025

Description of your changes

Uh oh!

coderabbitai bot commented Nov 5, 2025

Walkthrough

Changes

Estimated code review effort

Pre-merge checks

Relevant Context for PR Review

Crossplane Release Maintenance Policy

Renovate Configuration in Crossplane

Release Documentation and Maintenance

Checkpoints for Review

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants