2025-12-02 -> 2025-12-16 #70
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DankMaterialShell's author decided to be dumb and destroyed their git commit history, and apparently also broke the way their app and flake works too.. fun. I've gone ahead and fixed it, though this entire situation has made me want to quit using this shell entirely. On other, more pleasant news, we are now on the latest NixOS release. The most noticable change should be the update to GNOME 49. I don't visually notice much but I did notice an airplane mode button, cute. Lix 2.94 also released and removed the `no-url-literals` experimental feature, since it has now become a default. This is yet again another breaking change from upstream, since having this in your experimental features list will error out. Fair enough I suppose, though it does become a little annoying when one setup doesn't translate to the other cleanly. Overall a good change though, so I suppose there's that to be happy about.
I updated `nixpkgs`, `home-manager`, and `stylix`, mainly to stop the version mismatch warning.
DankMaterialShell changed their flake in a backwards incompatible way (again). This time, they've pinned quickshell as their own input, and also changed their package to `dms-shell`, which comprises both the Quickshell configuration as well as the CLI application (formerly known as `dankMaterialShell` and `dmsCli` respectively).
Instead of attaching both possible options into one, I dynamically generate the options based on which Nix variant is being used.
I feel like 20 runs is mildly excessive. It takes up a lot of CI time and from local testing, doesn't seem to really improve the accuracy of the final time measurement. At the very least, the accuracy is negligible compared to the runtime cost, so I'm dropping it by many factors. Warmup runs are going from 5 -> 4, and full runs are going from 20 -> 8.
This also adds the OpenRazer daemon, as that is the backend that Polychromatic communicates with.
The most important of these is the Polychromatic cache, and the OpenRazer config. I'm unsure if I really care much about the Polychromatic config, but for now I'm keeping it.
Frontear
commented
Dec 15, 2025
Doesn't make much sense, since peripherals can be swapped at any time.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello there, another bi-weekly staging cycle has started up. The last cycle was 2025-11-10 -> 2025-11-30.
Breaking Changes
New Features
nix-benchmark(cfec198)flake.lock(ff7cfd7)Fixes
nix-benchmark(49b8a89)