search

signalfx / signalfx-go-tracing

BSD 3-Clause "New" or "Revised" License
13 stars 16 forks source link

Bump github.com/gocql/gocql from 0.0.0-20200410100145-b454769479c6 to 1.5.2 in /contrib/gocql/gocql #553

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps github.com/gocql/gocql from 0.0.0-20200410100145-b454769479c6 to 1.5.2.

Release notes

Sourced from github.com/gocql/gocql's releases.

v1.5.2

Same as v1.5.0 (GitHub was not able to verify signature with embedded cleartext gpg message, even with armor lines prefixed)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

2023-06-12:
Switching signing key used for github.com/gocql/gocql tags (since v1.5.0)
from GPG key ID: E0C5EC9218CB255D
to SSH key with the following fingerprint:
SHA256:TcKxeY58a0HRfycY4dCuqMF23FrNyEcclOdVzUI9BBI
You can verify it with
martin.sucha@kiwi.com namespaces="git" ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIN8Cnim2/FWQqDJmhidmXK/9VNO64rLfVJrvZqKaLqUl
in your gpg.ssh.allowedSignersFile
-----BEGIN PGP SIGNATURE-----


iQIzBAEBCAAdFiEEW7CgRMsA2lq5yf6v4MXskhjLJV0FAmSHOcYACgkQ4MXskhjL
JV2IXhAAye6kQhLwiiCag6bHUKIbKxM0TQHiOZf7aRKYlU2s0aWcsOXMeS6S9pvC
cJqmjBdhDZx569bPrgjAy9+jMoe+rNBR5Cr8dcJUk31cKUTjm/7PsKfiCxfDrbnm
ARDY2Z3vdGJC39mvBjG16UurzAPlRnP66jzyWYaXBiFBJJGWkP1+m+PNG4eF9ggo
6W89MEeK6ZpLCxI0URq2RyB5JEgGkr1Gb9UB4/70euiTjUxeRjS+RHjosGREC0nG
MxfpHND/Z+gOhHXCYt87zrF7N7JWIFU3+4vOj/th8MvMGRYaDzOAKT7MQmc/wc3A
drBA5G/adltjNw9aWTRQGNV69jhaoaIkZfv4fy+AvPDz41iGOQD9Nulw8ujkocUC
8zr4OxPhc0LIX1LtqwA2ahYfJABXnC7ObzqZLyXsE0sW5yvWpPNlF+Bj/slAdO+6
d+4uxGs8dd3N/bOihFL2XZoeOStF6ehT5KIFsbr885FUueu6iRgZYPalfv/aWe95
VIh97ikNsfgFH3mO0ZTGP9tnjSCbGIwG2Oh3+0dj5J4tZU1ihJRKiHJJNQirG1xK
jMdu9EXOEPFK4CPwaXZgHpTy38cFF2MOxHbsrxErCuWJY8JxRpqlJeOyx0F+eTR4
NGQSrMKvxfKd/F192UznSUSfflRTrQT7stUOhZk3Lc4YcCSiDEk=
=em6i
-----END PGP SIGNATURE-----

v1.5.1

Same as v1.5.0 (GitHub was not able to verify signature with embedded cleartext gpg message)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

2023-06-12:
Switching signing key used for github.com/gocql/gocql tags (since v1.5.0)
from GPG key ID: E0C5EC9218CB255D
to SSH key with the following fingerprint:
SHA256:TcKxeY58a0HRfycY4dCuqMF23FrNyEcclOdVzUI9BBI
You can verify it with
martin.sucha@kiwi.com namespaces="git" ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIN8Cnim2/FWQqDJmhidmXK/9VNO64rLfVJrvZqKaLqUl
in your gpg.ssh.allowedSignersFile
-----BEGIN PGP SIGNATURE-----


</tr></table>

... (truncated)

Changelog

Sourced from github.com/gocql/gocql's changelog.

[1.5.2] - 2023-06-12

Same as 1.5.0. GitHub does not like gpg signed text in the tag message (even with prefixed armor), so pushing a new tag.

[1.5.1] - 2023-06-12

Same as 1.5.0. GitHub does not like gpg signed text in the tag message, so pushing a new tag.

[1.5.0] - 2023-06-12

Added

  • gocql now advertises the driver name and version in the STARTUP message to the server. The values are taken from the Go module's path and version (or from the replacement module, if used). (#1702) That allows the server to track which fork of the driver is being used.
  • Query.Values() to retrieve the values bound to the Query. This makes writing wrappers around Query easier. (#1700)

Fixed

  • Potential panic on deserialization (#1695)
  • Unmarshalling of dates outside of [1677-09-22, 2262-04-11] range. (#1692)

[1.4.0] - 2023-04-26

Added

Changed

  • gocql now refreshes the entire ring when it receives a topology change event and when control connection is re-connected. This simplifies code managing ring state. (#1680)
  • Supported versions of Cassandra that we test against are now 4.0.x and 4.1.x. (#1685)
  • Default HostDialer now uses already-resolved connect address instead of hostname when establishing TCP connections (#1683).

Fixed

  • Deadlock in Session.Close(). (#1688)
  • Race between Query.Release() and speculative executions (#1684)
  • Missed ring update during control connection reconnection (#1680)

[1.3.2] - 2023-03-27

Changed

  • Supported versions of Go that we test against are now Go 1.19 and Go 1.20.

Fixed

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 1 year ago

Superseded by #583.