You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the v24.2.1 tag should have been created in the wrong location, because both the master and v24.02 branches have a commit with the same description, causing the v24.2.1 branch to be created on the master by mistake. In addition, based on past habits, is it more appropriate to use v24.02 or v24.02.1 as the tag name?
A normal version number MUST take the form X.Y.Z where X, Y, and Z are non-negative integers, and MUST NOT contain leading zeroes. X is the major version, Y is the minor version, and Z is the patch version. Each element MUST increase numerically. For instance: 1.9.0 -> 1.10.0 -> 1.11.0.
What happened?
I think the v24.2.1 tag should have been created in the wrong location, because both the master and v24.02 branches have a commit with the same description, causing the v24.2.1 branch to be created on the master by mistake. In addition, based on past habits, is it more appropriate to use v24.02 or v24.02.1 as the tag name?
https://github.com/armbian/build/commits/v24.2.1/
How to reproduce?
.
Branch
other
On which host OS are you running the build script and observing this problem?
Ubuntu 22.04 Jammy
Are you building on Windows WSL2?
Relevant log URL
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: