OpenRiot v8.0.14: Paint It Cyan
“I see a green bar and I want it painted cyan. No colors anymore, I want them to turn to cyan. I see the folders walk by dressed in their summer green. I have to turn my head until the accent goes cyan.” – The OpenRiot Crew, channeling Mick Jagger, v8.0.14
Release Overview
v8.0.14 is the cleanup crew that walks through after the painter. The accent moved to cyan in the last release; the hardcoded lime green stayed behind in the corners, waiting to be noticed.
The highlights in Thunar turn cyan. The dunst popup frames turn cyan. The crypto icon stops being a yellow taxi and joins the teal family. Gnome Text Editor stops defaulting to CypherRiot Dark and goes back to Tokyo Night Dark.
No new features. No new daemons. The last of the green, painted over, so the desktop matches itself for once.
The Green Mile, Retired
#9ECE6A had a long career. It was the accent, the selection,
the Thunar highlight, the dunst frame, the bright green that
arrived in v5 and never left. Every release that kept it owed
it a debt it did not ask for.
The color is retired. In config/gtk-3.0/gtk.css and
config/gtk-4.0/gtk.css, every #9ECE6A becomes #50c9c3,
the candy cyan the folders already wear. Selected files and
folders in Thunar now glow the same blue-green as the window
border, so the thing you clicked and the thing you are working
on argue about nothing.
The Green Mile was a fine movie. The green mile was a fine color. Both have had their closing credits.
Paint It Cyan
The Rolling Stones wanted to paint the red door black. We wanted to paint the yellow crypto icon cyan.
The polybar crypto module used ${colors.yellow}, a sand color
that read as a taxi light. It now uses ${colors.cyan}, the
same teal the battery already wore. The icon did not change.
Its shirt did.
Dunst follows. The global and normal popup frames move from
lime to #37a29c, the window-border cyan, so a notification
and the focused window now belong to the same family. Low stays
muted. Critical stays red. Only the everyday popups calm down.
Tokyo Night, Second Take
Gnome Text Editor kept waking up in CypherRiot Dark because
config/dconf/org.gnome.TextEditor.ini still pinned
style-scheme='cypherriot'. The gsettings command from
earlier was real, and the install file overwrote it on the next
run. The system had two answers and a strong opinion about
which one won.
The dconf default is now tokyo-night. The editor opens in
Tokyo Night Dark and stays there. The CypherRiot Dark theme
still exists in the tree for the people who choose it on
purpose.
The Push Button Retry
The release target used to run git push && git push origin
v8.0.13. One transient timeout on the first push left main
half-released and the tag stranded locally, which is the
software equivalent of leaving the house with one shoe.
It now pushes main and the tag together, with three attempts and a five second pause in between. A flaky connection costs you ten seconds instead of a broken release.
🧾 Files Changed
| File | Change |
|---|---|
config/gtk-3.0/gtk.css |
Thunar highlights green to cyan |
config/gtk-4.0/gtk.css |
Active tab underline cyan |
config/dunst/dunstrc |
Popup frame green to cyan |
config/polybar/config.ini.tmpl |
Crypto icon yellow to cyan |
config/dconf/org.gnome.TextEditor.ini |
Default tokyo-night |
Makefile |
Release push retries, tag bundled |
🗣️ Final Words
“The green is gone. The yellow is gone. What remains is cyan, teal, and a text editor that remembers its name. The desktop matches itself, and Mick would approve.” – The OpenRiot Crew, v8.0.14