Skip to content

Release 1.0.5 — publish workflow hardening, dependency/tooling updates, and tracked lockfile

Choose a tag to compare

View all tags
@tobrien tobrien released this 20 Mar 15:00
· 3 commits to main since this release
v1.0.5
4784c9b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Main story

1.0.5 is primarily a packaging and release-process update. It tightens up publish-time checks, updates tooling/dependency versions, and ensures the repository consistently tracks the npm lockfile so installs and CI behave deterministically.

Changes in this release

Publishing & release hygiene

  • Hardened prerelease/publish prechecks so publish validation and lockfile policy checks behave consistently.
  • Lockfile is now tracked (and no longer ignored), making dependency resolution reproducible across machines and CI.
  • publishConfig.tag is set to dev in package.json, steering publishes toward the dev dist-tag by default.

Scripts and metadata

  • Updated package.json scripts to standardize the build/test/lint flow:
    • build: vite build
    • test / test:coverage: vitest run --coverage
    • precommit: build && lint && test
    • prepublishOnly: clean && build
  • Package metadata and dependency declarations were refreshed (including updated dev tooling versions).

Dependency/lockfile updates

  • Updated package-lock.json to reflect the current dependency tree.
  • Notable: while package.json depends on @modelcontextprotocol/sdk as ^1.0.4, the lockfile resolves it to a newer compatible version (as expected with a caret range).

Impact

For users

  • More predictable installs due to the committed lockfile.
  • No runtime behavior changes are indicated by this diff; changes are concentrated in packaging/tooling.

For maintainers/contributors

  • More consistent publish behavior due to tightened prechecks and explicit publish configuration.
  • CI/local parity improves because installs will match the committed lockfile.

Breaking changes / important notes

  • Potentially breaking (publishing behavior): publishConfig.tag is now dev. If you publish from this repo without overriding tags, npm publish will default to the dev dist-tag rather than latest.
    • If you intend a stable release to land on latest, publish with an explicit tag (for example, npm publish --tag latest) or adjust publishConfig for the release process.
  • No API- or code-level breaking changes were detected in this release range (changes are limited to repo config, scripts, and dependencies).
Assets 2
Loading