Skip to content

Conversation

@kranurag7
Copy link
Member

Signed-off-by: kranurag7 <81210977+kranurag7@users.noreply.github.com>
debasishbsws
debasishbsws previously approved these changes Dec 29, 2025
@octo-sts octo-sts bot added the bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. label Dec 29, 2025
Signed-off-by: kranurag7 <81210977+kranurag7@users.noreply.github.com>
Signed-off-by: kranurag7 <81210977+kranurag7@users.noreply.github.com>
Signed-off-by: kranurag7 <81210977+kranurag7@users.noreply.github.com>
Signed-off-by: kranurag7 <81210977+kranurag7@users.noreply.github.com>
Signed-off-by: kranurag7 <81210977+kranurag7@users.noreply.github.com>
Copy link
Member

@debasishbsws debasishbsws left a comment

Choose a reason for hiding this comment

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

LGTM! 👍
This is a great consolidation that simplifies our Kubernetes package maintenance. The approach of moving the -latest subpackages into the version-specific configs (like kubernetes-1.35.yaml) makes a lot of sense.

this will produce version streams like kubectl-latest-1.35.0-r1 and kubectl-latest-1.36.0-r0 when 1.36 releases. the package manager will always resolve to the highest version number, so we will automatically get the true latest version. This is better than the previous approach where we had to manually update a static pointer.

@kranurag7 kranurag7 merged commit 77ba0df into wolfi-dev:main Jan 5, 2026
16 of 17 checks passed
@kranurag7 kranurag7 deleted the kr/k8s-1.35 branch January 5, 2026 07:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants