Skip to content

{

Choose a tag to compare

released this 11 Jan 05:36
· 10 commits to working since this release
96f9a4c

"RELEASE_NOTES": {
"title": "@fjell/client-api 4.4.71 — dependency updates + build config cleanup",
"body": "## Summary
This is a maintenance release focused on keeping @fjell/client-api aligned with the latest patch versions of the Fjell ecosystem packages, correcting package metadata, and simplifying the TypeScript build configuration.

What changed

Dependency updates

Updated runtime dependencies to newer patch releases:

  • @fjell/core: ^4.4.76^4.4.77
  • @fjell/http-api: ^4.4.66^4.4.67
  • @fjell/logging: ^4.4.66^4.4.67
  • @fjell/registry: ^4.4.83^4.4.84
  • @fjell/types: ^4.4.6^4.4.7
  • @fjell/validation: ^4.4.3^4.4.4

Updated dev dependency:

  • @fjell/common-config: ^1.1.36^1.1.37

package-lock.json was updated accordingly to reflect the new resolved dependency graph.

Why it matters: these patch bumps typically carry bug fixes and small compatibility improvements in the underlying Fjell packages without requiring code changes in this repository.

Build / tooling

  • Removed tsconfig.build.json.

Why it matters: the build no longer relies on a dedicated build tsconfig file in this repo. If you previously referenced tsconfig.build.json directly in custom scripts, you’ll need to switch to tsconfig.json or provide your own build-specific tsconfig.

Package metadata

  • Updated package.json repository URL:
    • https://github.com/getfjell/client-api.githttps://github.com/fjellgrunn/client-api.git

Why it matters: fixes links shown in npm/package metadata and tooling that reads repository.url.

Impact

  • Users/consumers: No intentional runtime or API behavior changes in @fjell/client-api itself; you will pick up patch updates from the @fjell/* dependency chain.
  • Developers/contributors: If your workflow depended on tsconfig.build.json, update your build scripts to stop referencing it.

Breaking changes

No breaking API changes were detected in this repo’s code changes for this range. The only potential breaking impact is for source-based build workflows that explicitly referenced the removed tsconfig.build.json."
}
}