Repository navigation
0.0.26
·
40 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
Changed
- Breaking for a crate user:
ihe-iti0.3.0 andnl-generic-functions0.3.0 requireferrohealth-smart0.17, whoseOutboundClientand endpoint tables their clients are built from, andihe-itirequiresihe-atna0.11. In smart 0.17 every token and introspection endpoint a configuration table names is aSecretUrl, so a password in its userinfo reaches no rendering of the running configuration. Upgrade: takeferrohealth-smart0.17 andihe-atna0.11, and buildOauthSection::token_endpointwithSecretUrl::newand read it with.expose(). The server and the console move toferrohealth-smart0.17.0,ferrohealth-session0.11.0,ferrohealth-config0.4.3,ferrohealth-server0.8.2,ihe-atna0.11.0,ferrobridge-term0.4.0 andferrobridge-hl7v20.6.0, with no configuration key changed (#591).
Fixed
- The Helm chart 0.3.18, published ahead of this release, and this release's chart 0.3.19 fix the defaults. Chart 0.3.17 could not start FerroPIX 0.0.25 at its defaults: its values set
config.auth.audience, which the server stopped reading when the audience moved into each[[auth.issuer]]entry, so every install, standalone or as a dependency, stopped at start with "unknown fieldaudience". The values carry no audience now, the values schema refusesconfig.auth.audienceby name and points atconfig.auth.issuer[].audience(in the charts of this release, 0.3.18 and 0.3.19, only; the chart of the next release refuses it as any other value the server does not read), and the chart refuses to render without aconfig.auth.issuerentry, each with itsissuer,kindandaudience. Upgrade: move the audience into each issuer entry and give each itskind. CI and the release's chart leg now render the chart over every value set underdeploy/helm/ci, the defaults among them, and run the server's and the console'sconfig checkover the configuration it renders, so a chart whose values its images refuse is never published (#585).
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.