Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update KDE runtime to 6.6 #8

Merged
merged 1 commit into from
Apr 7, 2024
Merged

Update KDE runtime to 6.6 #8

merged 1 commit into from
Apr 7, 2024

Conversation

guihkx
Copy link
Collaborator

@guihkx guihkx commented Apr 7, 2024

This update is long overdue, but it was being postponed on purpose, to avoid triggering this bug:

nuttyartist/notes#611

That bug has been fixed in Qt 6.6.3, so now we can update.

This update is long overdue, but it was being postponed on purpose, to
avoid triggering this bug:

nuttyartist/notes#611

That bug has been fixed in Qt 6.6.3, so now we can update.
@flathubbot
Copy link
Contributor

Started test build 112916

@flathubbot
Copy link
Contributor

Build 112916 successful
To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/95722/io.github.nuttyartist.notes.flatpakref

@guihkx guihkx merged commit 33c4ec2 into flathub:master Apr 7, 2024
1 check passed
@guihkx guihkx deleted the qt6.6 branch April 7, 2024 19:30
@nuttyartist
Copy link
Collaborator

🥳

What about Qt 6.7?

@guihkx
Copy link
Collaborator Author

guihkx commented Apr 7, 2024

@nuttyartist

I chose not to jump to 6.7 right away, so I can test Notes on that version a bit better, for a bit longer.

I'm always hesitant to upgrade to ".0" Qt releases, as they often introduce regressions. :(

In contrast, I've been using Notes with the 6.6.3 build for about a week, and since I didn't encounter any new issue, I figured updating to the 6.6 runtime would be a safer bet.

In any case, I've opened an issue as a self reminder to update to 6.7 here: #9

@nuttyartist
Copy link
Collaborator

I'm always hesitant to upgrade to ".0" Qt releases, as they often introduce regressions. :(

Yep. I agree on that.

In any case, I've opened an issue as a self reminder to update to 6.7 here: #9

Great (:

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.

None yet

3 participants