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

What If... our Go dependencies were current? #383

Merged
merged 4 commits into from
May 10, 2023
Merged

What If... our Go dependencies were current? #383

merged 4 commits into from
May 10, 2023

Conversation

mckern
Copy link
Contributor

@mckern mckern commented May 4, 2023

What-if-Watcher

This is ground work for some other maintenance PRs that are coming over the wire soon. All existing tests are passing for this, but test coverage is still kind-of low so take this with a grain of salt.

$ go test -cover ./...
?   	github.com/segmentio/chamber/v2	[no test files]
ok  	github.com/segmentio/chamber/v2/cmd	1.001s	coverage: 18.1% of statements
ok  	github.com/segmentio/chamber/v2/environ	0.633s	coverage: 58.0% of statements
ok  	github.com/segmentio/chamber/v2/store	9.671s	coverage: 46.9% of statements
ok  	github.com/segmentio/chamber/v2/utils	0.940s	coverage: 100.0% of statements

closes #381

mckern added 3 commits May 4, 2023 15:02
This brings with it a LOT of dependency upgrades, which is probably a
good thing overall. Whether or not it breaks tests is a different
question. Note that this also includes a change to the declared
package path for analytics-go from
"gopkg.in/segmentio/analytics-go.v3"
to "github.com/segmentio/analytics-go/v3".
analytics-go has changed their
import path from "gopkg.in/segmentio/analytics-go.v3" to
"github.com/segmentio/analytics-go/v3", so we must update accordingly.
nitrocode
nitrocode previously approved these changes May 4, 2023
@mckern mckern marked this pull request as ready for review May 9, 2023 00:19
@mckern mckern requested a review from a team as a code owner May 9, 2023 00:19
@mckern mckern changed the title Experiment: what if everything was current? What If... our Go dependencies were current? May 9, 2023
alecjacobs5401
alecjacobs5401 previously approved these changes May 9, 2023
Copy link
Contributor

@alecjacobs5401 alecjacobs5401 left a comment

Choose a reason for hiding this comment

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

Two minor comments that I don't think are necessarily blockers for this PR specifically.

Thanks for doing this Ryan!

.github/workflows/release.yml Outdated Show resolved Hide resolved
.github/workflows/release.yml Outdated Show resolved Hide resolved
@mckern mckern merged commit d554ab6 into master May 10, 2023
@mckern mckern deleted the mckern/what-if branch May 10, 2023 18:05
@jmeridth
Copy link

@alecjacobs5401 when can we see a new release? Thank you so much for getting this change over the finish line. Cheers.

@alecjacobs5401
Copy link
Contributor

@jmeridth We're finishing up some internal testing and potentially getting some other things cleaned up. I'll defer to @mckern on a release for all this

@mckern
Copy link
Contributor Author

mckern commented May 12, 2023

@alecjacobs5401 @jmeridth I need to write release notes and update the README. That's the blocker right now.

@jmeridth
Copy link

@mckern saw the release happened last week. Thank you.

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.

Please consider dropping support for older golang versions like go1.15 and go1.16
4 participants