fix(ci): preserve next README prose in release policy - #241
Merged
Conversation
ankitTelnyx
marked this pull request as ready for review
September 13, 2026 17:22
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
nextREADME prose during both synthetic Release Please scanning and final release-tree replacement. Copy only the recognized Maven badge link, Gradle dependency, and Maven dependency versions.copy_gradle_version.pywith explicit--readmemode; existing Gradle callers remain unchanged. Missing, duplicate, malformed, inconsistent or unmarked version slots fail before target writes.Verification
python3 -m unittest discover -s .github/scripts -v— 76 tests passed.ruff format --checkon both Python files;git diff --check.actionlintpasses with only the existingSC2034unusedattemptwarning ignored; the identical warning was reproduced against unmodified master.origin/nextREADME overlay retained MCP and exact non-version parity.Ownership / durability / rollout
This is production-owned release policy, so the base is master, not staging. No new repository paths. Inspected live
team-telnyx/telnyx-java-staging/.github/workflows/promote-to-prod.yml: all three changed paths already restore from production master in both independent release-policy synchronization and full promotion. The existing release policy CI already invokestest_copy_gradle_version.py.After explicit approval/merge, run existing staging release-policy synchronization to carry this fix to production next and regenerate the open release PR, then verify its exact-head README and CI. This PR does not patch the generated release branch, merge anything, or publish a release.
Local durable plan:
clawd/.hermes/plans/java-readme-policy-v1.md(v1). Independent plan/diff review remains pending parent/human review; draft intentionally retained. Hosted CI is pending at creation.