Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When running the release.yml workflow, bump the version in README.md #50

Open
mxcl opened this issue Jun 9, 2022 · 2 comments
Open

Comments

@mxcl
Copy link
Member

mxcl commented Jun 9, 2022

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.

@jhheider
Copy link
Member

jhheider commented Jun 9, 2022

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.

@mxcl
Copy link
Member Author

mxcl commented Jun 9, 2022

Yep commit then tag

@teaxyz teaxyz deleted a comment from Adnan0017 Jul 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants