4.4.66 — publish-ready release and @fjell/core patch dependency bump

Overview

This release finalizes a prerelease into a normal patch release and updates the package's runtime dependency on @fjell/core to a newer patch version. The two commits in this set are focused on distribution metadata and dependency resolution — there are no source-code or API changes in this package itself. The intent is to publish a stable 4.4.66 package and ensure installations pick up the latest patch-level fixes from the shared core package.

Key changes (traceable to commits)

• Finalize prerelease → release

  • Updated package.json version from the prerelease identifier to a normal semver patch: from 4.4.66-dev.0 to 4.4.66 (commit 4782c3e).
  • Why this matters: removing the -dev.0 prerelease identifier changes the package identity used by registries and package managers. Installers and CI that treat prereleases specially (filters, pre-release channels, or exact-version pins) will now see this as the canonical patch release for 4.4.66.
  • Practical implication: publishing will produce a normal semver tag and consumers who request 4.4.66 (or use caret ranges that include it) will resolve to this published artifact. (See commit message: “Bump package.json version from prerelease to release”.)

• Bump @fjell/core patch dependency

  • Updated package.json dependency: "@fjell/core": "^4.4.75" → "@fjell/core": "^4.4.76" (commit c1c07d5).
  • Why this was done: the commit message indicates this is a patch-level bump intended to pull in fixes from the core package while preserving caret semantics (no change to the range operator). This is a dependency-resolution change rather than a local code/API change.
  • Practical implication: after installing, package managers will prefer @fjell/core@^4.4.76 where available. To ensure reproducible installs and CI builds, lockfiles should be updated (package-lock.json / pnpm-lock.yaml / yarn.lock) so environments use the intended core patch.

What changed in source/runtime

• There are no code changes to the package’s runtime or public API in this diff. The commit that sets the prerelease label (4.4.66-dev.0) (commit 5187144) is present in the log history but the final published manifest change is the removal of the prerelease identifier (commit 4782c3e...). All other modifications are to package.json metadata.

Compatibility and migration notes

• No breaking changes in this package

  • The update only touches package metadata and a caret-scoped dependency; there are no changes to exported APIs or runtime behavior in this repository.

• Recommended actions for consumers and CI

  • Run a fresh install and update lockfiles in your repository to capture the new dependency resolution: run npm install / pnpm install / yarn install and commit the updated lockfile. This ensures CI and reproducible builds resolve @fjell/core@^4.4.76 consistently (commit c1c07d5 indicates the intent to pull the patch).
  • If any workflows rely on prerelease filtering (for example, selecting only -dev versions), note that this release no longer carries the prerelease suffix and will be treated as a normal semver release (commit 4782c3e). Adjust any automatic promotion or channel-selection rules accordingly.
  • If you pin exact versions in CI (for example @fjell/http-api@4.4.66-dev.0), update those pins to the released 4.4.66 where appropriate.

Notes and implications

• This release emphasizes stable distribution and dependency hygiene rather than new functionality. The two metadata changes work together: one produces a publishable, non-prerelease package, and the other ensures consumers receive the latest patch fixes from the shared core package when they install this release (both commits are focused on package.json changes: 4782c3e... and c1c07d5...).

• Because the dependency bump uses a caret range (^4.4.76), downstream dependency resolution may still select a later compatible patch release if one exists and the consumer’s lockfile allows it; updating lockfiles is the only way to make the change reproducible across environments.

Commits included

• Bump package.json version from prerelease to release (commit 4782c3e)
• Bump @fjell/core dependency patch version in package.json (commit c1c07d5)
• Prerelease marker commit (4.4.66-dev.0) present in history (commit 5187144)

If you need further guidance on whether the core patch contains changes that affect runtime behavior for your project, inspect @fjell/core's changelog for the 4.4.76 entry and, if necessary, run the package test matrix with the updated lockfile to validate behavior before promoting to production.