Skip to content

Changed to 7.3.1 because 7.3.0 will not be released.#188

Merged
gr5 merged 1 commit intomasterfrom
gr/pr
May 17, 2025
Merged

Changed to 7.3.1 because 7.3.0 will not be released.#188
gr5 merged 1 commit intomasterfrom
gr/pr

Conversation

@gr5
Copy link
Collaborator

@gr5 gr5 commented May 16, 2025

I had to change the version number to 7.3.1 because I can't untag and then retag the latest master (at least I don't think so). So the release will be named 7.3.1. Not certain we are releasing as is. There may be one more code change.

@gr5 gr5 requested a review from githubdoe May 16, 2025 00:25
@atsju
Copy link
Collaborator

atsju commented May 16, 2025

It's possible to change tags on remote but not recommended.

If you want to create draft releases for test purpose, you can just do tags like v1.2.3-alpha1 or whatever respects server.org
This way you don't have to change release notes. Once ready redo a tag v1.2.3 on same commit and publish actual release. There will be 2 tags on same place (plus all the alphas123/betas...) but that's something usual

@gr5 gr5 merged commit 90c4cbd into master May 17, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants