Skip to content

Bump to 2.3.1#528

Merged
forsyth2 merged 1 commit intomainfrom
v2.3.1
Nov 8, 2023
Merged

Bump to 2.3.1#528
forsyth2 merged 1 commit intomainfrom
v2.3.1

Conversation

@forsyth2
Copy link
Collaborator

@forsyth2 forsyth2 commented Nov 8, 2023

Bump to 2.3.1

@forsyth2 forsyth2 added the Update version Code specifically to update the version label Nov 8, 2023
@forsyth2 forsyth2 self-assigned this Nov 8, 2023
@forsyth2 forsyth2 merged commit bc8c334 into main Nov 8, 2023
@forsyth2 forsyth2 deleted the v2.3.1 branch November 8, 2023 16:39
@forsyth2
Copy link
Collaborator Author

@xylar @tomvothecoder I just noticed I mistakenly bumped the version here to 2.3.1 rather than 2.3.1rc1. Is that going to cause a problem for the actual release?

@xylar
Copy link
Contributor

xylar commented Nov 13, 2023

@forsyth2, no worries. It doesn't really matter what the version number is within the code for a release candidate. What matters is that the version number is correct when you tag the release version.

@forsyth2
Copy link
Collaborator Author

Ok awesome, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Update version Code specifically to update the version

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants