Skip to content

1.0.13: Stop tracking `package-lock.json` and enforce lockfile ignore policy

Choose a tag to compare

View all tags
@tobrien-agent tobrien-agent released this 30 Mar 02:31
· 7 commits to working since this release
v1.0.13
a38c9db
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Summary

This release is primarily repository hygiene and release housekeeping. There are no functional/runtime code changes to the Gemini execution provider itself.

Changes

Release/versioning

  • Bumped package version to 1.0.13 in package.json.

Dependency/lockfile policy

  • Removed package-lock.json from the repository and updated .gitignore to ignore:
    • package-lock.json
    • .kodrdriv* artifacts (including .kodrdriv*package-lock.json)

This aligns the repo with a “do not commit lockfiles” policy.

Impact

For library consumers

  • No API or behavior changes expected from this release (no source changes were included in the diff).
  • Installation should continue to work normally via npm; you’ll simply no longer see a lockfile committed in this repo.

For contributors/maintainers

  • Do not commit package-lock.json going forward; it is now intentionally ignored.
  • If you had automation or checks that depended on a tracked lockfile, update them to reflect that lockfiles are not part of the repo state.

Breaking changes

  • No breaking changes to the public library API were detected in this release.
  • Workflow note (repo policy change): projects or processes expecting package-lock.json to be present in the repository will need adjustment.
Assets 2
Loading