feat/PL 6131/operator compat#282
Merged
Merged
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 129468e. Configure here.
75f9cf2 to
18e84db
Compare
silphid
approved these changes
Jun 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Note
Low Risk
Two struct-tag changes affect serialization only; no runtime logic or validation paths are modified in this diff.
Overview
Aligns Project and Release API types with Kubernetes operator / apimachinery expectations via struct tag tweaks only.
Project: The embedded
metav1.ObjectMetaonProjectMetadatano longer carries a separatejson:"metadata"on the inline field—onlyyaml:",inline"—so JSON encoding matches how nested metadata is expected for CRD-style resources.Release:
ReleaseSpec.ChartJSON encoding addsomitzero, so an unset/zeroReleaseChartis omitted from JSON instead of always serializingchart, treating chart as optional for operator consumers.Reviewed by Cursor Bugbot for commit 18e84db. Bugbot is set up for automated code reviews on this repo. Configure here.