I don't know much about the process behind upgrades. From your suggestions I'd say a combination of a news entry and the addition of the i3blocks-contrib package sounds good to me.
Am i understanding this correctly: Installing the i3blocks-contrib package adds the scripts to /usr/share/i3blocks/? (i don't have i3blocks-contrib package available as of now, as i understand that's because the package is not yet available) Den ons. 18. feb. 2026 kl. 21.23 skrev Jakob Haufe <[email protected]>: > Hi Lasse, > > this is an upstream change introduced between 1.4 and 1.5 by commit > 0e395b983a21b074c6365e34d96865334b994f4b: > > scripts: move to contrib > > The default scripts have been included in the contrib repository. From > now on, the i3blocks repository will only contain the C scheduler. > Packagers will be able to ship i3blocks with default scripts which fit > their system. > > Given I recently adopted i3blocks as part of the i3 team and am no user > of it myself, I'm a bit unsure how to proceed. > > I could add a NEWS entry to make sure users are aware of the change. > > Another option would be to simply restore the blocklets from 1.4, but don't > think that's very elegant. > > A third option would be to package i3blocks-contrib and make i3blocks > recommend it. > > Thoughts? > > -- > ceterum censeo microsoftem esse delendam. >
