Skip to content

Releases

v0.5.4

Choose a tag to compare

@github-actions github-actions released this 27 Oct 14:54

Changed

  • Updated dependencies: vitest to 5.0.5, @vitest/coverage-v8 to 5.0.5,
    jsdom to 30.1.3, and @types/node to 26.6.5.

Full Changelog: https://github.com/andiapps-dev/vscode-git-log-viewer/commits/v0.5.4

v0.5.3

Choose a tag to compare

@github-actions github-actions released this 03 Oct 15:16

Added

  • F5 to refresh — while a Git Log Viewer panel is focused, F5 re-fetches
    the commit list (or compare view) from git instead of falling through to
    VS Code's own default F5 behavior. A real contributed keybinding (not a
    hardcoded shortcut), so it's rebindable like any other command via
    Keyboard Shortcuts, and scoped to only this extension's own panels —
    F5 continues to behave normally everywhere else (e.g. starting a debug
    session).
  • A status bar item ("Git Log") for one-click access to the full
    repository log regardless of which file or folder is selected — in a
    single-folder workspace, the repo root has no right-clickable row in
    the Explorer at all (it's only shown as the panel's own title text), so
    this is the fix for that gap. Also available via the Command Palette
    ("Git Log Viewer: Show Git Log for Repository Root").
  • Ctrl+Alt+] / Cmd+Alt+] now falls back to the repository root log when
    nothing is focused (no active editor), instead of doing nothing —
    unchanged when a file is focused, which still shows that file's log.
  • The Refresh item in both right-click menus now shows F5 next to it,
    matching the keybinding that triggers it.

Fixed

  • Comparing two revisions had no working way to refresh from its
    right-click menu — the Refresh item was present but unconditionally
    hidden regardless of mode, a leftover from when it was deliberately
    hidden for the main log view (which has its own Refresh on the commit
    list instead). Compare view has no such alternative, so this left it
    with no menu-driven way to refresh at all.

Changed

  • Updated dependencies: vitest to 5.0.1, @vitest/coverage-v8 to 5.0.1,
    jsdom to 30.1.1, @types/node to 26.6.2, and @vscode/vsce to 4.0.0.

Full Changelog: https://github.com/andiapps-dev/vscode-git-log-viewer/commits/v0.5.3

v0.5.2

Choose a tag to compare

@github-actions github-actions released this 11 Sep 19:49

Changed

  • Raised the minimum required VS Code version from 1.85.0 to 1.136.0, to
    match @types/vscode's own bump to 1.136.0 — vsce refuses to package
    the extension otherwise, since the declared minimum has to cover
    whatever the type definitions expose. Users on VS Code older than
    1.136 will no longer be able to install or update the extension.
  • Updated dependencies: vitest to 5.0.0, @vitest/coverage-v8 to
    5.0.0, jsdom to 30.0.1, @types/node to 26.5.0, and the
    github/codeql-action GitHub Action to v4.
  • Raised the Node version used to build and test the extension (Docker
    images in build.sh/install.sh/test.sh/the demo scripts, and CI's
    actions/setup-node) from 20 to 22 — required by vitest 5 and
    jsdom 30, both of which dropped Node 20 support. This only affects
    the dev/CI toolchain, not the shipped extension itself (esbuild's
    bundled output is unaffected by the Node version it was built with).

Full Changelog: v0.5.1...v0.5.2

v0.5.1

Choose a tag to compare

@github-actions github-actions released this 02 Sep 20:50

Changed

  • Updated typescript to 7.0.2 (the new Go-ported compiler). Required adding an explicit
    "types": ["node"] to tsconfig.json — the new compiler no longer auto-discovers
    @types/node's ambient globals (path, fs, Buffer, process, etc.) without it.
    Dev-tooling only; the built extension is unaffected (esbuild does its own
    transpilation and never invokes tsc).

Full Changelog: v0.5.0...v0.5.1

v0.5.0

Choose a tag to compare

@github-actions github-actions released this 02 Sep 20:27

Added

  • Commit Graph — the commit list's leftmost column now draws branch/merge topology
    as a graph: one lane per line of development, colored consistently down its length,
    connected by smooth curves at every branch and merge point, with a hover tooltip on
    each commit's dot showing which branches/tags it's actually reachable from. Works in
    the main log, File Log, and Folder View alike, stays correctly connected while
    filtering, and is hidden automatically whenever the list isn't in git's own log order
    (a column sort is active, or in Line History mode).

Fixed

  • Fixed git log --follow (used for any single-file "Show File Log" view) silently
    returning duplicate commits once pagination reached a second page — --follow's
    internal rename-tracking doesn't compose correctly with --skip, a known git
    limitation. A scoped file's whole history is now fetched in one shot and paginated
    in-process instead of relying on git's own --skip for that case.

Full Changelog: v0.4.10...v0.5.0

v0.4.10

Choose a tag to compare

@github-actions github-actions released this 30 Aug 18:39

Added

  • Branches submenu — scope the commit list to specific branches (multi-select) or
    all branches, instead of just the checked-out branch, via a "Branches" item on the
    commit list's right-click menu.
  • View Line History — a new "Show Line History" command (editor right-click menu and
    Command Palette) shows the history of just the currently selected line(s).
  • View File Contents — a new action in the changed-files context menu opens a file's
    content at a given revision in a read-only tab, instead of only ever showing it as one
    side of a diff.
  • Folder View — a toggle in the changed-files context menu groups the list by
    directory instead of a flat list.
  • "Show Git Log" now also appears as an icon button in the editor tab bar and the Source
    Control panel title, in addition to the existing right-click menu and keyboard shortcut.
  • New gitLogViewer.pageSize setting to configure how many commits load per batch
    (default 100).

Fixed

  • Fixed a flaky test (formatTimeAgo's 59-second boundary case) that compared against
    real wall-clock time captured at a different moment than the function's own internal
    clock read, occasionally flipping the result across a minute boundary. Frozen fake
    timers now guarantee both reads see the same instant.
  • Fixed an intermittent error: Could not read <sha> / could not parse commit <sha>
    failure in the test suite's git fixture builder, seen only on GitHub-hosted CI runners.
    Root cause: git's gc --auto can trigger in a detached background process once a repo
    accumulates enough loose objects (this fixture creates 300+ commits across several
    branches), and a later git command in the same build can lose the race against that
    background repack. Disabled gc.auto for these throwaway, immediately-deleted repos.

Changed

  • Updated dependencies: vitest to 4.1.10, @vitest/coverage-v8 to 4.1.11, esbuild to
    0.28.2, @types/node to 26.1.2, c8 to 12.0.0, and the actions/checkout,
    actions/setup-node, actions/upload-artifact, actions/download-artifact, and
    softprops/action-gh-release GitHub Actions to their latest majors.
  • vitest.config.ts → vitest.config.mts, and dropped __dirname in favor of
    import.meta.dirname, ahead of a future Vite major version that removes the
    CommonJS-config-loading fallback these relied on.

Full Changelog: https://github.com/andiapps-dev/vscode-git-log-viewer/commits/v0.4.10