Update vlt to 1.0.2 - #591
Merged
Merged
Conversation
Upstream shipped 1.0.2 on 2026-08-07 (npm dist-tags latest + GitHub release agree); we sat on 1.0.1 because vlt had no version source of any kind — pkgmgr-rs#703 adds the npm dist-tags check so this can't silently recur. Lockfile regenerated (npm install --package-lock-only): version, resolved URL, and integrity hash move together; the version_is_exact standalone test pins the built binary to 1.0.2. Manual bump because the updater's version-only npm path parses 'npm install <pkg>@$VERSION' build scripts, not this package's committed-lockfile 'npm ci' flavor — updater support tracked as a pkgmgr-rs follow-up. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe PR updates the vlt package version from 1.0.1 to 1.0.2 in the build declaration and package dependency metadata. Changesvlt version update
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
bryan-minimal
enabled auto-merge
August 10, 2026 20:43
jtnkminimal
approved these changes
Aug 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upstream shipped 1.0.2 on 2026-08-07 (npm
dist-tags.latestand the GitHub release agree); we sat on 1.0.1 because vlt had no version source of any kind —checkskipped it every run and/pkgs upgradehad nothing newer to offer. pkgmgr-rs#703 adds the npm dist-tags version check so the staleness can't silently recur.build.nclversion → 1.0.2 (theversion_is_exactstandalone test pins the built binary to it)package.jsonpin +package-lock.jsonregenerated vianpm install --package-lock-only: version, resolved URL, and sha512 integrity move togethernpm install <pkg>@$VERSIONscripts, not this package's committed-lockfilenpm ciflavor (pkgmgr-rs follow-up)🤖 Generated with Claude Code
Summary by CodeRabbit