Release 4.4.1 — package.json version updated from dev tag to stable patch

Overview

This release only changes package metadata: the package.json version string was moved from a development tag to the canonical patch release value. There are no code, behavior, API, or test changes in this release — it is a metadata-only release that prepares the package for normal semver consumption and publishing.

What changed

• Bumped the package.json version string from "4.4.1-dev.0" to "4.4.1" (commit 76a409f).
  • The commit message explicitly states this is a metadata change and does not modify runtime behavior.

Why this matters

• Dependency resolution: Consumers and package managers will now see and resolve the package as version 4.4.1 instead of a dev-tagged version. This affects semver matching and installs that exclude prerelease versions by default.
• Publish and CI tooling: Normal npm pack/publish flows and CI checks that gate on non-dev version strings will treat this as a canonical patch release rather than a development snapshot.
• No functional impact: Because no source files or behavior were changed, projects depending on the package should not see behavioral differences when upgrading; only the package identity (version) has changed.

Recommended actions for users

• If you pin or reference prerelease/dev versions explicitly, update your dependency spec if you intend to consume the stable 4.4.1 release (for example, change a dependency from "@fjell/validation@4.4.1-dev.0" to "@fjell/validation@4.4.1").
• If your CI or publishing scripts treat prerelease versions differently, verify they now pick up the canonical 4.4.1 value as expected.

Files/areas touched

• package.json: version field updated (see commit 76a409f).

Breaking changes

• None. The release is metadata-only and does not change runtime behavior or public APIs.

Changelog reference

• Commit: 76a409f — "Bump package version in package.json from a dev tag to a concrete patch release"