@worldofpeace thanks! just to make sure, the current version and hash on 18.09 is fine and not broken?

@worldofpeace thanks! just to make sure, the current version and hash on 18.09 is fine and not broken?

Should be fine since Vivaldi in 18.09 is at 1.15.1147.42-1 and master is at 2.1.1337.51-1.
Though I think we should be backporting any browser updates for security.

Does Vivaldi provide some sort of changelog, so we know there's no current open security our current 1.15.x version?

Do they even consider 1.15.x a "stable branch", that's receiving any updates?

If they don't, we should bump 18.09 too 2.1.x, too…

It's chromium based so all chromium security issues effect Vivaldi. So backporting is needed.

Do they even consider 1.15.x a "stable branch", that's receiving any updates?

If you look at the url, on master, we're at the stable release.

It's chromium based so all chromium security issues effect Vivaldi. So backporting is needed.

Yes, but there's no listing of versions released, to see which version adresses a CVE / bumps chromium etc.

Do they even consider 1.15.x a "stable branch", that's receiving any updates?

If you look at the url, on master, we're at the stable release.

The 1.15.x version from 18.09 uses the same URL pattern, so there was a major version bump on their stable branch, and we should bump to that version on 18.09 as well.

@worldofpeace Can you prepare a PR for that?

Yes, but there's no listing of versions released, to see which version adresses a CVE / bumps chromium etc.

Just to know for the future, the changelog can be seen at https://update.vivaldi.com/update/X.x/relnotes/Major.minor.build.html

Here's the most recent one https://update.vivaldi.com/update/1.0/relnotes/2.1.1337.51.html

The 1.15.x version from 18.09 uses the same URL pattern, so there was a major version bump on their stable branch, and we should bump to that version on 18.09 as well.
@worldofpeace Can you prepare a PR for that?

Of course 👍