[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"similar-alibaba--nacos":3,"tool-alibaba--nacos":62},[4,18,28,37,45,53],{"id":5,"name":6,"github_repo":7,"description_zh":8,"stars":9,"difficulty_score":10,"last_commit_at":11,"category_tags":12,"status":17},4358,"openclaw","openclaw\u002Fopenclaw","OpenClaw 是一款专为个人打造的本地化 AI 助手，旨在让你在自己的设备上拥有完全可控的智能伙伴。它打破了传统 AI 助手局限于特定网页或应用的束缚，能够直接接入你日常使用的各类通讯渠道，包括微信、WhatsApp、Telegram、Discord、iMessage 等数十种平台。无论你在哪个聊天软件中发送消息，OpenClaw 都能即时响应，甚至支持在 macOS、iOS 和 Android 设备上进行语音交互，并提供实时的画布渲染功能供你操控。\n\n这款工具主要解决了用户对数据隐私、响应速度以及“始终在线”体验的需求。通过将 AI 部署在本地，用户无需依赖云端服务即可享受快速、私密的智能辅助，真正实现了“你的数据，你做主”。其独特的技术亮点在于强大的网关架构，将控制平面与核心助手分离，确保跨平台通信的流畅性与扩展性。\n\nOpenClaw 非常适合希望构建个性化工作流的技术爱好者、开发者，以及注重隐私保护且不愿被单一生态绑定的普通用户。只要具备基础的终端操作能力（支持 macOS、Linux 及 Windows WSL2），即可通过简单的命令行引导完成部署。如果你渴望拥有一个懂你",349277,3,"2026-04-06T06:32:30",[13,14,15,16],"Agent","开发框架","图像","数据工具","ready",{"id":19,"name":20,"github_repo":21,"description_zh":22,"stars":23,"difficulty_score":24,"last_commit_at":25,"category_tags":26,"status":17},9989,"n8n","n8n-io\u002Fn8n","n8n 是一款面向技术团队的公平代码（fair-code）工作流自动化平台，旨在让用户在享受低代码快速构建便利的同时，保留编写自定义代码的灵活性。它主要解决了传统自动化工具要么过于封闭难以扩展、要么完全依赖手写代码效率低下的痛点，帮助用户轻松连接 400 多种应用与服务，实现复杂业务流程的自动化。\n\nn8n 特别适合开发者、工程师以及具备一定技术背景的业务人员使用。其核心亮点在于“按需编码”：既可以通过直观的可视化界面拖拽节点搭建流程，也能随时插入 JavaScript 或 Python 代码、调用 npm 包来处理复杂逻辑。此外，n8n 原生集成了基于 LangChain 的 AI 能力，支持用户利用自有数据和模型构建智能体工作流。在部署方面，n8n 提供极高的自由度，支持完全自托管以保障数据隐私和控制权，也提供云端服务选项。凭借活跃的社区生态和数百个现成模板，n8n 让构建强大且可控的自动化系统变得简单高效。",184740,2,"2026-04-19T23:22:26",[16,14,13,15,27],"插件",{"id":29,"name":30,"github_repo":31,"description_zh":32,"stars":33,"difficulty_score":10,"last_commit_at":34,"category_tags":35,"status":17},10095,"AutoGPT","Significant-Gravitas\u002FAutoGPT","AutoGPT 是一个旨在让每个人都能轻松使用和构建 AI 的强大平台，核心功能是帮助用户创建、部署和管理能够自动执行复杂任务的连续型 AI 智能体。它解决了传统 AI 应用中需要频繁人工干预、难以自动化长流程工作的痛点，让用户只需设定目标，AI 即可自主规划步骤、调用工具并持续运行直至完成任务。\n\n无论是开发者、研究人员，还是希望提升工作效率的普通用户，都能从 AutoGPT 中受益。开发者可利用其低代码界面快速定制专属智能体；研究人员能基于开源架构探索多智能体协作机制；而非技术背景用户也可直接选用预置的智能体模板，立即投入实际工作场景。\n\nAutoGPT 的技术亮点在于其模块化“积木式”工作流设计——用户通过连接功能块即可构建复杂逻辑，每个块负责单一动作，灵活且易于调试。同时，平台支持本地自托管与云端部署两种模式，兼顾数据隐私与使用便捷性。配合完善的文档和一键安装脚本，即使是初次接触的用户也能在几分钟内启动自己的第一个 AI 智能体。AutoGPT 正致力于降低 AI 应用门槛，让人人都能成为 AI 的创造者与受益者。",183572,"2026-04-20T04:47:55",[13,36,27,14,15],"语言模型",{"id":38,"name":39,"github_repo":40,"description_zh":41,"stars":42,"difficulty_score":10,"last_commit_at":43,"category_tags":44,"status":17},3808,"stable-diffusion-webui","AUTOMATIC1111\u002Fstable-diffusion-webui","stable-diffusion-webui 是一个基于 Gradio 构建的网页版操作界面，旨在让用户能够轻松地在本地运行和使用强大的 Stable Diffusion 图像生成模型。它解决了原始模型依赖命令行、操作门槛高且功能分散的痛点，将复杂的 AI 绘图流程整合进一个直观易用的图形化平台。\n\n无论是希望快速上手的普通创作者、需要精细控制画面细节的设计师，还是想要深入探索模型潜力的开发者与研究人员，都能从中获益。其核心亮点在于极高的功能丰富度：不仅支持文生图、图生图、局部重绘（Inpainting）和外绘（Outpainting）等基础模式，还独创了注意力机制调整、提示词矩阵、负向提示词以及“高清修复”等高级功能。此外，它内置了 GFPGAN 和 CodeFormer 等人脸修复工具，支持多种神经网络放大算法，并允许用户通过插件系统无限扩展能力。即使是显存有限的设备，stable-diffusion-webui 也提供了相应的优化选项，让高质量的 AI 艺术创作变得触手可及。",162132,"2026-04-05T11:01:52",[14,15,13],{"id":46,"name":47,"github_repo":48,"description_zh":49,"stars":50,"difficulty_score":24,"last_commit_at":51,"category_tags":52,"status":17},1381,"everything-claude-code","affaan-m\u002Feverything-claude-code","everything-claude-code 是一套专为 AI 编程助手（如 Claude Code、Codex、Cursor 等）打造的高性能优化系统。它不仅仅是一组配置文件，而是一个经过长期实战打磨的完整框架，旨在解决 AI 代理在实际开发中面临的效率低下、记忆丢失、安全隐患及缺乏持续学习能力等核心痛点。\n\n通过引入技能模块化、直觉增强、记忆持久化机制以及内置的安全扫描功能，everything-claude-code 能显著提升 AI 在复杂任务中的表现，帮助开发者构建更稳定、更智能的生产级 AI 代理。其独特的“研究优先”开发理念和针对 Token 消耗的优化策略，使得模型响应更快、成本更低，同时有效防御潜在的攻击向量。\n\n这套工具特别适合软件开发者、AI 研究人员以及希望深度定制 AI 工作流的技术团队使用。无论您是在构建大型代码库，还是需要 AI 协助进行安全审计与自动化测试，everything-claude-code 都能提供强大的底层支持。作为一个曾荣获 Anthropic 黑客大奖的开源项目，它融合了多语言支持与丰富的实战钩子（hooks），让 AI 真正成长为懂上",161692,"2026-04-20T11:33:57",[14,13,36],{"id":54,"name":55,"github_repo":56,"description_zh":57,"stars":58,"difficulty_score":59,"last_commit_at":60,"category_tags":61,"status":17},8272,"opencode","anomalyco\u002Fopencode","OpenCode 是一款开源的 AI 编程助手（Coding Agent），旨在像一位智能搭档一样融入您的开发流程。它不仅仅是一个代码补全插件，而是一个能够理解项目上下文、自主规划任务并执行复杂编码操作的智能体。无论是生成全新功能、重构现有代码，还是排查难以定位的 Bug，OpenCode 都能通过自然语言交互高效完成，显著减少开发者在重复性劳动和上下文切换上的时间消耗。\n\n这款工具专为软件开发者、工程师及技术研究人员设计，特别适合希望利用大模型能力来提升编码效率、加速原型开发或处理遗留代码维护的专业人群。其核心亮点在于完全开源的架构，这意味着用户可以审查代码逻辑、自定义行为策略，甚至私有化部署以保障数据安全，彻底打破了传统闭源 AI 助手的“黑盒”限制。\n\n在技术体验上，OpenCode 提供了灵活的终端界面（Terminal UI）和正在测试中的桌面应用程序，支持 macOS、Windows 及 Linux 全平台。它兼容多种包管理工具，安装便捷，并能无缝集成到现有的开发环境中。无论您是追求极致控制权的资深极客，还是渴望提升产出的独立开发者，OpenCode 都提供了一个透明、可信",144296,1,"2026-04-16T14:50:03",[13,27],{"id":63,"github_repo":64,"name":65,"description_en":66,"description_zh":67,"ai_summary_zh":67,"readme_en":68,"readme_zh":69,"quickstart_zh":70,"use_case_zh":71,"hero_image_url":72,"owner_login":73,"owner_name":74,"owner_avatar_url":75,"owner_bio":76,"owner_company":77,"owner_location":77,"owner_email":77,"owner_twitter":77,"owner_website":78,"owner_url":79,"languages":80,"stars":114,"forks":115,"last_commit_at":116,"license":117,"difficulty_score":24,"env_os":118,"env_gpu":119,"env_ram":119,"env_deps":120,"category_tags":125,"github_topics":126,"view_count":24,"oss_zip_url":77,"oss_zip_packed_at":77,"status":17,"created_at":142,"updated_at":143,"faqs":144,"releases":180},10234,"alibaba\u002Fnacos","nacos","an easy-to-use dynamic service discovery, configuration and service management platform for building AI cloud native applications.","Nacos 是一个易于使用的动态服务发现、配置管理及服务平台，专为构建云原生应用和微服务架构而设计。在复杂的分布式系统中，服务实例繁多且状态多变，传统硬编码的配置方式难以应对频繁变更，且缺乏实时的健康感知能力。Nacos 正是为了解决这些痛点而生，它帮助开发者实现服务的自动注册与发现，实时监测服务健康状态以屏蔽故障节点，并支持配置的集中化动态管理——无需重启应用即可生效，极大提升了运维效率与系统敏捷性。\n\n此外，Nacos 还提供动态 DNS 服务和可视化的元数据管理面板，支持加权路由与流量控制，让负载均衡策略更加灵活。作为阿里巴巴开源的核心组件，Nacos 的一大技术亮点是其广泛的生态兼容性，能够无缝对接 Dubbo、gRPC、Spring Cloud 以及 Kubernetes 等多种主流技术栈，避免应用被特定厂商的 API 绑定。无论是正在构建微服务的后端开发者，还是负责架构演进的运维工程师，Nacos 都能提供稳定、开箱即用的基础设施支持，助您轻松驾驭云原生时代的复杂挑战。","\n\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_242251a30656.png\" width=\"50%\" syt height=\"50%\" \u002F>\n\n# Nacos: Dynamic  *Na*ming and *Co*nfiguration *S*ervice\n\n[![Gitter](https:\u002F\u002Fbadges.gitter.im\u002Falibaba\u002Fnacos.svg)](https:\u002F\u002Fgitter.im\u002Falibaba\u002Fnacos?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge)   [![License](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Flicense-Apache%202-4EB1BA.svg)](https:\u002F\u002Fwww.apache.org\u002Flicenses\u002FLICENSE-2.0.html)\n[![CI](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Factions\u002Fworkflows\u002Fci.yml\u002Fbadge.svg?branch=develop)](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Factions\u002Fworkflows\u002Fci.yml)\n[![codecov](https:\u002F\u002Fcodecov.io\u002Fgh\u002Falibaba\u002Fnacos\u002Fbranch\u002Fdevelop\u002Fgraph\u002Fbadge.svg)](https:\u002F\u002Fapp.codecov.io\u002Fgh\u002Falibaba\u002Fnacos\u002Ftree\u002Fdevelop)\n[![](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FNacos-Check%20Your%20Contribution-orange)](https:\u002F\u002Fopensource.alibaba.com\u002Fcontribution_leaderboard\u002Fdetails?projectValue=nacos)\n[![Ask DeepWiki](https:\u002F\u002Fdeepwiki.com\u002Fbadge.svg)](https:\u002F\u002Fdeepwiki.com\u002Falibaba\u002Fnacos)\n\n-------\n\n## What does it do\n\nNacos (official site: [nacos.io](https:\u002F\u002Fnacos.io)) is an easy-to-use platform designed for dynamic service discovery and configuration and service management. It helps you to build cloud native applications and microservices platform easily.\n\nService is a first-class citizen in Nacos. Nacos supports almost all type of services，for example，[Dubbo\u002FgRPC service](https:\u002F\u002Fnacos.io\u002Fdocs\u002Flatest\u002Fecology\u002Fuse-nacos-with-dubbo\u002F), [Spring Cloud RESTFul service](https:\u002F\u002Fnacos.io\u002Fdocs\u002Flatest\u002Fecology\u002Fuse-nacos-with-spring-cloud\u002F) or [Kubernetes service](https:\u002F\u002Fnacos.io\u002Fdocs\u002Flatest\u002Fquickstart\u002Fquick-start-kubernetes\u002F).\n\nNacos provides four major functions.\n\n* **Service Discovery and Service Health Check** \n    \n    Nacos makes it simple for services to register themselves and to discover other services via a DNS or HTTP interface. Nacos also provides real-time health checks of services to prevent sending requests to unhealthy hosts or service instances.\n\n* **Dynamic Configuration Management**\n  \n    Dynamic Configuration Service allows you to manage configurations of all services in a centralized and dynamic manner across all environments. Nacos eliminates the need to redeploy applications and services when configurations are updated, which makes configuration changes more efficient and agile.\n\n* **Dynamic DNS Service**\n    \n    Nacos supports weighted routing, making it easier for you to implement mid-tier load balancing, flexible routing policies, flow control, and simple DNS resolution services in the production environment within your data center. It helps you to implement DNS-based service discovery easily and prevent applications from coupling to vendor-specific service discovery APIs.\n\n* **Service and MetaData Management**\n\t\n    Nacos provides an easy-to-use service dashboard to help you manage your services metadata, configuration, kubernetes DNS, service health and metrics statistics.\n \n\n## Quick Start\nIt is super easy to get started with your first project.\n\n### Deploying Nacos on cloud\n\nYou can deploy Nacos on cloud, which is the easiest and most convenient way to start Nacos. \n\nUse the following [Nacos deployment guide](https:\u002F\u002Fcn.aliyun.com\u002Fproduct\u002Faliware\u002Fmse?spm=nacos-website.topbar.0.0.0) to see more information and deploy a stable and out-of-the-box Nacos server.\n\n\n### Start by the provided startup package\n\n#### Step 1: Download the binary package \n\nYou can download the package from the [latest stable release](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Freleases).  \n\nTake release `nacos-server-1.0.0.zip` for example:\n```sh\nunzip nacos-server-1.0.0.zip\ncd nacos\u002Fbin \n``` \n\n#### Step 2: Start Server\n\nOn the **Linux\u002FUnix\u002FMac** platform, run the following command to start server with standalone mode: \n```sh\nsh startup.sh -m standalone\n```\n\nOn the **Windows** platform, run the following command to start server with standalone mode.  Alternatively, you can also double-click the `startup.cmd` to run NacosServer.\n```\nstartup.cmd -m standalone\n```\n\nFor more details, see [quick-start.](https:\u002F\u002Fnacos.io\u002Fdocs\u002Flatest\u002Fquickstart\u002Fquick-start\u002F)\n\n## Quick start for other open-source projects:\n* [Quick start with Nacos command and console](https:\u002F\u002Fnacos.io\u002Fdocs\u002Flatest\u002Fquickstart\u002Fquick-start\u002F)\n\n* [Quick start with dubbo](https:\u002F\u002Fnacos.io\u002Fdocs\u002Flatest\u002Fecology\u002Fuse-nacos-with-dubbo\u002F)\n\n* [Quick start with spring cloud](https:\u002F\u002Fnacos.io\u002Fdocs\u002Flatest\u002Fecology\u002Fuse-nacos-with-spring-cloud\u002F)\n\n* [Quick start with kubernetes](https:\u002F\u002Fnacos.io\u002Fdocs\u002Flatest\u002Fquickstart\u002Fquick-start-kubernetes\u002F)\n\n\n## Documentation\n\nYou can view the full documentation from the [Nacos website](https:\u002F\u002Fnacos.io\u002Fdocs\u002Flatest\u002Foverview\u002F).\n\nYou can also read this online eBook from the [NACOS ARCHITECTURE & PRINCIPLES](https:\u002F\u002Fnacos.io\u002Fdocs\u002Febook\u002Fkbyo6n\u002F).\n\nAll the latest and long-term notice can also be found here from [GitHub notice issue](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Flabels\u002Fnotice).\n\n## Contributing\n\nContributors are welcomed to join Nacos project. Please check [CONTRIBUTING](.\u002FCONTRIBUTING.md) about how to contribute to this project.\n\n### How can I contribute?\n\n* Take a look at issues with tags marked [`good first issue`](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fissues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) or [`contribution welcome`](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fissues?q=is%3Aopen+is%3Aissue+label%3A%22contribution+welcome%22).\n* Answer questions on [issues](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fissues).\n* Fix bugs reported on [issues](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fissues), and send us a pull request.\n* Review the existing [pull request](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpulls).\n* Improve the [website](https:\u002F\u002Fgithub.com\u002Fnacos-group\u002Fnacos-group.github.io), typically we need\n  * blog post\n  * translation on documentation\n  * use cases around the integration of Nacos in enterprise systems.\n\n## Other Related Project Repositories\n\n* [nacos-spring-project](https:\u002F\u002Fgithub.com\u002Fnacos-group\u002Fnacos-spring-project) provides the integration functionality for Spring.\n* [nacos-group](https:\u002F\u002Fgithub.com\u002Fnacos-group) is the repository that hosts the eco tools for Nacos, such as SDK, synchronization tool, etc.\n* [spring-cloud-alibaba](https:\u002F\u002Fgithub.com\u002Fspring-cloud-incubator\u002Fspring-cloud-alibaba) provides the one-stop solution for application development over Alibaba middleware which includes Nacos.\n\n## Contact\n\n* [Gitter](https:\u002F\u002Fgitter.im\u002Falibaba\u002Fnacos): Nacos's IM tool for community messaging, collaboration and discovery.\n* [Twitter](https:\u002F\u002Ftwitter.com\u002Fnacos2): Follow along for latest nacos news on Twitter.\n* [Weibo](https:\u002F\u002Fweibo.com\u002Fu\u002F6574374908): Follow along for latest nacos news on Weibo (Twitter of China version).\n* [Nacos Segmentfault](https:\u002F\u002Fsegmentfault.com\u002Ft\u002Fnacos): Get latest notice and prompt help from Segmentfault.\n* Email Group:\n     * users-nacos@googlegroups.com: Nacos usage general discussion.\n     * dev-nacos@googlegroups.com: Nacos developer discussion (APIs, feature design, etc).\n     * commits-nacos@googlegroups.com: Commits notice, very high frequency.\n* Join us from DingDing(Group 1: 21708933(full), Group 2: 30438813(full), Group 3: 31222241(full), Group 4: 12810027056). \n\n### DingDing Group QR Code\n\n![](https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_f307fec5d102.png)\n\n### DingDing MCP Group QR Code\n\n![](https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_3cbb919ae490.png)\n\n### WeChat Group QR Code\n\n![](https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_593f8530eb9d.png)\n\n## Enterprise Service\nIf you need Nacos enterprise service support, or purchase cloud product services, you can join the discussion by scanning the following DingTalk group. It can also be directly activated and used through the microservice engine (MSE) provided by Alibaba Cloud.\nhttps:\u002F\u002Fcn.aliyun.com\u002Fproduct\u002Faliware\u002Fmse?spm=nacos-website.topbar.0.0.0\n\n\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_6e487dee4acd.png\" width=\"500\">\n\n\n## Download\n\n- [Nacos Official Website](https:\u002F\u002Fnacos.io\u002Fdownload\u002Fnacos-server)\n- [GitHub Release](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Freleases)\n  \n## Who is using\n\nThese are only part of the companies using Nacos, for reference only. If you are using Nacos, please [add your company here](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fissues\u002F273) to tell us your scenario to make Nacos better.\n\n\u003Ctable>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_e72d2b6eb5c6.png\"  alt=\"Alibaba Group\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_11576b7b10c7.png\"  alt=\"虎牙直播\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_c03c5da14480.png\"  alt=\"ICBC\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_dded33da33ca.jpg\"  alt=\"爱奇艺\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_d6157686502b.png\"  alt=\"平安科技\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_83474182bcdb.png\"  alt=\"华夏信财\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Fwww.urwork.cn\u002Fpublic\u002Fimages\u002Fui\u002Flogo.png\"  alt=\"优客工场\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_43b948864201.png\"  alt=\"贝壳找房\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_0a409144f04c.png\"  alt=\"瑞安农村商业银行\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_5af3d6e01bd0.png\"  alt=\"司法大数据\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Fwww.souyidai.com\u002Fwww-style\u002Fimages\u002Flogo.gif\"  alt=\"搜易贷\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_ebec2d1f7f09.png\"  alt=\"平行云\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_71e29d83e284.jpg\"  alt=\"甘肃紫光\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"http:\u002F\u002Fwww.seaskylight.com\u002Fcn\u002Fuploadfiles\u002Fimage\u002Flogo.png\"  alt=\"海云天\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_bfc22695567a.png\"  alt=\"Acmedcare+\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_fa2ae006ef96.png\"  alt=\"北京天合互联信息有限公司\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"http:\u002F\u002Fwww.mwclg.com\u002Fstatic-resource\u002Ffront\u002Fimages\u002Fhome\u002Fimg_logo_nav.png\"  alt=\"上海密尔克卫化工\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Fwww.synwe.com\u002Flogo-full.png\"  alt=\"大连新唯\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_f46a97b0d3f9.png\"  alt=\"立思辰\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_7ca2e41c9623.png\"  alt=\"东家\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"http:\u002F\u002Fwww.sh-guiyao.com\u002Fimages\u002Flogo.jpg\"  alt=\"上海克垚\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_eafd96ffb21b.png\"  alt=\"联采科技\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_6b6e5ed95bc5.jpg\"  alt=\"南京28研究所\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_5c13f22d7165.png\"  alt=\"凤凰网-汽车\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_16b73c89e09a.png\"  alt=\"中化信息\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_b12e72cb36d0.png\"  alt=\"一点车\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_c76618459617.png\"  alt=\"明传无线\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_165d15a2d3bd.png\"  alt=\"妙优车\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_566a0a37113f.png\"  alt=\"蜂巢\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_7c9ad0ace08e.png\"  alt=\"华存数据\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_679da7f02c01.png\"  alt=\"数云\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_72b64b5d59f7.png\"  alt=\"广通软件\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_3c5364b3e1dc.png\"  alt=\"菜菜\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_fcda4186c49b.png\"  alt=\"科蓝公司\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_dda476bf6d1b.png\"  alt=\"浩鲸\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_25fc254a3251.png\"  alt=\"未名天日语\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_c5e409132450.jpg\"  alt=\"金联创\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_d50e493c2418.png\"  alt=\"同窗链\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_61d959627b18.jpg\"  alt=\"顺能\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_6474db03650a.png\"  alt=\"百世快递\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_d1b4a70da917.jpg\"  alt=\"汽车之家\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_c4df266c4dbe.png\"  alt=\"鲸打卡\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_a2ae3a300c05.jpg\"  alt=\"时代光华\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_a3efdf111167.jpg\"  alt=\"康美\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_9972939f9a94.jpg\"  alt=\"环球易购\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_0b2f4b98d44c.png\"  alt=\"Nepxion\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_e88d403bb350.png\"  alt=\"chigua\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_54d56f68c9b0.jpg\"  alt=\"宅无限\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_8020b8ba0b9c.jpg\"  alt=\"天阙\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_8bc8397109c2.jpg\"  alt=\"联合永道\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_46014cf527f3.jpg\"  alt=\"明源云\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Fwww.daocloud.io\u002Fstatic\u002FLogo-Light.png\"  alt=\"DaoCloud\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_9210b6ebaa3d.jpg\"  alt=\"美菜\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_fde926b5b776.png\"  alt=\"松格科技\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_cd85ae412b1f.jpg\"  alt=\"集萃智能\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_a80fc198fac7.png\"  alt=\"吾享\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_4955ec94accc.png\"  alt=\"拓深科技\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Fwww.sunline.cn\u002Fu_file\u002FfileUpload\u002F2021-06\u002F25\u002F2021062586431.png\"  alt=\"长亮科技\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"http:\u002F\u002Fpmt2f499f.pic44.websiteonline.cn\u002Fupload\u002Fwv0c.png\"  alt=\"深圳易停车库\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"http:\u002F\u002Fwww.dragonwake.cn\u002Fstatic\u002Fcss\u002Fdefault\u002Fimg\u002Flogo.png\"  alt=\"武汉日创科技\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Fi4im-web.oss-cn-shanghai.aliyuncs.com\u002Fimages\u002Flogo.png\"  alt=\"易管智能\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_d84218edaafc.png\"  alt=\"云帐房\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Fwww.sinocare.com\u002Fsannuo\u002Ftemplates\u002Fweb\u002Fimg\u002Fbocweb-logo.svg\"  alt=\"三诺生物\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>郑州山水\u003C\u002Ftd>\n    \u003Ctd>知氏教育\u003C\u002Ftd>\n    \u003Ctd>\u003C\u002Ftd>\n    \u003Ctd>\u003C\u002Ftd>\n  \u003C\u002Ftr>\n\u003C\u002Ftable>\n","\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_242251a30656.png\" width=\"50%\" syt height=\"50%\" \u002F>\n\n# Nacos：动态的 *Na*ming 和 *Co*nfiguration *S*ervice\n\n[![Gitter](https:\u002F\u002Fbadges.gitter.im\u002Falibaba\u002Fnacos.svg)](https:\u002F\u002Fgitter.im\u002Falibaba\u002Fnacos?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge)   [![License](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Flicense-Apache%202-4EB1BA.svg)](https:\u002F\u002Fwww.apache.org\u002Flicenses\u002FLICENSE-2.0.html)\n[![CI](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Factions\u002Fworkflows\u002Fci.yml\u002Fbadge.svg?branch=develop)](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Factions\u002Fworkflows\u002Fci.yml)\n[![codecov](https:\u002F\u002Fcodecov.io\u002Fgh\u002Falibaba\u002Fnacos\u002Fbranch\u002Fdevelop\u002Fgraph\u002Fbadge.svg)](https:\u002F\u002Fapp.codecov.io\u002Fgh\u002Falibaba\u002Fnacos\u002Ftree\u002Fdevelop)\n[![](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FNacos-Check%20Your%20Contribution-orange)](https:\u002F\u002Fopensource.alibaba.com\u002Fcontribution_leaderboard\u002Fdetails?projectValue=nacos)\n[![Ask DeepWiki](https:\u002F\u002Fdeepwiki.com\u002Fbadge.svg)](https:\u002F\u002Fdeepwiki.com\u002Falibaba\u002Fnacos)\n\n-------\n\n## 它能做什么\n\nNacos（官方网站：[nacos.io](https:\u002F\u002Fnacos.io)）是一个易于使用的平台，专为动态服务发现、配置管理和服务治理而设计。它可以帮助您轻松构建云原生应用和微服务架构。\n\n在Nacos中，服务是一等公民。Nacos支持几乎所有类型的服务，例如[Dubbo\u002FgRPC服务](https:\u002F\u002Fnacos.io\u002Fdocs\u002Flatest\u002Fecology\u002Fuse-nacos-with-dubbo\u002F)、[Spring Cloud RESTFul服务](https:\u002F\u002Fnacos.io\u002Fdocs\u002Flatest\u002Fecology\u002Fuse-nacos-with-spring-cloud\u002F)或[Kubernetes服务](https:\u002F\u002Fnacos.io\u002Fdocs\u002Flatest\u002Fquickstart\u002Fquick-start-kubernetes\u002F)。\n\nNacos提供四大核心功能：\n\n* **服务发现与健康检查**\n  \n  Nacos使服务能够通过DNS或HTTP接口轻松注册自身并发现其他服务。同时，Nacos还提供实时的服务健康检查，以避免将请求发送到不健康的主机或服务实例。\n\n* **动态配置管理**\n  \n  动态配置服务允许您以集中化和动态的方式管理所有环境中的服务配置。当配置更新时，Nacos无需重新部署应用程序和服务，从而使配置变更更加高效和敏捷。\n\n* **动态DNS服务**\n  \n  Nacos支持加权路由，使您能够在数据中心的生产环境中更轻松地实现中间层负载均衡、灵活的路由策略、流量控制以及简单的DNS解析服务。它帮助您轻松实现基于DNS的服务发现，并防止应用程序与特定厂商的服务发现API耦合。\n\n* **服务与元数据管理**\n  \n  Nacos提供一个易于使用的服务仪表板，帮助您管理服务的元数据、配置、Kubernetes DNS、服务健康状况及指标统计。\n\n## 快速入门\n开始您的第一个项目非常简单。\n\n### 在云端部署Nacos\n\n您可以在云端部署Nacos，这是启动Nacos最简单便捷的方式。\n\n请使用以下[Nacos部署指南](https:\u002F\u002Fcn.aliyun.com\u002Fproduct\u002Faliware\u002Fmse?spm=nacos-website.topbar.0.0.0)获取更多信息，并部署一个稳定且开箱即用的Nacos服务器。\n\n\n### 使用提供的启动包开始\n\n#### 第一步：下载二进制包\n\n您可以从[最新稳定版本](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Freleases)下载软件包。\n\n以`nacos-server-1.0.0.zip`为例：\n```sh\nunzip nacos-server-1.0.0.zip\ncd nacos\u002Fbin \n``` \n\n#### 第二步：启动服务器\n\n在**Linux\u002FUnix\u002FMac**平台上，运行以下命令以单机模式启动服务器：\n```sh\nsh startup.sh -m standalone\n```\n\n在**Windows**平台上，运行以下命令以单机模式启动服务器。或者，您也可以双击`startup.cmd`来运行NacosServer。\n```\nstartup.cmd -m standalone\n```\n\n更多详细信息，请参阅[快速入门](https:\u002F\u002Fnacos.io\u002Fdocs\u002Flatest\u002Fquickstart\u002Fquick-start\u002F)。\n\n## 其他开源项目的快速入门：\n* [使用Nacos命令行和控制台快速入门](https:\u002F\u002Fnacos.io\u002Fdocs\u002Flatest\u002Fquickstart\u002Fquick-start\u002F)\n\n* [使用Dubbo快速入门](https:\u002F\u002Fnacos.io\u002Fdocs\u002Flatest\u002Fecology\u002Fuse-nacos-with-dubbo\u002F)\n\n* [使用Spring Cloud快速入门](https:\u002F\u002Fnacos.io\u002Fdocs\u002Flatest\u002Fecology\u002Fuse-nacos-with-spring-cloud\u002F)\n\n* [使用Kubernetes快速入门](https:\u002F\u002Fnacos.io\u002Fdocs\u002Flatest\u002Fquickstart\u002Fquick-start-kubernetes\u002F)\n\n\n## 文档\n\n您可以通过[Nacos官网](https:\u002F\u002Fnacos.io\u002Fdocs\u002Flatest\u002Foverview\u002F)查看完整文档。\n\n您还可以阅读在线电子书[《NACOS架构与原理》](https:\u002F\u002Fnacos.io\u002Fdocs\u002Febook\u002Fkbyo6n\u002F)。\n\n所有最新和长期的通知也可在此处找到：[GitHub通知议题](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Flabels\u002Fnotice)。\n\n## 贡献\n\n欢迎各位贡献者加入Nacos项目。请查阅[CONTRIBUTING](.\u002FCONTRIBUTING.md)，了解如何参与本项目。\n\n### 我该如何贡献？\n\n* 查看带有[`good first issue`](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fissues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22)或[`contribution welcome`](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fissues?q=is%3Aopen+is%3Aissue+label%3A%22contribution+welcome%22)标签的问题。\n* 回答[Github问题](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fissues)中的疑问。\n* 修复[Github问题](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fissues)中报告的Bug，并提交Pull Request。\n* 审核现有的[Pull Request](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpulls)。\n* 改进[官网](https:\u002F\u002Fgithub.com\u002Fnacos-group\u002Fnacos-group.github.io)，通常我们需要：\n  * 博客文章\n  * 文档翻译\n  * 关于Nacos在企业系统中集成的应用案例。\n\n## 其他相关项目仓库\n\n* [nacos-spring-project](https:\u002F\u002Fgithub.com\u002Fnacos-group\u002Fnacos-spring-project) 提供了与Spring框架的集成功能。\n* [nacos-group](https:\u002F\u002Fgithub.com\u002Fnacos-group) 是托管Nacos生态工具的仓库，例如SDK、同步工具等。\n* [spring-cloud-alibaba](https:\u002F\u002Fgithub.com\u002Fspring-cloud-incubator\u002Fspring-cloud-alibaba) 提供了一站式解决方案，用于基于包含Nacos在内的阿里巴巴中间件进行应用开发。\n\n## 联系方式\n\n* [Gitter](https:\u002F\u002Fgitter.im\u002Falibaba\u002Fnacos)：Nacos 社区的消息、协作与发现工具。\n* [Twitter](https:\u002F\u002Ftwitter.com\u002Fnacos2)：在 Twitter 上关注 Nacos 的最新动态。\n* [微博](https:\u002F\u002Fweibo.com\u002Fu\u002F6574374908)：在微博上关注 Nacos 的最新消息（中国的 Twitter）。\n* [Nacos SegmentFault](https:\u002F\u002Fsegmentfault.com\u002Ft\u002Fnacos)：从 SegmentFault 获取最新公告和及时帮助。\n* 邮件组：\n     * users-nacos@googlegroups.com：Nacos 使用通用讨论。\n     * dev-nacos@googlegroups.com：Nacos 开发者讨论（API、功能设计等）。\n     * commits-nacos@googlegroups.com：提交通知，频率非常高。\n* 欢迎加入钉钉群（群1：21708933已满，群2：30438813已满，群3：31222241已满，群4：12810027056）。\n\n### 钉钉群二维码\n\n![](https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_f307fec5d102.png)\n\n### 钉钉 MCP 群二维码\n\n![](https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_3cbb919ae490.png)\n\n### 微信群二维码\n\n![](https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_593f8530eb9d.png)\n\n## 企业服务\n如果您需要 Nacos 企业级服务支持，或购买云产品服务，可以通过扫描以下钉钉群加入讨论。您也可以通过阿里云提供的微服务引擎（MSE）直接开通并使用。\nhttps:\u002F\u002Fcn.aliyun.com\u002Fproduct\u002Faliware\u002Fmse?spm=nacos-website.topbar.0.0.0\n\n\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_6e487dee4acd.png\" width=\"500\">\n\n\n## 下载\n- [Nacos 官网](https:\u002F\u002Fnacos.io\u002Fdownload\u002Fnacos-server)\n- [GitHub 发布页面](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Freleases)\n\n## 使用案例\n以下仅列出部分使用 Nacos 的公司，仅供参考。如果您正在使用 Nacos，请[在此处添加您的公司](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fissues\u002F273)，告诉我们您的应用场景，帮助我们共同改进 Nacos。\n\n\u003Ctable>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_e72d2b6eb5c6.png\"  alt=\"阿里巴巴集团\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_11576b7b10c7.png\"  alt=\"虎牙直播\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_c03c5da14480.png\"  alt=\"工商银行\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_dded33da33ca.jpg\"  alt=\"爱奇艺\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_d6157686502b.png\"  alt=\"平安科技\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_83474182bcdb.png\"  alt=\"华夏信财\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Fwww.urwork.cn\u002Fpublic\u002Fimages\u002Fui\u002Flogo.png\"  alt=\"优客工场\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_43b948864201.png\"  alt=\"贝壳找房\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_0a409144f04c.png\"  alt=\"瑞安农村商业银行\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_5af3d6e01bd0.png\"  alt=\"司法大数据\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Fwww.souyidai.com\u002Fwww-style\u002Fimages\u002Flogo.gif\"  alt=\"搜易贷\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_ebec2d1f7f09.png\"  alt=\"平行云\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_71e29d83e284.jpg\"  alt=\"甘肃紫光\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"http:\u002F\u002Fwww.seaskylight.com\u002Fcn\u002Fuploadfiles\u002Fimage\u002Flogo.png\"  alt=\"海云天\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_bfc22695567a.png\"  alt=\"Acmedcare+\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_fa2ae006ef96.png\"  alt=\"北京天合互联信息有限公司\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"http:\u002F\u002Fwww.mwclg.com\u002Fstatic-resource\u002Ffront\u002Fimages\u002Fhome\u002Fimg_logo_nav.png\"  alt=\"上海密尔克卫化工\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Fwww.synwe.com\u002Flogo-full.png\"  alt=\"大连新唯\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_f46a97b0d3f9.png\"  alt=\"立思辰\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_7ca2e41c9623.png\"  alt=\"东家\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"http:\u002F\u002Fwww.sh-guiyao.com\u002Fimages\u002Flogo.jpg\"  alt=\"上海克垚\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_eafd96ffb21b.png\"  alt=\"联采科技\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_6b6e5ed95bc5.jpg\"  alt=\"南京28研究所\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_5c13f22d7165.png\"  alt=\"凤凰网-汽车\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_16b73c89e09a.png\"  alt=\"中化信息\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_b12e72cb36d0.png\"  alt=\"一点车\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_c76618459617.png\"  alt=\"明传无线\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_165d15a2d3bd.png\"  alt=\"妙优车\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_566a0a37113f.png\"  alt=\"蜂巢\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_7c9ad0ace08e.png\"  alt=\"华存数据\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_679da7f02c01.png\"  alt=\"数云\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_72b64b5d59f7.png\"  alt=\"广通软件\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_3c5364b3e1dc.png\"  alt=\"菜菜\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_fcda4186c49b.png\"  alt=\"科蓝公司\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_dda476bf6d1b.png\"  alt=\"浩鲸\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_25fc254a3251.png\"  alt=\"未名天日语\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_c5e409132450.jpg\"  alt=\"金联创\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_d50e493c2418.png\"  alt=\"同窗链\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_61d959627b18.jpg\"  alt=\"顺能\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_6474db03650a.png\"  alt=\"百世快递\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_d1b4a70da917.jpg\"  alt=\"汽车之家\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_c4df266c4dbe.png\"  alt=\"鲸打卡\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_a2ae3a300c05.jpg\"  alt=\"时代光华\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_a3efdf111167.jpg\"  alt=\"康美\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_9972939f9a94.jpg\"  alt=\"环球易购\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_0b2f4b98d44c.png\"  alt=\"Nepxion\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_e88d403bb350.png\"  alt=\"chigua\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_54d56f68c9b0.jpg\"  alt=\"宅无限\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_8020b8ba0b9c.jpg\"  alt=\"天阙\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_8bc8397109c2.jpg\"  alt=\"联合永道\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_46014cf527f3.jpg\"  alt=\"明源云\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Fwww.daocloud.io\u002Fstatic\u002FLogo-Light.png\"  alt=\"DaoCloud\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_9210b6ebaa3d.jpg\"  alt=\"美菜\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_fde926b5b776.png\"  alt=\"松格科技\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_cd85ae412b1f.jpg\"  alt=\"集萃智能\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_a80fc198fac7.png\"  alt=\"吾享\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_4955ec94accc.png\"  alt=\"拓深科技\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Fwww.sunline.cn\u002Fu_file\u002FfileUpload\u002F2021-06\u002F25\u002F2021062586431.png\"  alt=\"长亮科技\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"http:\u002F\u002Fpmt2f499f.pic44.websiteonline.cn\u002Fupload\u002Fwv0c.png\"  alt=\"深圳易停车库\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"http:\u002F\u002Fwww.dragonwake.cn\u002Fstatic\u002Fcss\u002Fdefault\u002Fimg\u002Flogo.png\"  alt=\"武汉日创科技\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Fi4im-web.oss-cn-shanghai.aliyuncs.com\u002Fimages\u002Flogo.png\"  alt=\"易管智能\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_readme_d84218edaafc.png\"  alt=\"云帐房\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003Cimg src=\"https:\u002F\u002Fwww.sinocare.com\u002Fsannuo\u002Ftemplates\u002Fweb\u002Fimg\u002Fbocweb-logo.svg\"  alt=\"三诺生物\" width=\"180\" height=\"120\">\u003C\u002Ftd>\n    \u003Ctd>\u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd>郑州山水\u003C\u002Ftd>\n    \u003Ctd>知氏教育\u003C\u002Ftd>\n    \u003Ctd>\u003C\u002Ftd>\n    \u003Ctd>\u003C\u002Ftd>\n  \u003C\u002Ftr>\n\u003C\u002Ftable>","# Nacos 快速上手指南\n\nNacos（Dynamic **Na**ming and **Co**nfiguration **S**ervice）是一个易于使用的平台，专为动态服务发现、配置管理和服务管理而设计。它帮助您轻松构建云原生应用和微服务平台。\n\n## 1. 环境准备\n\n在开始之前，请确保您的开发环境满足以下要求：\n\n*   **操作系统**：Linux \u002F Unix \u002F Mac 或 Windows\n*   **JDK 版本**：建议安装 JDK 1.8+ 或 JDK 11+（Nacos 2.x 版本推荐 JDK 11+ 以获得更好性能）\n*   **内存要求**：单机模式启动建议至少预留 512MB 可用内存\n*   **网络要求**：确保端口 `8848`（默认 HTTP 端口）和 `9848`\u002F`9849`（gRPC 通信端口，Nacos 2.x 必需）未被占用且防火墙已放行。\n\n> **提示**：国内用户可通过阿里云镜像或官网下载加速获取安装包。\n\n## 2. 安装步骤\n\n### 第一步：下载二进制包\n\n访问 [Nacos GitHub Release](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Freleases) 或 [Nacos 官网下载页](https:\u002F\u002Fnacos.io\u002Fdownload\u002Fnacos-server) 下载最新稳定版的压缩包。\n\n以 `nacos-server-2.x.x.zip` 为例，在终端执行解压并进入目录：\n\n```bash\nunzip nacos-server-2.x.x.zip\ncd nacos\u002Fbin\n```\n\n### 第二步：启动服务器\n\n根据您的操作系统选择对应的启动命令。以下命令将以**单机模式**（Standalone）启动，适合本地开发和测试。\n\n**Linux \u002F Unix \u002F Mac:**\n\n```bash\nsh startup.sh -m standalone\n```\n\n**Windows:**\n\n```cmd\nstartup.cmd -m standalone\n```\n\n或者直接双击运行 `startup.cmd` 文件（需手动修改脚本或命令行参数以指定 standalone 模式，推荐使用命令行方式）。\n\n启动成功后，控制台将输出类似 `Nacos started successfully in ...` 的日志。\n\n## 3. 基本使用\n\n### 访问控制台\n\n打开浏览器访问 Nacos 控制台：\n\n*   **地址**：`http:\u002F\u002Flocalhost:8848\u002Fnacos`\n*   **默认账号**：`nacos`\n*   **默认密码**：`nacos`\n\n登录后，您可以在控制台中进行服务管理和配置管理。\n\n### 核心功能示例\n\n#### 1. 服务注册与发现\nNacos 支持多种框架的服务注册，无需额外代码即可让服务自动注册。\n\n*   **Spring Cloud 应用**：只需在 `bootstrap.properties` 中配置：\n    ```properties\n    spring.cloud.nacos.discovery.server-addr=127.0.0.1:8848\n    spring.application.name=my-service\n    ```\n*   **Dubbo 应用**：在配置文件中指定注册中心：\n    ```properties\n    dubbo.registry.address=nacos:\u002F\u002F127.0.0.1:8848\n    ```\n\n启动应用后，可在 Nacos 控制台的“服务管理”列表中看到注册上来的服务实例。\n\n#### 2. 动态配置管理\n您可以在不重启应用的情况下动态更新配置。\n\n1.  登录 Nacos 控制台，进入 **配置管理** -> **配置列表**。\n2.  点击 **+** 号新建配置：\n    *   **Data ID**: `my-service.yaml` (通常格式为 `${spring.application.name}.${file-extension}`)\n    *   **Group**: `DEFAULT_GROUP`\n    *   **配置格式**: `YAML`\n    *   **配置内容**:\n        ```yaml\n        user:\n          name: nacos-user\n          age: 18\n        ```\n3.  点击发布。\n4.  在应用中监听该配置变化（以 Spring Cloud Alibaba 为例），应用会自动感知并刷新配置，无需重启。\n\n---\n*更多高级用法（如集群部署、Kubernetes 集成、权重路由等）请参考 [Nacos 官方文档](https:\u002F\u002Fnacos.io\u002Fdocs\u002Flatest\u002Foverview\u002F)。*","某电商团队在构建基于 Spring Cloud 的微服务架构时，面临多环境配置混乱与服务调用不稳定的挑战。\n\n### 没有 nacos 时\n- 每次修改数据库连接或功能开关配置，都必须重新打包并重启所有相关微服务，发布窗口长且风险高。\n- 新增服务实例需手动更新网关路由表或硬编码 IP 地址，扩容操作繁琐且容易因人为疏忽导致调用失败。\n- 缺乏统一的健康检查机制，流量常被分发到已宕机或响应缓慢的节点，引发用户端频繁报错。\n- 开发、测试、生产环境的配置文件散落在各个代码仓库中，版本难以同步，经常出现“本地正常但线上异常”的配置漂移问题。\n- 服务元数据不透明，运维人员无法直观查看当前集群的服务状态和依赖关系，故障排查如同盲人摸象。\n\n### 使用 nacos 后\n- 通过动态配置管理功能，运营人员可在控制台实时调整促销阈值或切换数据源，变更秒级生效且无需重启服务。\n- 服务启动时自动向 nacos 注册并心跳保活，消费者即时感知新实例上线，实现真正的弹性伸缩与自动发现。\n- 内置的实时健康检查机制自动剔除异常节点，确保请求只转发给健康实例，显著提升了系统可用性。\n- 利用命名空间（Namespace）和分组（Group）特性，一套代码即可完美隔离多环境配置，彻底杜绝配置混淆。\n- 借助可视化的服务仪表盘，团队能实时监控服务健康度、流量指标及元数据变更，运维效率大幅提升。\n\nnacos 将原本静态僵化的微服务治理转变为动态敏捷的自动化流程，成为云原生架构稳定运行的核心枢纽。","https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Falibaba_nacos_242251a3.png","alibaba","Alibaba","https:\u002F\u002Foss.gittoolsai.com\u002Favatars\u002Falibaba_f65f7221.png","Alibaba Open Source",null,"https:\u002F\u002Fopensource.alibaba.com\u002F","https:\u002F\u002Fgithub.com\u002Falibaba",[81,85,89,93,97,101,104,108,111],{"name":82,"color":83,"percentage":84},"Java","#b07219",92.7,{"name":86,"color":87,"percentage":88},"TypeScript","#3178c6",6.1,{"name":90,"color":91,"percentage":92},"SCSS","#c6538c",0.7,{"name":94,"color":95,"percentage":96},"JavaScript","#f1e05a",0.3,{"name":98,"color":99,"percentage":100},"PLpgSQL","#336790",0.1,{"name":102,"color":103,"percentage":100},"Shell","#89e051",{"name":105,"color":106,"percentage":107},"PLSQL","#dad8d8",0,{"name":109,"color":110,"percentage":107},"Batchfile","#C1F12E",{"name":112,"color":113,"percentage":107},"EJS","#a91e50",32874,13271,"2026-04-20T10:18:03","Apache-2.0","Linux, macOS, Windows","未说明",{"notes":121,"python":119,"dependencies":122},"Nacos 是基于 Java 的服务发现与配置管理工具，非 AI 模型，因此无 GPU、Python 或特定显存需求。支持单机模式（standalone）和集群模式部署。可通过下载二进制包直接运行，也支持 Kubernetes、Docker 及阿里云 MSE 部署。",[123,124],"Java (隐含，基于 startup.sh\u002Fcmd 脚本及 Spring Cloud\u002FDubbo 生态)","MSE (可选，阿里云微服务引擎)",[13],[65,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141],"dubbo","kubernetes","istio","spring-cloud","microservices","configuration-management","distributed-configuration","ai-registry","mcp","mcp-registry","a2a-registry","mcp-management","prompt","skills","agent","2026-03-27T02:49:30.150509","2026-04-20T23:57:21.630648",[145,150,155,160,165,170,175],{"id":146,"question_zh":147,"answer_zh":148,"source_url":149},45910,"Nacos 是否支持 Oracle、PostgreSQL、DB2 等非 MySQL 数据库？","官方版本主要支持 MySQL，但社区已有开源方案支持其他数据库。例如，有用户提供了支持 PostgreSQL 和 GaussDB 的 Nacos 2.2.0 版本，可以直接使用，项目地址为：https:\u002F\u002Fgithub.com\u002Fdylan-tao\u002Fnacos-gaussdb。","https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fissues\u002F2328",{"id":151,"question_zh":152,"answer_zh":153,"source_url":154},45911,"升级 Spring Boot 2.4+ 后报错找不到 ConfigurationBeanFactoryMetadata 类怎么办？","这是版本兼容性问题。建议将 Nacos Spring Boot Starter 升级到 0.2.11 或更高版本（如 0.2.12），即可兼容 Spring Boot 2.4.x 至 2.7.x 版本。请检查 pom.xml 中的依赖版本并进行升级。","https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fissues\u002F4554",{"id":156,"question_zh":157,"answer_zh":158,"source_url":159},45912,"Windows 环境下 Nacos 运行一段时间后 CPU 占用率飙升至 100% 如何解决？","该问题在 Windows 10\u002F11 环境下已被多次报告，表现为启动数小时后 Java 进程 CPU 占满。目前官方尚未给出确切修复补丁，临时建议避免在 Windows 生产环境长时间运行，或尝试通过任务管理器结束高占用进程后重启 Nacos。推荐在 Linux 环境下部署以获得更稳定的性能。","https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fissues\u002F3903",{"id":161,"question_zh":162,"answer_zh":163,"source_url":164},45913,"Nacos 开启鉴权后是否存在被绕过的安全风险？如何防护？","曾发现通过设置 HTTP Header 中的 User-Agent 为 'Nacos-Server' 可绕过鉴权访问接口。虽然代码逻辑中有相关判断，但建议不要仅依赖应用层鉴权。最佳实践是结合防火墙或网关配置 IP 白名单，限制只有受信任的内部 IP 才能访问 Nacos 服务端端口，从而增强安全性。","https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fissues\u002F4593",{"id":166,"question_zh":167,"answer_zh":168,"source_url":169},45914,"Nacos 3.0 对 JDK 版本有什么要求？客户端是否也需要升级？","Nacos Server 3.0 正式版已发布，服务端强制要求 JDK 17 及以上版本（因升级至 Spring Boot 3）。但 Nacos 客户端（Client）仍保持兼容，支持 JDK 8 及以上版本，无需强制升级客户端的 JDK 环境。","https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fissues\u002F12923",{"id":171,"question_zh":172,"answer_zh":173,"source_url":174},45915,"Docker 部署 Nacos 集群模式时出现疯狂 GC 或服务宕机，且集群节点显示异常 Hostname 怎么办？","在 Docker 集群模式下，必须正确配置每个节点的网络标识。不要混淆多网卡配置，每个节点应通过环境变量 `NACOS_SERVER_IP` 指定当前节点自身的 IP 地址，而不是配置多个地址。如果使用 Hostname 访问，需确保 Docker Compose 中配置了 `extra_hosts` 或正确的网络别名，否则会导致节点间通信失败引发频繁 GC 和宕机。","https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fissues\u002F3411",{"id":176,"question_zh":177,"answer_zh":178,"source_url":179},45916,"服务器已开放 8848、9848、9849 端口，但客户端仍报 'Server check fail, port 9848 is available' 错误？","Nacos 2.x 版本引入了 gRPC 通信，默认使用主端口偏移量 +1000 和 +1001 的端口（即 9848 和 9849）。除了确保防火墙开放这些端口外，还需检查服务器内部监听地址。如果 Nacos 绑定的是 localhost 而非 0.0.0.0 或具体内网 IP，外部客户端将无法连接。请检查启动日志确认监听地址，并确保服务端配置允许外部 IP 访问。","https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fissues\u002F7893",[181,186,191,196,201,206,211,216,221,226,231,236,241,246,251,256,261,266,271,276],{"id":182,"version":183,"summary_zh":184,"released_at":185},360853,"3.2.1-2026.04.03","Nacos `3.2.1-2026.04.03` 是一个 **快照** 版本，重点修复了 3.2.0 中发现的严重 bug，并对相关功能进行了增强，尤其是在 AI 模块稳定性、数据库兼容性以及控制台 UI 改进方面。\n\n主要亮点包括：\n\n- **AI 注册中心增强**：完善 Prompt 生命周期管理界面、AI 资源追踪日志记录，并优化列表 API 的过滤功能。\n- **数据库兼容性**：修复 PostgreSQL 和 Oracle 的 Schema 问题，确保使用 ORDER BY 子句时分页结果的确定性。\n- **依赖项更新**：将 MCP SDK 升级至 0.17.0，以解决 json-schema-validator 的冲突问题。\n- **并发修复**：消除了 AI 发布管道、命名模块以及客户端故障转移中的竞态条件。\n- **控制台 UI**：修复了配置编辑错误、命名空间 ID 校验问题以及批量导入异常。\n\n---\n\n## 功能特性\n\n- [#14807] 为旧版和新版控制台分别新增 Prompt 生命周期管理界面。\n- [#14809] 增强 AI 资源列表 API，支持过滤和排序功能。\n- [#14794] 允许管理员用户强制发布技能。\n\n## 功能改进与重构\n\n- [#14743] 在 DerbySnapshotOperation 中关闭 CallableStatement，防止 JDBC 资源泄漏。\n- [#14750] 修复 FailoverReactor.isFailoverSwitch 方法中“检查后操作”类型的竞态条件。\n- [#14751] 修复命名模块中 ConcurrentHashMap 的“检查后操作”类型竞态条件。\n- [#14784] 对 ops 控制器表单中的输入参数进行校验，提升安全性。\n- [#14806] 提升 v3 API 中集群指标聚合完整性的信号准确性。\n- [#14818] 继续优化 v3 API 中集群指标聚合完整性的信号准确性。\n- [#14822] 将 SkillOperationServiceImpl 和 AgentSpecOperationServiceImpl 中的重复逻辑提取到 AiResourceManager 和 VersionUtils 类中。\n- [#14834] 升级旧版和新版控制台的 UI 依赖项。\n\n## Bug 修复\n\n- [#14046] 修复 MySQL 下 ConfigInfoMapperByMySql.findConfigInfoLike4PageFetchRows 方法结果精度问题。\n- [#14741] 为 findConfigInfoLike4PageFetchRows 方法添加 ORDER BY 子句，确保分页结果的确定性。\n- [#14742] 同上。\n- [#14746] 为剩余的 MySQL 分页查询添加 ORDER BY 子句，保证结果的确定性。\n- [#14747] 为 Oracle 分页查询添加 ORDER BY 子句，确保结果的确定性。\n- [#14748] 为 Derby 分页查询添加 ORDER BY 子句，保证结果的确定性。\n- [#14764] 修复新 UI 在添加自定义命名空间时的命名空间 ID 校验问题。\n- [#14765] 修复 3.2 版控制台中配置文件编辑错误。\n- [#14768] 解决由于 json-schema-validator 依赖冲突导致 `\u002Fv3\u002Fconsole\u002Fai\u002Fmcp\u002FimportToolsFromMcp` 接口调用失败的问题。\n- [#14771] 修复旧版控制台 UI 中的批量导入失败问题。\n- [#14775] 在 application.properties 模板中补充缺失的 OIDC 相关配置。\n- [#14783] 从 AiClientProxy 接口中移除 downloadSkillZip 方法，直接通过 HTTP 客户端完成技能下载。\n- [#14786] 通过预先生成 executionId，消除 AI 发布管道中的竞态条件。\n- [#14810] 修复 PostgreSQL Schema 默认 ti","2026-04-03T10:05:35",{"id":187,"version":188,"summary_zh":189,"released_at":190},360854,"3.2.1-2026.03.30","Nacos `3.2.1-2026.03.30` 是一个 **快照** 版本，重点修复了 3.2.0 中发现的严重问题，尤其是在 AI 模块依赖冲突、控制台 UI 错误以及技能发布流程中的竞态条件等方面。\n\n主要更新包括：\n- **依赖项解决**：将 MCP SDK 升级至 0.17.0，以解决影响 AI 模块功能的 json-schema-validator 冲突问题。\n- **AI 模块稳定性**：修复了技能发布流程中的竞态条件，并优化了技能下载的路由逻辑。\n- **控制台 UI 修复**：解决了新版 UI 中配置文件编辑错误及命名空间 ID 验证问题。\n- **输入验证**：增强了运维控制器表单中的参数验证，以提升安全性。\n\n## 功能改进\n\n- [#14794] 支持管理员用户强制发布技能。\n\n## 优化\u002F重构\n\n- [#14784] 对运维控制器表单中的输入参数进行验证，以提升安全性。\n\n## 问题修复\n\n- [#14765] 修复 3.2 控制台中配置文件编辑错误。\n- [#14768] 修复因 json-schema-validator 依赖冲突导致的 `\u002Fv3\u002Fconsole\u002Fai\u002Fmcp\u002FimportToolsFromMcp` 接口调用失败问题。\n- [#14771] 修复旧版控制台 UI 中批量导入失败的问题。\n- [#14775] 在 application.properties 模板中添加缺失的 OIDC 相关配置。\n- [#14783] 从 AiClientProxy 接口中移除 downloadSkillZip 方法，直接通过 HTTP 客户端处理技能下载请求。\n- [#14786] 通过预先生成 executionId，消除了 AI 发布流程中的竞态条件。\n- [#14794] 修复新版 UI 在添加自定义命名空间时的命名空间 ID 验证问题。\n\n## 依赖更新\n\n- [#14782] 将 MCP SDK 升级至 0.17.0，以解决 json-schema-validator 冲突问题。\n\n**完整变更日志**：https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fcompare\u002F3.2.0...3.2.1-2026.03.30","2026-03-30T12:06:52",{"id":192,"version":193,"summary_zh":194,"released_at":195},360855,"3.2.0","Nacos 3.2.0 是一个重大版本，重点在于插件架构的增强、AI 注册中心的扩展、API 的现代化以及代码质量的提升。主要亮点包括：\n\n- **AI 注册中心完善“AI 三驾马车”**：技能注册中心和提示词注册中心加入现有的 MCP\u002FAgent 注册中心，并集成 Nacos Copilot 实现 AI 辅助管理。\n- **插件架构现代化**：基于 SPI 的全面插件管理功能，配备控制台 UI、集群范围同步机制以及 PostgreSQL 功能增强。\n- **API 清理**：移除旧版 UDP PUSH 支持，并将 \u002Fv1 和 \u002Fv2 HTTP API 提取至子模块，以备后续彻底移除。\n- **安全与代码质量**：新增 OIDC\u002FOAuth2 认证插件，修复多项 FindBugs 问题，移除死代码，并增强对 JDK 17+ 的兼容性。\n- **控制台现代化**：支持新旧控制台双 UI 切换，同时优化用户体验。\n\n## 功能特性\n\n- [#13699] 支持 MCP 工具的 outputSchema 字段。\n- [#14041] 将 nacos-plugin PostgreSQL 及基础实现合并到主仓库。\n- [#14056] 重构数据源插件结构，并增强 PostgreSQL 能力。\n- [#14077] 实现基于 SPI 的插件发现与管理 API。\n- [#14078] 实现插件的集群范围状态同步机制。\n- [#14079] 新增插件管理控制台 UI 和 API。\n- [#14084] 支持 MCP 工具的 _meta 和 annotations 字段。\n- [#14085] 增强 MCP 工具元数据，支持 annotations。\n- [#14101] 实现集群范围的状态同步功能。\n- [#14109] 引入提示词注册中心，作为 Nacos AI 注册中心的核心组件。\n- [#14110] 引入技能注册中心，完善 Nacos AI 注册中心的愿景。\n- [#14117] 新增插件管理控制台 UI 和 API。\n- [#14120] 在 Maintainer SDK 的 Get Agent Card 方法中增加 version 参数支持。\n- [#14527] 添加 OIDC\u002FOAuth2 认证插件（服务端）。\n- [#14534] 增加从 Nacos 中查找技能的能力，实现智能技能发现。\n- [#14623] 集成 skill-scanner，用于 AI 技能的安全扫描。\n- [#14641] 使用现代设计更新 Nacos 控制台 UI。\n- [#14653] 支持通过 contextPath 自适应，在新旧控制台之间进行双 UI 切换。\n- [#14672] 技能支持数据级别访问与可见性第二阶段。\n- [#14677] 技能支持数据级别访问与可见性第三阶段。\n\n## 优化与重构\n\n- [#14048] 重构数据源插件结构，并增强 PostgreSQL 能力。\n- [#14050] 将 \u002Fv1 和 \u002Fv2 HTTP API 提取至子模块，为后续移除做准备。\n- [#14052] 移除命名模块中的 UDP PUSH 支持。\n- [#14057] 重构 CreateTool 方法，并支持 output scheme。\n- [#14074] 从命名模块中移除旧版 UDP PUSH 支持。\n- [#14122] 在启动脚本中添加 JVM --add-opens 选项，以提高对 JDK 17+ 的兼容性。\n- [#14125] 默认启用 dev profile，以满足插件依赖需求。\n- [#14441] 使用常量重构版本比较及 JSON 字段处理逻辑。\n- [#14461] 移除过时的 p3c-pmd 插件，并清理注解。\n- [#14463] 统一使用自定义包进行组件扫描。","2026-03-27T05:32:53",{"id":197,"version":198,"summary_zh":199,"released_at":200},360856,"3.1.2","Nacos 3.1.2 是一个补丁版本，重点在于稳定性提升、安全修复以及 AI 模块的增强。主要亮点包括：\n\n- **安全**：将 Spring Boot 升级至 3.4.10，以修复 CVE-2025-55752 漏洞，并更新了 log4j 和 gRPC 的依赖。\n- **AI\u002FMCP**：修复了 MCP 缓存不一致的问题，并为 Agent Card 查询增加了版本参数支持。\n- **控制台**：通过自动同步服务器成员，改善了分布式部署体验，并修复了多个上下文路径问题。\n- **客户端**：消除了配置重新加载时的类卸载内存泄漏，并修复了模糊监听中的 UUID 传递问题。\n- **配置**：增强了配置元数据发布功能，增加了审计日志和通知机制。\n\n## 功能\n\n- [#13996] 为代理和 MCP 端点操作添加事件发布\n- [#13999] 为配置元数据发布添加审计日志和通知\n- [#14120] 为 Maintainer SDK 的 Get Agent Card 方法增加版本参数支持\n\n## 增强\u002F重构\n\n- [#14000] 使用 Configuration.initialize() 消除配置重新加载时的类卸载内存泄漏\n- [#14062] 防止客户端 ServiceInfoHolder 中潜在的数据修改风险\n- [#14099] 为 SubscribeServiceRequestHandler 中的 serviceName 和 groupName 添加校验\n- [#14449] 移除 MD5Utils 中无效的 ThreadLocal\n- [#14454] 当表单参数超出大小限制时抛出正确的异常\n\n## 修复\n\n- [#13770] 修复 importToolsFromMcp 及其他 AI 相关 API 中缺失的上下文路径\n- [#14009] 修复配置模糊监听中 UUID 传递问题，该问题导致初始化事件被过滤掉\n- [#14016] 修复分布式部署中控制台的自动服务器成员同步问题\n- [#14020] 修复数据库查询中缺失的 '?' 占位符\n- [#14024] 修复在使用相同名称重新创建 MCP 服务器时出现的 MCP 缓存索引不一致问题\n- [#14028] 修复导入\u002F导出操作时远程服务器选择逻辑，确保优先使用健康节点\n- [#14063] 修复控制插件的 bug\n- [#14104] 修复控制台中 AI API 的上下文路径错误\n- [#14114] 修复 ConfigMigrateService 中 grayRule 检测错误\n- [#14121] 修复控制台 UI 在 API 错误时分页重置为 0 而非 1 的问题\n- [#14210] 修复 MainLayout，使其能够处理语言切换并在更新时获取通知\n- [#14401] 修复 ConfigRowMapperInjector 返回的 created 字段错误\n- [#14402] 修复 MySQL LIKE 查询的转义问题，防止下划线和连字符混淆\n- [#14442] 修复 Derby 和 MySQL 的 LIKE 查询，正确处理转义字符\n- [#14450] 修复维护者客户端的控制台远程服务器上下文路径问题\n- [#14635] 修复健康状态更新方法，使其正确处理持久化实例\n\n## 依赖项\n\n- [#14006] 将 Spring Boot 升级至 3.4.10，以修复 CVE-2025-55752 漏洞\n- [#14055] 将 org.apache.logging.log4j:log4j-core 从 2.24.3 升级至 2.25.3\n- [#14714] 将 gRPC 版本升级至 1.78.0\n\n## 部署要求\n\n| 模块           | 所需 Java 版本 |\n| --------------- | -------------- |\n| Nacos-Server\u002FNacos-Console | Java 17        |\n| Nacos-Client    | Java 8         |","2026-03-26T02:53:14",{"id":202,"version":203,"summary_zh":204,"released_at":205},360857,"3.2.0-BETA","# Nacos 3.2.0 发行说明\n\n本版本重点围绕插件架构增强、API 现代化、AI 注册中心扩展以及代码质量提升展开。\n\n## 🎯 主要亮点\n\n### AI 注册中心完善“AI 三驾马车”\nNacos 3.2.0 引入了 **技能注册中心** 和 **提示词注册中心**，与现有的 MCP 注册中心和 Agent 注册中心共同构成了完整的 AI 控制平面愿景：\n- **技能注册中心**：用于集中管理可复用、与业务对齐的能力，这些能力由 MCP 工具组成，并支持版本控制、标签管理和基于文件夹的组织结构。\n- **提示词注册中心**：提供一流的提示词管理功能，包括多版本支持、基于标签的订阅、模板管理和 A\u002FB 测试能力。\n- **Nacos Copilot**：集成于 Nacos 控制台的 AI 助手，可帮助用户优化或创建提示词和技能，并智能地从注册中心中查找现有技能。\n\n### 插件架构现代化\n构建了全面的插件管理体系，支持基于 SPI 的插件发现、管理控制台 UI 以及集群范围的状态同步。PostgreSQL 数据源插件也得到了显著增强，合并了 nacos-plugin 仓库中的相关实现。\n\n### API 清理\n命名模块移除了遗留的 UDP PUSH 支持，转向更为简洁的 HTTP API 架构，并将 \u002Fv1 和 \u002Fv2 API 提取至子模块，以便后续逐步废弃。\n\n### MCP 功能增强\nMCP（模型上下文协议）的支持进一步扩展，新增了工具元数据、注解字段以及输出方案的支持。\n\n### 代码质量与兼容性\n修复了多项 FindBugs\u002FSpotBugs 问题，移除了死代码，并增强了对 JDK 17 及更高版本的兼容性。\n\n---\n\n## ⚠️ 重大变更与迁移说明\n\n### API 遗留适配插件（重要）\n> **需采取行动**：在本版本中，`plugins` 目录默认包含 `api-legacy-adapter` 插件，以保持与已提取的 \u002Fv1 和 \u002Fv2 HTTP API 的兼容性。**该插件将在未来版本中被移除。**\n> \n> 如果您确认部署环境不再使用旧版 \u002Fv1 或 \u002Fv2 API，则可以立即从 `plugins` 目录中安全移除 `api-legacy-adapter` 插件，以减少系统占用。\n\n---\n\n## 功能特性\n\n[#14050] 将 \u002Fv1 和 \u002Fv2 HTTP API 提取至子模块，为后续废弃做准备。\n[#14052] 移除命名模块的 UDP PUSH 支持。\n[#14077] 实现基于 SPI 的插件发现与管理 API。\n[#14078] 实现集群范围的状态同步。\n[#14079] 新增插件管理控制台 UI 和 API。\n[#14084] 支持 MCP 工具的元数据及注解字段。\n[#14109] 将提示词注册中心引入为 Nacos AI 注册中心的核心组件。\n[#14110] 引入技能注册中心，以完善 Nacos AI 注册中心的愿景。\n[#14122] 在启动脚本中添加 JVM --add-opens 参数，以支持 JDK 17 及更高版本。\n[#14245] 集成 Nacos Copilot，提供 AI 辅助的提示词和技能管理功能。\n[#14440] 添加提示词注册中心，并支持多版本管理。\n[#14453] 支持基于标签的订阅与管理。","2026-03-09T08:30:12",{"id":207,"version":208,"summary_zh":209,"released_at":210},360858,"3.1.1","本次发布重点提升了 Nacos 的 MCP 和 A2A（代理间）能力，增强了系统稳定性，并优化了安全性和配置管理。主要新增功能包括：支持批量注册代理端点、在导入 MCP 服务器时合并版本，以及通过 `overrideExisting` 选项提升更新 MCP 服务器的灵活性。此外，还引入了针对入站和出站通信的默认安全配置支持，为安全的 AI 代理交互奠定了基础。\n\n本版本的具体变更如下：\n\n## 功能特性\n\n[#13867] 更新 MCP 服务器时支持覆盖现有配置。\n[#13922] 添加线程池配置，允许核心线程超时。\n[#13946] 重构 AgentEndpoint 模型并新增字段，以支持高级协议和查询。\n[#13953] 增加对默认安全配置的支持，包括入站和出站安全方案的选择与设置。\n[#13957] 支持批量注册代理端点。\n[#13951] 为控制台模块添加可配置的 CORS 过滤器。\n\n## 优化与重构\n\n[#13822] 将客户端执行器与登录定时执行器的职责分离，防止线程池耗尽。\n[#13863] 优化 shutdown.sh 脚本，将多个 PID 合并为一行，使进程终止更加简洁。\n[#13911] 增强 importToolsFromMcp API，支持流式协议服务器。\n[#13914] 升级 checkStyle 插件版本，以改善代码检查和可维护性。\n[#13945] 在导入 MCP 服务器规范时支持版本合并。\n[#13963] 重构 List 配置接口，支持返回 configTags 和 desc。\n\n## Bug 修复\n\n[#13140] 修复当客户端命名空间为空时，ConfigChangeNotifyRequest 对命名空间的一致性处理问题。\n[#13860] 修复 ConfigMigrateService 中潜在的空指针异常风险。\n[#13866] 修复控制台中无法编辑已导入的 MCP 服务器的问题。\n[#13869] 修复因依赖注入缺失导致创建 bean 'consoleHealthController' 失败的问题。\n[#13877] 修复 McpRemoteHandler 中 namespaceId 问题，避免上下文传播错误。\n[#13882] 修复 TpsControlManager 的同步锁问题，并添加 volatile 关键字，以确保线程安全。\n[#13884] 修复导入过程中 MCP 服务器验证 API 的 JSON 解析错误。\n[#13902] 通过更新日志初始化逻辑，修复 Log4j2 包扫描的弃用警告。\n[#13948] 修复通过控制台界面更新代理卡片时失败的问题。\n[#13959] 修复独立部署控制台和服务器时密码更新失败的问题。\n[#13964] 修复当 nacos.extension.ai.enabled 设置为 false 时，Nacos 无法启动的问题。\n\n## 依赖项\n\n[#13879] 为 AI 相关组件添加单元测试。\n[#13881] 新增用于开发和测试的工具类 API。\n\n## 部署要求\n\n| 模块            | 所需 Java 版本 |\n| ----------------- | -------------- |\n| Nacos-Server\u002FNacos-Console | Java 17        |\n| Nacos-Client      | Java 8         |\n| Nacos-Maintainer-Client | Java 8         |\n\n","2025-11-26T07:11:44",{"id":212,"version":213,"summary_zh":214,"released_at":215},360859,"2.5.2","本版本主要进行了功能增强，并修复了 2.5.1 版本中的一些问题。\n\n请参阅以下详细变更说明：\n\n# 变更详情\n\n## 功能增强与重构\n[#12102] 修复 Log4j2 包扫描已弃用的警告。\n[#13183] 添加 gRPC 客户端请求指标开关。\n[#13234] 将监听查询中的 IP 输入框设置为必填项。\n[#13297] 添加 build-helper-maven-plugin，以支持 IDEA 自动识别生成的源文件。\n\n## Bug 修复\n[#12484] 修复 ConfigController.stopBeta 方法中 srcUser 参数为空的问题。\n[#13171] 修复灰度配置的完整正则转储问题。\n[#13193] 修复 MySQL 和 Derby 插件的配置数据库健康检查 SQL。\n[#13218] 修复命名服务 v1 目录页面接口在 pageSize 较大时返回所有数据的问题。\n[#13223] 修复 IP 维度查询配置监控的权限问题。\n[#13229] 修复配置导出过程中配置标签丢失的问题。\n[#13249] 修复配置变更插件返回不兼容的问题。\n[#13273] 修复创建集群客户端时不影响 nacos.remote.client.grpc 配置的问题。\n[#13400] 修复命名服务订阅者获取 appName 为 `-` 的问题。\n[#13614] 修复默认 namespaceId 从 `` 转换为 `public` 的命名空间转换 bug。\n[#13629] 修复更新实例元数据时传入 null 值导致 NPE 的问题。\n[#13716] 修复 Oracle 数据库插件中 namespaceId 没有默认值的问题。\n[#13744] 修复 CONFIG_INFO_GRAY_WRAPPER_ROW_MAPPER 未注册到数据库插件的问题。\n\n## 依赖升级\n[#13183] 将 tomcat-embed-core 升级至 9.0.99。\n[#13454] 将 nacos-logback-adapter 升级至 1.1.4。\n\n## 新贡献者\n* @psxjoy 在 https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13204 中完成了首次贡献。\n* @linwumingshi 在 https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13222 中完成了首次贡献。\n* @chunhai1127 在 https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13235 中完成了首次贡献。\n* @zhilu-tang 在 https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13298 中完成了首次贡献。\n* @kuchikij 在 https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13716 中完成了首次贡献。\n\n**完整变更日志**: https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fcompare\u002F2.5.1...2.5.2","2025-11-17T02:15:36",{"id":217,"version":218,"summary_zh":219,"released_at":220},360860,"3.1.0-bugfix","> 在 Nacos 3.1.0 发布期间，MCP 官方团队发布了注册中心协议的新版本（2025-09-16）。Nacos 3.1.0 已迅速完成对该协议的适配。要使用此功能，请下载最新的 Nacos 3.1.0 发行包及 Docker 镜像。\n\n本版本为正式发布版本，修复了 `3.1.0-BETA` 中的一些问题。\n\n在 `3.1.0` 版本中，Nacos 遵循新的 MCP 官方注册协议。所有用户均可将 Nacos 作为 MCP 官方注册中心进行私有化部署，从而构建属于自己的 MCP 服务器专用私有市场或注册中心。\nNacos 还支持通过 MCP 服务器规范 JSON 导入 MCP 服务器，并可通过 MCP URL 自动获取工具信息。这两项新功能将极大提升用户在 Nacos 中创建 MCP 服务器的使用体验。\n此外，该版本还支持用户在控制台中启用或禁用 MCP 服务器，并结合配置加密插件对存储的 MCP 工具方案进行加密。\n\n值得一提的是，本版本新增了 A2A 注册功能，允许用户或类似 `Spring AI Alibaba` 的代理框架发布和发现 AgentCard 及代理端点。目前仅支持按代理名称进行发现，未来将逐步支持按技能、标签或描述等条件进行发现。\n\n其他变更主要包括修复此前版本中发现的大量 bug，以及对部分依赖库进行升级。\n\n> 与 `3.1.0-BETA` 相比，存在一项需要注意的变更。如果您是从 `3.1.0-BETA` 升级而来，请务必在升级前删除所有 `AgentCard`，或者在升级后删除包含 `agent` 和 `agent-version` 的所有配置分组，并重新发布 `AgentCard`。若从其他版本升级，则可忽略此步骤。\n\n3.1.0 的详细变更如下：\n\n## 功能\n\n[#12191] 增加命名空间是否存在检查。\n[#13322] 支持 A2A 注册。\n[#13423] 支持在控制台中启用或禁用 MCP 服务器。\n[#13543] 新增支持注册中心的 MCP 服务器导入功能。\n[#13783] 新增配置元数据更新的管理 API。\n[#13808] 新增对官方 MCP 注册协议的支持。\n[#13814] 支持对 MCP 工具进行提示性加密。\n\n## 优化\u002F重构\n\n[#13777] 优化命名空间存在性检查逻辑，以提升代码质量。\n[#13829] 改进发布重复代理名称时的提示信息。\n\n## Bug 修复\n\n[#13744] 修复配置数据源插件中遗漏的 CONFIG_INFO_GRAY_WRAPPER_ROW_MAPPER。\n[#13752] 修复 NPE 并忽略 InterruptedException 的堆栈日志。\n[#13761] 修复删除角色时的校验逻辑，防止误删 ROLE_ADMIN 等问题。\n[#13767] 修复 K8S getSpec() 时可能出现的服务 NullPointerException。\n[#13773] 修复构建 MCP OpenAPI 衍生 URL 时保留协议斜杠的问题。\n[#13779] 修复 MCP 工具描述编辑限制问题。\n[#13787] 修复 Nacos MCP 控制台无法正确解析 OpenAPI 文件的问题。\n[#13801] 修复 MCP 控制台解析 OpenAPI 文件 URL 时偶尔出现乱码的 bug。\n[#13810] 修复在发布配置时，Derby 和 MySQL 数据库性能不一致的 bug。\n[#13824][#13826] 修复 AI gRPC 资源分配问题。","2025-09-22T05:34:40",{"id":222,"version":223,"summary_zh":224,"released_at":225},360861,"3.1.0-BETA","此版本为 `3.1.0` 的测试版。\n\n在 `3.1.0` 版本中，Nacos 遵循新的 MCP 官方注册中心协议。所有用户都可以将 Nacos 用作 MCP 官方注册中心的私有部署，从而为 MCP 服务器构建自己的私有市场或注册中心。\nNacos 还支持通过 MCP 服务器规范 JSON 导入 MCP 服务器，并支持通过 MCP URL 自动获取工具。这两项新功能将提升用户在 Nacos 中创建 MCP 服务器的使用体验。\n此外，该版本还支持用户在控制台中启用或禁用 MCP 服务器，并通过配置加密插件对存储的 MCP 工具方案进行加密。\n\n更进一步地，在此版本中，Nacos 支持 A2A 注册中心功能，允许用户或类似 `Spring AI Alibaba` 的代理框架发布和发现 AgentCard 及代理端点。目前仅支持按代理名称进行发现，未来 Nacos 将支持按技能、标签或描述进行发现。\n\n其他变更包括修复此前版本中发现的大量 bug，并对部分依赖库进行了升级。\n\n3.1.0 的详细变更如下：\n\n## 功能\n\n[#12191] 添加命名空间是否存在检查。\n[#13322] 支持 A2A 注册中心。\n[#13423] 支持在控制台中启用或禁用 MCP 服务器。\n[#13543] 添加支持注册中心的 MCP 服务器导入功能。\n[#13783] 添加配置元数据更新的管理 API。\n[#13808] 添加对官方 MCP 注册中心协议的支持。\n[#13814] 支持对 MCP 工具进行提示性加密。\n\n## 优化\u002F重构\n\n[#13777] 优化命名空间存在检查逻辑，以提升代码质量。\n\n## Bug 修复\n\n[#13744] 修复配置数据源插件中遗漏的 CONFIG_INFO_GRAY_WRAPPER_ROW_MAPPER。\n[#13752] 修复 NPE 并忽略 InterruptedException 堆栈日志。\n[#13761] 修复删除角色时的验证逻辑，防止误删 ROLE_ADMIN 等问题。\n[#13767] 修复 K8S getSpec() 时可能出现的服务 NullPointerException。\n[#13773] 修复构建 MCP OpenAPI 衍生 URL 时保留协议斜杠的问题。\n[#13779] 修复 MCP 工具描述编辑限制问题。\n[#13787] 修复 Nacos MCP 控制台无法正确解析 OpenAPI 文件的 bug。\n[#13801] 修复 MCP 控制台解析 OpenAPI 文件 URL 时偶尔出现乱码的 bug。\n[#13810] 修复在发布配置时 Derby 和 MySQL 数据库性能不一致的 bug。\n\n## 依赖库更新\n\n[#13385] 将 os-maven-plugin 版本升级至 1.7.1。\n[#13711] 将 Spring Boot 版本升级至 3.4.9。\n[#13753] 将 gRPC 版本升级至 1.75.0。\n\n## 部署要求\n\n| 模块 | 所需 Java 版本 |\n| ------- | -------------- |\n| Nacos-Server\u002FNacos-Console | Java 17 |\n| Nacos-Client | Java 8 |\n| Nacos-Maintainer-Client | Java 8 |\n\n## 新贡献者\n* @Melod-YI 在 https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13754 中做出了首次贡献。\n* @Similarityoung 在 https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13774 中做出了首次贡献。\n* @iggzq 在 https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13782 中做出了首次贡献。\n* @WangzJi 在 https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpul 中做出了首次贡献。","2025-09-16T08:30:18",{"id":227,"version":228,"summary_zh":229,"released_at":230},360862,"3.0.3","本版本主要聚焦于MCP生态系统的扩展与性能优化，在开发者体验和系统鲁棒性之间取得平衡，并修复了旧版本中的大量缺陷。\n\n在MCP注册中心的新特性方面，Nacos新增了MCP工具的动态管理功能（创建或更新时自动获取），支持通过Swagger API文件导入HTTP传输工具，同时增强了安全Schema定义及客户端侧的AI交互API。此外，引入内存索引以优化MCP ID\u002F名称查询性能，支持自定义gRPC监听IP配置，并新增frontEndpointConfig以简化前端集成。\n\n在系统与体验改进方面，Nacos重构了MCP管理UI，优化了Docker端口配置提示，改进了服务创建流程，并强化了各项校验机制（如用户名\u002F密码检查、删除前表是否存在验证等）。同时，还增强了MCP服务器的查询逻辑与错误日志，规范了就绪状态API响应，并确保SDK在返回MCP ID时的一致性。\n\n3.0.3版本的具体变更如下：\n\n## 功能\n[#13441] 支持在创建MCP服务器时添加MCP工具。\n[#13442] 支持在创建或更新MCP服务器时自动获取MCP工具。\n[#13455] 支持为MCP服务器定义安全Schema。\n[#13524][#13683] 为AI MCP新增客户端API。\n[#13526] 支持为mcpId和mcpName构建内存索引，以提升查询性能。\n[#13527] 在McpInfo中新增frontEndpointConfig。\n[#13542] 支持通过Swagger API文件导入MCP工具，用于HTTP方式传输至MCP服务器。\n[#13549] 支持指定gRPC监听IP，以替代默认的`0.0.0.0`。\n\n## 增强与重构\n[#13324] 当用户使用旧方式访问Nacos控制台UI时，增加Web提示信息。\n[#13437] 针对v3 Admin API，增强就绪状态API的响应码。\n[#13553] AI维护者SDK在创建新MCP服务器时将返回MCP ID。\n[#13559] 增强Docker Desktop页面中Nacos端口配置的导出功能。\n[#13565] 优化MCP服务器未找到场景下的错误日志。\n[#13585] 在删除BETA配置前，先检查表config_info_beta是否存在。\n[#13602] 优化获取MCP服务器的逻辑，减少创建后可能发生的重复查询。\n[#13625] 新增用户检查，确保用户名和密码不为空。\n[#13668][#13702] 增强并重构MCP管理的控制台UI。\n[#13678] 在创建新版本MCP服务器时，同步创建对应服务。\n\n## Bug修复\n[#13367] 修复nacos-custom-environment-plugin中的NPE问题。\n[#13454] 修复Logback 1.5+在使用Spring Cloud Alibaba时会打印提示及错误信息的问题。\n[#13458] 修复当functionMode设置为config或naming时Nacos无法启动的问题。\n[#13468] 修复Nacos配置客户端无法按groupName进行模糊监听配置的问题。\n[#13497] 修复getSpec()时可能出现的Service NullPointerException问题。\n[#13522] 确保LDAP相关Bean能够正确加载到Spring容器中。\n[#13523] 修复ConnectionBusyException抛出时DefaultPushFuture未能取消的问题。\n[#13566] 修复MCP列表分页查询异常。\n[#13585] 修复无法删除的问题。","2025-08-21T06:06:27",{"id":232,"version":233,"summary_zh":234,"released_at":235},360863,"3.0.2","This version is mainly fix some bugs found in 3.0.1 and 3.0.0. And also do some simple refactor to make code reasonable and readable.\r\n\r\nDetail Changes in 3.0.2 see:\r\n\r\n## Enhancement\u002FRefactor\r\n\r\n[#13440] Enhance the mcp version hint for creating mcp server.\r\n[#13492] Refactor Nacos MCP index of mcpId and mcpName.\r\n[#13493] Refactor AbstractMapper under plugin\u002Fdatasource to make code readable and enhance performance.\r\n[#13494] Enhance the client logs to desensitise accessKey.\r\n\r\n## BugFix\r\n\r\n[#13400] Fix naming subscriber get appName is `-` problem.\r\n[#13432] Fix config controller response code bug when publish config is limited\r\n[#13438] Fix use mcp name as endpoint name instead of mcp server id.\r\n[#13445] Fix Nacos maintainer SDK not support aliyun ram auth plugin.\r\n[#13449] Fix service list console ui wrong paged logic problem.\r\n[#13460] Fix mcp managerment can't used when console ui deployment with independent.\r\n[#13474] Fix stop config beta failure problem.\r\n[#13501] Fix namespace migration task identify nacos server request no correct problem.\r\n[#13514] Fix namespace errors may occur under scenarios with frequent configuration changes during Nacos 3.0 upgrade process.\r\n\r\n## Deployment Required\r\n\r\n| Module | Java Required |\r\n| ------- | -------------- |\r\n| Nacos-Server\u002FNacos-Console| Java 17 |\r\n| Nacos-Client | Java 8 |\r\n| Nacos-Maintainer-Client | Java 8 | \r\n\r\n## New Contributors\r\n* @wuxuer made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13484\r\n* @PengningYang made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13487\r\n* @OmCheeLin made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13459\r\n* @rst-coding made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13537\r\n\r\n**Full Changelog**: https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fcompare\u002F3.0.1.1...3.0.2","2025-06-25T07:11:36",{"id":237,"version":238,"summary_zh":239,"released_at":240},360864,"3.0.1.1","This version is fixed the block issue #13430. Other version changes please see [3.0.1](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Freleases\u002Ftag\u002F3.0.1)\r\n\r\nThe following change logs is from [3.0.1](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Freleases\u002Ftag\u002F3.0.1):\r\n\r\nThis version is based on the `3.0.0` release and introduces support for MCP's multi-namespace management capabilities and multi-version management capabilities. The Nacos community has contributed to the MCP Registry API standard and is the first to implement the standard [MCP Registry API](https:\u002F\u002Fgithub.com\u002Fmodelcontextprotocol\u002Fregistry\u002Fblob\u002Fmain\u002Fapi\u002Fopenapi.yaml).\r\n\r\nWhen deploying Nacos 3.0.1, the standard MCP Registry API can be enabled by setting the parameter `nacos.ai.mcp.registry.enabled=true`, and the parameter `nacos.ai.mcp.registry.port` (default 9080) specifies the port for the MCP Registry API. Since the MCP Registry API requires additional ports and resources, it remains disabled by default in standard configurations.\r\n\r\n> Due to changes in the official MCP Registry API standard, metadata definitions for MCP Server have been updated, leading to potential incompatible data structure changes. Upgrading from version 3.0.0 to 3.0.1 may cause the console to fail reading data from previous MCP Servers. The Nacos community has provided a migration tool that relocates existing MCP Servers to the default namespace public after execution. Detailed instructions for using the migration tool [mcp-migration-tool.jar](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Freleases\u002Fdownload\u002F3.0.1\u002Fmcp-migration-tool.jar) are available in [documentation](https:\u002F\u002Fnacos.io\u002Fdocs\u002Flatest\u002Fmanual\u002Fadmin\u002Fupgrading\u002F#218-迁移mcp服务可选).\r\n> With the MCP Registry API now finalized, the data structure of MCP Server has stabilized, ensuring backward compatibility in future releases.\r\n\r\nIn addition to new features, this version optimizes initial password prompts and startup scripts for Windows systems, while also fixing several bugs present in the 3.0.0 version.\r\n\r\nDetail Changes in 3.0.1 see:\r\n\r\n## Feature\u002FRefactor\r\n\r\n[#13356] Support multiple namespace for MCP feature.\r\n[#13377] Support [mcp registry](https:\u002F\u002Fgithub.com\u002Fmodelcontextprotocol\u002Fregistry\u002Fblob\u002Fmain\u002Fapi\u002Fopenapi.yaml) api in nacos mcp module.\r\n[#13401] Support version controller for mcp server.\r\n\r\n## Enhancement\u002FRefactor\r\n\r\n[#13335] Enhance the windows startup.cmd to reduce duplicate hint for secret.token.key.\r\n[#13348] Enhance the hints for initing password.\r\n\r\n## BugFix\r\n\r\n[#13249] Fix configuration change plugin return incompatibility.\r\n[#13267] Fix cannot delete service which contains illegal character.\r\n[#13273] Fix create cluseter client don't use `nacos.remote.client.grpc` config.\r\n[#13321] Fix prometheus metrics api can't accept problem.\r\n[#13345] Fix apiClient readTimeout must be zero.\r\n[#13368] Fix cannot delete the namespace in console ui problem.\r\n[#13405] Fix listen config problem with default namespace.\r\n[#13413] Fix Hints problem for mcp stdio server.\r\n\r\n## Deployment Required\r\n\r\n| Module | Java Required |\r\n| ------- | -------------- |\r\n| Nacos-Server\u002FNacos-Console| Java 17 |\r\n| Nacos-Client | Java 8 |\r\n| Nacos-Maintainer-Client | Java 8 | \r\n\r\n## New Contributors\r\n* @zhilu-tang made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13298\r\n* @Aias00 made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13364\r\n* @2200376luhuabin made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13362\r\n* @sunheyi6 made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13360\r\n* @jujiale made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13380\r\n* @Saltysth made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13397\r\n\r\n**Full Changelog**: https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fcompare\u002F3.0.0...3.0.1","2025-05-23T10:39:34",{"id":242,"version":243,"summary_zh":244,"released_at":245},360865,"3.0.1","> Release Assets has updated to [3.0.1.1](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Freleases\u002Fedit\u002F3.0.1.1), Download from this release assets is same with 3.0.1.1 release.\r\n\r\nThis version is based on the `3.0.0` release and introduces support for MCP's multi-namespace management capabilities and multi-version management capabilities. The Nacos community has contributed to the MCP Registry API standard and is the first to implement the standard [MCP Registry API](https:\u002F\u002Fgithub.com\u002Fmodelcontextprotocol\u002Fregistry\u002Fblob\u002Fmain\u002Fapi\u002Fopenapi.yaml).\r\n\r\nWhen deploying Nacos 3.0.1, the standard MCP Registry API can be enabled by setting the parameter `nacos.ai.mcp.registry.enabled=true`, and the parameter `nacos.ai.mcp.registry.port` (default 9080) specifies the port for the MCP Registry API. Since the MCP Registry API requires additional ports and resources, it remains disabled by default in standard configurations.\r\n\r\n> Due to changes in the official MCP Registry API standard, metadata definitions for MCP Server have been updated, leading to potential incompatible data structure changes. Upgrading from version 3.0.0 to 3.0.1 may cause the console to fail reading data from previous MCP Servers. The Nacos community has provided a migration tool that relocates existing MCP Servers to the default namespace public after execution. Detailed instructions for using the migration tool [mcp-migration-tool.jar](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Freleases\u002Fdownload\u002F3.0.1\u002Fmcp-migration-tool.jar) are available in [documentation](https:\u002F\u002Fnacos.io\u002Fdocs\u002Flatest\u002Fmanual\u002Fadmin\u002Fupgrading\u002F#218-迁移mcp服务可选).\r\n> With the MCP Registry API now finalized, the data structure of MCP Server has stabilized, ensuring backward compatibility in future releases.\r\n\r\nIn addition to new features, this version optimizes initial password prompts and startup scripts for Windows systems, while also fixing several bugs present in the 3.0.0 version.\r\n\r\nDetail Changes in 3.0.1 see:\r\n\r\n## Feature\u002FRefactor\r\n\r\n[#13356] Support multiple namespace for MCP feature.\r\n[#13377] Support [mcp registry](https:\u002F\u002Fgithub.com\u002Fmodelcontextprotocol\u002Fregistry\u002Fblob\u002Fmain\u002Fapi\u002Fopenapi.yaml) api in nacos mcp module.\r\n[#13401] Support version controller for mcp server.\r\n\r\n## Enhancement\u002FRefactor\r\n\r\n[#13335] Enhance the windows startup.cmd to reduce duplicate hint for secret.token.key.\r\n[#13348] Enhance the hints for initing password.\r\n\r\n## BugFix\r\n\r\n[#13249] Fix configuration change plugin return incompatibility.\r\n[#13267] Fix cannot delete service which contains illegal character.\r\n[#13273] Fix create cluseter client don't use `nacos.remote.client.grpc` config.\r\n[#13321] Fix prometheus metrics api can't accept problem.\r\n[#13345] Fix apiClient readTimeout must be zero.\r\n[#13368] Fix cannot delete the namespace in console ui problem.\r\n[#13405] Fix listen config problem with default namespace.\r\n[#13413] Fix Hints problem for mcp stdio server.\r\n\r\n## Deployment Required\r\n\r\n| Module | Java Required |\r\n| ------- | -------------- |\r\n| Nacos-Server\u002FNacos-Console| Java 17 |\r\n| Nacos-Client | Java 8 |\r\n| Nacos-Maintainer-Client | Java 8 | \r\n\r\n## New Contributors\r\n* @zhilu-tang made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13298\r\n* @Aias00 made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13364\r\n* @2200376luhuabin made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13362\r\n* @sunheyi6 made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13360\r\n* @jujiale made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13380\r\n* @Saltysth made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13397\r\n\r\n**Full Changelog**: https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fcompare\u002F3.0.0...3.0.1","2025-05-22T08:46:21",{"id":247,"version":248,"summary_zh":249,"released_at":250},360866,"3.0.0","3.0.0 (Apr 25th, 2025)\r\n\r\nThis version is a GA version of 3.0.0. In this version, Nacos based on Nacos [3.0.0-BETA](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Freleases\u002Ftag\u002F3.0.0-BETA.2) to support MCP(Model Content Protocol) management.\r\n\r\nIn This 3.0.0 GA Version, Nacos will do these important features and changes:\r\n\r\n1. APIs are categorized into different types, and different types of APIs will adopt different default authentication strategies.\r\n2. Enabled nacos console authentication and need more configuration setting when deploying first time.\r\n3. Nacos console UI use new v3 console API replace old v1 API, and default disable old v1 API old console UI used.\r\n4. The default namespace public change its id from ``(empty string) to `public`.\r\n5. Support xDS protocol directly. currently, support EDS, LDS, RDS and CDS.\r\n6. Upgrade spring boot to 3.4.1 and upgrade jdk version to 17.\r\n7. Add a serial of ADMIN API for Nacos 3.0 to make maintainer and custom console can maintain and get Nacos' data.\r\n8. Support Nacos console independent deployment, some of configuration of nacos server and nacos console changed, please check `applciation.properties` beforce do upgrading.\r\n9. Support MCP(Model Content Protocol) management.\r\n10. Support experimental feature distributed lock.\r\n11. Support experimental feature fuzzy listen services and configurations.\r\n\r\nDetail Changes in 3.0.0 see:\r\n\r\n## Feature\u002FRefactor\r\n\r\nSync services and endpoints from k8s.\r\n- [#8309]\r\n\r\nSupport CDE, EDS, incremental EDS of xDS.\r\n- [#8313]\r\n\r\nSupport LDS and RDS of xDS.\r\n- [#10389]\r\n\r\nSupport fuzzy listen services and configuration\r\n- [#11856][#12997][#13043][#13043]\r\n\r\nCategorize Console APIs.\r\n- [#12017][#12420][#12474][#12553][#12591]\r\n\r\nBump Spring Boot to 3.4.1\r\n- [#12028][#13029]\r\n\r\nConsole UI use new Console APIs to replaced old APIs.\r\n- [#12687][#12795][#12802][#12804]\r\n\r\nEnabled Console APIs authentication by default.\r\n- [#12813][#12814][#12816][#13001][#13007]\r\n\r\nDeprecated old api and default disabled old api.\r\n- [#12830]\r\n\r\nEnabled Inner APIs authentication by default.\r\n- [#12886]\r\n\r\nUnified default namespace Id as `public`.\r\n- [#12887]\r\n\r\nDependent Console port and Server port.\r\n- [#12959][#12990][#13009][#13011]\r\n\r\nSupport distributed lock.\r\n- [#12962]\r\n\r\nCategorize new Admin APIs.\r\n- [#12953][#12968][#12983][#12984][#12988][#13044][#13049]\r\n\r\nNew Nacos maintainer sdk.\r\n- [#12979][#13064][#13081][#13086][#13087][#13089][#13095][#13100][#13101][#13118][#13112][#13154]\r\n\r\nSupport nacos console deployment independent.\r\n- [#13072][#13080][#13110][#13134][#13142][#13146][#13149]\r\n\r\nNacos default auth plugin change to new login API\r\n- [#13143][#13148][#13159]\r\n\r\nClient will judge whether server support target feature like distributed lock or fuzzy watch.\r\n- [#13155]\r\n\r\nEnhance start up script to check required configuration and can setting them.\r\n- [#13165]\r\n\r\nSupport for unifying empty namespaces and Public namespaces in the Nacos 3.0 configuration center.\r\n- [#9846][#13187][#13188][#13192][#13194]\r\n\r\nSupport MCP(Model Content Protocol) management.\r\n- [#13246]\r\n\r\n## BugFix\r\n\r\n[#12972] Fix publish configuration with wrong namespace problem in console.\r\n[#13038] Fix multiple thread initialize Spring Beans cause start up failed.\r\n[#13057] Fix client can't callback listener for beta config.\r\n[#13067] Fix prometheus auth manager problem.\r\n[#13140] Fix Config change notify namespace support.\r\n[#13156] Fix publish configuration with wrong namespace problem in console.\r\n[#13160] Fix missing default namespace check when cloning\u002Fimporting configuration.\r\n[#13177] Fix missing subscriber for MembersChangeEvent.\r\n[#13259] Fix default plugin check default namespace permission error.\r\n\r\n## New Contributors\r\n* @EmanuelGi made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F9220\r\n* @RocketEngine26 made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F9158\r\n* @PoisonGravity made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F11208\r\n* @RickonZhang0929 made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12420\r\n* @psxjoy made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13204\r\n* @linwumingshi made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13222\r\n* @chunhai1127 made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13235\r\n* @luoxiner made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13301\r\n\r\n**Full Changelog**: https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fcompare\u002F2.5.1...3.0.0","2025-04-27T09:15:06",{"id":252,"version":253,"summary_zh":254,"released_at":255},360867,"3.0.0-BETA.2","The Beta 2 release is fix the block issue [#13200] in [3.0.0-BETA](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Freleases\u002Ftag\u002F3.0.0-BETA). So this release only for server part, without client part.\r\n\r\nFor issue [#13200], It cause 3.0.0-beta can't run with derby database which effect default starting up failed for standalone mode.\r\n\r\n## BugFix\r\n\r\n- [#13200] Beta can't run with derby database. \r\n","2025-03-24T01:59:55",{"id":257,"version":258,"summary_zh":259,"released_at":260},360868,"3.0.0-BETA","This version is a pre beta version of 3.0.0. In this version, Nacos based on Nacos [3.0.0-ALPHA.2](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Freleases\u002Ftag\u002F3.0.0-alpha.2) and support independent console deployment and support upgrading from 2.X verison smoothly.\r\n\r\nThere are also some important changes in `BETA`:\r\n1. Due to support Nacos console independent deployment, some of configuration of nacos server and nacos console changed, please check `applciation.properties` beforce do upgrading.\r\n2. Many ADMIN APIs and CONSOLE APIs do some changed for the response, please using the new API document to adapt.\r\n\r\nIn Nacos 3.0.0-BETA, The main features and develops has finished, 3.0.0-GA will main fix the bugs during the BETA step. The GA version released time will depend BETA step result. Welcome community developers and users test and try out this version and report problem and suggest to Nacos.\r\n\r\n> Warning: 3.0.0-BETA is a pre version, it's features and APIs might so some adjustment in future versions, please don't used in product environments.\r\n\r\n> Suggest use [3.0.0-BETA.2](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Freleases\u002Ftag\u002F3.0.0-BETA.2) if you want to start up with derby database.\r\n\r\nDetail Changes in 3.0.0-BETA see:\r\n\r\n## Feature\u002FRefactor\r\n\r\nSync services and endpoints from k8s.\r\n- [#8309]\r\n\r\nSupport CDE, EDS, incremental EDS of xDS.\r\n- [#8313]\r\n\r\nSupport LDS and RDS of xDS.\r\n- [#10389]\r\n\r\nSupport fuzzy listen services and configuration\r\n- [#11856][#12997][#13043][#13043]\r\n\r\nCategorize Console APIs.\r\n- [#12017][#12420][#12474][#12553][#12591]\r\n\r\nBump Spring Boot to 3.4.1\r\n- [#12028][#13029]\r\n\r\nConsole UI use new Console APIs to replaced old APIs.\r\n- [#12687][#12795][#12802][#12804]\r\n\r\nEnabled Console APIs authentication by default.\r\n- [#12813][#12814][#12816][#13001][#13007]\r\n\r\nDeprecated old api and default disabled old api.\r\n- [#12830]\r\n\r\nEnabled Inner APIs authentication by default.\r\n- [#12886]\r\n\r\nUnified default namespace Id as `public`.\r\n- [#12887]\r\n\r\nDependent Console port and Server port.\r\n- [#12959][#12990][#13009][#13011]\r\n\r\nSupport distributed lock.\r\n- [#12962]\r\n\r\nCategorize new Admin APIs.\r\n- [#12953][#12968][#12983][#12984][#12988][#13044][#13049]\r\n\r\nNew Nacos maintainer sdk.\r\n- [#12979][#13064][#13081][#13086][#13087][#13089][#13095][#13100][#13101][#13118][#13112][#13154]\r\n\r\nSupport nacos console deployment independent.\r\n- [#13072][#13080][#13110][#13134][#13142][#13146][#13149]\r\n\r\nNacos default auth plugin change to new login API\r\n- [#13143][#13148][#13159]\r\n\r\nClient will judge whether server support target feature like distributed lock or fuzzy watch.\r\n- [#13155]\r\n\r\nEnhance start up script to check required configuration and can setting them.\r\n- [#13165]\r\n\r\nSupport for unifying empty namespaces and Public namespaces in the Nacos 3.0 configuration center.\r\n- [#9846][#13187][#13188][#13192][#13194]\r\n\r\n## BugFix\r\n\r\n[#12972] Fix publish configuration with wrong namespace problem in console.\r\n[#13038] Fix multiple thread initialize Spring Beans cause start up failed.\r\n[#13057] Fix client can't callback listener for beta config.\r\n[#13067] Fix prometheus auth manager problem.\r\n[#13140] Fix Config change notify namespace support.\r\n[#13156] Fix publish configuration with wrong namespace problem in console.\r\n[#13160] Fix missing default namespace check when cloning\u002Fimporting configuration.\r\n[#13177] Fix missing subscriber for MembersChangeEvent.\r\n\r\n\r\n## New Contributors\r\n* @EmanuelGi made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F9220\r\n* @RocketEngine26 made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F9158\r\n* @PoisonGravity made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F11208\r\n* @RickonZhang0929 made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12420\r\n\r\n**Full Changelog**: https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fcompare\u002F2.5.1...3.0.0-BETA","2025-03-20T05:39:15",{"id":262,"version":263,"summary_zh":264,"released_at":265},360869,"2.5.1","This version is mainly do some enhancement and fix some bugs from 2.5.0.\r\n\r\nPlease see the details of the changes below:\r\n\r\n# Change details\r\n\r\n## Enhancement&Refactor\r\n[#12823] Randomly generate TokenRefreshWindow for default nacos auth plugin in client.\r\n[#13119] Remove old config tag and beta tables, using gray table replaced.\r\n[#13122] Add TLS information to connection meta so that server can find client whether open TLS.\r\n[#13129] Optimize Client connection parameter configuration to Properties.\r\n[#13135] Support callback service listeners anyway when listeners added.\r\n[#13138] Enhance invalid parameter transfer during Nacos client get or subscribe service.\r\n\r\n## BugFix\r\n[#12991] Set the correct result status code for Distro protocol data processing exceptions.\r\n[#13027] Fix persistent service instance metadata will not be expired after instance deregister.\r\n[#13090] Fix V2 openAPI get configuration for specified namespace id.\r\n[#13093] Fix missing tansformation of default namespace id in config center.\r\n[#13106] Fix TopN config no init config value in server start.\r\n\r\n## Dependency\r\n[#13133] Remove unused common-codec.\r\n\r\n## New Contributors\r\n* @cnzakii made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13073\r\n* @luky116 made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13137\r\n\r\n**Full Changelog**: https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fcompare\u002F2.5.0...2.5.1","2025-03-11T05:52:25",{"id":267,"version":268,"summary_zh":269,"released_at":270},360870,"3.0.0-alpha.2","This version is a pre alpha version of 3.0.0. In this version, Nacos based on Nacos [3.0.0-ALPHA](https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Freleases\u002Ftag\u002F3.0.0-alpha) and support more features:\r\n\r\n1. According to Vote Issue #12923, almost all participants agreed to upgrade the JDK and Spring Boot versions. So in `ALPHA.2`, upgrade spring boot to 3.4.1 and upgrade jdk version to 17.\r\n2. Add a serial of `ADMIN API` for Nacos 3.0 to make maintainer and custom console can maintain and get Nacos' data.\r\n3. Support beta feature `distributed lock`.\r\n4. More addition beta feature fuzzy listen services and configurations.\r\n\r\nThere are also some important changes in `ALPHA.2`:\r\n1. According to Vote Issue #12922, most of participants agreed to remove the supported for Nacos 1.x clients. However, a few of users are concerned that some less frequently used multilingual SDKs are still not compatible with gRPC access. Removing the client's API would make it impossible to use these SDKs. Therefore, the community has temporarily only **blocked the 1.x and 2.x console API and admin API** (they can still be enabled with a switch). The 1.x openAPI has not been blocked, and further discussion and observation within the community are needed to decide whether to remove it in the BETA or the official 3.0.0 release.\r\n2. According to 3.0 planning, the `Admin API`, `Console API` and `Inner API` is need to authentication by default. In `ALPHA` version, the `Console API` has open default auth, so from `ALPHA.2`, the `Admin API` is authed by default, access `Admin API` should with admin user `nacos`.\r\n\r\nWelcome community developers and users test and try out this version and report problem and suggest to Nacos.\r\n\r\n> Warning: 3.0.0-ALPHA.2 is a pre version, it's features and APIs might so some adjustment in future versions, please don't used in product environments.\r\n\r\nDetail Changes in 3.0.0-ALPHA see:\r\n\r\n## Feature\u002FRefactor\r\n\r\nSync services and endpoints from k8s.\r\n- [#8309]\r\n\r\nSupport CDE, EDS, incremental EDS of xDS.\r\n- [#8313]\r\n\r\nSupport LDS and RDS of xDS.\r\n- [#10389]\r\n\r\nSupport fuzzy listen services and configuration\r\n- [#11856][#12997][#13043][#13043]\r\n\r\nCategorize Console APIs.\r\n- [#12017][#12420][#12474][#12553][#12591]\r\n\r\nBump Spring Boot to 3.4.1\r\n- [#12028][#13029]\r\n\r\nConsole UI use new Console APIs to replaced old APIs.\r\n- [#12687][#12795][#12802][#12804]\r\n\r\nEnabled Console APIs authentication by default.\r\n- [#12813][#12814][#12816][#13001][#13007]\r\n\r\nDeprecated old api and default disabled old api.\r\n- [#12830]\r\n\r\nEnabled Inner APIs authentication by default.\r\n- [#12886]\r\n\r\nUnified default namespace Id as `public`.\r\n- [#12887]\r\n\r\nDependent Console port and Server port.\r\n- [#12959][#12990][#13009][#13011]\r\n\r\nSupport distributed lock.\r\n- [#12962]\r\n\r\nCategorize new Admin APIs.\r\n- [#12953][#12968][#12983][#12984][#12988][#13044][#13049]\r\n\r\n## BugFix\r\n\r\n[#12972] Fix publish configuration with wrong namespace problem in console.\r\n[#13038] Fix multiple thread initialize Spring Beans cause start up failed.\r\n\r\n\r\n## New Contributors\r\n* @DaniellaHubble made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12885\r\n* @ifrankwang made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12904\r\n* @DirtyBit64 made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12926\r\n* @20144101037 made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12914\r\n* @llkkk made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12982\r\n* @SoilChang made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12950\r\n\r\n**Full Changelog**: https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fcompare\u002F3.0.0-alpha...3.0.0-alpha.2","2025-01-21T03:57:53",{"id":272,"version":273,"summary_zh":274,"released_at":275},360871,"2.5.0","This version mainly introduces the configuration gray history record feature and refactors and optimizes the configuration gray management to enable users to manage configuration releases and gray configurations more efficiently. It is important to note that this update may lead to certain changes in the database table structure used by Nacos, and the first startup after the upgrade may take some time for automatic data migration (this situation only applies to clusters that have used the beta gray feature in older versions).\r\n\r\nIn addition to the above features, this version also includes significant optimizations and bug fixes for several other functions, including but not limited to the following:\r\n\r\n- Unified client addressing logic and provision of custom extension interfaces.\r\n- The client will automatically refresh the token when encountering a no-permission status during requests, without waiting for the token to expire.\r\n\r\nPlease see the details of the changes below:\r\n\r\n# Change details\r\n\r\n## Feature\r\n[#12217] Support beta config history.\r\n[#12257] client auth plugin support refreshing server list.\r\n[#12719] nacos client support refresh access token when request with 403.\r\n\r\n## Enhancement&Refactor\r\n[#11659] Refactor config query to chain of responsibility.\r\n[#12189] Unified Nacos Client address module code.\r\n[#12342] Improve the retrieval of ConfigInfoState to facilitate the extension and implementation of databases like Oracle.\r\n[#12644] Enhance to return cached instances when getAllInstance with subscribe exception.\r\n[#12748] Support custom client configuration timeout.\r\n[#12756] Enhance Disk operation for DiskUtils.\r\n[#12757] Refactor update password api auth check and add unit test.\r\n[#12773] Enhance hint message when adding duplicate permissions or binding relationship.\r\n[#12371] Refactor beta and gray config model.\r\n[#12851] Cluster grpc request add server identity info.\r\n[#12872] Refactor ConfigCache and related pathways, uniformly use UTF-8 encoding for md5 fields.\r\n[#12911] Use lambda to replace some for loop and add unit tests.\r\n[#12928] Replace document url in console ui and README.\r\n[#12950] Enhance nacos client destruction log and give better messages.\r\n[#12982] Enhance to support resolving JAVA_HOME from symbolic links when `which java` is used.\r\n[#13023] Optimize the logic for Config query API.\r\n\r\n## BugFix\r\n[#11153] Fix Hints error when access console index and redirect to login page.\r\n[#11930] Fix leak namespace description for default namespace problem.\r\n[#12769] Fix clean config history error for derby datasource.\r\n[#12871] Fix duplicate defined items in console ui.\r\n[#12875] Fix config search failed when using `type` for MySQL datasource.\r\n[#12940] Fix return empty when ip or port is null for API `\u002Fservice\u002Fsubscriber\u002Flist`.\r\n[#12960] Fix config rollback page error when use advanced options.\r\n[#12970] Fix NamingMetadataManager.removeInstanceMetadata() error.\r\n[#13003] Fix don't use derby default staring with standalone mode.\r\n\r\n## Dependency\r\n[#12686] Bump Spring Security version to 5.8.15.\r\n[#12735][#12965][#13035] Bump console ui dependencies by npm audit.\r\n[#12777] Bump maven-enforcer-plugin to 3.5.0.\r\n[#12862] Bump tomcat-embed-core from 9.0.93 to 9.0.96.\r\n[#13025] Bump org.apache.tomcat.embed:tomcat-embed-core from 9.0.96 to 9.0.98.\r\n\r\n\r\n## New Contributors\r\n* @totalo made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12274\r\n* @lucky8987 made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12765\r\n* @94pengchengxin made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12866\r\n* @littlesparklet made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12874\r\n* @DaniellaHubble made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12885\r\n* @ifrankwang made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12904\r\n* @DirtyBit64 made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12926\r\n* @20144101037 made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12914\r\n* @llkkk made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12982\r\n* @SoilChang made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12950\r\n* @mawen12 made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F13022\r\n\r\n**Full Changelog**: https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fcompare\u002F2.4.3...2.5.0","2025-01-21T03:11:26",{"id":277,"version":278,"summary_zh":279,"released_at":280},360872,"2.5.0-BETA","This version mainly introduces the configuration gray history record feature and refactors and optimizes the configuration gray management to enable users to manage configuration releases and gray configurations more efficiently. It is important to note that this update may lead to certain changes in the database table structure used by Nacos, and the first startup after the upgrade may take some time for automatic data migration (this situation only applies to clusters that have used the beta gray feature in older versions).\r\n\r\nIn addition to the above features, this version also includes significant optimizations and bug fixes for several other functions, including but not limited to the following:\r\n\r\n- Unified client addressing logic and provision of custom extension interfaces.\r\n- The client will automatically refresh the token when encountering a no-permission status during requests, without waiting for the token to expire.\r\n\r\nPlease see the details of the changes below:\r\n\r\n# Change details\r\n\r\n## Feature\r\n[#12217] Support beta config history.\r\n[#12257] client auth plugin support refreshing server list.\r\n[#12719] nacos client support refresh access token when request with 403.\r\n\r\n## Enhancement&Refactor\r\n[#11659] Refactor config query to chain of responsibility.\r\n[#12189] Unified Nacos Client address module code.\r\n[#12342] Improve the retrieval of ConfigInfoState to facilitate the extension and implementation of databases like Oracle.\r\n[#12644] Enhance to return cached instances when getAllInstance with subscribe exception.\r\n[#12748] Support custom client configuration timeout.\r\n[#12756] Enhance Disk operation for DiskUtils.\r\n[#12757] Refactor update password api auth check and add unit test.\r\n[#12773] Enhance hint message when adding duplicate permissions or binding relationship.\r\n[#12371] Refactor beta and gray config model.\r\n[#12851] Cluster grpc request add server identity info.\r\n[#12872] Refactor ConfigCache and related pathways, uniformly use UTF-8 encoding for md5 fields.\r\n[#12911] Use lambda to replace some for loop and add unit tests.\r\n[#12928] Replace document url in console ui and README.\r\n\r\n## BugFix\r\n[#11153] Fix Hints error when access console index and redirect to login page.\r\n[#11930] Fix leak namespace description for default namespace problem.\r\n[#12769] Fix clean config history error for derby datasource.\r\n[#12871] Fix duplicate defined items in console ui.\r\n[#12875] Fix config search failed when using `type` for MySQL datasource.\r\n[#12960] Fix config rollback page error when use advanced options.\r\n[#12970] Fix NamingMetadataManager.removeInstanceMetadata() error.\r\n\r\n## Dependency\r\n[#12686] Bump Spring Security version to 5.8.15.\r\n[#12735][#12965] Bump console ui dependencies by npm audit.\r\n[#12777] Bump maven-enforcer-plugin to 3.5.0.\r\n[#12862] Bump tomcat-embed-core from 9.0.93 to 9.0.96.\r\n\r\n## New Contributors\r\n* @MatthewAden made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12507\r\n* @totalo made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12274\r\n* @lucky8987 made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12765\r\n* @94pengchengxin made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12866\r\n* @littlesparklet made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12874\r\n* @DaniellaHubble made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12885\r\n* @ifrankwang made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12904\r\n* @DirtyBit64 made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12926\r\n* @20144101037 made their first contribution in https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fpull\u002F12914\r\n\r\n**Full Changelog**: https:\u002F\u002Fgithub.com\u002Falibaba\u002Fnacos\u002Fcompare\u002F2.4.3...2.5.0-BETA","2024-12-19T02:42:01"]