chore(deps): manual upgrade to Alpine 3.23

[Vlaaaaaaad]

what

#5658 is failing so here's a manual update of Alpine from 3.21 to 3.23, including package version updates.

why

TL;DR: Alpine 3.21 is too old — I needed Alpine 3.22 or 3.23 for .NET 10. Renovate configs beat me, so I did it manually.

I have some instances of Atlantis that, through Terraform and terraform-aws-lambda, call code to build Lambda functions written in .NET. This has been going great until .NET 10 was released in November and the automated dotnet9 to dotnet10 version bump caused my Atlantis image to fail building (my image is basically FROM ghcr.io/runatlantis/atlantis plus .NET, Python, and a few other exotic dependencies). I finally got to look into this, and the cause turned out to be Atlantis using Alpine 3.21 which only supports dotnet8 and dotnet9.

I noticed the automated dependency upgrades for Atlantis have been failing for a while in #5658 and, after failing to fix Renovate, I decided to do the version upgrades manually: I manually bumped the Alpine image to 3.23.2 and I manually updated all the packages to their latest versions.

It would be a good idea to have a follow-up PR that fixes/checks the Renovate configuration for Alpine, but I'll leave that to someone with more Renovate experience — I totally failed to do that and the intersection of Renovate best practices, Alpine versioning, mulled wine, and regex was too annoying to solve.

tests

• container image builds successfully
• container image tested in production successfully. Question: is this needed? If yes, I am happy to do it but it'll take a few days.

references

• Alpine 3.23 package versions: ca-certificates, curl, git, unzip, bash, openssh, dumb-init, gcompat, coreutils-env
• Failing version auto-update PR: chore(deps): update alpine docker tag to v3.23.2 in dockerfile (main) - autoclosed #5658

[jamengual]

@Vlaaaaaaad Thanks for the contribution.

[Vlaaaaaaad]

Renovate seems to be able to bump Alpine versions without issue now, so no follow-up needed! 🎉