Skip to content

v1.2.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 25 Sep 17:02
· 157 commits to main since this release
v1.2.0
42e0166
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Attack Shark Linux v1.2.0 — First Stable Release

Attack Shark Linux is a desktop configurator for the Attack Shark X6 mouse on Linux. This is its first stable-version release: a single application for monitoring the mouse, adjusting its settings, and installing future updates with your approval. It is not affiliated with or endorsed by Attack Shark.

Configure your X6

  • Performance: configure up to eight DPI stages, select a polling rate from 125 to 1000 Hz, and adjust response time, sleep timing, and other supported mouse settings.
  • Lighting: choose lighting effects and colors from the dedicated configuration view.
  • Buttons: assign basic, multimedia, scrolling, and DPI actions to supported buttons. Changes can be reviewed before they are applied.
  • Live status: see battery and physical DPI changes reported by the dongle. The Device view also shows connection information and the installed application version.
  • Recovery: keep settings locally per device, across app restarts where the device identity permits it, and restore factory defaults when needed. Local settings are not profiles stored in the mouse.

The interface includes dedicated views for these controls, as well as minimize and close buttons. It does not require a tray application or a background service.

Install and update

Download install.sh from this release’s assets to install the user-local x86_64 AppImage. On the first installation, --install-udev offers to set up the X6 access rule; the installer asks for confirmation before using sudo. Do not run the application as root.

The installer and updater verify an Ed25519-signed release manifest and the AppImage’s SHA-256 digest. Updates require explicit approval in the app, shown in a persistent card at the upper right. An update replaces only the installed user-local AppImage: it does not change udev rules or request elevated privileges. Stable installations stay on the stable update channel; RC installations do not automatically switch to stable and should use the stable installer explicitly.

Release validation

The signed RC.4→RC.5 rehearsal replaced the installed AppImage with bytes matching the published RC.5 digest. The maintainer observed the persistent in-app card and the application relaunch. The changes subsequently added for this stable candidate passed the PR’s Go, frontend, and security checks. The stable tag’s release workflow runs its own checks before publishing its assets.

Current limits

Macros and profiles stored on the mouse are not included. DEB, RPM, and AUR packages are not provided; the supported release artifact is the Linux x86_64 AppImage.

Assets 7
Loading