Skip to content

Conversation

@tao12345666333
Copy link
Member

What this PR does / why we need it:

Which issue this PR fixes

Fixes #35

Special notes for your reviewer:

PR Readiness Checklist:

Complete these before marking the PR as ready to review:

  • the CHANGELOG.md release notes have been updated to reflect significant changes

Signed-off-by: Jintao Zhang <[email protected]>
@tao12345666333 tao12345666333 self-assigned this Nov 28, 2025
@tao12345666333 tao12345666333 marked this pull request as ready for review December 1, 2025 09:11
@tao12345666333 tao12345666333 requested a review from a team as a code owner December 1, 2025 09:11
Copy link
Member

@pmalek pmalek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually there's one caveat: this should only happen for releases that are marked as latest.

Otherwise, if we already released 2.1, we'll overwrite the CRDs with 2.0.7.

@tao12345666333
Copy link
Member Author

tao12345666333 commented Dec 1, 2025

Actually there's one caveat: this should only happen for releases that are marked as latest.

Yes, once #2642 is merged, will that mitigate this issue?

Or, I can add a check to see whether the latest has been set?

@pmalek
Copy link
Member

pmalek commented Dec 1, 2025

Actually there's one caveat: this should only happen for releases that are marked as latest.

Yes, once #2642 is merged, will that mitigate this issue?

Or, I can add a check to see whether the latest has been set?

#2642 will only make sure that links are version aware. If the scenario I mentioned above happens, docs specific for 2.1 would get removed.

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Automate developers.konghq.com PR creation during release

3 participants