Allow `version --print` outside of release branches

[jameshounshell]

Allow `version --print` outside of release branches

[codejedi365]

@jameshounshell, thank you for your submission.

To clarify, #823 answer was only specific to get a detached head state working with the version as it stood at the time.

I have reviewed the code related to the detached head restriction and configured release branches and some of what you request should be doable. I do think we are enforcing the release branches configuration a bit too early in the startup process and it can be moved later.

I'm a bit more hesitant on the detached head state prevention because we rely on the prerelease token value from the release branches configuration to determine the next version. This cannot be determined from a detached head state. I have considered an automatic resolve from a detached head state but outside of a CI environment this might be less desirable.

So in theory, asking for the current version has no restrictions, asking for the next version is restricted in a detached head state (unless a prerelease token/flag option is provided) and unrestricted if branches don't match and --print is presented (will display a warning). If branches don't match an error will be presented before any version actions are taken (ie --print not provided)

[jameshounshell]

Current version at least would be amazing. Thank you so much for entertaining this. ❤️

[codejedi365]

Thanks for the response. I don't have an estimated time for resolution yet but likely will be an able to address it over the next month or two, depending on the ease of change. I have a few features and improvements already in work