Skip to content

[release] hotfix 1.0.6: port imgborders to Hyprland 0.57 for Fedora - #643

Closed
neur0map wants to merge 1 commit into
mainfrom
release/1.0.6-hotfix
Closed

neur0map wants to merge 1 commit into
mainfrom
release/1.0.6-hotfix

Conversation

@neur0map

Copy link
Copy Markdown
Member

The v1.0.6 tag publishes failed for Fedora: hyprland-devel moved to 0.57,
whose renderer passes an explicit CRenderContext and dropped m_renderData,
so the vendored image-border plugin no longer compiled. The port is already
on unstable-dev (5689604); this cherry-picks it onto main so the v1.0.6
tag can be moved to a tree whose Fedora repository publishes cleanly.

The Arch lane is unchanged in artifact content (it resolves the same
0.56.2 source commit from the refreshed bundle), so the frozen v1.0.6 Arch
and CachyOS repositories already published stay valid; only the Fedora and
Void publishers will be re-dispatched on the moved tag.

Fedora moved hyprland-devel to 0.57: the renderer passes an explicit
CRenderContext, m_renderData is gone, and IPassElement's virtuals
changed, so the vendored plugin no longer compiled and the whole Fedora
publish stopped. Refresh the vendored bundle to upstream's current
commit (plus a Ryoku master that keeps the 0.56 source pins the Arch
lane resolves) and carry the 0.57 port as a Fedora fetch-hook patch, so
the Arch build keeps choosing the unchanged 0.56.2 source.

Verified: git bundle verify; git apply --check on the pinned commit;
libimgborders.so links in fedora:44 and fedora:45 containers with
hyprland-devel 0.57.0; the Arch resolver still maps 0.56.2 to the same
source commit.

Note: Fixed: the Fedora repository publish failed because the image-border plugin did not compile against Hyprland 0.57; Fedora now ships a ported build.
@neur0map neur0map closed this Oct 28, 2026
@neur0map
neur0map deleted the release/1.0.6-hotfix branch October 28, 2026 20:18
neur0map added a commit that referenced this pull request Oct 28, 2026
Main carries the release PR merge commits (#642, #643); unstable already
holds the same content as its own commits, so only the topology differs.
VERSION stays on the unstable line at 1.6.9.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant