v0.1.3 — release: package version bump, @eldrforge dependency updates, and agentic enablement

Summary

This release publishes @eldrforge/tree-execution as 0.1.3. The change set is intentionally small and focused: the package version was bumped to 0.1.3 and three internal dependencies were advanced to their latest patch/minor versions. The package-lock was updated to lock the new dependency resolutions. A recent commit also adds/explicitly enables "agentic"-related configuration flags in the codebase.

Affected files (high level)

• package.json — version and dependency version bumps
• package-lock.json — lockfile updated to match new dependency versions

Primary commits included (from main -> HEAD)

• e37bbc3 — chore(release): bump package version to 0.1.3
  • Update package.json version from 0.1.3-dev.0 to 0.1.3 for release build
• bef77de — chore(deps): bump @eldrforge dependencies and update lockfile
  • Bump @eldrforge/tree-core to ^0.1.3
  • Bump @eldrforge/git-tools to ^0.1.15
  • Bump @eldrforge/shared to ^0.1.4
  • Update package-lock.json
• 39a3ea9 — Adding agentic
  • Introduces / enables agentic-related configuration and flags (see details below)

What changed (concrete)

1. package.json

   • package version: 0.1.2 -> 0.1.3
   • dependency version updates:
     • @eldrforge/tree-core: ^0.1.2 -> ^0.1.3
     • @eldrforge/git-tools: ^0.1.14 -> ^0.1.15
     • @eldrforge/shared: ^0.1.3 -> ^0.1.4
   • No other public-facing exports or package metadata were changed.

2. package-lock.json

   • Updated to resolve the new versions above (locks tree-core@0.1.3, git-tools@0.1.15, shared@0.1.4).

3. Agentic-related code (context)

   • The commit labeled "Adding agentic" corresponds to enabling/introducing agentic-related flags and configuration in the codebase. The code contains explicit references to an "agentic" boolean and related settings in CLI and configuration handling (examples found in src/tree.ts and src/types/config.ts where runConfig.commit?.agentic, runConfig.release?.agentic and maxAgenticIterations appear).
   • This release packages the project with those capabilities available to consumers (the exact surface is controlled via configuration flags; see Developer Notes below).

Why these changes

• The package version bump (0.1.3) marks a stable release (removes dev suffix) and packages the current state of the library, including dependency updates and agentic support.
• The dependency bumps bring in the latest bug fixes and improvements from the @eldrforge family (tree-core, git-tools, shared). These packages are closely related and used as internal building blocks for tree-execution; keeping them aligned reduces integration issues.
• The agentic changes implement or expose an opt-in behavior (agentic/self-reflection and iteration limits) which is part of higher-level orchestration and automated workflows engineered in the repository.

Impact for users

• Upgrading: Consumers who install or update to @eldrforge/tree-execution@0.1.3 should run npm install (or equivalent) so the updated dependency versions are installed and locked.
• Behavior: There are no functional changes to the public API of this package documented in package.json; however, the codebase exposes agentic-related flags and configuration which can change runtime behavior if enabled.
• Backwards compatibility: The changes are limited to dependency bumps and a release version bump. An automated scan reported no obvious breaking changes between v0.1.2 and v0.1.3. The bumped packages use caret ranges (^0.1.x), and the specific bumps are patch/minor-level within the 0.1.x line. Because this is in the 0.x namespace, be aware that "0.x" versions can carry breaking changes in their minor bumps in some projects — but there is no evidence in this change set of an intentional breaking API change.

Impact for developers / maintainers

• Tests & CI: Run the test suite and CI (same prepublish steps are configured in package.json: lint, build, test) to verify the dependency upgrades don't surface regressions in your environment.
• Local development: Node engine requirement remains >= 18.0.0 (no change). Rebuild artifacts (npm run build) after installing dependencies.
• Agentic flags: The codebase exposes agentic/selfReflection flags and maxAgenticIterations in execution and release flows. These are opt-in; enabling them will alter execution flows (for example, commit and release commands may accept --agentic and --max-agentic-iterations CLI flags). Confirm the behavior in your workflows before enabling in CI or automated runs.

Risk assessment / breaking changes

• Automated and manual review of the changes in this release show no breaking API changes to @eldrforge/tree-execution itself (no exports added/removed from package.json or types/files altered by this specific release commit). The main risk is transitive: any changes in the bumped dependency packages could alter behavior.
• Recommendation: Projects that rely on precise behavior from @eldrforge/tree-core, git-tools, or shared should run a quick integration smoke test. The test and prepublish scripts are present and should be used as part of validation.

How this release fits the project history

• This release is a continuation of the 0.1.x line: previous tags include v0.1.2 and intermediate dev tags (v0.1.3-dev.0). The release simply advances the stable package version and aligns with parallel updates made to the @eldrforge family packages.
• The repository has recently seen work to consolidate extracted utilities into companion packages (@eldrforge/tree-core, git-tools, shared). The dependency bumps keep tree-execution in sync with those library versions.

Developer notes / implementation details

• package.json scripts of note (unchanged by this release):
  • build: tsc
  • test: vitest run
  • prepublishOnly: runs clean, build, and test
• Files included in package: dist, README.md, LICENSE
• The package-lock was updated — commits include both package.json and package-lock.json changes to ensure reproducible installs.

Changelog (short)

• chore(release): bump package version to 0.1.3 — e37bbc3
• chore(deps): bump @eldrforge dependencies and update lockfile — bef77de
  • tree-core ^0.1.3, git-tools ^0.1.15, shared ^0.1.4
• Adding agentic — 39a3ea9

Final notes

• The release is focused and low-risk: it marks a stable package publish and aligns dependency versions across tightly-coupled @eldrforge packages while making agentic-related configuration available in the runtime. No breaking API changes were detected in the tree-execution surface; however, standard due diligence (install, build, run tests) is recommended when upgrading.