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
A packaging fix release — no API or behavior changes, but an important upgrade if you use the Java backend from a pip-installed cldk.
Fixed: pip install cldk bundles the codeanalyzer-java JAR again
Every wheel published from 1.2.0 through 1.4.3 shipped without the bundled codeanalyzer-java JAR, so calling CLDK.java(...) after a plain pip install cldk failed at runtime with:
CodeanalyzerExecutionException: codeanalyzer jar not found
The JAR is tracked in git, but the build backend (hatchling) applied the repo's root *.jar ignore rule at build time and dropped it from the wheel and sdist. 1.4.4 force-includes the JAR, and the release pipeline now hard-fails if any build is ever missing it — so this can't silently regress again.
If you installed any of 1.2.0–1.4.3 and hit the "jar not found" error, upgrading fixes it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
cldk 1.4.4
A packaging fix release — no API or behavior changes, but an important upgrade if you use the Java backend from a
pip-installed cldk.Fixed:
pip install cldkbundles thecodeanalyzer-javaJAR againEvery wheel published from 1.2.0 through 1.4.3 shipped without the bundled
codeanalyzer-javaJAR, so callingCLDK.java(...)after a plainpip install cldkfailed at runtime with:The JAR is tracked in git, but the build backend (hatchling) applied the repo's root
*.jarignore rule at build time and dropped it from the wheel and sdist. 1.4.4 force-includes the JAR, and the release pipeline now hard-fails if any build is ever missing it — so this can't silently regress again.If you installed any of 1.2.0–1.4.3 and hit the "jar not found" error, upgrading fixes it.
Upgrade
Links
Beta Was this translation helpful? Give feedback.
All reactions