Skip to content

0.1.3

Choose a tag to compare

View all tags
@tobrien tobrien released this 16 Feb 15:35
· 0 commits to master since this release
v0.1.3
ff10865
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 updates the package metadata and development tooling. The only changed file in this release is package.json. The package version is now 0.1.3 and several developer-facing dependencies and scripts have been refreshed to align the project with current tooling expectations.

What changed

  • package.json
    • Version bumped to 0.1.3.
    • Developer tooling and scripts refreshed (devDependencies and scripts adjusted).
    • Project now declares Node engine requirement "node": ">=24.0.0".
    • Runtime dependencies listed in package.json (notably @modelcontextprotocol/sdk at 1.25.3 and @redaksjon/protokoll ^1.0.14) are present in the manifest.

No other source files were modified in this release.

Why it matters

  • Version bump: prepares a packaged release (0.1.3) for distribution and dependency consumers.
  • Developer tooling refresh: keeps linters, TypeScript, build and test tools up to date so contributors have a reproducible, modern development environment.
  • Node engine requirement: CI, contributors and deploy targets must run Node 24 or newer. This prevents running the CLI in older Node environments that may not support modern JS/TS features used by the build or runtime.

Problems addressed

  • Keeps build/test/lint toolchain dependencies current to reduce friction when developing, building, or publishing the package.
  • Ensures package metadata and scripts (build, test, lint, prepublish) match current expectations for the project’s workflow.

Impact on users and developers

  • Users of the published CLI package gain an officially published 0.1.3 release (metadata only). No functional changes to runtime code were included in this release.
  • Developers should run npm install after pulling this release to pick up updated devDependencies.
  • CI and local development environments must use Node >= 24.0.0 per the engines field. Ensure build agents are updated if they run older Node versions.

Breaking changes

  • No code-level breaking changes were detected (no API or behavior changes in source files). The only potential breaking item is the increased Node engine minimum (>=24.0.0). If any developer or CI environment was using Node < 24, that will need to be upgraded to continue building or running tasks that respect the engine field.

Practical notes

  • To update local environment:
    • Run: npm install
    • Ensure Node 24+ is used (nvm use 24 or upgrade system Node).
  • CI: update pipeline images/runners to Node 24+ if they currently use an older version.

If you need a list of the exact devDependency updates or the diff of package.json, that can be provided on request.

Assets 2
Loading