Skip to content

Conversation

@flouthoc
Copy link
Collaborator

Fixes issue caught in #6385

What type of PR is this?

/kind api-change
/kind bug
/kind cleanup
/kind deprecation
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake
/kind other

What this PR does / why we need it:

How to verify it

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

None

@flouthoc
Copy link
Collaborator Author

@nalind @Luap99 PTAL

.cirrus.yml Outdated
# Runs within Cirrus's "community cluster"
container:
image: docker.io/library/golang:1.24.0
image: docker.io/library/golang:1.24.7
Copy link
Member

Choose a reason for hiding this comment

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

would it not be better to just use the 1.24 tag without patch release instead? That way it should always use the latest which means we don't have to update this manually so often.

Copy link
Member

Choose a reason for hiding this comment

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

This value exactly matches what's in go.mod.

Copy link
Member

Choose a reason for hiding this comment

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

right but we get bumps like #6385 where dependencies like to bump to go 1.24.2 for whatever reasons... so then it means it requires a manual update here.

Copy link
Member

Choose a reason for hiding this comment

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

Why isn't the bot updating this part, too?

Copy link
Member

Choose a reason for hiding this comment

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

well you could make the action do that, but I don't think you can teach renovate to do that which is what I would care about mainly?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I will rebase this PR with version changed to 1.24 once @nalind agrees.

Copy link
Member

Choose a reason for hiding this comment

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

I thought renovate couldn't handle the layout of the container-libs repository (it hasn't opened one for any of the components we get from it), and keeping the dependency updates automated was part of the motivation for podmanbot.
The do-not-merge bit isn't only being set because it's still being debugged?

Copy link
Member

Choose a reason for hiding this comment

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

renovate cannot handle proper updates in the container-libs repo, for updates here it should work fine in theory. Though we still have to bump it to tagged versions once to make the go pseudo version work.

The point of podmanbot is to vendor every PR as WIP PR here and ensure all buildah tests still pass not to merge them

Copy link
Member

Choose a reason for hiding this comment

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

@flouthoc Make a commit to vendor latest main from go.podman.io/{common,image,storage} and then also make a commit to bump this version here 1.24.2 then it will make all the test PRs work.

Copy link
Collaborator Author

@flouthoc flouthoc Sep 16, 2025

Choose a reason for hiding this comment

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

@Luap99 there is no 1.24.2 on https://hub.docker.com/_/golang , I guess I will just do 1.24

Edit: Nevermind 1.24.2 is there.

@flouthoc flouthoc force-pushed the test_vendor_update_go branch from 62e4ea1 to 233aee6 Compare September 16, 2025 19:53
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 16, 2025
@packit-as-a-service
Copy link

Ephemeral COPR build failed. @containers/packit-build please check.

@flouthoc flouthoc force-pushed the test_vendor_update_go branch from 233aee6 to 5bb6d9e Compare September 16, 2025 19:56
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 16, 2025
@flouthoc flouthoc requested review from Luap99 and nalind September 16, 2025 19:56
Copy link
Member

@Luap99 Luap99 left a comment

Choose a reason for hiding this comment

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

LGTM

@flouthoc
Copy link
Collaborator Author

@nalind @TomSweeneyRedHat PTAL

@TomSweeneyRedHat
Copy link
Member

LGTM
@nalind any objections?

@flouthoc
Copy link
Collaborator Author

@nalind gentle reminder ! is there anything blocking this PR.

Copy link
Member

@nalind nalind left a comment

Choose a reason for hiding this comment

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

It'll do. Maybe the gaps are something agentic AI can fill.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 24, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: flouthoc, Luap99, nalind

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:
  • OWNERS [Luap99,flouthoc,nalind]

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

@TomSweeneyRedHat
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Sep 24, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit af3199a into containers:main Sep 24, 2025
40 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants