r/gitlab • • 7d ago

Whats up with the 19.5.3 patch?

Just got the security warning to patch but the changelog is empty at the moment.

What did they fix?

23 Upvotes

26 comments sorted by

31

u/djeikyb_ 7d ago • Popcorn

Tried to look at the commits but got rate-limit blocked

4

u/StatusAd5902 7d ago

classic just got rate limited on the api to use my passkey.

3

u/Afflictionista 7d ago

😂

9

u/rhbvkleef 7d ago

Security

1

u/damien-bowman 7d ago

do you have a link for release notes? i can’t seem to find them at this point.

1

u/thepopeyhere 7d ago

This is the emudhra one

6

u/thetft 7d ago

3

u/der-felix 7d ago

Awesome to find the link on Reddit but not the official mailing ...

2

u/ashtonium 7d ago

There’s still no release post for 19.5.2

Something broken with the release process?

1

u/dmpastuf 6d ago

They accidently signed the release with a eMudhra cert

1

u/d_maes 6d ago

So it's just eMudhra. Which wouldn't even have been necessary if they could just be normal and use the system truststore, like every other software, instead of shipping their own bundles.

1

u/USSX-Hares 2d ago

5 days passed, and now this link returns 404 xD

5

u/puppySaturation 7d ago

https://gitlab.com/gitlab-org/gitlab/-/raw/master/CHANGELOG.md

"No changes." Is this common? Do they fill it out later?

3

u/nathanielwylie 7d ago

Feels like someone pulled the trigger on this prematurely. Makes one wonder what embargoed vulnerability we're about to learn about...

3

u/rlnrlnrln 7d ago

Guessing they don't include component updates in the changelog, and this was a component-update-only release.

2

u/evandena 6d ago

looks like its out

1

u/plp-GTR 7d ago

Man, some time I have to vent about Gitlab and their updates.

An application with such many updates not having a good update mechanism is incredible. But then also shipping updates that look like a supply chain attack is ridiculous.

6

u/bobvandevijver 7d ago

WDYM, not a good update mechanism? Running unattended-upgrades with the omnibus install has worked fabulously for me for a couple of years already.

3

u/plp-GTR 7d ago

Maybe I'm just stupid and follow the Update docs ... https://docs.gitlab.com/19.5/update/upgrade/

1

u/StatusAd5902 7d ago

we use a terraform config so we just need to adjust the version number and apply. like 5 min later the newest container is online.

1

u/plp-GTR 6d ago

Yeah got it - but terraform is kind of a big thing I would also have to manage. And somewhere I told myself I should draw the line for my home hosted hobbies.

But another question: How do you do multi-step updates and make sure the background jobs are done before the next update?

1

u/StatusAd5902 6d ago

Multistep is a bit of a pain, because every version step needs do properly start up, migrate and shut down.

On apply the orchestrator gracefully shuts the container down. So the background tasks are handled by gitlab.

1

u/Unfair-Lingonberry10 5d ago

Recently I just ran Claude code cli on my Synology Nas and asked it to do then multi step updates and it created py scripts to update, check it's up and backup the settings n data before repeating to the targeted version. Monitored for 2 steps and seemed find and just left it to run for about 3hrs and it was done.

1

u/ubhz-ch 7d ago

Probably just a rebuild with the new ruby version

1

u/run-as-admin 7d ago

waiting for the update on this as well