Partially automate release - release branch creation and version updates [DI-669] #1366
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
…tes [DI-669] _Partially_ automates the steps listed in [the `C++ Client Release Process` documentation](https://hazelcast.atlassian.net/wiki/spaces/HZC/pages/129810774/C+Client+Release+Process). Specifically, steps: - `Create branch` - `Update next version` By scripting and chaining the steps, the (manual) release work is reduced and consistency is improved. Testing (in my fork): - [example execution](https://github.com/JackPGreen/hazelcast-cpp-client/actions/runs/19166496611) - [branch created](https://github.com/JackPGreen/hazelcast-cpp-client/tree/5.5.0) - [version update PR raised](#5) Post-merge actions: - [ ] update docs _Partially addresses_: [DI-669](https://hazelcast.atlassian.net/browse/DI-669)
1 task
nishaatr
requested changes
Nov 7, 2025
nishaatr
previously approved these changes
Nov 7, 2025
Contributor
nishaatr
left a comment
nishaatr
left a comment
There was a problem hiding this comment.
Good from my side
if we keep using PR its fine but still would prefer direct push
Contributor
Author
I'll raise on the standup next week. It's probably a wider issue than the C++ client. |
ldziedziul
reviewed
Nov 8, 2025
| git push origin ${{ steps.project_version.outputs.version }} | ||
|
|
||
| update-version: | ||
| name: Update version in `${{ inputs.BRANCH_NAME }}` to `${{ inputs.NEW_VERSION }}` |
There was a problem hiding this comment.
Suggested change
| name: Update version in `${{ inputs.BRANCH_NAME }}` to `${{ inputs.NEW_VERSION }}` | |
| name: Set next development version in `${{ inputs.BRANCH_NAME }}` to `${{ inputs.NEW_VERSION }}` |
Contributor
Author
There was a problem hiding this comment.
I'm not sure what the issue is with how it was?
Co-authored-by: Łukasz Dziedziul <l.dziedziul@gmail.com>
…streview-3441986352
Contributor
Author
|
Might've got carried away with find and replace... |
…streview-3452919662
Contributor
Author
ihsandemir
reviewed
Nov 13, 2025
| inputs: | ||
| SOURCE_BRANCH_NAME: | ||
| description: The source branch to create a release branch from | ||
| required: true |
Collaborator
There was a problem hiding this comment.
you can make the default to be master for convenience.
| TARGET_BRANCH_NAME: | ||
| description: The target branch to create - optional, otherwise derived from the version in the source branch | ||
| required: false | ||
| NEW_VERSION_TO_UPDATE_SOURCE_BRANCH_TO: |
Collaborator
There was a problem hiding this comment.
This will be the same as TARGET_BRANCH_NAME, right?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Partially automates the steps listed in the
C++ Client Release Processdocumentation.Specifically, steps:
Create branchUpdate next versionBy scripting and chaining the steps, the (manual) release work is reduced and consistency is improved.
Testing (in my fork):
master, it's not actually in the PR)Post-merge actions:
Partially addresses: DI-669