fix: Propagate repo level dependency change sdk-platform-java-config to each module's release notes #11294
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
google-cloud-shared-config
andgoogle-cloud-shared-dependencies
are consolidated intosdk-platform-java-config
. The only repo level dependency change in google-cloud-java issdk-platform-java-config
now.This PR removes the outdated logic in release notes splitting that still looks for
google-cloud-shared-config
andgoogle-cloud-shared-dependencies
, add the logic to propagatesdk-platform-java-config
change to each module's release notes.This PR is dependent on the behavior that
sdk-platform-java-config
update is in the main release notes at least, which is not happening at this moment because it is a chore. There will be a follow up PR to update thesdk-platform-java-config
dependency update to afix
.