Repository navigation
0.0.24
·
52 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
Changed
- The ITI-21 RSP^K22 is checked against RSP_K21 as IHE ITI TF-2 constrains it before it leaves: QRI optional (Table 3.21-6) and QPD-3 repeating, one parameter a repetition (§3.21.4.1.2.3), through
ferrobridge-hl7v20.4.0'sIHE_ITI_21. An answer that does not conform, such as a PID with no name, is answeredAE, as the RSP^K23 is (#538). - The compose quickstart and the Helm chart's CI values run the development OpenID Provider
mock-oauth2-server6.1.5, and the release and image scans run Trivy 0.76.2 (#557). ihe-iti0.0.84 requiresferrohealth-smart0.15 (caret0.15.0) andihe-atna0.9 (caret0.9.0), andnl-generic-functions0.0.51 requiresferrohealth-smart0.15 andihe-iti0.0.84. Both nameferrohealth-smartandihe-atnatypes in their public API, so a product on those lines needs this release; no signature of either crate moves. Upgrade: moveferrohealth-smartto 0.15.0 andihe-atnato 0.9.0 beside them (#561).- Breaking for an operator: the server and the console move to
ferrohealth-smart0.15.1,ferrohealth-session0.9.0,ihe-atna0.9.1,ferrohealth-config0.4.0,ferrohealth-server0.8.0,ferrohealth-telemetry0.4.0 andferrohealth-usage-report0.4.0, so the lock holds one copy of each family crate. Every span of time and size in the sections those crates own is now a string with its unit, under a key that names none, and a bare number is refused. Upgrade: in[server]writebody_limit = "1MiB",request_timeout,header_read_timeout,idle_timeout,drain_delay,shutdown_timeout,retry_afterandcompression_min_size(each was…_ms,…_sor…_bytes) and[server.tls] reload_interval; in each[[auth.issuer]]writeclock_skew,jwks_max_age,jwks_refresh_intervalandtimeout, withintrospection.cache_max_age,[auth.basic] cache_ttland the OAuth tables'refresh_marginandtimeout; moveauth.ca_fileto[auth.tls] trust_roots_file, and the OTLP collector'strust_roots_fileandclient_identity_fileunder[telemetry.otlp.tls]. In the console write[session] sign_in_timeout,idle_timeoutandabsolute_timeout("30min", notidle_timeout_s = 1800) and[oidc] timeout, and moveoidc.ca_fileto[oidc.tls] trust_roots_file. Each old key fails the start as an unknown key, and the loader names the new one where it can. The[auth]keys of the shapes beforeferrohealth-smart0.9 now fail as unknown keys too, without naming their replacement (#561). - Breaking for an operator: FerroPIX's own sections write every span of time and size the same way, under a key that names no unit. Upgrade:
[audit] spool_max_size = "64MiB"andspool_write_timeout, with the delivery'stimeoutandretry.max_backoffunder[audit.endpoint](below);[outbox] retention = "30d";[pmir.feed] initial_backoffandmax_backoff;[hl7v2] frame_limit,idle_timeoutandframe_timeout, each consumer'sconnect_timeoutandreply_timeout, and[hl7v2.notification] initial_backoffandmax_backoff;[xcpd] delivery_initial_backoff,delivery_max_backoffanddelivery_timeout; the terminology server'stimeoutwith itsretry.initial_backoffandretry.max_backoffunder[terminology.endpoint](below); and the console's[pix] timeout. In this release each old key refuses the start and names the key that replaces it, all of them in one refusal; from the next release each fails as an unknown key (#561). - Breaking for a crate user:
ihe-iti0.1.0 requiresferrohealth-smart0.16 (caret0.16.0) andihe-atna0.10 (caret0.10.0), andnl-generic-functions0.1.0 requiresferrohealth-smart0.16 andihe-iti0.1.0. Both nameferrohealth-smartandihe-atnatypes in their public API, so the move of those public dependencies takes each crate's minor step, and a product on those lines needs this release; no signature of either crate moves. Upgrade: moveferrohealth-smartto 0.16.0 andihe-atnato 0.10.0 beside them (#571). - Breaking for an operator: the server reaches the audit repository and the terminology server through
ferrohealth-smart's outbound client, each configured by its endpoint table, so the lock holds one copy of each family crate (ferrohealth-smart0.16.2,ferrohealth-session0.10.0,ihe-atna0.10.0,ferrohealth-config0.4.1,ferrohealth-server0.8.1,ferrobridge-term0.3.0,ferrobridge-hl7v20.5.0). Upgrade: write the audit repository as[audit.endpoint]withurl,timeoutand[audit.endpoint.retry] max_backoff(wasaudit.url,audit.timeout_msandaudit.retry_max_ms); itsmax_backoffis also the wait between two delivery rounds, and the table takesconnect_timeout,retry.max_attempts,tlsandcredentials(HTTP Basic or the client credentials grant) as well. Write the terminology server as[terminology.endpoint]withurl,timeout,retry,credentialsandtls(wasterminology.base_url,timeout_ms,[terminology.retry],[terminology.credentials]and[terminology.tls]); compose and the Helm chart (0.3.16) name itFERROPIX__TERMINOLOGY__ENDPOINT__URLandconfig.terminology.endpoint.url. In this release each old key refuses the start and names its place under the endpoint table; from the next release each fails as an unknown key (#571). - A configuration the server or the console does not start on is refused with a line that opens
cannot start(exit 78), andhealthcheckwith one that opensnot up(exit 1), throughferrohealth-server's run path; the server's line openedthe configuration is refusedbefore (#571). ihe-iti0.1.0 andnl-generic-functions0.1.0 require the FerroBRIDGE crates by caret ranges,fhir-search0.1.130andfhir-types0.1.130, whereihe-iti0.0.84 requiredfhir-searchexactly, so a product whose other family crates take another compatible patch of them builds with one copy (#543) (#571).- The keys of the family sections that v0.0.24 renamed are refused by name in this release, each with the key that replaces it, all of them in one refusal, read from the file, the environment and
--setbefore the rest of the configuration. On the server:[server]request_timeout_ms,header_read_timeout_ms,idle_timeout_ms,body_limit_bytes,drain_delay_ms,shutdown_timeout_ms,retry_after_s,compression_min_bytesandtls.reload_interval_s;auth.ca_file,auth.basic.cache_ttl_seconds,auth.dpop.max_age_secondsandclock_skew_seconds; each[[auth.issuer]]entry'sclock_skew_seconds,jwks_max_age_seconds,jwks_refresh_interval_seconds,timeout_msandintrospection.cache_max_age_seconds; the OAuth tables'refresh_margin_ms,timeout_ms,ca_file,client_certificate_file,client_key_fileandprevious_key_overlap_ms; and the OTLP collector'strust_roots_fileandclient_identity_file. On the console:[session]sign_in_timeout_s,idle_timeout_sandabsolute_timeout_s,[oidc]timeout_sandca_file,[oidc.tls]client_certificate,client_keyandclient_key_file, and the OTLP collector's files. From the next release each fails as an unknown key (#575).
Removed
- The named refusal of
[xcpd] client_certificate_file,client_key_fileandreply_trust_file, which v0.0.22 retired in favour of[xcpd.tls]. Each key now fails the start as an unknown key of[xcpd](#561).
Fixed
- The server exports its spans and metrics over the TLS
[telemetry.otlp.tls]names: it installs its telemetry throughferrohealth-server's installer, which reads the collector's trust roots and client identity, where before it built the exporter without them (#571).
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.