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

[CI:BUILD] Add golang 1.21 update warning #22073

Merged
merged 1 commit into from
Mar 26, 2024

Conversation

cevich
Copy link
Member

@cevich cevich commented Mar 18, 2024

This is needed on the off-chance that some tool or a human suggests updating the minimum version to 1.21 or later. Since doing so would cause Fedora and Debian to start behaving differently WRT builds.

Ref: containers/automation#187

Does this PR introduce a user-facing change?

None

Copy link

Cockpit tests failed for commit 4b295e0ab49ffe649cda4f6a5ffe79863a6669fc. @martinpitt, @jelly, @mvollmer please check.

@cevich cevich force-pushed the add_golang121_warning branch from f5a4b1f to d10cbe8 Compare March 18, 2024 15:20
@cevich
Copy link
Member Author

cevich commented Mar 18, 2024

@nalind @rhatdan @mtrmac @Luap99 PTAL. If this language is acceptable, I'd like to dupe this change into Buildah and Skopeo as well as any other golang repos you think important.

See also containers/automation#187

Copy link

Cockpit tests failed for commit f5a4b1fa9182ab5f188cb4df9226cd95d214e71e. @martinpitt, @jelly, @mvollmer please check.

Copy link

Cockpit tests failed for commit d10cbe89fbbc3ba0e6e6380f089bc5a4b5d8ae2d. @martinpitt, @jelly, @mvollmer please check.

Copy link
Collaborator

@mtrmac mtrmac left a comment

Choose a reason for hiding this comment

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

I do like the idea of the warning.

It might be a bit clearer to explicitly separate the two:

  • go is set to the latest go of all dependencies. That can’t be prevented, other than not updating the dependency.
  • toolchain is bumped when increasing go for some reason (and based on the currently running tools, not on what any dependency declares). If, at the time of the go bump (or later), we choose a toolchain version acceptable to us, it is not going to be auto-updated until a go auto-update happens.

This is needed on the off-chance that some tool or a human suggests
updating the minimum version to 1.21 or later. Since doing so would
cause Fedora and Debian to start behaving differently WRT builds.

Signed-off-by: Chris Evich <[email protected]>
@cevich cevich force-pushed the add_golang121_warning branch from d10cbe8 to 48b8d7f Compare March 26, 2024 18:41
@cevich cevich requested a review from mtrmac March 26, 2024 18:41
@cevich
Copy link
Member Author

cevich commented Mar 26, 2024

@nalind @rhatdan @mtrmac @Luap99 PTAL. I've updated the comment text based on Miloslav's comments/corrections. Assuming it's correct now, after this merges, I intend to make a similar change in buildah and skopeo (and any other Renovate-managed repos you think are important).

Copy link
Collaborator

@mtrmac mtrmac left a comment

Choose a reason for hiding this comment

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

This LGTM

Meanwhile, https://bodhi.fedoraproject.org/updates/?packages=golang suggests that F38 now does support Go 1.21. So maybe we can update soon — but that is not a reason to not merge this PR right now.

@mtrmac
Copy link
Collaborator

mtrmac commented Mar 26, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 26, 2024
Copy link
Member

@ashley-cui ashley-cui left a comment

Choose a reason for hiding this comment

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

/approve

Copy link
Contributor

openshift-ci bot commented Mar 26, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ashley-cui, cevich

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 26, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 52a64aa into containers:main Mar 26, 2024
43 checks passed
@stale-locking-app stale-locking-app bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Jun 25, 2024
@stale-locking-app stale-locking-app bot locked as resolved and limited conversation to collaborators Jun 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. release-note-none
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants