@greatland1959 I‘m living in Germany.

@andrew84 He misunderstood you, actually. He thinks you were claiming they were on 135, whereas you stated the contrary.

@Opera-Security Thank you for explaning. You‘ll find me nearly convinced now.
Would you think it’s possible to have a general post on your blog about your handling of Chromium, security fixes and your security policies generally? Maybe, as you‘ve done with the „Debunking…“-post about spyware allegations.
It seems to me that I‘m not the only one having these concerns.

@andrew84 He misunderstood you, actually. He thinks you were claiming they were on 135, whereas you stated the contrary.

I've made this test with the latest update from today. So what should I make with that? It seems there are a lot of unfixed issues in Opera's most recent Chromium version, so that I get a security alert. I'm really concerned.
I'm almost on the jump for security reasons. Opera might have some fancy features but what about the browser's security?

It doesn't matter anyway, as we're dealing with lots of open vulnerabilities, as it seems.

It has also detected version 134 BTW.

@andrew84 I see, that's what they also say on their blogs. But in Beta's case, they give us this:

That's already from more than a week ago. So I wouldn't count it as unrealistic to moving 119 to the same Chromium as you have on Developer.

@andrew84 It may be so, it may be not: As even beta is already on 135.0.7049.115 for eight days already.

My installation of this update still keeps me on Chromium 134, I'm afraid.

@greatland1959 I‘m living in Germany.

@sgunhouse I'm not having this issue, actually. Maybe a problem only for some regions?

@leocg Maybe, I‘ve found out, what triggered it. I logged in via the code that was sent by mail, first. In this case, I was logged out after restart.
But the next time I logged in I chose to do this with my password. And then, fingers crossed, I was being remembered.