Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

✨ k/k 1.31.0 rebase #92

Merged
merged 1 commit into from
Sep 11, 2024
Merged

✨ k/k 1.31.0 rebase #92

merged 1 commit into from
Sep 11, 2024

Conversation

mjudeikis
Copy link
Contributor

@mjudeikis mjudeikis commented Aug 17, 2024

Summary

Rebase to 1.31.

Changes:

  1. Update all external generators to match future versions of kcp
  2. regression (our side kind of) fix for genclient:skipVerbs=list,watch. If skipped, on our end we skip List, Watch and DeleteCollections. It should be just List and Watch. Need to fix this or redo our generators
  3. Make definition def.Strict = false as we (k/k) changed some tags where now they are group=, meaning its not full key-value-pair. This passes the validation as its non-strict mode. This could have consequences that we miss some API groups in the future.

In general, we should see how to make these generators closer to upstream v2 as now they are bespoke solutions. Or live with a bespoke solution. I would better invest time in refactoring them while we have time, and it's not a hard blocker for rebase.

Related issue(s)

Fixes #

Release Notes

1.31 rebase 
Make generator stricts=false 

@kcp-ci-bot kcp-ci-bot added dco-signoff: yes Indicates the PR's author has signed the DCO. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Aug 17, 2024
@mjudeikis mjudeikis marked this pull request as draft August 17, 2024 11:54
@kcp-ci-bot kcp-ci-bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 17, 2024
@mjudeikis mjudeikis marked this pull request as ready for review August 17, 2024 12:05
@kcp-ci-bot kcp-ci-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 17, 2024
@mjudeikis mjudeikis force-pushed the 1.31.0-prep branch 3 times, most recently from 4969f43 to ad2daa2 Compare September 8, 2024 15:01
@kcp-ci-bot kcp-ci-bot added the lgtm Indicates that a PR is ready to be merged. label Sep 10, 2024
@kcp-ci-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: fc304296f4af40b279cb31aec95cf54cddf06ee2

Copy link
Member

@embik embik left a comment

Choose a reason for hiding this comment

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

/approve

@kcp-ci-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: embik

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kcp-ci-bot kcp-ci-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 11, 2024
@kcp-ci-bot kcp-ci-bot merged commit cd963f0 into kcp-dev:main Sep 11, 2024
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has signed the DCO. lgtm Indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants