Skip to content

Patch release: publish-ready metadata and @fjell/core patch bump (4.4.65)

Choose a tag to compare

View all tags
released this 20 Dec 13:21
· 17 commits to working since this release
v4.4.65
9aa9774

Overview

This release is a focused patch that prepares the package for publishing and aligns the resolved dependency on @fjell/core to a newer patch release. The changes are small and deliberate: the package manifest was moved from a prerelease identifier to a normal patch version, and the project dependency and lockfile were updated so installs resolve @fjell/core@4.4.75. Together these changes ensure consumers and CI see a consistent, publishable artifact and a deterministic dependency resolution.

What changed (high level)

  • Package version metadata was converted from a prerelease identifier to a release patch version in package.json (commit 0bc6adb).
  • The declared dependency range for @fjell/core was bumped from ^4.4.74 to ^4.4.75 in package.json (commit c68e63f).
  • The lockfile was updated to pin the resolved @fjell/core artifact to the 4.4.75 tarball and its integrity checksum (commit 72dadc8).

Why these changes were made (analysis)

  • Transition from prerelease to release: The package.json version change removes the dev/prerelease identifier and sets a concrete semver patch (4.4.65). This changes how package managers, CI, and registries treat the artifact: it becomes a normal semver release rather than a prerelease, which affects publish behavior and consumers who depend on exact versions. Making this explicit in metadata avoids accidental consumption of prerelease artifacts by consumers that do not expect them (commit 0bc6adb).

  • Align dependency and lockfile for deterministic installs: Bumping the dependency range in package.json to ^4.4.75 ensures the package will accept the newer core patch; updating the lockfile pins the resolved artifact and integrity hash so installs using this repository will deterministically fetch @fjell/core@4.4.75 instead of 4.4.74 (commits c68e63f and 72dadc8). This pair of changes prevents mismatches between declared ranges and the lockfile during CI, local installs, or when publishing the package.

Sections

Improvements

  • Publish-ready version metadata: Updated package.json version from a prerelease value to "4.4.65", making the package manifest reflect a normal semver patch release that package managers and registries will treat as a stable patch (commit 0bc6adb). Impact: CI and publishing pipelines that gate on non-prerelease versions will now recognize this artifact as a publishable release.

  • Dependency patch alignment: Changed the declared dependency for @fjell/core from "^4.4.74" to "^4.4.75" in package.json (commit c68e63f). Why it matters: this ensures the package can pick up the latest patch fixes from the core package without widening the allowed semver range beyond a patch-level update.

  • Deterministic lockfile update: Updated package-lock.json to record the resolved @fjell/core entry at 4.4.75 and the corresponding integrity metadata (commit 72dadc8). Why it matters: the lockfile change guarantees that installs using this repository (or CI that consumes this lockfile) will fetch the exact 4.4.75 tarball and checksum, removing ambiguity between declared ranges and actual resolution.

Developer guidance / migration notes

  • If you maintain a checked-out copy of this repository, run your package manager install to refresh node_modules from the updated lockfile. The intended result is @fjell/core@4.4.75 being installed according to the lockfile (see commit 72dadc8).

  • If your downstream project pinned this package by exact version (for example, depending on @fjell/http-api@4.4.65-dev.0), note that the package identity changed to 4.4.65 (commit 0bc6adb). Update any exact-version references to the released 4.4.65 if you intend to consume the release instead of a prerelease.

  • No API or behavior changes are recorded in these commits; the changes are limited to metadata and dependency resolution. However, because the core dependency moved to a newer patch, downstream behavior may change only insofar as fixes or tweaks in @fjell/core@4.4.75 affect runtime. Consumers who rely on exact behavior should verify compatibility by running tests against the new resolution.

Files changed (for quick reference)

  • package.json — version set to 4.4.65 and @fjell/core dependency bumped to ^4.4.75 (commits 0bc6adb, c68e63f).
  • package-lock.json — updated resolved entry and integrity for @fjell/core to reflect 4.4.75 (commit 72dadc8).

Breaking changes

  • None recorded in these commits. The release is a metadata and dependency alignment patch. Still, downstream projects should run their test suites because the resolved @fjell/core artifact upgraded a patch version (4.4.75) which may contain fixes or small behavior changes from 4.4.74.

Traceability

  • Version bump to release: commit 0bc6adb
  • package.json dependency bump: commit c68e63f
  • lockfile resolution update: commit 72dadc8

If you need more detail about what changed in @fjell/core between 4.4.74 and 4.4.75, inspect that package's changelog or its own commit history; this release intentionally updates the dependency to pick up whatever patch fixes were published there while keeping this package's public API and code unchanged.

Assets 2
Loading