Snap Store release stuck on v26.1.22 due to expired Snapcraft credentials in CI/CD pipeline

### What system are you running Yazi on? Linux X11 ### What terminal are you running Yazi in? kitty v0.47.0 ### `yazi --debug` output ```Shell Yazi Version: 26.1.22 (4e0acf8c 2026-01-22) Debug : false Triple : x86_64-unknown-linux-gnu (linux-x86_64) Rustc : 1.93.0 (254b5960 2026-01-19) Ya Version: No such file or directory (os error 2) Config Init : /home/geekboy/.config/yazi/init.lua (31 chars) Yazi : /home/geekboy/.config/yazi/yazi.toml (25 chars) Keymap : /home/geekboy/.config/yazi/keymap.toml (No such file or directory (os error 2)) Theme : /home/geekboy/.config/yazi/theme.toml (26 chars) VFS : /home/geekboy/.config/yazi/vfs.toml (No such file or directory (os error 2)) Package : /home/geekboy/.config/yazi/package.toml (216 chars) Dark/light flavor: "dracula" / "" Emulator TERM : Some("xterm-kitty") TERM_PROGRAM : None TERM_PROGRAM_VERSION: None Brand.from_env : Some(Kitty) Emulator.detect : Emulator { kind: Left(Kitty), version: "kitty(0.47.0)", light: false, csi_16t: (14, 32), force_16t: false } Adapter Adapter.matches : Kgp Dimension.available: Dimension { rows: 31, columns: 137, width: 1918, height: 992 } Desktop XDG_SESSION_TYPE : Some("x11") WAYLAND_DISPLAY : None DISPLAY : Some(":0") SWAYSOCK : None HYPRLAND_INSTANCE_SIGNATURE: None WAYFIRE_SOCKET : None SSH shared.in_ssh_connection: false WSL WSL: false Variables SHELL : Some("/bin/bash") EDITOR : Some("code --wait") VISUAL : Some("code --wait") YAZI_FILE_ONE : None YAZI_CONFIG_HOME : None YAZI_ZOXIDE_OPTS : None FZF_DEFAULT_OPTS : None FZF_DEFAULT_COMMAND: None Text Opener default : Some(OpenerRule { run: "${EDITOR:-vi} %s", block: true, orphan: false, desc: "$EDITOR", for: None, spread: true }) block-create: Some(OpenerRule { run: "${EDITOR:-vi} %s", block: true, orphan: false, desc: "$EDITOR", for: None, spread: true }) block-rename: Some(OpenerRule { run: "${EDITOR:-vi} %s", block: true, orphan: false, desc: "$EDITOR", for: None, spread: true }) Multiplexers TMUX : false tmux version : No such file or directory (os error 2) tmux build flags : enable-sixel=Unknown ZELLIJ_SESSION_NAME: None Zellij version : No such file or directory (os error 2) Dependencies file : 5.45 ueberzugpp : No such file or directory (os error 2) ffmpeg/ffprobe: 6.1.1-3 / 6.1.1-3 pdftoppm : 24.02.0 magick : ExitStatus(unix_wait_status(32512)), "magick: error while loading shared libraries: libgomp.so.1: cannot open shared object file: No such file or directory\n" fzf : 0.44.1 fd/fdfind : 9.0.0 / 9.0.0 rg : 14.1.0 chafa : 1.14.0 zoxide : 0.9.3 7zz/7z : 23.01 / 23.01 resvg : No such file or directory (os error 2) jq : 1.5 Clipboard wl-copy/paste: 2.2.1 / 2.2.1 xclip : 0.13 xsel : No such file or directory (os error 2) Routine `file -bL --mime-type`: text/plain See https://yazi-rs.github.io/docs/plugins/overview#debugging on how to enable logging or debug runtime errors. ``` ### Describe the bug The Snapcraft deployment for the stable channel seems to be stuck at version 26.1.22. Newer versions (like 26.5.6) are available on GitHub, but they are not reaching the Snap Store. I checked the GitHub Actions logs for the "Publish" workflow and noticed the "Promote snap to stable" step failed with an error: "Error fetching account information from store: The request is missing an Authorization header field containing a valid macaroon" Because of this, the Snap Store page shows a recent "Last Updated" timestamp matching the release date, but the actual binary version remains pointing to the old January build. I have attached screenshots of the failed runner log and the Snap Store page for reference. <img width="1392" height="207" alt="Image" src="https://github.com/user-attachments/assets/f59382cd-0779-4926-ab17-c1787ad86217" /> <img width="864" height="334" alt="Image" src="https://github.com/user-attachments/assets/1c265cc7-1b6e-4bfb-a2b4-9b94226ff719" /> ### Minimal reproducer N/A. This is a deployment pipeline failure on GitHub Actions, not an application bug. The reproduction step is visible in the repository's own Actions history: 1. Go to Actions -> Publish workflow logs for the recent releases. 2. Observe the failed "Promote snap to stable" step. ### Anything else? _No response_ ### Checklist - [x] I tried the [latest nightly build](https://yazi-rs.github.io/docs/installation#binaries), and the issue is still reproducible - [x] I updated the debug information (`yazi --debug`) input box to the nightly that I tried - [x] I can reproduce it after disabling all custom configs/plugins (`mv ~/.config/yazi ~/.config/yazi-backup`)