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 WebKit-5.0 to WebKit-6.0 #799

Closed
badcel opened this issue Feb 11, 2023 · 4 comments · Fixed by #889
Closed

Update WebKit-5.0 to WebKit-6.0 #799

badcel opened this issue Feb 11, 2023 · 4 comments · Fixed by #889
Milestone

Comments

@badcel
Copy link
Member

badcel commented Feb 11, 2023

As WebKit-5.0 is a development release it should be updated to it's final version 6.0 once it is available in the flatpak SDK (probably with GNOME 44).

See: #746 (comment)

@badcel badcel mentioned this issue Feb 11, 2023
@mcatanzaro
Copy link

It's already available in org.gnome.Platform//master and will indeed be available in org.gnome.Platform//44, yes. (You'll notice because it replaces the -5.0 API.)

@mcatanzaro
Copy link

and will indeed be available in org.gnome.Platform//44

Um, and this should appear sometime next week hopefully, because the runtime is branched with the 44.beta release, and the tarball deadline for that was 10 minutes ago.

@badcel
Copy link
Member Author

badcel commented Feb 12, 2023

Do you know how long the flatpak runtimes are supported? If the runtime version "43" is supported in parallel to version "44" there must be probably both versions available as nuget packages.

@mcatanzaro
Copy link

Do you know how long the flatpak runtimes are supported?

12 months. The 43 runtime (last to ship webkit2gtk-5.0) will go EOL when the 45 runtime is released in September.

@badcel badcel added this to the 0.4.0 milestone May 8, 2023
@badcel badcel mentioned this issue Jul 18, 2023
1 task
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 a pull request may close this issue.

2 participants