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

Downgrade and do not automatically update Go deps #1979

Merged
merged 1 commit into from
Nov 15, 2024
Merged

Conversation

fmeum
Copy link
Member

@fmeum fmeum commented Nov 14, 2024

What type of PR is this?

Bug fix

What package or component does this PR mostly affect?

go_deps

What does this PR do? Why is it needed?

With Bzlmod now being the primary way Gazelle is used, we should no longer update the Go dependencies with each release as this just reduces the amount of flexibility afforded to dependent projects. Thanks to MVS, they can easily force newer versions.

Also test with Bazel 8.0.0rc2 in BCR presubmit.

Which issues(s) does this PR fix?

Work towards #1977

Other notes for review

@fmeum fmeum force-pushed the downgrade-fsnotify branch from f9c3f60 to 9d164b7 Compare November 14, 2024 21:10
@fmeum fmeum changed the title Downgrade Go deps to work around fs-notify issue Downgrade and do not automatically update Go deps Nov 14, 2024
@fmeum fmeum requested a review from tyler-french November 14, 2024 21:10
With Bzlmod now being the primary way Gazelle is used, we should no longer update the Go dependencies with each release as this just reduces the amount of flexibility afforded to dependent projects. Thanks to MVS, they can easily force newer versions.
@fmeum fmeum force-pushed the downgrade-fsnotify branch from 9d164b7 to 5a5cac1 Compare November 14, 2024 21:13
@fmeum fmeum marked this pull request as ready for review November 14, 2024 21:13
@fmeum fmeum requested a review from linzhp November 14, 2024 22:00
@fmeum fmeum merged commit 28f43a4 into master Nov 15, 2024
16 checks passed
@fmeum fmeum deleted the downgrade-fsnotify branch November 15, 2024 07:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants