spring-cloud-alibaba 管理记录：关闭的 issues、关闭的 PR、批准运行的 actions、合并的 PR

xuxiaowei · 2026 年4 月 18 日 15:25

关闭 issues

github.com/alibaba/spring-cloud-alibaba

只使用nacos配置中心的话 ,修改配置后eureka重新注册服务需要3次以上才能注册成功

已打开 04:40AM - 30 Mar 20 UTC

已关闭 12:44PM - 23 Apr 26 UTC

EscapeeX

stale

Closing org.springframework.context.annotation.AnnotationConfigApplicationContex…t@60116288: startup date [Thu Mar 26 11:22:11 GMT+08:00 2020]; parent: org.springframework.context.annotation.AnnotationConfigApplicationContext@7f02692f 2020-03-26 11:22:11:614 INFO [byh-video-service] 8 [d2-2d439a4ff442] s.c.a.AnnotationConfigApplicationContext [,,] : Closing org.springframework.context.annotation.AnnotationConfigApplicationContext@7f02692f: startup date [Thu Mar 26 11:21:31 GMT+08:00 2020]; root of context hierarchy 2020-03-26 11:22:11:651 INFO [byh-video-service] 8 [d2-2d439a4ff442] com.netflix.discovery.DiscoveryClient [,,] : Shutting down DiscoveryClient ... 2020-03-26 11:22:11:652 INFO [byh-video-service] 8 [d2-2d439a4ff442] o.s.c.n.eureka.InstanceInfoFactory [,,] : Setting initial instance status as: STARTING 2020-03-26 11:22:14:653 INFO [byh-video-service] 8 [d2-2d439a4ff442] com.netflix.discovery.DiscoveryClient [,,] : Unregistering ... 2020-03-26 11:22:22:665 ERROR [byh-video-service] 8 [d2-2d439a4ff442] c.n.d.s.t.d.RedirectingEurekaHttpClient [,,] : Request execution error. endpoint=DefaultEndpoint{ serviceUrl='http://discover:1111/eureka/} 前2次默认都是失败,第三次会显示注册成功

关闭 PR

github.com/alibaba/spring-cloud-alibaba

Upgrade outdated dependencies in spring-cloud-starter-stream-rocketmq, ensuring no incompatibility issues or redundant dependencies. (#4023)

2023.x ← DepUpdater:2023.x

已打开 04:45AM - 21 Jul 25 UTC

DepUpdater

+848 -10

### Describe what this PR does / why we need it This pull request upgrades all …dependencies in the `[module-name]` module, ensuring: - **No incompatibility issues**: After the upgrade, the module still compiles and runs successfully. - **No redundant dependencies**: Any new dependencies introduced by the upgrade that weren't previously required are removed. ### Does this pull request fix one issue? - **Dependency upgrades** keep the project up-to-date with the latest features and fixes. - **Redundant dependencies** are eliminated, reducing the project's complexity and maintaining a clean dependency tree. - Ensures the **module's stability** by preventing compatibility issues and unnecessary dependencies. ### Describe how you did it - Upgrades the dependencies to the latest stable versions while ensuring compatibility. - Removes unnecessary dependencies that were introduced during the upgrade process. ### Describe how to verify it - The tool was run on the `spring-cloud-starter-stream-rocketmq` module, and all dependencies were updated with no issues. - The module passed all tests in `spring-cloud-alibaba-starters/spring-cloud-starter-stream-rocketmq/src/test` after the upgrade, confirming that the changes are compatible. ### Special notes for reviews - Please review the updated dependencies and the proposed changes. - If accepted, this update will improve the project's maintainability and prepare it for future upgrades.

github.com/alibaba/spring-cloud-alibaba

Develop 2025.1.0.0-preview Support Spring Boot 4.0 (#4197)

2025.1.x ← yingqiaoli8:develop-2025.1.0.0-preview

已打开 05:39PM - 27 Dec 25 UTC

yingqiaoli8

+67 -115

### Describe what this PR does / why we need it Project Revision: 2025.1.0.0-pr…eview Spring Boot version: 4.0.0 Spring Cloud version: 2025.1.0 spring Cloud build: 5.0.0 ### Does this pull request fix one issue? ### Describe how you did it 1. update the pom.xml and make it support Spring Boot 4.0 2. update the readme file 3. update the code to support new version dependency 4. org.springframework.boot.env.EnvironmentPostProcessor change to org.springframework.boot.EnvironmentPostProcessor and avoid SpringFactoriesEnvironmentPostProcessorsFactory <img width="1823" height="909" alt="image" src="https://github.com/user-attachments/assets/09ef0e26-b6f0-498b-a7e3-fde2e152a8ce" /> <img width="945" height="657" alt="image" src="https://github.com/user-attachments/assets/64d9b7bd-0199-443a-b76c-43c61952b9e1" /> 5. RocketMQInboundChannelAdapter change the retry logic (based on **RequestHandlerRetryAdvice.**class) <img width="1803" height="900" alt="image" src="https://github.com/user-attachments/assets/f998cbbf-7b4f-4846-b6aa-577fa4b9cb95" /> <img width="1797" height="858" alt="image" src="https://github.com/user-attachments/assets/5c0d53b9-5880-404f-bd1e-a8e751b7e2ac" /> ### Describe how to verify it 1. maven package it, make sure compile successfully; 2. run the test file with every module; 3. maven install it and change your other old project to the install version. ### Special notes for reviews 1. try skip the checkstyle and test when you package your code and open them when you debug your code 2. Prepare a rollback plan before deploy the new version code

批准运行 actions

github.com/alibaba/spring-cloud-alibaba

fix: use Nacos config snapshot in ConfigData loader (#4319)

2025.1.x ← DragonFSKY:fix-nacos-configdata-snapshot

已打开 05:22PM - 03 May 26 UTC

DragonFSKY

+301 -14

### Describe what this PR does / why we need it `NacosContextRefresher` stores …the pushed Nacos config content in `NacosSnapshotConfigManager` before publishing the refresh event. However, the ConfigData reload path uses `NacosConfigDataLoader#pullConfig`, which directly calls `ConfigService#getConfig(...)`. As a result, the pushed snapshot is not consumed in this path, and refresh may still read stale config from a Nacos cluster. This PR makes `NacosConfigDataLoader` consume the pushed snapshot before falling back to `ConfigService#getConfig(...)`. ### Does this pull request fix one issue? Addresses #4296 ### Describe how you did it `NacosConfigDataLoader#pullConfig` now first calls `NacosSnapshotConfigManager#getAndRemoveConfigSnapshot(dataId, group)`. If the snapshot is `null` or empty, it keeps the previous behavior and calls `ConfigService#getConfig(...)`. ### Describe how to verify it Added `NacosConfigDataLoaderTest` covering: - snapshot exists: loader uses the snapshot and does not call remote `getConfig` - snapshot is empty: loader falls back to remote `getConfig` Test command: ```bash ./mvnw -pl spring-cloud-alibaba-starters/spring-alibaba-nacos-config -Dlicense.skip=true -Dcheckstyle.skip=true test ``` Result: ```text Tests run: 22, Failures: 0, Errors: 0, Skipped: 0 ``` ### Special notes for reviews The change is limited to the ConfigData loader path and preserves the existing fallback behavior when no valid snapshot is available.

github.com/alibaba/spring-cloud-alibaba

refactor: remove legacy bootstrap dependency from nacos-tests for 2025.1.x (#4320)

2025.1.x ← elnafateh:2025.1.x

已打开 04:19PM - 07 May 26 UTC

elnafateh

+0 -9

### Describe what this PR does / why we need it This PR removes the legacy sp…ring-cloud-starter-bootstrap dependency from the nacos-tests module. Since the 2025.1.x branch targets Spring Boot 4.0 and Spring Cloud 2025, the "bootstrap" method of configuration is officially deprecated and removed from the core architecture. Cleaning this up ensures the test suite remains compliant with the new spring.config.import standard. ### Does this pull request fix one issue? Fixes #4258 ### Describe how you did it 1. Modified spring-cloud-alibaba-tests/nacos-tests/pom.xml to remove the spring-cloud-starter-bootstrap dependency. 2. Verified that the existing test resources in this module are correctly using application.yml / application.properties with the spring.config.import syntax. 3. Cleaned up the dependency tree to prevent legacy configuration loading during the test runtime. ### Describe how to verify it Run the automated test suite for the specific module to ensure it passes without the bootstrap library: mvn clean test -pl spring-cloud-alibaba-tests/nacos-tests ### Special notes for reviews

github.com/alibaba/spring-cloud-alibaba

fix: use config snapshot in NacosConfigDataLoader to fix stale config in cluster mode (#4333)

2025.1.x ← EvanYao826:fix/nacos-config-data-loader-snapshot

已打开 01:06PM - 21 May 26 UTC

EvanYao826

+11 -1

## What does this PR do? Fixes [#4296](https://github.com/alibaba/spring-cloud-…alibaba/issues/4296): the config snapshot mechanism from PR #3644 is not effective in 2025.1.0.0. ## Root Cause In Spring Boot 3.x (2025.x), config loading goes through `NacosConfigDataLoader.pullConfig()` instead of `NacosPropertySourceBuilder.loadNacosData()`. The snapshot mechanism was only integrated into the old path. ## Changes - `NacosConfigDataLoader.pullConfig()`: Check `NacosSnapshotConfigManager` before calling `configService.getConfig()` - Added import for `NacosSnapshotConfigManager` Assisted-by: Hermes Agent

github.com/alibaba/spring-cloud-alibaba

fix: resolve config refresh failure with spring.config.import on 2025.0.x (#4335)

2025.0.x ← wushiyuanmaimob:fix/nacos-config-refresh-mismatch-4331

已打开 10:37AM - 25 May 26 UTC

wushiyuanmaimob

+198 -7

### Describe what this PR does / why we need it Fix two defects in `Nacos…PropertySourceRefreshListener` that prevented dynamic config refresh when using `spring.config.import=nacos:` on the 2025.0.x branch. **Defect 1: PropertySource name mismatch** - ConfigData path uses `group@dataId` naming (`NacosConfigDataLoader.java:146`) - RefreshListener looked for `dataId,group` (`NacosPropertySourceRefreshListener.java:103`) - Result: `target.get(sourceName)` always returned null, so refresh never happened **Defect 2: File extension hardcoded** - RefreshListener hardcoded `"properties"` as file extension (`NacosPropertySourceRefreshListener.java:108`) - Actual extension (yml/json/xml) was stored in `NacosItemConfig.suffix` but not propagated - Result: yml/json/xml configs were parsed as properties after refresh, causing errors ### Does this pull request fix one issue? Fixes #4331 ### Describe how you did it 1. Add `suffix` field to `NacosPropertySource` to preserve file extension 2. Update `NacosPropertySourceBuilder` and `NacosConfigDataLoader` to pass suffix when creating `NacosPropertySource` 3. Update `NacosPropertySourceRefreshListener` to: - Try both naming conventions (bootstrap `dataId,group` and ConfigData `group@dataId`) - Read actual file extension from `NacosPropertySource.getSuffix()` instead of hardcoding `"properties"` ### Describe how to verify it 1. Set up a Spring Boot 3.x app with `spring.config.import=nacos:test-config.yml` 2. Change the config value in Nacos 3. Verify the app's Environment reflects the new value (previously it would stay at old value) Regression tests added in `NacosPropertySourceRefreshListenerTest`. ### Special notes for reviews - The module has pre-existing checkstyle violations unrelated to this PR - Due to project dependency issues in the current branch, tests cannot run locally, but the fix logic is straightforward and covered by unit tests

合并

无