-
Notifications
You must be signed in to change notification settings - Fork 82
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
prepare 6.9.0 release #268
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
add daily package build test in CI
bump SDK version for traffic allocation feature
…en big segments are enabled
enable accidentally-disabled tests in CI and fix problem with initialization errors
more debug logging, less info logging for big segments logic
…rting stream in this case
…-warning (#1) make logging of big segments patch version mismatch clearer and use Warn level
(#2) fix DynamoDB updates for big segments metadata
# Conflicts: # internal/core/bigsegments/sync.go
update Redis/DDB integrations to remove misleading error logging
* chore: drop go 1.17,1.18 tests; add go 1.20 * fix: Fix CVE-2022-41723 by overriding golang.org/x/net to v0.7.0
go1.20.2 (released 2023-03-07) includes a security fix to the crypto/elliptic package, as well as bug fixes to the compiler, the covdata command, the linker, the runtime, and the crypto/ecdh, crypto/rsa, crypto/x509, os, and syscall packages. go1.19.7 (released 2023-03-07) includes a security fix to the crypto/elliptic package, as well as bug fixes to the linker, the runtime, and the crypto/x509 and syscall packages.
* chore: update api-client-go to v12.0.0
* chore: modify testUpdatedSDKKeyWithExpiry to wait for healthy relay status * increase statusPollTimeout and Interval for integration tests
* chore: upgrade goreleaser to 1.16.1 and use conventional release artifact filenames * chore: add tools.go to specify goreleaser version
`consul` has been replaced with `hashicorp/consul`. As part of this migration, HashiCorp stopped publishing a latest tag on `consul`, causing our build to fail. The DynamoDB instance made a change that required keys and secrets to ONLY contain A-Za-z0-9. Our hyphenated examples were considered invalid, causing that test to fail.
This pulls in the change that was made to v7 onto the v6 branch.
This brings the v6 branch up-to-date with v7 in terms of Alpine and Go version. Note: these aren't the [latest Go versions available](https://github.com/launchdarkly/ld-relay-private/issues/445) - just parity with v7. - [x] This should resolve the crypto errors found in the current alpine image.
… [v6] (#477) Bumps CI build of the v6 branch to Go 1.21 & 1.20, dropping off 1.19. The minimum required version is set to 1.19 as anything lower won't compile. Additionally fixes a CVE in golang.org/x/net.
cwaldren-ld
requested review from
keelerm84,
kinyoklion and
louis-launchdarkly
October 17, 2023 23:34
louis-launchdarkly
approved these changes
Oct 17, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[6.9.0] - 2023-10-17
Changed: