Skip to content

Update module github.com/zeromicro/go-zero to v1.9.3 #27

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update module github.com/zeromicro/go-zero to v1.9.3 #27

wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 3, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
github.com/zeromicro/go-zero v1.6.2 -> v1.9.3 age confidence

Release Notes

zeromicro/go-zero (github.com/zeromicro/go-zero)

v1.9.3

Compare Source

We are excited to announce the release of go-zero v1.9.3! This release brings several important enhancements and bug fixes that improve the framework's reliability, performance, and alignment with industry best practices.

🎉 Highlights

  • Consistent Hash Load Balancing: New gRPC load balancer for session affinity
  • gRPC Best Practices: Changed NonBlock default to align with gRPC recommendations
  • Improved Distributed Tracing: Fixed gateway trace header propagation
  • ORM Improvements: Fixed zero value scanning for pointer destinations

✨ New Features

Consistent Hash Balancer Support (#​5246)

Contributor: @​zhoushuguang

A new consistent hash load balancer has been added to the zRPC package, enabling session affinity for gRPC services.

Key Features:

  • Hash-based request routing to maintain session affinity
  • Distributes requests based on a hash key from context
  • Minimal request redistribution on node changes
  • Built on go-zero's existing core/hash/ConsistentHash implementation

Usage Example:

// Set hash key in context
ctx := zrpc.SetHashKey(ctx, "user_123")

// Requests with the same key will be routed to the same backend
resp, err := client.SomeMethod(ctx, req)

Configuration:

c := zrpc.RpcClientConf{
    Endpoints: []string{"localhost:8080", "localhost:8081"},
    BalancerName: "consistent_hash",  // Use consistent hash balancer
}

Benefits:

  • Enables stateful service interactions
  • Improves cache hit rates on backend services
  • Reduces session data synchronization overhead
  • Maintains load distribution while supporting affinity

🐛 Bug Fixes

Fixed Gateway Trace Headers (#​5256, #​5248)

Contributor: @​kevwan

Fixed an issue where OpenTelemetry trace propagation headers were not being properly forwarded through the gateway to upstream gRPC services, breaking distributed tracing.

Problem:
The gateway was not forwarding critical W3C Trace Context headers (traceparent, tracestate, baggage) to gRPC metadata, causing trace context to be lost at the gateway boundary.

Solution:

  • Enhanced ProcessHeaders function to forward trace propagation headers
  • Headers are now properly converted to lowercase per gRPC metadata conventions
  • Maintains distributed tracing across HTTP → gRPC boundaries

Impact:

  • End-to-end tracing now works correctly through the gateway
  • Improved observability for microservice architectures
  • Better debugging and performance analysis capabilities

Technical Details:

// Trace headers now properly forwarded
var traceHeaders = map[string]bool{
    "traceparent": true,  // W3C Trace Context
    "tracestate":  true,  // Additional trace state
    "baggage":     true,  // W3C Baggage propagation
}
Fixed Multiple Trace Initialization (#​5244)

Contributor: @​kevwan

Problem:
When running multiple services (e.g., REST + RPC) in the same process, the trace agent could be initialized multiple times, potentially causing resource leaks or unexpected behavior.

Solution:

  • Used sync.Once to ensure trace agent is initialized only once
  • Aligned with similar patterns used in prometheus.StartAgent and logx.SetUp
  • Added sync.OnceFunc for shutdown to prevent double cleanup

Code Changes:

var (
    once           sync.Once
    shutdownOnceFn = sync.OnceFunc(func() {
        if tp != nil {
            _ = tp.Shutdown(context.Background())
        }
    })
)

func StartAgent(c Config) {
    if c.Disabled {
        return
    }

    once.Do(func() {
        if err := startAgent(c); err != nil {
            logx.Error(err)
        }
    })
}

Benefits:

  • Prevents resource conflicts in multi-server processes
  • Ensures single global tracer provider instance
  • Safer concurrent initialization
  • Proper cleanup on shutdown
Fixed ORM Zero Value Scanning for Pointer Destinations (#​5270)

Contributor: @​lerity-yao (first contribution! 🎊)

Problem:
When scanning database results into struct fields with pointer types, zero values (0, false, empty string) were not being properly distinguished from NULL values. This caused nil pointers to be set to zero values incorrectly.

Solution:
Enhanced the getValueInterface function to properly initialize nil pointers before scanning, ensuring the SQL driver can correctly populate them with zero or non-zero values.

Code Changes:

func getValueInterface(value reflect.Value) (any, error) {
    if !value.CanAddr() || !value.Addr().CanInterface() {
        return nil, ErrNotReadableValue
    }

    // Initialize nil pointer before scanning
    if value.Kind() == reflect.Pointer && value.IsNil() {
        baseValueType := mapping.Deref(value.Type())
        value.Set(reflect.New(baseValueType))
    }

    return value.Addr().Interface(), nil
}

Impact:

type User struct {
    Name    string   `db:"name"`      // Always set
    Age     *int     `db:"age"`       // Can distinguish NULL vs 0
    Active  *bool    `db:"active"`    // Can distinguish NULL vs false
}

// Before: age=0 and age=NULL both resulted in nil pointer
// After:  age=0 → *int(0), age=NULL → nil pointer ✓

Benefits:

  • Correct handling of NULL vs zero values
  • Better semantic representation of optional fields
  • Prevents unexpected nil pointer dereferences
  • Aligns with Go's SQL scanning best practices

🔄 Breaking Changes (With Backward Compatibility)

Changed NonBlock Default to True (#​5259)

Contributor: @​kevwan

Motivation:
Aligned with gRPC official best practices which discourage blocking dials.

Change:

// zrpc/config.go
type RpcClientConf struct {
    // Before: NonBlock bool `json:",optional"`
    // After:
    NonBlock bool `json:",default=true"`  // Now defaults to true
}

Why This Matters:

  1. Blocking dials are deprecated: grpc.WithBlock() is an anti-pattern
  2. Connection state is dynamic: Being connected at dial time doesn't guarantee future connectivity
  3. RPCs handle waiting: All RPCs automatically wait until connection or deadline
  4. Simpler code: No need to check "ready" state before making calls

Migration Guide:

For most users, no action required - the new default is the recommended behavior.

If you explicitly need blocking behavior (not recommended):

// Option 1: Configuration
c := zrpc.RpcClientConf{
    NonBlock: false,  // Explicit blocking
}

// Option 2: Client option (deprecated)
client := zrpc.MustNewClient(c, zrpc.WithBlock())

Backward Compatibility:

  • Existing configs with NonBlock: false continue to work
  • New WithBlock() option available (marked deprecated)
  • No changes needed for services already using NonBlock: true

Documentation:
See GRPC_NONBLOCK_CHANGE.md for detailed migration guide and rationale.

👥 New Contributors

We're thrilled to welcome new contributors to the go-zero community! 🎉

Thank you for your contributions! We look forward to your continued involvement in the project.

📦 Installation & Upgrade

Install
go get -u github.com/zeromicro/go-zero@v1.9.3
Update
# Update go.mod
go get -u github.com/zeromicro/go-zero@v1.9.3
go mod tidy

🔗 Links

📝 Detailed Changes

Core Enhancements
Load Balancing
  • Added consistent hash balancer for gRPC (zrpc/internal/balancer/consistenthash)
  • Context-based hash key API: SetHashKey() and GetHashKey()
  • Configurable replica count and hash function
  • Comprehensive test coverage
Distributed Tracing
  • Fixed trace header propagation in gateway
  • Proper handling of W3C Trace Context headers
  • Case-insensitive header matching per gRPC conventions
  • Single initialization with sync.Once pattern
ORM/Database
  • Fixed pointer field scanning for zero values
  • Proper NULL vs zero value distinction
  • Enhanced getValueInterface() with nil pointer initialization
  • Support for sql.Null* types
gRPC Client
  • Changed NonBlock default to true
  • Added deprecated WithBlock() option for compatibility
  • Explicit handling of both blocking and non-blocking modes
  • Updated client initialization logic
Testing & Quality
  • Added comprehensive test coverage for all changes
  • Edge case handling in ORM tests
  • Gateway trace header test cases
  • Consistent hash balancer benchmarks

🙏 Acknowledgments

Special thanks to all contributors, issue reporters, and community members who made this release possible. Your feedback and contributions continue to make go-zero better!

💬 Feedback

If you encounter any issues or have suggestions for future releases, please:

Happy coding with go-zero! 🚀

v1.9.2

Compare Source

Overview

This release is solely focused on addressing a critical problem related to the go-redis dependency. Previous versions of go-redis were retracted, which could cause build failures, dependency resolution issues, or unexpected behavior for downstream projects relying on stable releases.

What's Fixed
  • go-redis Version Issue: The only change in this release is updating go-redis to circumvent the retracted versions. This ensures that consumers of this library can continue to build and use it reliably without encountering problems from retracted dependencies.
Impact
  • No Functional Changes: There are no new features, bug fixes, or breaking changes in this release. Functionality remains the same as the previous version.
  • Dependency Stability: Users should upgrade to this release if they are experiencing issues related to go-redis retractions or want to ensure their dependency tree remains stable.
New Contributors

While this release only addresses the go-redis issue, we'd like to acknowledge recent first-time contributors to the project:

Changelog

For a full list of changes between v1.9.1 and v1.9.2, see the changelog.

Upgrade Recommendation:
If you depend on redis, it is strongly recommended to upgrade to this release to avoid issues caused by the retracted versions.

v1.9.1

Compare Source

Highlights

  • Logging enhancements:
    • Customize log key names to fit your log schema and downstream tooling.
    • Prefer json.Marshaler over fmt.Stringer when emitting JSON logs, improving correctness and structure.
  • REST/SSE stability and operability:
    • Fix SSE handler blocking and reduce noisy logs by downgrading SetWriteDeadline errors to debug.
    • Add SetSSESlowThreshold to help detect slow clients and long writes.
  • Diagnostics and performance:
    • Improved mapreduce panic stacktraces for faster root-cause analysis.
    • Optimized machine performance data reading to reduce runtime overhead.

Detailed Changes

Logging
  • Support customizing log keys so you can align emitted fields (e.g., time, level, caller, message) to your organization’s conventions or ingestion pipeline requirements.
    PR: feat: support customize of log keys by @​WqyJh (@​5103)
  • Prefer json.Marshaler over fmt.Stringer when generating JSON logs, ensuring structured fields are serialized using their explicit JSON representations rather than ad-hoc strings.
    PR: feat: prefer json.Marshaler over fmt.Stringer for JSON log output by @​WqyJh (@​5117)
REST/SSE
  • Fix SSE handler blocking behavior that could stall responses under certain conditions.
    PR: fix: SSE handler blocking by @​wuqinqiang (@​5181)
  • Reduce log noise for transient I/O conditions by downgrading SetWriteDeadline errors to debug level in REST SSE.
    PR: fix(rest): change SSE SetWriteDeadline error log to debug level by @​wuqinqiang (@​5162)
  • Add sseSlowThreshold to surface slow SSE writes, enabling better observability about backpressure or slow clients.
    PR: feat(handler): add sseSlowThreshold by @​wuqinqiang (@​5196)
MapReduce
  • Improve panic stacktrace reporting in mapreduce, making error contexts clearer and debugging faster.
    PR: optimize: mapreduce panic stacktrace by @​kevwan (@​5168)
Performance and Runtime
  • Optimize machine performance data reading to lower collection overhead and reduce runtime impact.
    PR: opt: optimization of machine performance data reading by @​wanwusangzhi (@​5174)
Bug Fixes

Migration and Usage Notes

  • Logging key customization:
    • If you rely on specific field names in log pipelines, consider setting the new custom key configuration to preserve schema consistency.
  • JSON log output:
    • If your types implement json.Marshaler, expect more accurate JSON in logs. If you previously depended on stringified representations, review downstream consumers to ensure compatibility.
  • SSE tuning:
    • Consider using SetSSESlowThreshold to flag slow clients or network conditions in environments sensitive to latency.
    • The SetWriteDeadline log level change reduces noise; adjust logger settings if you still want to surface these events.

Acknowledgements

Full Changelog

v1.9.0

Compare Source

What's Changed

New Contributors

Detailed Release Notes: https://go-zero.dev/en/reference/releases/v1.9.0
Full Changelog: zeromicro/go-zero@v1.8.5...v1.9.0

v1.8.5

Compare Source

Features

  • SQL Read/Write Splitting: Introduced SQL read/write splitting for improved database performance and scalability (#​4976, #​4990, #​5000).
  • Serverless Support in REST: Added support for serverless use in REST services (#​5001).

Bug Fixes & Improvements

  • Fixed HTTP SSE method timeout not working when timeout is set by server (#​4932)
  • Fixed timeout 0s not working in API files (#​4932)
  • Fixed panic caused by time.Duration type with numerical values (#​4944)
  • Fixed duration type comparison in environment variable processing (#​4979)

New Contributors

Full Changelog: v1.8.4...v1.8.5

v1.8.4

Compare Source

Highlights

  • Continuous profiling support (#​4867). 
    Profiling:
   ServerAddr: http://<pyroscope-server>:<port>
  • Embedded File Server Enhancements: Added support to serve files using embed.FS, simplifying static file serving (#​4847, #​4851).
  • Performance Optimizations: Improved performance for hashing and slicing operations (#​4891, #​4877).

What's Changed

  • New Features:
    • File server now supports embed.FS (#​4847).
    • Continuous profiling support (#​4867).
  • Optimizations:

New Contributors

Thank you to all our contributors!

Full Changelog: zeromicro/go-zero@v1.8.3...v1.8.4

v1.8.3

Compare Source

🌟 Highlights

  • MCP Server SDK: Added comprehensive Model Context Protocol server SDK support with real-time communication, JSON-RPC, prompt management, and more.
  • API Route Improvements: Enhanced handling of special characters in API route paths.

🚀 Features

  • MCP server SDK:

    • Real-time Communication: Robust SSE-based system with persistent client connections
    • JSON-RPC Support: Complete implementation with proper request processing and response formatting
    • Tool System: Register custom tools with schema validation and support for various return types
    • Prompt Management: Static prompts with templating and dynamic prompts with handler functions
    • Resource Handling: Register and deliver file resources with proper MIME type support
    • Embedded Resources: Include files directly in conversation messages
    • Content Flexibility: Support for text, code, images, and binary content
    • Protocol Features: Proper initialization sequences and capability negotiation
    • Comprehensive Error Handling: Proper error reporting with appropriate error codes
    • Performance Optimizations: Configurable timeouts and efficient resource management
    • Context Awareness: All handlers receive context for timeout and cancellation support

    ⚠️ API Stability Notice: Since this is the initial release of the MCP SDK and AI technology is rapidly evolving, the APIs might change in future releases to improve developer experience and adapt to emerging industry standards.

    📚 Tutorial: For detailed documentation and usage examples, check out the MCP Tutorial

  • API Enhancements:

    • Fixed handling of special characters (like periods) in API route paths

🐛 Bug Fixes

  • Fixed marshaler bug when handling arrays

📦 Dependency Updates

  • Bumped github.com/redis/go-redis/v9 from 9.7.3 to 9.8.0

👋 Welcome to New Contributors

A warm welcome to our new contributors who made their first contributions to go-zero in this release:

🔗 Links

v1.8.2

Compare Source

We're pleased to announce the release of go-zero v1.8.2. This release includes new features, bug fixes, dependency updates, and code improvements.

🚀 New Features

  • SSE Support: Added rest.WithSSE to build Server-Sent Events routes more easily (#​4729)
  • Redis Command: Added support for Redis GETDEL command (#​4709)
  • HTTP Client Enhancement: Added support for serialization of anonymous fields in HTTP client (httpc) (#​4676)

🐛 Bug Fixes

  • PostgreSQL Data Types: Fixed issues with numeric/decimal data types in PostgreSQL (#​4686)

📦 Dependency Updates

  • Bumped github.com/prometheus/client_golang from 1.21.0 to 1.21.1 (#​4683)
  • Bumped github.com/fullstorydev/grpcurl from 1.9.2 to 1.9.3 (#​4701)
  • Bumped github.com/redis/go-redis/v9 from 9.7.1 to 9.7.3 (#​4722)
  • Bumped github.com/golang-jwt/jwt/v4 from 4.5.1 to 4.5.2 (#​4734)
  • Bumped github.com/jackc/pgx/v5 from 5.7.2 to 5.7.4 (#​4737)

🧹 Code Maintenance

👋 New Contributors

We're excited to welcome the following new contributors to the go-zero project:

🔭 Coming Soon

  • MCP Server Support: We'll be adding Model Context Protocol (MCP) server support in the next release.

🔗 Additional Information

v1.8.1

Compare Source

🎉 Celebrating 30,000 Stars Milestone! 🎉

We are thrilled to announce that go-zero has reached the incredible milestone of 30,000 GitHub stars! This achievement wouldn't have been possible without our amazing community of developers, contributors, and users who have supported us throughout this journey.

From its humble beginnings, go-zero has grown to become one of the most popular Go microservices frameworks, enabling developers worldwide to build high-performance, reliable, and scalable systems with ease. This milestone is a testament to the value go-zero brings to the Go ecosystem and the trust the community places in our project.

✨ What's New in v1.8.1

We're excited to present go-zero v1.8.1, which includes several new features, bug fixes, and performance improvements.

🔑 Key Highlights
  • Redis v7 Compatibility: Fixed username not working in Redis v7
  • Gateway Context Propagation: Fixed HTTP gateway context propagation
🚀 Features
  • Fixed global fields applying to third-party log modules by @​JiChenSSG
  • Simplified HTTP query array parsing by @​kevwan
🐛 Fixes
🔧 Improvements & Maintenance
  • Performance tuning for stable runner by @​kevwan
  • Various dependency updates to keep the project up-to-date
  • Multiple code style improvements and test coverage enhancements

📦 Dependency Updates

This release includes several dependency updates:

  • Updated github.com/go-sql-driver/mysql from 1.8.1 to 1.9.0
  • Updated github.com/prometheus/client_golang from 1.20.5 to 1.21.0
  • Updated github.com/redis/go-redis/v9 from 9.7.0 to 9.7.1
  • Updated go.mongodb.org/mongo-driver from 1.17.2 to 1.17.3
  • Updated various golang.org/x packages

👋 Welcome New Contributors

A special welcome to our new contributor who made their first contribution in this release:

🙏 Thank You

As we celebrate 30,000 stars, we want to express our deepest gratitude to everyone who has contributed to go-zero, used it in their projects, filed issues, or helped spread the word. This community-driven success pushes us to continue improving and innovating.

For a complete list of changes, please check the full changelog.

v1.8.0

Compare Source

✨ Highlights

  • Added inbound HTTP to outbound HTTP in gateway, previously only inbound HTTP to outbound gRPC
  • Introduced automatic config validation
  • Added FreeBSD support
  • Enhanced logging capabilities with new Debugfn and Infofn functions
  • Added SQL metrics functionality
  • Added Redis user authentication support

🚀 Features

  • Support for HTTP to HTTP in gateway
  • Automatic configuration validation
  • FreeBSD platform support
  • New SQL metrics functionality
  • Added Debugfn and Infofn to logx/logc
  • Redis authentication with new User property in RedisConf
  • Improved metrics collection for MySQL

🐛 Bug Fixes

  • Resolved etcd discovery mechanism on gRPC with idle manager on latest gRPC versions
  • Fixed health check issues, returns OK before server finishing start
  • Fixed httpx.ParseJsonBody error with []byte fields
  • Fixed empty form values handling in HTTP requests

🧹 Chores & Optimizations

  • Updated Go version
  • Multiple dependency updates:
    • golang.org/x/time to v0.9.0
    • golang.org/x/sys to v0.29.0
    • google.golang.org/protobuf to v1.36.4
    • golang.org/x/net to v0.34.0
    • go.mongodb.org/mongo-driver to v1.17.2
  • Optimized error messages for mapping data method
  • Enhanced logging system with more tests

🎉 New Contributors

Welcome to our new contributors who helped make this release possible:

Full Changelog: zeromicro/go-zero@v1.7.6...v1.8.0

v1.7.6

Compare Source

What's Changed

Full Changelog: zeromicro/go-zero@v1.7.5...v1.7.6

v1.7.5

Compare Source

What's Changed

New Contributors

Full Changelog: zeromicro/go-zero@v1.7.4...v1.7.5

v1.7.4

Compare Source

What's Changed

New Contributors

Full Changelog: zeromicro/go-zero@v1.7.3...v1.7.4

v1.7.3

Compare Source

What's Changed

New Contributors

Full Changelog: zeromicro/go-zero@v1.7.2...v1.7.3

v1.7.2

Compare Source

What's Changed

New Contributors

Full Changelog: zeromicro/go-zero@v1.7.1...v1.7.2

v1.7.1

Compare Source

What's Changed

New Contributors

Full Changelog: zeromicro/go-zero@v1.7.0...v1.7.1

v1.7.0

Compare Source

What's Changed

Important: Go >= 1.20

New Contributors

Full Changelog: zeromicro/go-zero@v1.6.6...v1.7.0

v1.6.6

Compare Source

What's Changed

New Contributors

Full Changelog: zeromicro/go-zero@v1.6.5...v1.6.6

v1.6.5

Compare Source

What's Changed

New Contributors

Full Changelog: zeromicro/go-zero@v1.6.4...v1.6.5

v1.6.4

Compare Source

What's Changed

New Contributors

Full Changelog: zeromicro/go-zero@v1.6.3...v1.6.4

v1.6.3

Compare Source

What's Changed

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.6.3 Update module github.com/zeromicro/go-zero to v1.6.4 Apr 9, 2024
@renovate renovate bot force-pushed the renovate/github.com-zeromicro-go-zero-1.x branch from 59a4518 to ac775ac Compare April 9, 2024 15:52
@renovate renovate bot force-pushed the renovate/github.com-zeromicro-go-zero-1.x branch from ac775ac to 833c020 Compare May 12, 2024 16:30
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.6.4 Update module github.com/zeromicro/go-zero to v1.6.5 May 12, 2024
@renovate renovate bot force-pushed the renovate/github.com-zeromicro-go-zero-1.x branch from 833c020 to a9bb458 Compare June 21, 2024 14:23
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.6.5 Update module github.com/zeromicro/go-zero to v1.6.6 Jun 21, 2024
@renovate
Copy link
Contributor Author

renovate bot commented Jun 21, 2024 •
edited
Loading

ℹ Artifact update notice

File name: helloworld/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 38 additional dependencies were updated

Details:

Package Change
github.com/grpc-ecosystem/grpc-gateway/v2 v2.19.1 -> v2.20.0
google.golang.org/genproto/googleapis/api v0.0.0-20240205150955-31a09d347014 -> v0.0.0-20240711142825-46eb208f015d
google.golang.org/grpc v1.61.0 -> v1.65.0
google.golang.org/protobuf v1.35.2 -> v1.36.5
github.com/cenkalti/backoff/v4 v4.2.1 -> v4.3.0
github.com/cespare/xxhash/v2 v2.2.0 -> v2.3.0
github.com/fatih/color v1.16.0 -> v1.18.0
github.com/go-logr/logr v1.3.0 -> v1.4.2
github.com/golang-jwt/jwt/v4 v4.5.0 -> v4.5.2
github.com/golang/protobuf v1.5.3 -> v1.5.4
github.com/openzipkin/zipkin-go v0.4.2 -> v0.4.3
github.com/pelletier/go-toml/v2 v2.1.1 -> v2.2.2
github.com/prometheus/client_golang v1.18.0 -> v1.21.1
github.com/prometheus/client_model v0.5.0 -> v0.6.1
github.com/prometheus/common v0.45.0 -> v0.62.0
github.com/prometheus/procfs v0.12.0 -> v0.15.1
go.etcd.io/etcd/api/v3 v3.5.12 -> v3.5.15
go.etcd.io/etcd/client/pkg/v3 v3.5.12 -> v3.5.15
go.etcd.io/etcd/client/v3 v3.5.12 -> v3.5.15
go.opentelemetry.io/otel v1.19.0 -> v1.24.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.19.0 -> v1.24.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.19.0 -> v1.24.0
go.opentelemetry.io/otel/exporters/zipkin v1.19.0 -> v1.24.0
go.opentelemetry.io/otel/sdk v1.19.0 -> v1.24.0
go.opentelemetry.io/otel/trace v1.19.0 -> v1.24.0
go.opentelemetry.io/proto/otlp v1.0.0 -> v1.3.1
go.uber.org/automaxprocs v1.5.3 -> v1.6.0
golang.org/x/net v0.20.0 -> v0.35.0
golang.org/x/oauth2 v0.16.0 -> v0.24.0
golang.org/x/sys v0.16.0 -> v0.30.0
golang.org/x/term v0.16.0 -> v0.29.0
golang.org/x/text v0.14.0 -> v0.22.0
golang.org/x/time v0.5.0 -> v0.10.0
google.golang.org/genproto/googleapis/rpc v0.0.0-20240125205218-1f4bbc51befe -> v0.0.0-20240701130421-f6361c86f094
k8s.io/api v0.29.1 -> v0.29.3
k8s.io/apimachinery v0.29.1 -> v0.29.4
k8s.io/client-go v0.29.1 -> v0.29.3
k8s.io/utils v0.0.0-20230726121419-3b25d923346b -> v0.0.0-20240711033017-18e509b52bc8

@renovate renovate bot force-pushed the renovate/github.com-zeromicro-go-zero-1.x branch from a9bb458 to f640111 Compare July 27, 2024 13:37
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.6.6 Update module github.com/zeromicro/go-zero to v1.7.0 Jul 27, 2024
@renovate renovate bot force-pushed the renovate/github.com-zeromicro-go-zero-1.x branch from f640111 to 43e26e1 Compare September 1, 2024 09:32
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.7.0 Update module github.com/zeromicro/go-zero to v1.7.1 Sep 1, 2024
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.7.1 Update module github.com/zeromicro/go-zero to v1.7.2 Sep 3, 2024
@renovate renovate bot force-pushed the renovate/github.com-zeromicro-go-zero-1.x branch from 43e26e1 to 149ee12 Compare September 3, 2024 03:50
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.7.2 Update module github.com/zeromicro/go-zero to v1.7.3 Oct 19, 2024
@renovate renovate bot force-pushed the renovate/github.com-zeromicro-go-zero-1.x branch from 149ee12 to 4830193 Compare October 19, 2024 19:16
@renovate renovate bot force-pushed the renovate/github.com-zeromicro-go-zero-1.x branch from 4830193 to 10d8dee Compare November 24, 2024 14:04
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.7.3 Update module github.com/zeromicro/go-zero to v1.7.4 Nov 24, 2024
@renovate renovate bot force-pushed the renovate/github.com-zeromicro-go-zero-1.x branch from 10d8dee to 139d454 Compare November 29, 2024 04:00
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.7.4 Update module github.com/zeromicro/go-zero to v1.7.4 - autoclosed Dec 12, 2024
@renovate renovate bot closed this Dec 12, 2024
@renovate renovate bot deleted the renovate/github.com-zeromicro-go-zero-1.x branch December 12, 2024 21:25
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.7.4 - autoclosed Update module github.com/zeromicro/go-zero to v1.7.4 Dec 13, 2024
@renovate renovate bot reopened this Dec 13, 2024
@renovate renovate bot force-pushed the renovate/github.com-zeromicro-go-zero-1.x branch from 83042af to 139d454 Compare December 13, 2024 00:12
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.7.4 Update module github.com/zeromicro/go-zero to v1.7.4 - autoclosed Dec 14, 2024
@renovate renovate bot closed this Dec 14, 2024
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.7.4 - autoclosed Update module github.com/zeromicro/go-zero to v1.7.4 Dec 15, 2024
@renovate renovate bot reopened this Dec 15, 2024
@renovate renovate bot force-pushed the renovate/github.com-zeromicro-go-zero-1.x branch from 800e83a to 139d454 Compare December 15, 2024 00:51
@renovate renovate bot force-pushed the renovate/github.com-zeromicro-go-zero-1.x branch from 139d454 to dbf035c Compare January 1, 2025 18:07
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.8.1 Update module github.com/zeromicro/go-zero to v1.8.2 Apr 6, 2025
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.8.2 Update module github.com/zeromicro/go-zero to v1.8.2 - autoclosed Apr 14, 2025
@renovate renovate bot closed this Apr 14, 2025
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.8.2 - autoclosed Update module github.com/zeromicro/go-zero to v1.8.2 Apr 14, 2025
@renovate renovate bot reopened this Apr 14, 2025
@renovate renovate bot force-pushed the renovate/github.com-zeromicro-go-zero-1.x branch from 2ec9a50 to a56cfb0 Compare May 4, 2025 10:34
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.8.2 Update module github.com/zeromicro/go-zero to v1.8.3 May 4, 2025
@renovate renovate bot force-pushed the renovate/github.com-zeromicro-go-zero-1.x branch from a56cfb0 to 860bf8f Compare June 8, 2025 18:09
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.8.3 Update module github.com/zeromicro/go-zero to v1.8.4 Jun 8, 2025
@renovate renovate bot force-pushed the renovate/github.com-zeromicro-go-zero-1.x branch from 860bf8f to 1389e37 Compare July 12, 2025 16:54
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.8.4 Update module github.com/zeromicro/go-zero to v1.8.5 Jul 12, 2025
@renovate renovate bot force-pushed the renovate/github.com-zeromicro-go-zero-1.x branch from 1389e37 to 0e0a631 Compare August 17, 2025 05:27
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.8.5 Update module github.com/zeromicro/go-zero to v1.9.0 Aug 17, 2025
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.9.0 Update module github.com/zeromicro/go-zero to v1.9.0 - autoclosed Aug 24, 2025
@renovate renovate bot closed this Aug 24, 2025
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.9.0 - autoclosed Update module github.com/zeromicro/go-zero to v1.9.0 Aug 24, 2025
@renovate renovate bot reopened this Aug 24, 2025
@renovate renovate bot force-pushed the renovate/github.com-zeromicro-go-zero-1.x branch from b2ead69 to 0e0a631 Compare August 24, 2025 22:27
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.9.0 Update module github.com/zeromicro/go-zero to v1.9.0 - autoclosed Sep 12, 2025
@renovate renovate bot closed this Sep 12, 2025
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.9.0 - autoclosed Update module github.com/zeromicro/go-zero to v1.9.0 Sep 13, 2025
@renovate renovate bot reopened this Sep 13, 2025
@renovate renovate bot force-pushed the renovate/github.com-zeromicro-go-zero-1.x branch from f192e38 to 0e0a631 Compare September 13, 2025 23:47
@renovate renovate bot force-pushed the renovate/github.com-zeromicro-go-zero-1.x branch from 0e0a631 to ac71537 Compare October 2, 2025 18:24
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.9.0 Update module github.com/zeromicro/go-zero to v1.9.1 Oct 2, 2025
@renovate renovate bot force-pushed the renovate/github.com-zeromicro-go-zero-1.x branch from ac71537 to 503bf27 Compare October 11, 2025 09:04
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.9.1 Update module github.com/zeromicro/go-zero to v1.9.2 Oct 11, 2025
@renovate renovate bot force-pushed the renovate/github.com-zeromicro-go-zero-1.x branch from 503bf27 to 7135884 Compare November 16, 2025 14:05
@renovate renovate bot changed the title Update module github.com/zeromicro/go-zero to v1.9.2 Update module github.com/zeromicro/go-zero to v1.9.3 Nov 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant