You keep fixing 'em, I'll keep… well, playing around at least.
Ok, I've updated to 0.15.1 (ea37c98, dated 5th March this year). I started a new branch for some updates I needed to perform, so
git pkgs branch add bk/vulns
This appeared to process all ~9k commits in the repo, but it was fast, so I didn't think much of it. Then I actually made my commit with an update (the diff-driver output was minimal, thank you!).
After #151, I thought the following would work:
but it said "Analyzing 28 commits on origin/main"—interesting! Well, I can always do
git pkgs reindex -b bk/vulns
(it analyzes the 1 new commit and finds that it has dependency changes). Oddly, though, git show (with diff drivers) shows just one version change in package-lock.json. Meanwhile, git pkgs show shows 103 package changes… from version X to version X! In other words, no actual changes (and it omits the one of interest). How bizarre.
I'm not sure whether to class this as user error or a bug given the weird reindexing bit, so… let me know what you think :)
You keep fixing 'em, I'll keep… well, playing around at least.
Ok, I've updated to 0.15.1 (ea37c98, dated 5th March this year). I started a new branch for some updates I needed to perform, so
This appeared to process all ~9k commits in the repo, but it was fast, so I didn't think much of it. Then I actually made my commit with an update (the diff-driver output was minimal, thank you!).
After #151, I thought the following would work:
but it said "Analyzing 28 commits on origin/main"—interesting! Well, I can always do
(it analyzes the 1 new commit and finds that it has dependency changes). Oddly, though,
git show(with diff drivers) shows just one version change inpackage-lock.json. Meanwhile,git pkgs showshows 103 package changes… from versionXto versionX! In other words, no actual changes (and it omits the one of interest). How bizarre.I'm not sure whether to class this as user error or a bug given the weird reindexing bit, so… let me know what you think :)