-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
chore: update loki modules for 3.0 release #12433
Conversation
Signed-off-by: Edward Welch <edward.welch@grafana.com>
lokiring "github.com/grafana/loki/v3/v3/pkg/util/ring" | ||
util_ring "github.com/grafana/loki/v3/v3/pkg/util/ring" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That import looks wrong
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yup, there were a few of these, fixed them, not sure what happened here with that tool
Signed-off-by: Edward Welch <edward.welch@grafana.com>
updated all protos to use v3 packages as well as import v3 in their deps updated all the integration test files to use v3 imports (missed by the auto tool) fixed a few more v3/v3 errors Signed-off-by: Edward Welch <edward.welch@grafana.com>
Signed-off-by: Edward Welch <edward.welch@grafana.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
Signed-off-by: Edward Welch <edward.welch@grafana.com>
What this PR does / why we need it:
My apologies to anyone with outstanding PR's, but there is no easy way to do this.
This will address the problems we introduced with v2.0 described here when we release 3.0 soon.
This was done using this tool
And this command
mod upgrade -t=3
Also manually updated the
pkg/push/go.mod
file to have a module:module github.com/grafana/loki/v3/pkg/push
Then updated the go.mod to import the push package at v3
Then manually updated all the protos to have v3 package generation as well as use v3 imports
Update for posterity:
It was incorrect to update the submodule (nested module) in the fashion I did, so this PR #12438 reverts that change.
Currently that submodule is untagged, which is not necessarily a problem but something we can solve separately.
To actually make that tagged 3.0 my understanding is we would need to:
module github.com/grafana/loki/pkg/push/v3
pkg/push/v3.0.0
(to publish the module)Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Checklist
CONTRIBUTING.md
guide (required)CHANGELOG.md
updatedadd-to-release-notes
labeldocs/sources/setup/upgrade/_index.md
production/helm/loki/Chart.yaml
and updateproduction/helm/loki/CHANGELOG.md
andproduction/helm/loki/README.md
. Example PRdeprecated-config.yaml
anddeleted-config.yaml
files respectively in thetools/deprecated-config-checker
directory. Example PR