chore(release): 0.14.0

[client-software-ci]

0.14.0 (2026-10-15)

BREAKING CHANGES

• create_job raises ModelValidationError instead of ExpressionError for a let-binding failure, some templates that decoded before are now rejected (and/or after an unresolved operand, nested lists with mismatched element types, parameter-dependent invalid timeouts), and building from source needs Rust 1.97 (feat!: Bump openjd-* Rust crates to the openjd-model 0.13.0 release #378) (d9322c9)

Features

• Bump the openjd-rs crates to the openjd-model 0.13.0 release: openjd-expr 0.12.0, openjd-model 0.13.0, openjd-sessions 0.8.1 (feat!: Bump openjd-* Rust crates to the openjd-model 0.13.0 release #378) (d9322c9)

Bug Fixes

• Type field-annotation walkers' model as Any for pydantic 2.14 (feat!: Bump openjd-* Rust crates to the openjd-model 0.13.0 release #378) (d9322c9)

[github-actions]

Nit: The 0.14.0 Features section lists the same change twice. Lines 5 and 6 both describe the Rust crate bump and link the same commit d9322c9; the only difference is the (#378) suffix. Most likely the generator picked up both the squash-merge title and the commit body. Delete line 6 and keep the entry that has the PR reference.

[github-actions]

Addressed: The duplicate Features entry was removed, and a single combined entry with the (#378) reference replaces both.

[github-actions]

Claude review · advisory

Reviewed fdccc20 (changes since d8d698c): 0 new, 1 resolved.

Open: 0 blocking · 0 should-fix · 0 nit. ✅ Nothing blocking.

_{Fix or reply to each thread; the next revision's review re-checks open threads and resolves those it agrees are handled. Resolving a thread yourself also closes it. Later revisions review only what changed.}

[leongdl]

The Windows test failures on this PR are a known flaky test, not a problem with the release. The fix is in #380, which I will merge after this release ships.

What fails. The first tests in test/openjd/expr/test_strings.py::TestReprPwshWindowsValidation time out with subprocess.TimeoutExpired ... timed out after 10 seconds. On a fresh windows-latest runner, the first powershell.exe launch can take longer than the 10-second per-call timeout. This PR changes only CHANGELOG.md.

This run, same SHA d8d698c:

Attempt	Result	Failing job	Failed tests
1	failure	windows 3.13	4, at about 10.1 s each
2	failure	windows 3.14	2
3	success

In attempt 1, windows 3.12 ran all 13 tests in the class and passed. When PowerShell starts in time, the output is correct.

History. The same timeout caused failures in 8 of the last 60 Code Quality runs (2026-09-04 to 2026-10-15), on Python 3.10, 3.12, 3.13 and 3.14. test_pwsh_string_simple_roundtrip, the first test in the class, failed every time.

Run	Branch	Matrix entry
38812686088	bump/0.14.0 (this PR)	windows 3.13
36489492414	bump/openjd-rs-0.10.0	windows 3.13
35389550086	bump/0.11.14	windows 3.13
35388482964	bump/0.11.14	windows 3.10
34878851632	deps/openjd-rs-0.7.1	windows 3.12
34659720422	deps/openjd-rs-0.7.1	windows 3.10
34534243611	bump/0.11.11	windows 3.13
33927512300	ci/dependabot-cargo-v2	windows 3.14

Run 35389550086 failed on attempt 1 and passed on attempt 2 at the same SHA, f2f0967. This run did the same thing, failing twice before passing on attempt 3.