Skip to content

0.28.1

Choose a tag to compare

View all tags
@RIAEvangelist RIAEvangelist released this 09 Sep 06:10
0.28.1
fbbe015

[Roshi's Codex PRIME]

0.28.1

DBOPFS creates application tables on demand instead of creating product-specific default folders during initialization.

  • Initialization opens only the application scope. Applications use the existing getTableHandle(name) API after readyPromise when their own storage requires a table.
  • Concurrent requests for the same physical table share handle creation. Logical memories and physical memory remain aliases; deleting the table clears both cached names.
  • File Manager discovers existing physical directories when no explicit directory list is supplied, including its default layout.
  • Explicit clearAllStorage() leaves the cleared scope empty rather than recreating defaults.
  • Existing data and folders remain untouched by upgrading; there is no migration or automatic unused-folder cleanup.

The direct npm resources and public module/entity namespaces introduced in 0.28.0 remain unchanged. Server listener configuration, application policy and Node mail APIs are unchanged.

Upgrade

Update the ordinary npm dependency or alias and its lockfile to arcane-os@0.28.1, then refresh the application's current managed maps/projections through the public SDK workflow. Applications own their table creation and should wait for DBOPFS readiness only at operations that consume storage; page rendering need not wait. Existing getTableHandle callers continue to create their requested tables lazily.

Selected package

Publication uses that selected tarball without rebuilding current source. Consumer adoption and runtime behavior are independently owned.

Verification evidence

Selected Check 34317374328 passed package-source validation, packing and the
installed-package capability smoke on Linux. The downloaded artifact's package
metadata identifies 0.28.1 and retains the direct module/entity exports.

A supplemental Windows run of the broad runtime-api-behavior fixture exited
before its test report when a shared readiness event reached User.js and raised
ReferenceError: dbopfs is not defined. No pass is claimed for that file; the
fixture investigation is separate from the selected package. This is not evidence
of execution in a consuming application. No production server was accessed.

Assets 3
Loading