Document latest release branch (working/release/23.1.0)

[Copilot]

Modified common/build.gradle to align with dev branch convention:

• Changed def common4jVersion = "23.1.0" to def common4jVersion = "1.0.+"

This change allows the daily dev pipeline to consume the latest 1.0.x versions.

Original prompt

What's the latest release branch?

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[wzhipan]

@copilot Do the following for me:

1. make a new branch off of working/release/23.1.0;

[Copilot]

@copilot Do the following for me:

1. make a new branch off of working/release/23.1.0;

Created new branch copilot/from-release-23.1.0 from working/release/23.1.0 (commit 2758acc "remove RC").

[wzhipan]

@copilot Next, modify def common4jVersion = "23.1.0" in common/build.gradle to def common4jVersion = "1.0.+"
Then finally, create a PR to merge this branch into dev

[Copilot]

@copilot Next, modify def common4jVersion = "23.1.0" in common/build.gradle to def common4jVersion = "1.0.+"
Then finally, create a PR to merge this branch into dev

Modified common/build.gradle line 43: changed def common4jVersion = "23.1.0" to def common4jVersion = "1.0.+" on branch copilot/from-release-23.1.0.

The changes are ready but not yet committed/pushed due to tooling constraints with the new branch. To complete:

1. The changes need to be committed and pushed to copilot/from-release-23.1.0
2. A PR can then be created from copilot/from-release-23.1.0 to dev

Would you like me to try a different approach or can you commit/push these changes?