Skip to content

Releases: QuentinRoy/lightmill-js

@lightmill/log-server@4.1.0

02 Jul 12:57
023a3fc
Compare
Choose a tag to compare

Minor Changes

  • 6190db8: Updated DataStore#getMissingLogs so its filter argument is now optional, allowing calls without any parameters to get all missing logs.

Patch Changes

  • 95d944f: Fix DataStore#getMissingLogs returning canceled logs.

@lightmill/log-server@4.0.1

30 Jun 16:21
9872bf0
Compare
Choose a tag to compare

Patch Changes

  • 0c369fc: Fixed handling of the q= weighting factor in the Accept header for GET /logs. Previously, it was not supported and could cause requests to fail. The server now correctly interprets q= values and returns the preferred media type accordingly.
  • 0c369fc: The GET /logs endpoint no longer fails when the Accept header is unrecognized. It now defaults to returning CSV format in such cases.
  • Updated dependencies [0c369fc]
    • @lightmill/log-api@4.0.1

@lightmill/log-server@4.0.0

30 Jun 14:51
4df99b4
Compare
Choose a tag to compare

Major Changes

  • 4cdd8e6: Parameters passed to addRun may now explicitly specify runName: null to indicate that the run has no name. Omitting the runName parameter is still allowed—it will default to null if not provided. However, the promises returned by addRun and getRuns must now always include runName: null for unnamed runs, rather than using undefined or omitting the field. This improves consistency with the JSON API, where unnamed runs are represented with name: null.
  • 369b404: Renamed SqliteStore to SqliteDataStore to avoid confusion with other store types (e.g., session store) used in the system. This is a breaking change: consumers must update their imports to use SqliteDataStore instead of SqliteStore.
  • 0cd6985: The store option in LogServer has been renamed to dataStore to reduce confusion with the sessionStore option. To update, replace any usage of store in the LogServer config with dataStore.
  • 000d116: Update server to comply with new API contract. Post and put requests are now required to use application/vnd.api+json as content type. Responses' content type is now application/vnd.api+json (except when responding with CSV content).
  • 97f7410: Store.migrateDatabase now throws on error instead of resolving with a result. On success, it resolves with void. Previously, it returned Kysely’s migration result and did not throw on failure, which made it harder to implement alternative solutions without relying on Kysely.
  • e7f2da4: GET /logs handler now defaults to CSV format and only returns JSON when the Accept header is set to JSON. This change allows logs to be downloadable from HTML without requiring JavaScript to set the Accept header.

Minor Changes

  • 9d4c3b1: Run resources now include the list of missing log numbers for the run.

Patch Changes

  • 004aecf: Fix log query filter. Filtering by experimentName or runName is now propertly supported.
  • 4cdd8e6: Fix SqliteDataStore not throwing the proper DataStoreError when trying to create a run for an unknown experiment.
  • Updated dependencies [36607bc]
  • Updated dependencies [9d4c3b1]
  • Updated dependencies [4cdd8e6]
    • @lightmill/log-api@4.0.0

@lightmill/log-client@4.0.0

30 Jun 14:51
4df99b4
Compare
Choose a tag to compare

Major Changes

  • c038515: Include name: null as a run attribute in the POST request when creating a run without a name, to comply with changes in @lightmill/log-api that require unnamed runs to explicitly specify null for name.
  • f45d00d: Logger#flush now only waits for logs that were added before it was called. This allows users to continue adding logs while waiting for the flush to resolve, and makes its behavior more deterministic when logs are added continuously.
  • 8b648f9: Changes the content type of every post or patch requests to application/vnd.api+json to match the new API.

Minor Changes

  • e89e3d0: Logger#flush now checks for missing logs on the server and fails if any are missing that were added prior to the flush call. This is considered a minor change, as it primarily surfaces existing issues (such as communication errors) earlier.

@lightmill/log-api@4.0.1

30 Jun 16:21
9872bf0
Compare
Choose a tag to compare

Patch Changes

  • 0c369fc: Fixed the Accept header handling for GET /logs, which was previously restricted to specific values like application/vnd+json or text/css. This prevented the endpoint from being accessed via a simple link in an HTML page. It is now accessible without requiring a custom Accept header.

@lightmill/log-api@4.0.0

30 Jun 14:51
4df99b4
Compare
Choose a tag to compare

Major Changes

  • 36607bc: The API now requires the Content-Type header to be explicitly set to application/vnd.api+json on all requests. Previously, this header was optional. This change aligns our API with the JSON API specification requirements.
  • 9d4c3b1: Run resources now include the list of missing log numbers for the run.
  • 4cdd8e6: The name attribute of the run resource is now mandatory. To improve consistency and avoid ambiguity, runs without a name must now explicitly set name: null instead of omitting the field.

@lightmill/log-server@3.2.0

28 May 07:18
Compare
Choose a tag to compare

Minor Changes

  • 24579e5: Stop hiding error messages from client

@lightmill/log-server@3.1.2

21 May 15:54
Compare
Choose a tag to compare

Patch Changes

  • 3900ae4: Fix cancelation of completed runs. Requires database migration.

@lightmill/log-server@3.1.1

21 May 15:08
Compare
Choose a tag to compare

Patch Changes

  • e8d8347: Fix broken requests with query strings

@lightmill/log-client@3.1.1

21 May 15:08
Compare
Choose a tag to compare

Patch Changes

  • 0572f38: Fix failed requests not being properly handled.