Changelog

October 1, 2026

Register DOIs from inside the submission

DOI registration goes live for submissions: register and retry from the submission detail page, see each Crossref step and failure reason in the DOI row as it works, and watch the registered DOI appear across every submission surface once it lands. Site admins get an Eligible Submission Kinds control to decide which kinds can register DOIs and the content type each one deposits as, Site → Website, Advanced, and Domains pick up a fonts, typography, and redirects design pass, and readers on openRxiv Labs get article files and images that stream through the edge cache without a redirect hop.

Curvenote SCMS

Site admins can register DOIs for submissions directly from the submission detail page. The submission DOI row and timeline refresh on their own while Crossref works, show each step with the specific failure reason or warning when there is one, and keep refreshing through a failed status check so a transient error does not leave the row stuck. Once a DOI registers, it is shown on the submission detail page, in submission lists, on the author’s submission page, in the submission search index, and on the public API payload.

The Register DOI dialog reviews the registration details — authors, content type, publication date, agency, and versioning policy — before a site admin deposits the DOI with Crossref.

The Register DOI dialog reviews the registration details — authors, content type, publication date, agency, and versioning policy — before a site admin deposits the DOI with Crossref.

Admins get a parallel control on Site → DOI Registration — an Eligible Submission Kinds card to pick which Submission Kinds can register DOIs and the Crossref content type each one deposits as, with locked indicators that explain why a kind cannot be moved while it has live DOIs. The Register DOI confirmation dialog now separates blocking metadata problems from non-blocking warnings and shows the exact publication day a submission will be deposited under, so admins know what they must fix versus what they can proceed through.

On the Foundry-imported MyST side, the admin’s work-version timeline shows a Web Version row driven by the task converter: queued and building states while a conversion runs, a failed row with the full converter error in a hover tooltip and a Retry action, and a working View button on success.

Curvenote Sites

Site admins pick up the submission-side DOI registration experience: the submission detail page carries a DOI row with Register and Retry actions, live Crossref state while a deposit is in flight, and the registered DOI shown on the submission timeline once Crossref responds.

Alongside the DOI work, the site admin surface gets a fonts, typography, and redirects design pass. Site → Website picks up a refreshed typography and font picker, footer links, and site skeleton; Site → Advanced reworks the DOI custom-prefix form, font license, site metadata, site settings, and submission settings; and Site → Domains gets a redesigned redirects form with a redirect tester you can try before you save. Theme config now validates and explains issues section-by-section rather than as one wall of errors.

The refreshed typography picker on Site → Website sets body and heading fonts against a live site preview, with search and upload-a-font options alongside the built-in choices.

The refreshed typography picker on Site → Website sets body and heading fonts against a live site preview, with search and upload-a-font options alongside the built-in choices.

Curvenote CLI

The curvenote@0.17.5 release is a transitive dependency bump only, picking up releases of @curvenote/common and @curvenote/cli-plugin from the SCMS Version Packages roll. No new user-facing CLI behavior.