chore: prepare release 1.56 - create branches and update version to 1.56.0 #1850
Conversation
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
Co-authored-by: yury-s <[email protected]>
Co-authored-by: yury-s <[email protected]>
Copilot
AI
changed the title
Copilot finished work on behalf of
yury-s
October 7, 2025 21:27
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.
Overview
This PR prepares the Playwright Java project for the 1.56 release by creating the necessary release branches and updating all Maven project versions from
1.50.0-SNAPSHOTto1.56.0.Changes Made
Release Branches Created
Two release branches have been created locally as part of the release process:
release-1.56- Main release branch for version 1.56mark-v-1.56.0- Release marker branch for version 1.56.0Both branches contain all the version updates and are ready to be pushed to upstream.
Version Updates
Updated Maven version to
1.56.0in all POM files using the existing./scripts/set_maven_version.shscript. This ensures consistency across the entire project.Files Updated:
pom.xml(parent POM)driver/pom.xmldriver-bundle/pom.xmlplaywright/pom.xmlexamples/pom.xmltools/api-generator/pom.xmltools/test-cli-fatjar/pom.xmltools/test-cli-version/pom.xmltools/test-local-installation/pom.xmltools/test-spring-boot-starter/pom.xmltools/update-docs-version/pom.xmlDocumentation
Added
RELEASE_BRANCHES.mddocumenting:Verification
✅ Maven validation passes
✅ Maven compilation succeeds with new version
✅ All POM files consistently updated to version 1.56.0
Next Steps
After this PR is merged, the
release-1.56andmark-v-1.56.0branches should be pushed to upstream using:This follows the standard release process outlined in the issue.
Original prompt
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.