These 3 commits are when the Protocol Buffers files have changed:
| Commit: | d0187aa | |
|---|---|---|
| Author: | 吴晟 Wu Sheng | |
| Committer: | GitHub | |
Move to Go 1.26 floor with Go 1.27 tested, verify plugin hook points and refresh framework ranges (#260) Go 1.25 reached end of life with the Go 1.27 release. Go versions: - Every project module declares go 1.26.0. The floor stays below 1.27 because the agent's go directive becomes the minimum for every application that imports it, and Go 1.26 is still supported. - CI, plugin/e2e/Windows jobs, and the published base images move to Go 1.26 and Go 1.27. - golang.org/x/net moves to v0.61.0, which closes the HTTP/2 advisories left open by #258, along with the other x/* modules. - golangci-lint v2.15.0, installed from golangci-lint.run/install.sh. Older copies of the script pick the SBOM checksum and fail for every release since v2.12.2. Plugin test harness: - Build each scenario case with GOWORK=off. Minimal version selection across go.work lifted the framework to the newest version required by any plugin or scenario module, so most cases did not build the version they were named after. - The go-elasticsearch and goframe scenarios declare the full module path, so their version matrix applies. cross-goroutine uses the local toolkit. kratosv2 runs in CI again, and one failing scenario no longer cancels the others. Plugins: - Every plugin module requires the newest framework version whose hook-point signatures match the last tested version, and each scenario tests that version on Go 1.26 and Go 1.27. - Lower bounds rise where older versions never worked or never built: dubbo-go v3.0.2, kratos v2.6.3, go-micro v4.9.0, gorm v1.25.1, and go-sql-driver/mysql v1.5.0. - grpc v1.84.0 is handled by a new plugins/grpc-v184, and dubbo-go v3.3.1 by a new plugins/dubbo-v331, since both releases changed the internals the interceptors are compiled against. The existing plugins keep older releases and builds whose version cannot be detected. - amqp also intercepts PublishWithDeferredConfirm, which Publish and PublishWithContext reach since amqp091-go v1.10.0, and injected headers reach messages published with nil Headers. - go-redis no longer traces the connection setup commands that run through the client hooks since v9.9.0; HELLO and AUTH exported the password in span tags. - zap reports after the pre-write hooks of v1.28.0, and logrus no longer panics on entries with nil Data. - The skywalking-go-agent binary has no reachable third-party advisories left (go-git, go-billy, circl, amqp091-go).
| Commit: | fd87ffe | |
|---|---|---|
| Author: | Klein | |
| Committer: | GitHub | |
plugin grpc Unary (#88)
The documentation is generated from this commit.
| Commit: | 7eb6629 | |
|---|---|---|
| Author: | mrproliu | |
| Committer: | GitHub | |
Support dubbo plugin (#33)