Skip to content

2026-02-25 -> 2026-03-25#73

Draft
Frontear wants to merge 5 commits intomainfrom
staging
Draft

2026-02-25 -> 2026-03-25#73
Frontear wants to merge 5 commits intomainfrom
staging

Conversation

@Frontear
Copy link
Owner

@Frontear Frontear commented Feb 25, 2026

Hello there! A new staging cycle has been started up. The last cycle was 2026-01-23 -> 2026-02-20.

As per the convention set forth by the previous cycle, this one has its duration extended to 4 weeks to accommodate my priorities to school. Small maintenance and upkeep of the system is the main goal of this cycle, with some (hopefully) minor updates to existing systems to make them work smoother.

Breaking Changes

TODO

New Features

  • feat: add support for Canadian English to VSCode cSpell (72e83b5)
  • feat: bump flake.lock (1b9a942)
  • feat: configure Java extension to stop misbehaving (3789360)
  • feat: add placeholder envrc files for templates (f2109ec)

Fixes

  • fix: rollback nh to avoid specialisation issue (c01b5b8)

The base extension only supports US and UK English; other languages need to be installed as separate extensions. Nixpkgs only has German and French packaged, so I had to pull it myself locally. I think it'd be a good idea for me to submit the other languages up to Nixpkgs at some point in the future.
Everything works completely fine with no changes required. I saw some minor version updates but nothing particularly noteworthy in that regard.
The extension seems to get confused when there are too many different `*.java` files lying around, and on occasion isn't able to correctly determine if the project is using Gradle, which causes it to misbehave (example being that it creates `bin` folders with the compiled `.class` files, rather than leaving that to Gradle). Forcing it to be selected manually is a safer, albiet slightly more tedious option.

Furthermore, the extension doesn't automatically reload the project when Gradle files change, which is usually something that people would want, hence I'm enabling that by default.
In the latest version of nh (version 4.3.0), some changes were done to simplify the process of configuration switching, which broke how specialisations were setup. Currently, if you don't invoke nh with `--no-specialisation`, nh will not attempt to install the specialisation, and will instead only install whatever you're currently booted into. That means, if I run `nh os boot .` from GNOME, then only GNOME is installed, which is obviously a problem.

In an effort to avoid the issue entirely, I'm simply rolling back to version 4.2.0. Once the issue has been resolved upstream, I'll bump back to the latest.
The reason I am adding these is because they include a very nice snippet (courtesy of a fellow NixOS user) that can sync the revisions of certain flake inputs from the system registry for that localized flake. This de-duplicates the various nixpkgs flake inputs that I have by making them mostly all consistent, but without using the weird semantics of the flake registry in the flake inputs directly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant