chore: upgrade Komorebi client to v0.1.26

[CtByte]

I intend to address an issue that is now fixed with Komorebi and Stackbar, as @LGUG2Z was kind enough to create a new release when this issue was fixed, just to make things faster.

This also helps those who upgrade Komorebi to a higher version compared to what is currently being used by Zebar, see #52.

[adriankarlen]

I'm not sure if komorebi is using semantic versioning but would it not make sense to wildcard the minor version, assuming that it is not a breaking change most of the time?

Perhaps @LGUG2Z can give some clarity on the versioning of komorebi, but it feels unsustainable to keep bumping for every bugfix in komorebi.

[LGUG2Z]

These are not bugfix releases; the last few releases have seen some major additions to the state format with the introduction of features like the Stackbar.

What I think makes sense here is for Zebar and other integrators who only care about a small subset of the state to wrap the notifications received in structs that only specify the fields they are interested in, and then deserialize the notifications to that struct.

[CtByte]

I can see that I should have clarified the purpose of this PR in the description. I will fix that now.

I agree that the Komorebi integration could be more flexible as to what fields to map. In this particular case, the new Komorebi version also added a new layout type that is probably better to include, rather than make a workaround to ignore it.

[LGUG2Z]

Might as well bump this PR to tag v0.1.26 now

[CtByte]

Sure, I will test it a bit first 😉

Edit: I've made the necessary adjustments for komorebi v0.1.26

@LGUG2Z Congrats on the release 🎉

[LGUG2Z]

Might as well bump this PR to tag v0.1.27 now 😅

[github-actions]

🎉 This PR is included in version 1.4.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀