Skip to content

GitBolt 0.3.0

Choose a tag to compare

@github-actions github-actions released this 08 Oct 02:43
· 60 commits to main since this release
d49ddcc

Added

  • Windows: GitBolt builds, runs and installs on Windows 10 and 11: an NSIS installer (per user,
    no administrator rights) and an MSI (per machine), both unsigned for now, so SmartScreen warns.
    Chromium runs sandboxed, as on Linux. Editors and IDEs, File Explorer, Open with and the folder
    picker use Windows' own.
  • Updates from GitHub Releases. GitBolt checks for a new release at startup and once a day
    (Settings › Updates, with Include pre-releases), and on Help › Check for updates. A pill at
    the bottom right downloads the package for your install, checks it against the release's
    SHA256SUMS, and installs it: through your desktop's password prompt (pkexec) on Linux, then Restart
    GitBolt
    ; on Windows by starting the installer. GitBolt's own version is in the status bar.
  • Reply and resolve (or unresolve) beside Reply in a resolvable thread (Ctrl+Shift+Enter).
  • Software centre metadata in the Linux packages. A .deb opened in GNOME Software, Ubuntu's App
    Center or Discover now shows the homepage and a full description, and GNOME Software the MIT
    license; none of them shows a package's icon before it's installed. Once installed, GitBolt
    has AppStream metadata (dev.gitbolt.desktop: description, license, links, screenshot and
    release history), icons from 32 px to 512 px, and a Debian machine-readable copyright file.
    The Arch package lists the licenses of the code it bundles, not only MIT.

Changed

  • Push tags with branches is on by default: a push also sends the annotated tags on the pushed
    commits that the remote lacks (--follow-tags), so a release's tag goes out with its commit.
    A settings file that already has it off keeps it off.

Fixed

  • A repeat request GitHub answered with "not modified" failed ("gzip decompression failed"): GitHub
    labels those empty answers as gzipped. It affected the update check and GitHub MR/PR polling.
  • In the rendered Markdown diff, an edited heading (## Windows (in progress) → ## Windows) or
    short block showed as removed and added; it now shows as one change, its words diffed.
  • A GitLab thread's own system note ("changed this line in version 3 of the diff") showed at the
    bottom of the MR's timeline; it now shows inside its thread.
  • GitLab images that an older build had failed to load stayed missing for a day (its "not found" was
    remembered); images are now asked for again. An upload's Open in browser uses GitLab's
    /-/project/<id>/uploads/… address, the one GitLab 17 and later serve.