Closed Philmod closed 8 months ago
We could add more automation by doing the hatch version $_NEW_VERSION
in the build, but that means giving the build access to write to GitHub main branch, but a human would still have to deal with the CHANGELOG so not sure if it's worth it.
We could add more automation by doing the
hatch version $_NEW_VERSION
in the build, but that means giving the build access to write to GitHub main branch, but a human would still have to deal with the CHANGELOG so not sure if it's worth it.
Agree. Given that we manually update the CHANGELOG for now, let's keep it the way you have implemented it.
Use a GCB build to release a new version of kagglehub both on pypi and in this repo as a GitHub release.
I ran it for
0.1.5
:http://b/314006079