Skip to content

0.0.29

Choose a tag to compare

@github-actions github-actions released this 12 Nov 02:46
· 17 commits to main since this release
Immutable release. Only release title and notes can be modified.
v0.0.29
d87b7ab

Changed

  • FerroPIX moves to ferrohealth-smart 0.19, ferrohealth-session 0.14,
    ihe-atna 0.13, ferrobridge-term 0.6 and ferrobridge-hl7v2 0.9. The
    issuer [[auth.attributes]], [[auth.federation]], [[auth.party]] and
    auth.scopeless_subjects name is a SecretUrl now, so a password in its
    userinfo appears in no config check output, no written-back
    configuration and no Debug rendering (#636).
  • Breaking for crate users: ihe-iti 0.5.0 requires ferrohealth-smart
    0.19 and ihe-atna 0.13, and nl-generic-functions 0.5.0 requires
    ferrohealth-smart 0.19 and ihe-iti 0.5. Their public API carries the
    types of those crates (the outbound client, the endpoint table and the
    audit user), so a consumer moves to the same lines (#636).

Fixed

  • The Helm chart moves to 0.3.21 for FerroPIX 0.0.28. The v0.0.28 release
    raised the chart's appVersion without raising the chart version, so its
    chart leg refused to publish over 0.3.20. A pull request that changes the
    packaged chart now has to raise its version (#632).
  • A private_key_jwt client assertion the server signs, for an OAuth 2.0
    client of an outbound lane or of [auth.issuer.introspection], is valid
    for 60 seconds, down from 300, so an authorization server that caps the
    assertion lifetime below SMART App Launch 2.2.0's five-minute ceiling
    accepts it. FerroPIX moves to ferrohealth-smart 0.19.1,
    ferrohealth-secret 0.2.1, ferrohealth-config 0.4.4,
    ferrohealth-telemetry 0.4.1, ferrohealth-server 0.8.4 and
    ferrohealth-usage-report 0.4.1; ihe-iti and nl-generic-functions
    move to 0.5.1 and take the same lines (#640).

Support period

Only the newest release is supported: there are no maintenance branches, no long-term-support line and no backports, and upgrading is free. Under the Cyber Resilience Act, Cadasto B.V. commits to keep publishing security fixes for at least five years after each release (Art 13(8)) and ships them only in the newest release (Art 13(10)). For this release that commitment runs until the end of November 2031 (Regulation (EU) 2024/2847 Art 13(19)); see SECURITY.md.