Skip to content

Atomic Bomberman 0.7.5

Latest

Choose a tag to compare

@github-actions github-actions released this 11 Nov 13:07
· 3 commits to main since this release

Atomic Bomberman 0.7.5, built from 5069899f407ec8d54e4a5804a5ef6e2475635e93.

0.7.5

  • Support Ubuntu 22.04 and newer, plus compatible x86-64 Linux distributions
    with glibc 2.35 or newer and X11/XWayland. The AppImage's launcher, game,
    helpers and bundled libraries are built on Ubuntu 22.04.
  • Fix startup with newer Mesa/LLVM graphics drivers by using the system's
    GCC/C++ runtimes alongside its graphics drivers.
  • Rename the Linux download to atomic-bomberman-0.7.5-x86_64.AppImage, with
    matching checksum and build-manifest names.
  • Check the same AppImage on Ubuntu 22.04, 24.04, 26.04 and Debian 12, then run
    AppImageHub's unchanged catalog checker before publication. Packaging and
    release verification reject bundled ELF requirements above glibc 2.35.

Ordinary AppImage startup continues to work without FUSE. Original game data,
completed HD packs, mods, settings and private server links remain usable.
Protocol 8 and the 0.7.0 compatibility family are unchanged; compatible existing
clients and relays can continue playing together. Physical graphics, audio and
controller hardware are separate from the automated software-rendering checks.

Release verification: published packages, compatibility checks, and deployed relay.

Linux packaging update (2026-11-12)

The existing v0.7.5 Linux AppImage now includes AppStream metadata with a gameplay screenshot, plus the stable GitHub Releases update channel and a matching .AppImage.zsync file for AppImageUpdate-compatible tools. Game executables and bundled libraries are unchanged. The small bootstrap was rebuilt on Ubuntu 22.04 to handle update-information queries. The build manifest records the original package and all repackaging inputs; the version tag remains unchanged.

Updated AppImage SHA-256: 51bed3d7607b278085f6922967a357f9bbba693b2de53fee808cb9698e7256b8.

AppImageHub retest passed and catalogue refresh merged. The official AppImageUpdate CLI detected the same-version replacement, reconstructed the exact published AppImage, and confirmed no further update was needed.