Epsilon_02/niri
1
0
Fork 0
mirror of https://github.com/YaLTeR/niri.git synced 2025-10-05 16:12:47 +02:00
Code Issues Packages Projects Releases Wiki Activity

Bump version to 25.08

Browse Source
This commit is contained in:
Ivan Molodetskikh
2025-08-27 14:20:22 +03:00
parent ddb9dd407d
commit af4b5f99e9
16 changed files with 32 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
Cargo.lock generated
View File

@@ -2351,7 +2351,7 @@ dependencies = [
[[package]]
name = "niri"
version = "25.5.1"
version = "25.8.0"
dependencies = [
"accesskit",
"accesskit_unix",
@@ -2411,7 +2411,7 @@ dependencies = [
[[package]]
name = "niri-config"
version = "25.5.1"
version = "25.8.0"
dependencies = [
"bitflags 2.9.3",
"csscolorparser",
@@ -2428,7 +2428,7 @@ dependencies = [
[[package]]
name = "niri-ipc"
version = "25.5.1"
version = "25.8.0"
dependencies = [
"clap",
"schemars",
@@ -2438,7 +2438,7 @@ dependencies = [
[[package]]
name = "niri-visual-tests"
version = "25.5.1"
version = "25.8.0"
dependencies = [
"anyhow",
"gtk4",

6
Cargo.toml
View File

@@ -6,7 +6,7 @@ members = [
]
[workspace.package]
version = "25.5.1"
version = "25.8.0"
description = "A scrollable-tiling Wayland compositor"
authors = ["Ivan Molodetskikh <yalterz@gmail.com>"]
license = "GPL-3.0-or-later"
@@ -74,8 +74,8 @@ keyframe = { version = "1.1.1", default-features = false }
libc = "0.2.175"
libdisplay-info = "0.2.2"
log = { version = "0.4.27", features = ["max_level_trace", "release_max_level_debug"] }
niri-config = { version = "25.5.1", path = "niri-config" }
niri-ipc = { version = "25.5.1", path = "niri-ipc", features = ["clap"] }
niri-config = { version = "25.8.0", path = "niri-config" }
niri-ipc = { version = "25.8.0", path = "niri-ipc", features = ["clap"] }
ordered-float = "5.0.0"
pango = { version = "0.20.12", features = ["v1_44"] }
pangocairo = "0.20.10"

2
docs/wiki/Accessibility.md
View File

@@ -1,6 +1,6 @@
## Screen readers
<sup>Since: next release</sup>
<sup>Since: 25.08</sup>
Niri has basic support for screen readers (specifically, [Orca](https://orca.gnome.org)) when running as a full desktop session, i.e. not as a nested window.
We implement the `org.freedesktop.a11y.KeyboardMonitor` D-Bus interface for Orca to listen and grab keyboard keys, and we expose the main niri UI elements via [AccessKit](https://accesskit.dev).

4
docs/wiki/Configuration:-Animations.md
View File

@@ -91,7 +91,7 @@ You can get a feel for them on pages like [easings.net](https://easings.net/).
- `ease-out-cubic`
- `ease-out-expo`
- `linear` <sup>Since: 0.1.6</sup>
- `cubic-bezier` <sup>Since: next release</sup>
- `cubic-bezier` <sup>Since: 25.08</sup>
A custom [cubic Bézier curve](https://www.w3.org/TR/css-easing-1/#cubic-bezier-easing-functions). You need to set 4 numbers defining the control points of the curve, for example:
```kdl
animations {
@@ -379,7 +379,7 @@ animations {
#### `exit-confirmation-open-close`
<sup>Since: next release</sup>
<sup>Since: 25.08</sup>
The open/close animation of the exit confirmation dialog.

6
docs/wiki/Configuration:-Debug-Options.md
View File

@@ -263,7 +263,7 @@ debug {
### `skip-cursor-only-updates-during-vrr`
<sup>Since: next release</sup>
<sup>Since: 25.08</sup>
Skips redrawing the screen from cursor input while variable refresh rate is active.
@@ -279,7 +279,7 @@ debug {
### `deactivate-unfocused-windows`
<sup>Since: next release</sup>
<sup>Since: 25.08</sup>
Some clients (notably, Chromium- and Electron-based, like Teams or Slack) erroneously use the Activated xdg window state instead of keyboard focus for things like deciding whether to send notifications for new messages, or for picking where to show an IME popup.
Niri keeps the Activated state on unfocused workspaces and invisible tabbed windows (to reduce unwanted animations), surfacing bugs in these applications.
@@ -295,7 +295,7 @@ debug {
### `keep-max-bpc-unchanged`
<sup>Since: next release</sup>
<sup>Since: 25.08</sup>
When connecting monitors, niri sets their max bpc to 8 in order to reduce display bandwidth and to potentially allow more monitors to be connected at once.
Restricting bpc to 8 is not a problem since we don't support HDR or color management yet and can't really make use of higher bpc.

6
docs/wiki/Configuration:-Input.md
View File

@@ -147,7 +147,7 @@ input {
> [!NOTE]
>
> <sup>Since: next release</sup>
> <sup>Since: 25.08</sup>
>
> If the `xkb` section is empty (like it is by default), niri will fetch xkb settings from systemd-localed at `org.freedesktop.locale1` over D-Bus.
> This way, for example, system installers can dynamically set the niri keyboard layout.
@@ -235,7 +235,7 @@ A few settings are common between `touchpad`, `mouse`, `trackpoint`, and `trackb
- `scroll-method`: when to generate scroll events instead of pointer motion events, can be `no-scroll`, `two-finger`, `edge`, or `on-button-down`.
The default and supported methods vary depending on the device type.
- `scroll-button`: <sup>Since: 0.1.10</sup> the button code used for the `on-button-down` scroll method. You can find it in `libinput debug-events`.
- `scroll-button-lock`: <sup>Since: next release</sup> when enabled, the button does not need to be held down. Pressing once engages scrolling, pressing a second time disengages it, and double click acts as single click of the the underlying button.
- `scroll-button-lock`: <sup>Since: 25.08</sup> when enabled, the button does not need to be held down. Pressing once engages scrolling, pressing a second time disengages it, and double click acts as single click of the the underlying button.
- `left-handed`: if set, changes the device to left-handed mode.
- `middle-emulation`: emulate a middle mouse click by pressing left and right mouse buttons at once.
@@ -254,7 +254,7 @@ Settings specific to `touchpad` and `mouse`:
- `scroll-factor`: <sup>Since: 0.1.10</sup> scales the scrolling speed by this value.
<sup>Since: next release</sup> You can also override horizontal and vertical scroll factor separately like so: `scroll-factor horizontal=2.0 vertical=-1.0`
<sup>Since: 25.08</sup> You can also override horizontal and vertical scroll factor separately like so: `scroll-factor horizontal=2.0 vertical=-1.0`
Settings specific to `tablet`s:

2
docs/wiki/Configuration:-Key-Bindings.md
View File

@@ -252,7 +252,7 @@ binds {
#### `spawn-sh`
<sup>Since: next release</sup>
<sup>Since: 25.08</sup>
Run a command through the shell.

8
docs/wiki/Configuration:-Miscellaneous.md
View File

@@ -74,7 +74,7 @@ Thanks to this, apps that you configured to autostart in GNOME will also "just w
### `spawn-sh-at-startup`
<sup>Since: next release</sup>
<sup>Since: 25.08</sup>
Add lines like this to run shell commands at niri startup.
@@ -235,7 +235,7 @@ overview {
### `xwayland-satellite`
<sup>Since: next release</sup>
<sup>Since: 25.08</sup>
Settings for integration with [xwayland-satellite](https://github.com/Supreeeme/xwayland-satellite).
@@ -286,7 +286,7 @@ hotkey-overlay {
#### `hide-not-bound`
<sup>Since: next release</sup>
<sup>Since: 25.08</sup>
By default, niri will show the most important actions even if they aren't bound to any key, to prevent confusion.
Set the `hide-not-bound` flag if you want to hide all actions not bound to any key.
@@ -301,7 +301,7 @@ You can customize which binds the hotkey overlay shows using the [`hotkey-overla
### `config-notification`
<sup>Since: next release</sup>
<sup>Since: 25.08</sup>
Settings for the config created/failed notification.

2
docs/wiki/FAQ.md
View File

@@ -60,7 +60,7 @@ A combination of factors:
All in all, the situation works out in favor of avoiding Xwayland integration.
<sup>Since: next release</sup> niri has seamless built-in xwayland-satellite integration that by and large works as well as built-in Xwayland in other compositors, solving the hurdle of having to set it up manually.
<sup>Since: 25.08</sup> niri has seamless built-in xwayland-satellite integration that by and large works as well as built-in Xwayland in other compositors, solving the hurdle of having to set it up manually.
I wouldn't be too surprised if, down the road, xwayland-satellite becomes the standard way of integrating Xwayland into new compositors, since it takes on the bulk of the annoying work, and isolates the compositor from misbehaving clients.

6
docs/wiki/Integrating-niri.md
View File

@@ -17,7 +17,7 @@ Splitting the niri config file into multiple files, or includes, are not support
Xwayland is required for running X11 apps and games, and also the Orca screen reader.
<sup>Since: next release</sup> Niri integrates with [xwayland-satellite](https://github.com/Supreeeme/xwayland-satellite) out of the box.
<sup>Since: 25.08</sup> Niri integrates with [xwayland-satellite](https://github.com/Supreeeme/xwayland-satellite) out of the box.
The integration requires xwayland-satellite >= 0.7 available in `$PATH`.
Please consider making niri depend on (or at least recommend) the xwayland-satellite package.
If you had a custom config which manually started `xwayland-satellite` and set `$DISPLAY`, you should remove those customizations for the automatic integration to work.
@@ -26,7 +26,7 @@ You can change the path where niri looks for xwayland-satellite using the [`xway
### Keyboard layout
<sup>Since: next release</sup> By default (unless [manually configured](./Configuration:-Input.md#layout) otherwise), niri reads keyboard layout settings from systemd-localed at `org.freedesktop.locale1` over D-Bus.
<sup>Since: 25.08</sup> By default (unless [manually configured](./Configuration:-Input.md#layout) otherwise), niri reads keyboard layout settings from systemd-localed at `org.freedesktop.locale1` over D-Bus.
Make sure your system installer sets the keyboard layout via systemd-localed, and niri should pick it up.
### Autostart
@@ -41,7 +41,7 @@ If this is inconvenient, you can also add [`spawn-at-startup`](./Configuration:-
### Screen readers
<sup>Since: next release</sup> Niri works with the [Orca](https://orca.gnome.org) screen reader.
<sup>Since: 25.08</sup> Niri works with the [Orca](https://orca.gnome.org) screen reader.
Please see the [Accessibility](./Accessibility.md) page for details and advice for accessibility-focused distributions.
### Desktop components

2
docs/wiki/Nvidia.md
View File

@@ -42,7 +42,7 @@ The fix shipped in the driver at the time of writing uses a value of 0, while th
### Screencast flickering fix
<sup>Until: next release</sup>
<sup>Until: 25.08</sup>
If you have screencast glitches or flickering on NVIDIA, set this in the niri config:

4
docs/wiki/Xwayland.md
View File

@@ -1,8 +1,6 @@
## Using xwayland-satellite
<sup>Since: next release</sup>
Niri integrates with [xwayland-satellite](https://github.com/Supreeeme/xwayland-satellite) out of the box.
<sup>Since: 25.08</sup> Niri integrates with [xwayland-satellite](https://github.com/Supreeeme/xwayland-satellite) out of the box.
Ensure xwayland-satellite >= 0.7 is installed and available in `$PATH`.
With no further configuration, niri will create X11 sockets on disk, export `$DISPLAY`, and spawn xwayland-satellite on-demand when an X11 client connects.
If xwayland-satellite dies, niri will automatically restart it.

2
niri-config/Cargo.toml
View File

@@ -12,7 +12,7 @@ bitflags.workspace = true
csscolorparser = "0.7.2"
knuffel = "3.2.0"
miette = { version = "5.10.0", features = ["fancy-no-backtrace"] }
niri-ipc = { version = "25.5.1", path = "../niri-ipc" }
niri-ipc = { version = "25.8.0", path = "../niri-ipc" }
regex = "1.11.2"
smithay = { workspace = true, features = ["backend_libinput"] }
tracing.workspace = true

2
niri-ipc/README.md
View File

@@ -12,5 +12,5 @@ Use an exact version requirement to avoid breaking changes:
```toml
[dependencies]
niri-ipc = "=25.5.1"
niri-ipc = "=25.8.0"
```

2
niri-ipc/src/lib.rs
View File

@@ -41,7 +41,7 @@
//!
//! ```toml
//! [dependencies]
//! niri-ipc = "=25.5.1"
//! niri-ipc = "=25.8.0"
//! ```
//!
//! ## Features

4
niri-visual-tests/Cargo.toml
View File

@@ -11,8 +11,8 @@ repository.workspace = true
adw = { version = "0.7.2", package = "libadwaita", features = ["v1_4"] }
anyhow.workspace = true
gtk = { version = "0.9.7", package = "gtk4", features = ["v4_12"] }
niri = { version = "25.5.1", path = ".." }
niri-config = { version = "25.5.1", path = "../niri-config" }
niri = { version = "25.8.0", path = ".." }
niri-config = { version = "25.8.0", path = "../niri-config" }
smithay.workspace = true
tracing.workspace = true
tracing-subscriber.workspace = true