libredb-studio: bump to 0.9.59 and declare supported architectures#758
Open
yusuf-gundogdu wants to merge 1 commit into
Open
libredb-studio: bump to 0.9.59 and declare supported architectures#758yusuf-gundogdu wants to merge 1 commit into
yusuf-gundogdu wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the LibreDB Studio service from
0.9.27to the current release0.9.59, and fills in thetemplate.architectureannotation, which was left empty.docker manifest inspect ghcr.io/libredb/libredb-studio:0.9.59returns bothlinux/amd64andlinux/arm64, so ARM users were being filtered out unnecessarily.Verified before submitting: the service's own defaults from
app.yaml(image, env vars, volume mount, container port) were run locally on 0.9.59. The health endpoint is green, login works with the template's default admin credentials, and a saved connection survives a container restart. The run was on aarch64, which also confirms the arm64 claim.yamllint -c services/.yamllintreports no new issues (the one line-length warning predates this change).