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
If you haven't yet created that tag or release in GitHub yet, you get a 404 page for it.
Maybe we want to change the output for in-progress releases here. And maybe add an indicator for when it's running from a git commit that's not tagged as a version, including both additional commits and local changes.
Also, the version string in ronn --version doesn't include the ".preN" suffix for prereleases. Should probably add that; I like the version string to exactly reflect what you're running.
The text was updated successfully, but these errors were encountered:
apjanke
changed the title
GitHub URL in ronn --version is bogus for untagged releases, doesn't reflect add'l commits/changesronn --version probs: no ".pre" part, bogus GitHub URL for untagged releases, doesn't reflect add'l commits/changes
Jan 6, 2024
Here's what
ronn --version
does when you've bumped the version string in the source code.If you haven't yet created that tag or release in GitHub yet, you get a 404 page for it.
Maybe we want to change the output for in-progress releases here. And maybe add an indicator for when it's running from a git commit that's not tagged as a version, including both additional commits and local changes.
Also, the version string in
ronn --version
doesn't include the ".preN" suffix for prereleases. Should probably add that; I like the version string to exactly reflect what you're running.The text was updated successfully, but these errors were encountered: