Skip to content

Update the release process for versioning #91

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

BewareMyPower
Copy link
Contributor

Motivation

Adopt the same versioning rule with the Node.js client, see apache/pulsar-client-node#287.

Add an extra step to commit the version update directly before pushing the tag. For example, fda5086

### Motivation

Adopt the same versioning rule with the Node.js client, see
apache/pulsar-client-node#287.

Add an extra step to commit the version update directly before pushing
the tag. For example, apache@fda5086
@BewareMyPower BewareMyPower added the documentation Improvements or additions to documentation label Feb 2, 2023
@BewareMyPower BewareMyPower added this to the 3.2.0 milestone Feb 2, 2023
@BewareMyPower BewareMyPower self-assigned this Feb 2, 2023
@merlimat merlimat merged commit cbd31e7 into apache:main Feb 2, 2023
@BewareMyPower BewareMyPower deleted the bewaremypower/update-release-process branch February 2, 2023 07:02
@BewareMyPower BewareMyPower modified the milestones: 3.2.0, 3.1.0 Feb 16, 2023
BewareMyPower added a commit that referenced this pull request Feb 16, 2023
### Motivation

Adopt the same versioning rule with the Node.js client, see
apache/pulsar-client-node#287.

Add an extra step to commit the version update directly before pushing
the tag. For example, fda5086

(cherry picked from commit cbd31e7)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants