Release 4.4.36 — stable release, dependency bumps, and added runtime logging dependency

Overview

This release promotes the package from a prerelease tag to a stable semver release and updates a small set of runtime dependencies. The changes are focused and narrowly scoped: the package version changes from a prerelease identifier to 4.4.36 (changing how package managers treat it), several @fjell/* dependencies were advanced, and a runtime logging dependency was added to package.json. See the commits listed in this release for the exact changes (commits: 2e53ff4, 9262ac6, bf26306).

Breaking Changes

• None recorded in the commit messages. No API code changes are present in the logs — only package.json metadata and dependency version updates were committed (see commit 9262ac6). However, consumers should read the "Upgrade notes" below for practical implications.

What changed (by area)

Versioning and release tag

• Promoted package from prerelease to stable: package.json version was changed from the prerelease string to "4.4.36" (commit 2e53ff4). Why it matters: registries and package managers treat prerelease versions differently; making this a stable semver release means consumers and registries will consider 4.4.36 a normal release rather than a prerelease. If your workflows or CI pin to non-prerelease versions, this affects which version is selected automatically. (commit: 2e53ff4...)

Dependency updates and runtime additions

• Bumped @fjell core packages in package.json (commit 9262ac6):

  • "@fjell/core": ^4.4.74 → ^4.4.76
  • "@fjell/lib": ^4.4.84 → ^4.4.86
  • "@fjell/registry": ^4.4.82 → ^4.4.83
  • "@fjell/types": ^4.4.5 → ^4.4.6

  Why: The commit message indicates these bumps align package with newer patch/minor releases of core fjell packages and updated type/runtime contracts across the codebase. Practically, this means the package now declares compatibility with the newer minor/patch releases of those packages — consumers that rely on exact resolution may see a change when installing (commit: 9262ac6...).

• Added a runtime logging dependency: "@fjell/logging": ^4.4.66 (commit 9262ac6). Why it matters: this is a new runtime dependency introduced in package.json, so consumers installing this package will now also install the logging runtime. If your application has a locked dependency graph or relies on a different logging implementation, you should verify there are no conflicts. The commit message explicitly states this was added as a runtime dependency for logging functionality (commit: 9262ac6...).

• Ensured presence of runtime/type-support packages in dependencies (commit 9262ac6): "@types/uuid": ^11.0.0, "deepmerge": ^4.3.1, "uuid": ^13.0.0. These entries appear (or are asserted) in package.json as part of the update; the commit notes these reflect required runtime/type support surfaced in package.json.

Why these changes were grouped

• The dependency updates and the addition of a runtime logging package are related: the commit message frames them as aligning this package's declared dependencies with updated type/runtime contracts across the codebase and introducing runtime logging support. Together they change the package's dependency surface (what gets installed at runtime) and the version ranges consumers should expect. This is why the version bump to a stable release is coordinated in the same set of commits: once the package declares these runtime contracts, it is published as a non-prerelease release (commits: 9262ac6 → 2e53ff4).

Upgrade notes and practical implications

• If you pin exact dependency versions or use a lockfile (npm shrinkwrap, package-lock.json, pnpm lockfile, yarn.lock): regenerate the lockfile after upgrading to 4.4.36 to ensure the new transitive graph (including @fjell/logging, new uuid/deepmerge versions) is resolved consistently. The commits change only package.json; lockfiles will need updates in downstream projects.

• If your runtime environment or bundler has strict duplicate-dependency policies: the bumped @fjell/* versions may introduce peer/duplicate versions alongside other packages that depend on older ^4.4.x ranges. Audit your bundle/installation if you see warnings after upgrading.

• If your project had previously relied on the package being a prerelease (for example, using npm dist-tags or CI rules that only accept prerelease versions): note that 4.4.36 is a stable release and will be treated differently by semver resolution. (See commit 2e53ff4 for the exact change from the prerelease string to stable version.)

Traceability (commits referenced)

• Bump package version from prerelease to stable in package.json: commit 2e53ff4 — describes replacing "4.4.36-dev.0" with "4.4.36" and the effect on npm resolution.

• Bump fjell dependencies and add logging + runtime type deps in package.json: commit 9262ac6 — lists the dependency version updates and insertion of "@fjell/logging" plus ensuring uuid/deepmerge/@types/uuid entries.

• Dev marker commit for prerelease label (unchanged functional content): commit bf26306 — the log message is the prerelease marker string "4.4.36-dev.0".

Files changed

• package.json — version field updated and dependency list modified (see commits above).

Notes and what was not changed

• There are no source code changes in these commits (no changes to library exports, runtime code, or public APIs are present in the commit messages). The changes are limited to package.json metadata and dependency version ranges. Therefore, no migration of code usage is required beyond dependency-resolution considerations described above.

• No explicit breaking API changes are recorded in the commit messages; nonetheless, because runtime dependencies changed, consumers should validate their application's dependency graph after upgrading.

If you maintain downstream packages that consume this library, test upgrades in a controlled environment (CI or a branch) to confirm there are no dependency collisions or unexpected interactions with the newly-added @fjell/logging runtime dependency.

Acknowledgements

• All changes described above are taken directly from the repository commit messages referenced earlier. Each bullet above ties back to those commits so you can inspect the exact diffs and commit text for details.