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 possible, honestly this is a little tedious to debug since you need to commit then use that commit as the release SHA. Close if too tricky since long term we will use the version in the README as the release version using tea to extract that version into the virtual environment.
The text was updated successfully, but these errors were encountered:
Hm. Obviously, we can't have a commit with its own SHA in it. README.md could definitely be updated with the semver, then that commit tagged and released. That's probably the right way. Or some kind of GHA badge, but I don't think that helps tea front matter.
If possible, honestly this is a little tedious to debug since you need to commit then use that commit as the release SHA. Close if too tricky since long term we will use the version in the README as the release version using tea to extract that version into the virtual environment.
The text was updated successfully, but these errors were encountered: