@kjerneverk/execution 1.0.14 — Publish/CI lockfile handling and KodrDriv config tracking

Summary

This release focuses on making publishing more reliable by standardizing how package-lock.json is handled and by committing the KodrDriv publish configuration needed to enforce that policy. There are no runtime/library API changes in this release.

Changes

Publishing and repository hygiene

• Stop tracking package-lock.json and ignore it in git

  • package-lock.json is now explicitly gitignored, and the repository is expected to be clean without committing a lockfile.
  • This aligns with the publish process expectations and avoids publish failures caused by a “dirty” lockfile generated during automated steps.

• Track KodrDriv publish configuration

  • .kodrdriv/config.yaml is now kept in the repo (the .kodrdriv/ directory remains ignored except for this file).
  • Adds publish.lockfilePolicy: ignore, ensuring the publish flow does not require a committed lockfile.

CI behavior (impact)

• CI already installs dependencies without relying on a committed lockfile (it removes package-lock.json and uses npm install --force). This release makes that workflow consistent with the repository policy and publish requirements.

Version

• Bumps package version to 1.0.14.

Impact for users and developers

• Library consumers: No functional changes expected.
• Contributors/maintainers:
  • Do not commit package-lock.json going forward.
  • If you previously relied on the lockfile being present/committed for local workflows, adjust accordingly (the intended workflow is lockfile-free for this repo to satisfy publish clean-check constraints).

Breaking changes

• None detected (no API or behavior changes in the library code).
• Note: The lockfile policy change may require minor workflow adjustments for contributors, but it is not an API breaking change for consumers.