ending your lucky days

i will be assuming you use flakes, or atleast i do. your process may differ tho

step zero: check if there is really not an update yet

using nix package search you can find out if the update is already present in another channel.

and yes ive done so much work when i could just use another channel lol

step one: getting hash and latest version

download the latest release and take note of the version numbers, in my case 0.0.93

when finished downloading we will use nix-hash to get the hash.

> nix-hash --base64 --type sha256 --flat ./discord-0.0.93.tar.gz
/CTgRWMi7RnsIrzWrXHE5D9zFte7GgqimxnvJTj3hFY=

step two: fork nixpkgs and updating it

fork the nix channel you are using

i just reccomend doing it on github, as it will save your ass trying to build nix from a local git repo

find the discord/default.nix file and change the version number and the hash

# Version
{
  #stable = "0.0.91";
  stable = "0.0.93";
  ptb = "0.0.136";
  canary = "0.0.649";
  development = "0.0.73";
}

# Hash
{
  x86_64-linux = {
    stable = fetchurl {
      url = "https://stable.dl2.discordapp.net/apps/linux/${version}/discord-${version}.tar.gz";
      #hash = "sha256-vGRK1YJoaM4+tUaQd4f7ImaVnUkAdjH+RW7r+bOMx6I=";
      hash = "sha256-/CTgRWMi7RnsIrzWrXHE5D9zFte7GgqimxnvJTj3hFY=";
    };
  };
}

push it to github, and then set your flake and boom. it should work

okay byee