changelog-app[bot]
commented
2 weeks ago Generate changelog in changelog-dir>`changelog/@unreleased`</changelog-dir
What do the change types mean?
- `feature`: A new feature of the service. - `improvement`: An incremental improvement in the functionality or operation of the service. - `fix`: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way. - `break`: Has the potential to break consumers of this service's API, inclusive of both Palantir services and external consumers of the service's API (e.g. customer-written software or integrations). - `deprecation`: Advertises the intention to remove service functionality without any change to the operation of the service itself. - `manualTask`: Requires the possibility of manual intervention (running a script, eyeballing configuration, performing database surgery, ...) at the time of upgrade for it to succeed. - `migration`: A fully automatic upgrade migration task with no engineer input required. _Note: only one type should be chosen._How are new versions calculated?
- ❗The `break` and `manual task` changelog types will result in a major release! - 🐛 The `fix` changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease. - ✨ All others will result in a minor version release.Type
Description
johnhany97
autorelease3[bot]
Before this PR
After this PR
conda feedstock tries to run git to get the version during conda build because I removed the logic that checks if _version.py already exists, which is does in that case, and we don't want this logic run at that point.
Also, some users of this lib have stored pickles of the old version of
TransportAdapterand then when unpickling against this new version the_enable_keep_alivefield is missing so changing state such that we can handle said case even though it's an odd workflow. ==COMMIT_MSG== ==COMMIT_MSG==Possible downsides?