Skip to content
This repository was archived by the owner on Nov 7, 2026. It is now read-only.

Finalize 0.1.14 — package metadata, lockfile normalization, and git-tools bump

Choose a tag to compare

View all tags
released this 25 Dec 02:04
· 20 commits to working since this release
v0.1.14
f7557a5

Overview

This release is focused on finalizing packaging metadata for a stable 0.1.14 release and ensuring reproducible installs. It contains three coordinated, metadata-only changes: promotion of the package version from a prerelease identifier to the final 0.1.14 value, normalization of package-lock.json to reflect the stable version, and a patch-level dependency bump for @eldrforge/git-tools. None of the commits change source files or runtime behavior; they prepare the package for correct semver/registry handling and deterministic installs.

Packaging & release metadata

  • Promoted package version to a final semver identifier (commit c8fc7fa).

    • What changed: package.json was updated to change the version from the prerelease string ("0.1.14-dev.0") to the stable "0.1.14" ("Promote package version from pre-release to final 0.1.14").
    • Why it matters: removing the prerelease suffix changes how registries and semver tooling treat the package identity — downstream tools and consumers will now see this as the normal 0.1.14 release rather than a dev prerelease (this is explicitly called out in the commit). This is primarily a publishing/metadata change, not a code change.
    • Trace: commit c8fc7fa (Promote package version from pre-release to final 0.1.14).

  • Normalized package-lock.json entries to record the stable version (commit 3c2c50f).

    • What changed: package-lock.json top-level "version" and the packages[""].version entry were updated from the prerelease string to "0.1.14"; the lockfileVersion (3) and dependency entries were left unchanged.
    • Why it matters: aligning the lockfile's recorded package version with package.json avoids a mismatch between published package metadata and the lockfile, and it affects how package identity is read by npm tooling and reproducible installs/publish metadata (this effect is described in the commit message).
    • Trace: commit 3c2c50f (Replace prerelease version strings in package-lock.json with stable 0.1.14).

Dependency updates

  • Bumped @eldrforge/git-tools to ^0.1.11 in package.json (commit 3e29832).
    • What changed: the dependency entry for @eldrforge/git-tools was updated (the commit message records the change from "^0.1.10" to "^0.1.11"). The caret range remains in place, so npm will still resolve versions >=0.1.11 and <0.2.0.
    • Why it matters: this is a patch-level dependency bump intended to pick up fixes or compatible improvements in the git-tools package. Because package.json changed, installs may resolve a different package-tree than before unless the lockfile is refreshed — the commit explicitly recommends refreshing the lockfile in CI or before release so installs reproduce the new resolved dependency version.
    • Trace: commit 3e29832 (Bump @eldrforge/git-tools dependency to ^0.1.11 in package.json).

Developer / CI notes (what to do now)

  • Refresh and commit the lockfile before publishing (recommended; referenced in commit 3e29832).

    • Rationale: the dependency bump can change resolved dependency versions. The dependency commit explicitly notes that the lockfile should be refreshed in CI or before release so installs reproduce the new resolved dependency version — do this to avoid nondeterministic installs between CI and local environments.
    • Practical effect: after regenerating the lockfile, the top-level package version recorded there will match package.json (commit 3c2c50f) and package identity will be consistent for consumers and registries.

  • Expect no functional/runtime changes from this release.

    • Rationale: the commit messages for the version promotion and dependency bump both state that no other source files were changed and that the package.json updates are limited to metadata used for publishing/version checks. There are therefore no API or behavioral changes introduced by these commits (see commits c8fc7fa and 3e29832).

Impact and verification

  • Semver and registry behavior: because the prerelease suffix was removed, semver tooling and registries will treat 0.1.14 as a normal release rather than a prerelease; this can change resolution for ranges that previously excluded prereleases (commit c8fc7fa).

  • Reproducible installs: updating package-lock.json to contain the stable version ensures the lockfile reflects the eventual published package identity. If you depend on strict reproducibility, regenerate the lockfile in your CI and confirm installs resolve the intended versions (commit 3c2c50f and 3e29832).

No breaking changes

  • There are no intended breaking changes in this set of commits. The work is packaging- and metadata-focused and does not alter source files or public APIs.

Commits included in this release

  • c8fc7fa — Promote package version from pre-release to final 0.1.14
  • 3c2c50f — Replace prerelease version strings in package-lock.json with stable 0.1.14
  • 3e29832 — Bump @eldrforge/git-tools dependency to ^0.1.11 in package.json

If you maintain downstream integrations or CI pipelines that relied on prerelease semantics or on a previously committed lockfile, review and regenerate your lockfiles and dependency assertions so they align with the final 0.1.14 metadata included here.

Assets 2
Loading