SpinFire Publish 2025.1.0 Release Notes

Overview

SpinFire Publish 2025.1.0 updates importers, consolidates installation experience, simplifies the way services are configured and ran, and fully supports migrating away from ArangoDB to an internal database. (NB: Starting with this version, ArangoDB is no longer supported as a database for Publish customers).

Assembly Version

2025.1.02839.19639

Latest supported ArangoDB version

⚠️ No longer supported

Earliest supported ArangoDB version

⚠️ No longer supported

Attention

SpinFire Publish (formerly Centro CAD Publisher) customers MUST now use a one-time app to migrate from the 3rd-party-managed database (ArangoDB) to an app-managed database (SQLite). Click here for more info.

New Features and Improvements

  • Simplify installation and upgrade procedures, now only require a single installer

  • Merge Pipeline Manager and Pipeline Host Service into a single PipelineService

  • Merge configuration folders for all apps into a single common source

  • Applications retain their ‘Log on as’ settings during an upgrade (only for upgrades beyond 2025.1.0)

  • Remember destination folder of previous install during upgrade

  • Enable Test Action in Publish mode (was previously only available in SpinFire Manage)

  • Disabled overly-verbose ‘svclog’ logging

  • Importer updates:

    NX

    Up to NX2412

    CATIA V5

    Up to V5-6R2025 (R35)

    STEP

    Added support for AP 242 Ed2 and Ed3

    IFC

    FC2 up to 2.3.0.1, IFC4 up to 4.3

    Autodesk Inventor

    Up to 2026

    Parasolid

    Up to 37.1

    Revit

    Up to 2025

    Solid Edge

    Up to 2025

    SolidWorks

    Up to 2025

Bug Fixes

  • Pipeline Host fails to start when Pipelines have schedules

  • Constraint violation error when importing pipeline

  • ‘Some jobs had errors in the last 24 hours’ button now correctly loads errored jobs with updates within the last 24 hours.

  • Users registering themselves should themselves be the Agent on the UserAdded Activity.

Note

SDK Users:

  • The CentroActionsIntegrationExample still expects an existing ArangoDB database to retrieve importer options from. We recommend customers using SpinFire Publish and the SDK to migrate to SQLite but leave their ArangoDB 3.11 instance running for the SDK portion. We are planning to remove the SDK dependency on ArangoDB in an upcoming release.
  • Note that when building the CentroActionsIntegrationExample, adding a Core.Standard.dll reference to the project is now also required alongside the previous references.
  • Visual Studio Projects using the Centro SDK must now target .NET Framework 4.8 minimum and turn on automatic binding redirects.

Supported Environments

Centro Web / File Server Environment

Minimum

Recommended

Optimum

Operating System

Windows Server 2016/2019/2022 (64-bit)

Windows 10/11 (64-bit)

Windows Server 2016/2019/2022 (64-bit)

Windows Server 2016/2019/2022 (64-bit)

CPU/Processor *

Intel i7 8 Core 4 GHz (or equivalent)

Intel i7 8 Core 4 GHz (or equivalent)

Memory

16 GB

64 GB

128 GB

Disk Space †

10 GB free

50 GB free

100 GB free

It’s recommended to have n+1 core processors where n is the number of total concurrent jobs running.

† The amount of available free space is dependent on the amount and size of files and revisions uploaded as resources to the Catalog.

Client Environment

Minimum

Recommended

Optimum

Browser

WebGL Compatible Browser

  • FireFox

  • Chrome

  • Microsoft Edge (on Chromium-Based)

Chrome

FireFox

Edge

Chrome / Edge

Memory

2 GB

4 GB

8 GB

Prerequisite Installations