发布

  • Enhance support agent example and fix protoless service scaffolding (#2986)

    frostbyte_neo 发布于 2026-06-22 09:22:25 +00:00

    • examples: support desk agent + blog walkthrough

    A real-world, runnable example (examples/support): customers/tickets/notify
    services become the agent's tools, a flow turns a ticket.created event into
    the agent's work, and an approval gate guards the one action that touches a
    customer. Runs with no API key (mock model) or against a live provider.

    Adds blog/28 'Building a Support Agent in Go' and indexes both.

    Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com
    Claude-Session: https://claude.ai/code/session_01CmdEY7pYmV5zzwCjNJ4ykL

    • fix(new): protoless services by default; fix @latest install (#2985)

    micro new now scaffolds a reflection-based service by default — plain Go
    types registered via service.Handle, no .proto, no Makefile proto target.
    The generated project builds and runs with 'go run .' and zero external
    tooling. Protocol Buffers move behind --proto (the crud/pubsub/api
    templates imply it). When the proto workflow is used and protoc /
    protoc-gen-go / protoc-gen-micro are missing, print exact install
    instructions instead of failing with a cryptic plugin error.

    Also fixes the 'go install go-micro.dev/v6/cmd/micro@latest' version
    constraint conflict: the vanity go-import meta still advertised /v5, so Go
    fell back to the bare module and resolved an ancient v1.x tag. Advertise
    /v6 (keeping /v5 for existing users) and add a version-pin fallback note to
    the install docs.

    Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com
    Claude-Session: https://claude.ai/code/session_01CmdEY7pYmV5zzwCjNJ4ykL

    • fix(new,install): pin generated go.mod to current go-micro; lead install with prebuilt binary (#2985)
    • micro new now requires the exact go-micro version the CLI was built from
      (via build info), falling back to 'latest' for dev builds. An explicit
      require is also more robust than a bare import: 'go mod tidy' reliably
      resolves it, where a requireless go.mod could fail vanity discovery.
    • Make the precompiled binary (curl install.sh) the recommended install in
      the docs; demote 'go install' to a from-source option with the version-pin
      fallback note.
    • Sync the stale internal/scripts/install.sh to the working website script
      (it expected an old micro-OS-ARCH asset name; releases ship
      micro_OS_ARCH.tar.gz).

    Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com
    Claude-Session: https://claude.ai/code/session_01CmdEY7pYmV5zzwCjNJ4ykL

    • website: add corrected nginx vanity-import config (#2985)

    The live go-micro.dev handler echoed the full request path into the
    go-import prefix ($host$1), so go install go-micro.dev/v6/cmd/micro@latest
    got prefix go-micro.dev/v6/cmd/micro — a package, not the module root — and
    Go fell back to the ancient v1.x tags (version constraints conflict).

    Add a dedicated /vN location that emits the module root (go-micro.dev/vN)
    for any sub-path, and make the catch-all advertise the current module roots
    instead of echoing arbitrary paths.

    Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com
    Claude-Session: https://claude.ai/code/session_01CmdEY7pYmV5zzwCjNJ4ykL


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

    下载附件