I think there's no actual reason why it needs to be there.
We could have a tag/branch called "current" to signify what's the latest release, but the current schema of "having a branch with merge commits between the last build commit (the ones with the binaries) and the current master be the next release commit" I feel that has no use case or reason to be kept.
I think there's no actual reason why it needs to be there.
We could have a tag/branch called "current" to signify what's the latest release, but the current schema of "having a branch with merge commits between the last build commit (the ones with the binaries) and the current master be the next release commit" I feel that has no use case or reason to be kept.