Skip to content
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

version numbers are on project-level now #2267

Merged
merged 1 commit into from
Aug 11, 2024
Merged

version numbers are on project-level now #2267

merged 1 commit into from
Aug 11, 2024

Conversation

r10s
Copy link
Member

@r10s r10s commented Aug 10, 2024

@zeitschlag did i got that correctly? that with #2265 resp. #2266 the version number needs to be changed only once in the project settings?

no need to change them for every target any longer \o/
see #2265 and #2266
@r10s r10s requested a review from zeitschlag August 10, 2024 21:45
Copy link
Collaborator

@zeitschlag zeitschlag left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Maybe it'd make sense to add a little screenshot?

Screenshot 2024-08-11 at 10 58 17

@r10s
Copy link
Member Author

r10s commented Aug 11, 2024

i personally always use "vim" for going through RELEASE.md, so i would not push for a screenshot :)

but i would not be against it :)

@r10s r10s merged commit 976b70e into main Aug 11, 2024
1 check passed
@r10s r10s deleted the r10s/update-RELEASE-md branch August 11, 2024 19:47
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.

2 participants