-
Notifications
You must be signed in to change notification settings - Fork 122
[Python] Update package version during CLI release #2676
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This LGTM, but I'm not familiar with the "version" stanza.
It also loses the ability to disambiguate dev versions from the released one. Any way we could address that and retain a +dev suffix, or some other indicator that a built wheel is a development copy?
@andrewnester Can you TAL as well?
|
Databricks SDK for Python doesn't use |
## Changes Add release workflow to publish `databricks-bundles` PyPi package Should be merged after #2676 ## Why It publishes PyPi package that is co-versioned with CLI
Changes
Update the
databricks-bundlespackage version during the CLI release process.Flit normally supports reading the
version.pyfile directly, but in our setup, it doesn't work. We have a parentdatabrickspackage with a shared__init__.py. Flit expects theversion.pyto be placed directly alongside the parent package, which would set the version for any Databricks package.versionproperty in.codegen.jsonis handled through replacement. Any additional content in the file remains intact. Therefore, this method works for updating thepyproject.tomlwithout the need to inline the entire content.Why
We want to keep the CLI version in sync with the Python code.
Tests
I've tested manually by commenting out parts of tagging.py