Release 4.4.85 — package metadata stable release and @fjell/core patch bump

Overview

This release contains two small, related package.json changes: the package version was promoted from a prerelease identifier to a stable 4.4.85 and the @fjell/core dependency was advanced from ^4.4.74 to ^4.4.75. Both commits are metadata-only (package.json) and do not change source code files. See the commits referenced below for the exact edits.

Why this matters

• Promoting the version from a prerelease to a stable semver release changes how package managers and release tooling will select and publish this package. A prerelease (e.g. 4.4.85-dev.0) is treated differently by semver-aware tooling than a normal 4.4.85 tag; changing to the stable form makes the artifact the default for consumers who don't explicitly request prereleases. (commit 1233870)
• Bumping @fjell/core from ^4.4.74 to ^4.4.75 is a patch-level dependency upgrade intended to pick up backwards-compatible fixes in @fjell/core. Because this is a dependency change, it can affect runtime behavior or test outcomes even though no source code in this package changed. (commit ae32a9b)

Changes

• Release metadata

  • Updated package.json version field to the stable 4.4.85 (replacing the prerelease 4.4.85-dev.0) — commit 1233870. Impact: publishing and dependency resolution will treat this artifact as a normal release rather than a prerelease; consumers who previously depended on a prerelease will now see the stable release unless they pin specifically.

• Dependency bump

  • Updated @fjell/core dependency from "^4.4.74" to "^4.4.75" in package.json — commit ae32a9b. Impact: npm/Yarn will resolve to the newer patch release of @fjell/core, which should be backwards-compatible but may include behavioral fixes that change runtime/test behavior.

Files changed

• package.json — only file modified in this release (both commits). There are no source-level changes, no code refactors, and no changes to tests or documentation in this repository.

Implications and recommended actions for consumers and maintainers

• For package consumers:

  • No API-breaking changes are expected from this release as the version change here is metadata and the @fjell/core bump is a patch-level dependency upgrade. However, because dependency patches can fix or change behavior, run your test suite and smoke tests after upgrading to confirm nothing in your environment is sensitive to the patched behavior.
  • If your CI or deployment pins prereleases explicitly, note that this package is now a stable 4.4.85 release; update any pinning rules if you still need prerelease artifacts.

• For maintainers and release automation:

  • Publishing semantics have changed: the artifact will be published as a stable release (4.4.85). Ensure release pipelines and changelog generation expect the stable tag rather than a prerelease tag — this was the explicit intent in commit 1233870.
  • After changing package.json dependency ranges, regenerate lockfiles (package-lock.json / yarn.lock) and run CI to capture any transitive changes introduced by @fjell/core@^4.4.75.
  • If you maintain a changelog or downstream compatibility notes, review @fjell/core's 4.4.75 changelog to see what fixes were pulled in and whether any follow-up is needed here.

References

• Promote prerelease → stable: commit 1233870 — "Bump package.json version from prerelease to stable 4.4.85"
• Bump @fjell/core patch: commit ae32a9b — "Bump @fjell/core dependency patch version in package.json"

No breaking changes

There are no breaking changes in this repository introduced by these commits: only package metadata (version and a patch-level dependency range) were modified. The primary behavioral effect is on packaging, publishing, and dependency resolution; verify CI and lockfiles after pulling this release.