Release 4.4.3 — package metadata finalized and @fjell/types pinned to 4.4.6

Overview

This release contains only package metadata changes: the package.json version was converted from a development snapshot to a canonical patch release string, and the pinned @fjell/types dependency was advanced from 4.4.5 to 4.4.6. There are no changes to runtime source files in this package; the work here is about release semantics and the TypeScript dependency surface. (See commits d8f98e3 and 3394669.)

Breaking Changes

• There are no code-level breaking changes in library behavior. However, one change affects how installs resolve dependency versions and may have downstream effects on type checking:
  • @fjell/types is pinned exactly to 4.4.6 (no caret) in package.json, replacing 4.4.5 (commit 3394669). This exact pin means installs will resolve to 4.4.6 rather than allowing a range — see "Impact & recommendations" below.

What changed

• Finalize release version string

  • Converted package.json version from the development snapshot string to the canonical patch release "4.4.3" (commit d8f98e3). The commit message describes this as a metadata-only change that affects npm/yarn resolution and publish semantics.
  • Why it matters: tooling and consumers that read package.json for exact version values (CI scripts, publish tooling, lockfile generators) will now see a concrete patch-level version instead of a dev snapshot. This is important for reproducible installs and publish flows.

• Advance pinned TypeScript types package

  • Updated the exact (unpinned-without-caret) dependency @fjell/types from 4.4.5 → 4.4.6 in package.json (commit 3394669).
  • Why it matters: this repo consumes type definitions from @fjell/types. Even though runtime code here didn't change, a patch-level change to type definitions can alter TypeScript diagnostics or inferred types during CI/compile. The commit notes this as a low semantic risk but recommends running type checks and the CI build.

Impact & recommendations

• Re-generate lockfiles after updating

  • Because package.json metadata and an exact dependency pin changed, consumers and CI should regenerate package-lock.json / yarn.lock and reinstall to ensure the lockfile matches the new manifest. This follows directly from both commit messages and avoids inconsistent installs across environments (commits d8f98e3, 3394669).

• Run type checks and CI build

  • The bump to @fjell/types is a types-only change at the patch level; it may still influence TypeScript diagnostics for downstream projects that import this package. Run your TypeScript checks and CI pipelines to confirm there are no unexpected type regressions (commit 3394669).

• No runtime code changes

  • The release is explicitly described as metadata-only in the version bump commit; no source or behavior changes were made to library code (commit d8f98e3). Therefore, there should be no runtime behavioral differences introduced by this release.

Technical notes and traceability

• Commits included in this release:

  • Bump pinned @fjell/types dependency to 4.4.6 — 3394669
  • Bump package version metadata from dev tag to concrete patch release — d8f98e3
  • Dev snapshot commit (record of dev version) — 7662ce3

• Practical checklist for integrators:

  • Update local lockfile: run npm install / yarn install to update package-lock.json or yarn.lock to reflect @fjell/types@4.4.6.
  • Run TypeScript type checks and the full CI build to detect any changes in diagnostics.
  • No application code changes are required unless type-check failures appear; if they do, they will be caused by changes in the consumed @fjell/types definitions (commit 3394669).

If you maintain downstream packages that depend on this library, treating this release as a metadata and type-definition update will be sufficient in most cases. The primary operational actions are lockfile regeneration and a CI/type-check pass to verify nothing in the type surface changed unexpectedly.