🤖
1404 in / 1858 out / 3262 total tokens
Bumped memradar from 3.2.1 to 3.3.0. The commit message mentions tooltip cost display and cached token calculation fix, but the actual diff only touches the version fields in package. and package-lock.. Feature implementation and bug fixes were already done in previous commits — this is just the version stamp before release.
Going by semver, bumping the minor version (3.3.0) instead of a patch (3.2.x) suggests the tooltip cost display was considered a user-facing UI change. The token calculation fix alone could've been a patch, but bundled with a feature addition, a minor bump makes sense.
This pattern feels familiar from game dev. Unreal Engine tracks version numbers in ModuleDescriptor files, and plugin updates involve committing just that value for the pipeline to pick up. In the npm ecosystem, keeping lockfile and package. versions in sync is standard practice — hence both files changing as a set.
The lockfileVersion 3 format has been around since npm v7+. Older lockfile formats were a pain during collaboration due to merge conflicts. v3 tracks dependency trees per package more explicitly, reducing those headaches.
"version": "3.3.0"
That single line carries weight. Once you npm publish, this version hits the registry, and users can pin it with npx memradar@3.3.0. CI/CD pipelines also use this as the tag reference for automated deployment.
A version number isn't documentation — it's a contract. Once you bump it, there's no going back.