项目文件夹

文件

T

Asim Aslam c7657f73f4

goreleaser / goreleaser (push) Has been cancelled

Refactor agent plan storage, update docs, and release v6 (#2977 )

* test(harness): read agent plan from the scoped store

The store-scoping change moved an agent's plan from the default table
key agent/{name}/plan to its own table (database "agent", table {name},
key "plan"). The plan-delegate harness tests still read the old key and
failed with 'not found'; read through store.Scope(mem, "agent", name)
like the agent does.

* docs: orient agents-first across README, landing, and docs overview

Lead with agents (then services and flows), surface MCP + A2A as the
interop story, and frame agents as services. Landing hero and feature
grid reordered agents-first with an A2A gateway card.

* v6: module path go-micro.dev/v6, TLS secure by default, NewService

Cut v6. Three breaking changes, bundled so the major bump is paid once:

- Module path go-micro.dev/v5 -> go-micro.dev/v6 across all imports + go.mod.
- TLS verification on by default (was off). MICRO_TLS_SECURE removed;
  MICRO_TLS_INSECURE=true opts out for self-signed/dev.
- micro.NewService(name, opts...) is the canonical service constructor,
  symmetric with NewAgent/NewFlow; micro.New kept as a deprecated alias;
  the old name-less NewService(opts...) removed. Generators emit NewService.

Also ports the JWT auth token provider in-module (go-micro.dev/v6/auth/jwt/token
on golang-jwt/jwt/v5), dropping the v5-pinned github.com/micro/plugins/v5/auth/jwt
and the deprecated dgrijalva/jwt-go.

Docs/README/landing updated to v6 and @latest; v5->v6 migration guide added;
CHANGELOG cut as [6.0.0]. Blog posts left at their historical versions.

---------

Co-authored-by: Claude <noreply@anthropic.com>

2026-06-18 11:55:35 +01:00

1.9 KiB

原始文件 永久链接 Blame 文件历史

TLS Security Update - Important Information

What Changed

The TLS configuration in go-micro now includes a security deprecation warning.

Current Behavior (v5.x)

Default: TLS certificate verification is disabled for backward compatibility

This maintains existing behavior to avoid breaking production deployments
A deprecation warning is logged once per process startup

Why: Changing the default to secure would be a breaking change that could disrupt:

Production systems during routine upgrades
Distributed systems with mixed versions
Services using self-signed certificates

How to Enable Security (Recommended)

Option 1: Environment Variable

export MICRO_TLS_SECURE=true

Option 2: Use SecureConfig

import (
    "go-micro.dev/v6/broker"
    mls "go-micro.dev/v6/util/tls"
)

broker := broker.NewHttpBroker(
    broker.TLSConfig(mls.SecureConfig()),
)

Migration Timeline

v5.x (Current): Insecure by default, opt-in security via MICRO_TLS_SECURE=true
v6.x (Future): Secure by default (breaking change with major version bump)

Why This Approach?

This addresses the concerns raised about:

Major version requirements: No breaking change in v5, deferred to v6
Cross-host compatibility: All hosts use same default behavior
Production safety: Existing deployments continue working during upgrades
Migration path: Clear opt-in path with documentation

Documentation

See SECURITY_MIGRATION.md for detailed migration guide.

Security Recommendation

For production deployments:

Test with MICRO_TLS_SECURE=true in staging
Use proper CA-signed certificates
Consider service mesh (Istio, Linkerd) for automatic mTLS
Plan migration before v6 release

Questions?

Open an issue on GitHub or check the documentation at https://go-micro.dev/docs/

1.9 KiB 原始文件 永久链接 Blame 文件历史