Repository navigation
0.1.7
Summary
This release increments the package to version 0.1.7 and includes small packaging and developer-tooling updates. There are no functional changes to the CLI runtime behavior — the update is limited to package metadata and build/test scripts/dependencies.
What changed
- Bumped package version to 0.1.7 in package.json.
- Updated package.json scripts and developer dependencies (lint/build/test scripts maintained; devDependencies refreshed).
- Build/test/lint scripts remain present: build, dev, watch, test, lint, precommit, prepublishOnly, etc.
- Node engine requirement declared as ">=24.0.0" (no change to runtime entry point or published bin).
- Dependency versions in package.json are present and were refreshed as part of the package chore.
Total diff size: 1 file changed (package.json), 2 insertions, 2 deletions. Three commits (all chore/package updates) by a single contributor.
Why this matters
- Versioning: Prepares a new release (0.1.7) for publishing and downstream consumption.
- Developer experience: Keeps build, lint and test scripts and devDependencies up to date — helps contributors have a consistent local development and CI experience.
- Stability: No runtime or API changes were introduced, so users of the CLI should see no change in behavior.
Impact on users and developers
- Users: No functionality changes. If you install 0.1.7 you should see the same CLI behavior as before.
- Developers / CI: Pulling the release may update developer tooling versions in devDependencies. Ensure your local environment satisfies the declared Node engine (>=24.0.0) if you run build/test tasks.
- Package consumers: No code-level or API changes; only a version bump and metadata/dev tooling updates.
Breaking changes
- None detected. A scan of changes shows only package metadata and dev tooling updates. No public API or CLI behavior changes were made.
Practical notes
- To upgrade: npm install @redaksjon/protokoll-cli@0.1.7
- If you contribute: run the standard scripts (npm run lint, npm run build, npm run test) — the precommit and prepublishOnly hooks remain configured to run these checks.