suse-edge/Factory
SHA256
13
0
Fork 14
Code Issues Pull Requests 6 Actions Packages Projects Releases Wiki Activity

create new kubectl image #187

Merged
dprodanov merged 1 commits from kubectl-bump into 3.3 2025-06-10 12:30:04 +02:00
Conversation 4 Commits 1 Files Changed 7 +12 -12
dprodanov commented 2025-06-10 11:37:35 +02:00
Owner
Copy Link
No description provided.
dprodanov added 1 commit 2025-06-10 11:37:35 +02:00
create new kubectl image
Some checks failed
Check Release Manifest Local Charts Versions / Check Release Manifest Local Charts Versions (pull_request) Successful in -1m19s
Details
Build PR in OBS / Build PR in OBS (pull_request_target) Failing after 52m58s
Details
13b4cd50e2
steven.hardy commented 2025-06-10 11:51:13 +02:00
Owner
Copy Link

We should perhaps wait until #186 merges and backport both commits together?

We should perhaps wait until #186 merges and backport both commits together?
dprodanov commented 2025-06-10 11:52:35 +02:00
Author
Owner
Copy Link

we need that one first than the other one. I will merge them together starting with this first

we need that one first than the other one. I will merge them together starting with this first
steven.hardy approved these changes 2025-06-10 11:55:41 +02:00
steven.hardy left a comment
Owner
Copy Link

Ok I expected us to pick both commits into a single PR but whatever works :)

I would suggest using a prefix for backport PR titles though e.g [3.3] create new kubectl image - this is a good habit for when we have backports which need to be tracked through multiple release branches

Ok I expected us to pick both commits into a single PR but whatever works :) I would suggest using a prefix for backport PR titles though e.g `[3.3] create new kubectl image` - this is a good habit for when we have backports which need to be tracked through multiple release branches
👍 1
dprodanov commented 2025-06-10 12:29:52 +02:00
Author
Owner
Copy Link

agreed, for some reason I did not do it here but only on SV updates. I usually try to keep the versions like you suggest in all my PRs

agreed, for some reason I did not do it here but only on SV updates. I usually try to keep the versions like you suggest in all my PRs
dprodanov merged commit 43d5ffa2bd into 3.3 2025-06-10 12:30:04 +02:00
dprodanov deleted branch kubectl-bump 2025-06-10 12:30:05 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
steven.hardy
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
amorgante atanasdinov atrendafilov dbekhit dprodanov eminguez fdegirmenci ipetrov117 jtomasek kzhelyazkov mchiappero nbelouin roxenham steven.hardy
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: suse-edge/Factory#187
No description provided.
Delete Branch "kubectl-bump"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?