Skip to content

Release 2.9.2

Choose a tag to compare

View all tags
@martinjoconnor martinjoconnor released this 24 Aug 18:19
· 326 commits to main since this release
release-2.9.2
76dd4eb

CEDAR 2.9.2 Release

We’re pleased to announce CEDAR 2.9.2.

This release strengthens CEDAR’s metadata-authoring and integration foundations. It hardens YAML artifact workflows and public API boundaries, improves permission handling, and modernizes the build and testing infrastructure across the CEDAR backend.

The wider CEDAR ecosystem also gains a new release of the CEDAR Embeddable Editor 2.0.1 and the first stable release of the CEDAR Model TypeScript Library 1.0.2.

What’s New

Enhanced YAML Workflows

Building on the first-class YAML support introduced in CEDAR 2.9.0, this release improves how YAML artifacts are accepted, completed, validated, and stored.

A sparse YAML instance can now be completed against its template before being stored as CEDAR JSON. Missing context, child order, and empty value slots are reconstructed from the template while preserving the values supplied by the author.

Additional improvements include:

  • Automatically selecting the correct reader from the submitted representation.
  • Validating an artifact in the serialization in which it was submitted.
  • Consistent YAML negotiation across artifact endpoints.
  • More reliable handling of nested child identifiers and property IRIs.
  • Preservation and repair of artifact provenance.
  • Clearer JSON response content types after YAML processing.

JSON behavior remains unchanged: JSON instances must continue to provide the complete structure required by their template.

Security and API Improvements

CEDAR 2.9.2 makes authorization and API behavior more consistent:

  • Permission denials for authenticated users consistently return 403 Forbidden.
  • Artifact inclusion and permission queries apply stronger access controls.
  • Backend CORS origins are now configurable.

Reliability and Maintenance

A broad reliability pass improves service operation and recovery:

  • External-authority searches for ORCID, ROR, DOI, PubMed, RRID, NIH grants, and PFAS now share one consistent routing and response contract.
  • An external registry outage no longer unnecessarily marks the entire bridge service unhealthy.
  • Queue processors shut down cleanly and retry failed permission events before moving them to a dead-letter queue.
  • Messaging operations better handle concurrent first messages, unresolved sender names, and mailbox state changes.
  • Group names are enforced consistently and rename conflicts return 409 Conflict.
  • Resource, submission, import, and worker operations provide more predictable failure behavior.

Build and Quality Improvements

CEDAR’s multi-repository backend build has moved from the retired Travis configuration to GitHub Actions.

The new build foundation includes:

  • Continuous verification across the complete backend on Java 17.
  • A Maven wrapper pinned to Maven 3.9.14.
  • Central management of dependency and plugin versions.
  • Automated publication of verified development snapshots.
  • Fresh snapshot resolution in downstream builds.
  • Consistent CI workflows across the CEDAR component repositories.

These changes make local, continuous-integration, and release builds more reproducible.

Important Notes for Integrators

  • CEE 2.x removes or renames several legacy configuration properties. Applications embedding CEE should review the CEE 2.0.1 configuration changes.
  • Artifact validation can no longer be disabled. The obsolete CEDAR_VALIDATION_ENABLED setting has been removed.
  • Artifact creation requests must include the required @id property with a value of null, allowing the repository to assign the identifier.
  • The unreliable conditional-update parameter has been removed from artifact and resource PUT routes.

For the complete technical change history, see the comparison between CEDAR 2.9.0 and 2.9.2.

Assets 2
Loading