Repository navigation
v1.5.7
Release 1.5.7
Summary
- This release contains a small maintenance update: package metadata, version bump to 1.5.7, and refreshes to scripts and dependency declarations in package.json. No functional code or runtime modules were modified — only package.json changed.
What changed
- Version bumped to 1.5.7.
- package.json metadata and scripts were refreshed:
- Build/test/lint scripts remain but were re-validated (build, dev, watch, test, lint, prepublishOnly, etc.).
- Node engine declared as ">=24.0.0".
- Dependency/development dependency updates and housekeeping:
- Dependencies listed: dayjs, glob, js-yaml, moment-timezone, semver, zod (no runtime dependency removed).
- DevDependencies refreshed (examples: ajv, esbuild, typescript, vite, vitest, vite-plugin-dts, winston present in devDeps for local test/linting).
- Peer dependencies unchanged (still @grunnverk/git-tools and winston, both marked optional in peerDependenciesMeta).
- No source files were added, removed, or modified other than package.json.
Why this matters
- Keeps project metadata and build/test toolchain up to date, which reduces friction for contributors and maintainers when building, testing, and publishing the package.
- Declaring Node engine ensures consumers and CI use a supported Node version (>=24).
- Dev dependency refresh can prevent build/test-time errors that appear when local tool versions diverge.
Impact on users and developers
- Users (runtime consumers): No change to runtime behavior or public API. This is a non-breaking, metadata-only release — you do not need to change how you import or use the package.
- Developers (contributors/maintainers): You should run npm install to pick up refreshed dev dependencies. The updated scripts and devDeps may affect local build/test flows and CI; CI that runs Node versions older than 24 will need to be updated to Node >=24 to match the declared engine.
- Publishing/CI: prepublish and precommit scripts remain strict (lint, build, tests) — CI must satisfy those commands.
Breaking changes
- None detected. The change set only updates package.json; no API or implementation changes were made. Manual review is recommended if you rely on very specific dev-tool versions, but there are no runtime or API breaking changes in this release.
Action items / Notes
- If you contribute or run CI:
- Run npm install after pulling this release.
- Ensure CI uses Node >=24 to match "engines" in package.json.
- Expect the usual prepublish / precommit checks (lint/build/test) to run as before.
- If you consume the package as a dependency:
- No immediate action required — upgrade safely when desired.
Changelog (high level)
- chore(package): bump version to 1.5.7 and refresh package metadata, scripts, and devDependencies.
If you need details about the specific package.json changes, inspect the diff for package.json; only that file was changed in this release.