[Feature]: system major updates #67

Open
opened 2026-09-25 14:56:31 +00:00 by bahrom04 · 3 comments
Owner

Feature Description

System updates in every rolling releases. Below some consepts.

  • Notification of new update
  • Details about update. Bug fixes, new features. Something like markdown file about update
  • Verify that update is relevand for this PC. Then download update. Make changes for system config in flake.nix. Inputs url change?
  • Apply now, apply on boot, update tonight? Cancel update
  • Stable, beta, nightly update channels
  • Auto download and auto updates, scheduled updates.
  • Hardware specific updata. A/B testing.
  • Remote builds or prebuild config.

TODO

Additional Context

Screenshot 2026-09-25 at 19.46.04

### Feature Description System updates in every rolling releases. Below some consepts. - Notification of new update - Details about update. Bug fixes, new features. Something like markdown file about update - Verify that update is relevand for this PC. Then download update. Make changes for system config in flake.nix. Inputs url change? - Apply now, apply on boot, update tonight? Cancel update - Stable, beta, nightly update channels - Auto download and [auto updates](https://wiki.nixos.org/wiki/Automatic_system_upgrades), scheduled updates. - Hardware specific updata. A/B testing. - Remote builds or prebuild config. ### TODO - Create adr design: https://adr.github.io/ ### Additional Context ![Screenshot 2026-09-25 at 19.46.04](/attachments/3c961165-e8f2-4741-bc96-c195b09f89d6)
bahrom04 added this to the 26.11 project 2026-09-25 14:56:31 +00:00
Owner

It is also necessary to write about what needs to be done on the server side.

It is also necessary to write about what needs to be done on the server side.
Owner

To send updates to the user:

I see two approaches:

  1. We could potentially store their configuration on the server.
  2. The user requests an update index—for instance, noting the date of their last update—and we check the difference in time.
To send updates to the user: I see two approaches: 1. We could potentially store their configuration on the server. 2. The user requests an update index—for instance, noting the date of their last update—and we check the difference in time.
Author
Owner

@lambdajon wrote in #67 (comment):

2. the date of their last update

1 and 2 argument both related to each other in my opinion

we could create custom nix options and write it down in updates.nix to track update log. For example

xinux.update = [
{
  status = "done";
  date = "2026.09.02 13:00";
  scheduled = true;
  duration = "45min"
 },
{
  status = "done";
  date = "2026.05.13 11:00";
  scheduled = false;
  duration = "38min"
 },
 ... # so on
];

Periodicly or in every relago report we could save or track this in case user touches /etc/nixos config

@lambdajon wrote in https://git.oss.uzinfocom.uz/xinux/settings/issues/67#issuecomment-5904: > 2\. the date of their last update 1 and 2 argument both related to each other in my opinion we could create custom nix options and write it down in updates.nix to track update log. For example ```nix xinux.update = [ { status = "done"; date = "2026.09.02 13:00"; scheduled = true; duration = "45min" }, { status = "done"; date = "2026.05.13 11:00"; scheduled = false; duration = "38min" }, ... # so on ]; ``` Periodicly or in every relago report we could save or track this in case user touches `/etc/nixos` config
Sign in to join this conversation.
No milestone
No project
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
xinux/settings#67
No description provided.