Skip to content

fix: auto-resolve latest stable release instead of hardcoding version - #1

Merged
ahze merged 1 commit into
mainfrom
fix/auto-resolve-stable-version
Oct 5, 2026
Merged

ahze merged 1 commit into
mainfrom
fix/auto-resolve-stable-version

Conversation

@ahze

@ahze ahze commented Oct 5, 2026

Copy link
Copy Markdown
Member

No description provided.

@ahze
ahze requested a review from jtrotsky October 5, 2026 07:43
@ahze ahze assigned jtrotsky and ahze Oct 5, 2026

@jtrotsky jtrotsky left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Curious what needed jq ca_root_nss , oh I see it fetching upstream version

@ahze

ahze commented Oct 5, 2026

Copy link
Copy Markdown
Member Author

jq comes from base, it's used to parse versions out of this json: https://api.github.com/repos/gtsteffaniak/filebrowser/releases

They are both in the base image and not needed here. I'll force commit here and remove them.

@ahze
ahze force-pushed the fix/auto-resolve-stable-version branch from 9bf6ed7 to f2cc5c0 Compare October 5, 2026 19:42
@ahze
ahze merged commit 4190c6b into main Oct 5, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants