Skip to content

@eldrforge/commands-git 0.1.1 — dependency refresh (no functional changes)

Choose a tag to compare

View all tags
@tobrien tobrien released this 10 Jan 22:48
· 23 commits to working since this release
v0.1.1
2d4228e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Overview

This release is a patch update focused on keeping @eldrforge/commands-git aligned with the latest patch versions of its @eldrforge/* dependencies. There are no source/code changes in this range—only versioning and dependency updates.

Changes in this release

Version bump

  • Package version: 0.1.0 → 0.1.1

Dependency updates (patch-level)

Updated @eldrforge/* dependencies to the latest patch versions:

  • @eldrforge/core: ^0.1.0 → ^0.1.1
  • @eldrforge/git-tools: ^0.1.16 → ^0.1.17
  • @eldrforge/github-tools: ^0.1.18 → ^0.1.19
  • @eldrforge/ai-service: ^0.1.17 → ^0.1.18
  • @eldrforge/shared: ^0.1.6 → ^0.1.7

Lockfile refresh

  • package-lock.json was regenerated to reflect the updated dependency graph.
    • This can result in many transitive dependency changes even though top-level changes are small.
    • Note: the lockfile currently reports the package version as 0.1.1-dev.0 (while package.json is 0.1.1). This typically doesn’t affect consumers of the published package, but it can be confusing for contributors using npm ci.

Why this matters

  • Pulls in upstream fixes and improvements from the @eldrforge/* packages without requiring code changes in this package.
  • Keeps dependency trees consistent across the @eldrforge ecosystem.

Impact

For users

  • No behavioral changes are expected from @eldrforge/commands-git itself.
  • You may see different resolved transitive dependency versions after upgrading (due to the lockfile refresh).

For developers/contributors

  • After pulling this release, run npm install (or npm ci) to pick up the updated lockfile.
  • Some updated transitive/dev tooling dependencies include stricter Node engine requirements (common in the current ecosystem). If your environment is older, you may need to upgrade Node to install/build reliably.

Breaking changes

  • None identified in this diff range.
  • Caution: while this package did not change APIs, dependency updates can indirectly introduce compatibility constraints (notably Node engine requirements) via upstream packages.
Assets 2
Loading