Skip to content

chore(release): 0.15.3 - #19

Closed
github-actions[bot] wants to merge 1 commit into
rt-cifrom
bot/release-model-0.15.3
Closed

github-actions[bot] wants to merge 1 commit into
rt-cifrom
bot/release-model-0.15.3

Conversation

@github-actions

Copy link
Copy Markdown

0.15.3 (2026-11-17)

Bug Fixes

  • correct a typo in a comment (d5979c5)

0.15.3 (2026-11-17)

Bug Fixes

  • correct a typo in a comment (d5979c5)

0.15.2 (2026-11-09)

Bug Fixes

0.15.1 (2026-11-09)

Bug Fixes

  • When a BOOL job parameter gets a value it can't accept, the error message now shows the submitted value (the integer, float or string). For unsupported types it shows the type name instead. Before, the message only listed the accepted forms, so you had to find the bad value yourself. (fix: name the rejected value in BOOL coercion errors #12)

0.15.0 (2026-11-05)

BREAKING CHANGES

0.14.0 (2026-10-15)

BREAKING CHANGES

Features

Bug Fixes

0.13.0 (2026-10-05)

Features

0.12.0 (2026-09-28)

BREAKING CHANGES

Features

Bug Fixes

0.11.14 (2026-09-18)

Bug Fixes

0.11.13 (2026-09-16)

Features

Bug Fixes

  • Bump the openjd-rs crates for their latest fixes: openjd-expr 0.8.0, openjd-model 0.8.0, openjd-sessions 0.6.0 (chore(deps): Bump openjd-* Rust crates to 0.8.0 OpenJobDescription/openjd-model-for-python#365) (1d0cc51)
  • Type-check an in/not in item against the list's element type, so 'a' in [1, 2] raises rather than returning False (openjd-rs#396)
  • Check resolved-value constraints at template validation, so an over-long interpolated job name or an undeclared parameter in a chunks defaultTaskCount is rejected at decode (openjd-rs#383)
  • Accept a single-valued allOf of one literal and one whole-field expression, and re-check the resolved count at job creation (openjd-rs#397)
  • Render a NONCONTIGUOUS chunk range as an explicit list to match the v0 reference: [1, 2, 4, 6] is 1,2,4,6 (openjd-rs#398)
  • Accept preprocess_job_parameters output as its own input for a LIST[PATH] parameter defaulting to [] (openjd-rs#384)
  • Reject an embedded filename of . or .., or one containing a null byte, at template validation (openjd-rs#359)

0.11.12 (2026-09-14)

Bug Fixes

0.11.11 (2026-09-10)

Bug Fixes

0.11.10 (2026-09-09)

Bug Fixes

0.11.9 (2026-09-04)

Bug Fixes

  • A LIST[BOOL] job parameter now holds real booleans in the created job, so a list item accepts every spelling Template Schemas §2.15 allows for a scalar BOOL: the case-insensitive strings true/yes/on/1 and false/no/off/0, and the numbers 0 and 1. A mixed list such as ["yes", 0, true] previously failed to validate with List contains incompatible types, and a uniform list such as ["yes", "no"] was accepted as a list of strings and then failed only once a boolean operator touched an element. ["yes", "no"] now interpolates as true/false. A decoded template is unchanged and still round-trips the spellings its author wrote. (fix: coerce LIST[BOOL] items per RFC 0007 §2.15 OpenJobDescription/openjd-model-for-python#352)
  • A step's template-scope let (Template Schemas §3.6) is resolved once, at job creation, using POSIX path format so a created job does not depend on the host that created it. It is no longer merged into the script's own let. The merge left the bindings to be evaluated a second time in the host's format when the session ran, and that second value overwrote the first: on Windows, startswith(path("/foo/bar"), "/foo") went from true at job creation to false in the session. This is a breaking change for a consumer that calls StepTemplate.resolve_syntax_sugar(): the step's resolved bindings now travel in create_job_with_symbol_tables(...).step_symbol_tables[step_name] and must be forwarded to the session that runs the step. A consumer that does not forward them loses step-level bindings silently rather than failing. openjd-cli forwards them as of fix: Forward the create-time step symbol table to openjd-sessions OpenJobDescription/openjd-cli#237. (fix: Evaluate step-level let bindings in template scope OpenJobDescription/openjd-model-for-python#341)

0.11.8 (2026-09-03)

Features

Bug Fixes

0.11.7 (2026-09-01)

Bug Fixes

  • Bound floatstring range element expansion by the field's char cap (e7a17b3)
  • Render floatstring range elements exactly and in plain notation (d6d5540)
  • Normalize intstring/floatstring task parameter range elements (f5da1b0)

0.11.6 (2026-08-25)

Bug Fixes

  • Allow an environment to define only onExit (5b9c661)

0.11.5 (2026-08-24)

Bug Fixes

  • bump openjd-rs crate deps to 0.4.0/0.5.2/0.5.2 (7222ce3)

0.11.4 (2026-08-19)

Features

  • return resolved symbol tables from create_job (4d3a732)
  • add SerializedSymbolTable JSON accessors (69d996d)

0.11.3 (2026-08-14)

Bug Fixes

0.11.2 (2026-08-04)

Bug Fixes

0.11.1 (2026-07-24)

Features

0.11.0 (2026-07-09)

Features

Bug Fixes

0.10.1 (2026-06-25)

There are no new changes introduced in this release, it is identical to 0.10.0. This release was made to publish all release artifacts on PyPI and the GitHub releases page that were missed in the 0.10.0 release due to a new build and release process.

0.10.0 (2026-06-23)

Features

  • An experimental rust-based implementation of the OpenJD model and expression language are now available as opt-in features, delivering significant performance improvements for template parsing, expression evaluation, and job creation. Consumers can opt into the Rust implementation by importing from openjd.model._v1 or openjd.expr directly, with the _v1 prefix indicating these APIs are experimental and may evolve. (3d853e5)
    • openjd.expr — New expression language, with evaluate_expression, parse_expression, path mapping (PathFormat, PathMappingRule), range expressions, symbol tables, and typed error hierarchy.
    • openjd.model._v1 — Rust-backed template decoding (decode_job_template), job creation (create_job), capability validation, and all template/job types.

Bug Fixes

  • make userInterface control field optional for all parameter types (#278) (5e10e2c)
  • require attribute and amount names to be unique (#265) (c5ba60e)
  • reject control characters in job names (#263) (0d428c4)

0.9.1 (2026-02-20)

Bug Fixes

0.9.0 (2026-02-02)

BREAKING CHANGES

  • The types of some model class fields are extended from Optional[int] to Optional[int | FormatString], so downstream code
    that relies on those types can fail type checking.

Features

  • Implement FEATURE_BUNDLE_1 RFC 0004, increasing limits
    for job parameter counts and name lengths, enabling format strings in integer properties, providing control over embedded file line endings, and adding syntax sugar
    to simplify templates that run simple scripts with common interpreters (86f79ee)

0.8.7 (2025-12-29)

Bug Fixes

0.8.6 (2025-12-15)

Bug Fixes

  • handle None value for environment field in EnvironmentTemplate (41b2494)

0.8.5 (2025-10-27)

Bug Fixes

  • Running in Python 3.14 produces a pydantic.v1 warning message. (3e9086e)

0.8.4 (2025-09-12)

Bug Fixes

0.8.3 (2025-08-18)

Features

0.8.2 (2025-07-08)

Bug Fixes

  • Adding a TypeAdapter cache to fix a performance regression with larger templates. (b62a4f1)

0.8.1 (2025-06-30)

Features

Bug Fixes

0.8.0 (2025-05-22)

BREAKING CHANGES

  • Creation of a DynamicConstrainedStr or FormatString now requires a model parsing context, including the Open Job Description revision and any extensions that are enabled. (2a8db9d)
  • instantiate_model no longer accepts optional loc and within_field arguments. (2a8db9d)

Features

  • Added extension definition, REDACTED_ENV_VARS, for RFC-0003: Redacted Environment Variables (460656a)

0.7.0 (2025-03-03)

BREAKING CHANGES

  • The IntRangeExpr class now normalizes the steps of individual range components like "3-1:-2" to be positive like "1-3:2".

Features

  • Implement 'in' operator and chunksize overide for StepParameterSpaceIterator (b33c6cf)

0.6.0 (2025-02-25)

BREAKING CHANGES

  • This release includes a few small changes to the public contract of IntRangeExpr and the StepParameterSpaceIterator. Review the changes to see if this affects your usage (9253018).
  • Model classes migrated from Pydantic V1 to Pydantic V2, which is not backwards compatible. If you depend on Pydantic V1 APIs, consult this guide to migrate usage to Pydantic V2.(0753a1b).

Features

  • Implement step parameter space iteration for chunks (9253018)
  • Implement the task chunking RFC 0001 (c51683e)
  • Implement the extensions RFC 0002 (cd0e289)

0.5.1 (2024-11-08)

0.5.0 (2024-11-05)

BREAKING CHANGES

Bug Fixes

0.4.4 (2024-06-24)

Features

0.4.3 (2024-06-11)

Bug Fixes

0.4.2 (2024-03-27)

Features

0.4.1 (2024-02-26)

Bug Fixes

0.4.0 (2024-02-13)

BREAKING CHANGES

0.3.1 (2024-02-12)

Bug Fixes

0.3.0 (2024-02-08)

BREAKING CHANGES

Features

Bug Fixes

0.2.0 (2024-01-18)

BREAKING CHANGES

Features

Bug Fixes

0.1.2 (2023-10-27)

0.1.1 (2023-09-15)

BREAKING CHANGES

  • remove ValidationError and FormatString.validate (a145a1b)

Features

Bug Fixes

  • make typed union disciminators function correctly (55982f3)

0.1.0 (2023-09-12)

BREAKING CHANGES

Release notes check

This PR keeps the generated notes because the release-notes generator wrote no release notes. Edit CHANGELOG.md on this branch by hand if they need work.

  • generator: generate_release_notes.py wrote no release notes

Release PR opened by the release train for a fork rehearsal of the openjd-model release flow (release-train rehearsal, not an official release). Changes since 0.15.2. Once merged, the train tags the merge commit on this fork, creates a prerelease GitHub Release here and publishes the build to a private package repository; nothing goes to PyPI. Merge with Squash and merge and keep the title: the squash commit's subject is this PR's title, and semantic-release computes the next version from it.

Signed-off-by: Sean Tang <171081544+seant-aws@users.noreply.github.com>
@seant-aws

Copy link
Copy Markdown
Owner

Closing: duplicate of the merged 0.15.3 release.

@seant-aws seant-aws closed this Nov 17, 2026
@seant-aws
seant-aws deleted the bot/release-model-0.15.3 branch November 17, 2026 21:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant