4.4.86 — promote stable release and bump @fjell dependency patches

Overview

This release promotes the package from a prerelease tag to a stable 4.4.86 artifact and updates several @fjell peer/internal dependencies to their next patch versions. The changes in this release are confined to package.json metadata (version and dependency ranges). There are no source-code changes in this release.

What changed (high level)

• The package version was changed from a prerelease token to a stable semver: 4.4.86-dev.0 → 4.4.86. This is a metadata-only change that affects how npm/semver treats this package when resolving dependencies (commit 8d9eae3, message: "Bump package.json from prerelease to stable 4.4.86").
• Four @fjell-scoped dependencies had their caret version ranges advanced at patch level in package.json: @fjell/core ^4.4.75 → ^4.4.76, @fjell/registry ^4.4.82 → ^4.4.83, @fjell/types ^4.4.5 → ^4.4.6, and @fjell/validation ^4.4.2 → ^4.4.3 (commit 77e31b9, message: "Bump several @fjell package dependencies to next patch releases in package.json").

Why this matters

• Semver and dependency resolution: Changing the package version from a prerelease (4.4.86-dev.0) to a stable release (4.4.86) means package managers and consumers will treat this as a normal release rather than a prerelease. Installers and CI pipelines that filter or behave differently for prerelease versions will now see 4.4.86 as eligible for normal installs (see commit 8d9eae3 for rationale).

• Pulling in patch fixes from internal packages: The dependency bumps are all patch-level updates (same major and minor). That indicates the intention to incorporate backward-compatible bug fixes or small improvements from those packages without changing public APIs. However, the actual runtime impact depends on the contents of those downstream patch releases — consumers should run their test suites to validate behaviour after updating (see commit 77e31b9 for details).

Concrete details and tracing

• Version promotion

  • What changed: package.json version field replaced prerelease token with stable 4.4.86 (commit 8d9eae3). The commit message explicitly notes this is metadata-only and does not modify source files or runtime code.
  • Why it was done: so npm/semver resolution treats the artifact as stable rather than a prerelease; this affects publishing and downstream consumers that may filter prereleases.
  • Impact to watch for: CI or release scripts that branch behavior on prerelease tags should be reviewed to ensure they still work as intended now that the package is a stable release.

• Dependency bumps (patch-level)

  • What changed: package.json dependency ranges were updated as follows (commit 77e31b9):
    • @fjell/core: ^4.4.75 → ^4.4.76
    • @fjell/registry: ^4.4.82 → ^4.4.83
    • @fjell/types: ^4.4.5 → ^4.4.6
    • @fjell/validation: ^4.4.2 → ^4.4.3
  • Why it was done: bring in the latest patch releases from those packages (commit message explicitly: "intend to pull backwards-compatible bugfixes or minor improvements"). Only package.json was modified.
  • Impact to watch for: because these are patch-level bumps, they should be backward compatible; nevertheless, consumers should run tests after installing the new ranges because runtime behaviour changes depend on those packages' patch contents.

Release scope and risk

• Scope: package.json-only changes (version and dependency ranges). No source files, tests, or devDependencies were modified in the commits associated with this release (commits 8d9eae3 and 77e31b9). The prerelease commit (0128f9e) indicates the prior prerelease tag exists in history but was replaced by the stable bump.

• Risk: low for code regressions inside this package because there are no runtime code changes here. Primary risk is behavioral: consumers relying on prerelease semantics, or CI/release tooling that looked for "-dev" suffixes, may need to adapt. Additionally, pulling in patched dependencies could surface changes from those packages; standard validation (install + test) is recommended.

Actions for consumers

• If you run automated tooling that excludes prerelease versions, note that 4.4.86 is now a stable release and will be considered for normal installs (no action required unless you intended to keep using prereleases).
• After updating to this release, run your project's test suite and CI to ensure the bumped @fjell/* patch releases do not introduce unexpected behavior in your environment.
• If your release or CI scripts depend on looking for the prerelease suffix, update them to handle the stable 4.4.86 token (see commit 8d9eae3 for context).

Commits referenced

• 8d9eae3 — "Bump package.json from prerelease to stable 4.4.86"
• 77e31b9 — "Bump several @fjell package dependencies to next patch releases in package.json"
• 0128f9e — "4.4.86-dev.0" (historical prerelease marker)

If you need a changelog of what the patched @fjell/* releases contain, review those packages' release notes before upgrading — this package only updated the ranges to reference those patches.