Release v0.6.0 - #126
Merged
Merged
Conversation
A compose deployment can now arrive wired up: SONARR_URL / SONARR_API_KEY and the RADARR_* pair are inserted on start, so the *arr pre-warm shipped in v0.4.0 has something to read without a trip through Settings first. It runs only while no instance exists, which is what keeps the UI the source of truth: no overwriting an edited key, no duplicate when someone corrects a URL, nothing re-applied on restart. Half a pair is treated as a typo and skipped. The keys are AppHost parameters, so they land in the generated compose file and its .env alongside TVDB_APIKEY rather than having to be added by hand. Closes #5 Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
The mirror pushed to {registry}/chrison-dev/... for both registries, but there is
no chrison-dev namespace on Docker Hub — its API answers 404. The account is
chrison, so the channel could never have worked; nobody found out because it had
no credentials to get that far.
DockerHubNamespace is now its own parameter, applied by PushDockerHub the same
way the registry is.
Closes #115
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
:edge said nothing about where the images came from; :develop does. The target, the workflow and the docs all move with it, so one concept has one name across both registries. Anyone following ghcr.io/...:edge must switch to :develop — the old tag stops being updated rather than disappearing. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
The spike this issue asked for found the key in a far better place than feared: ZDF's homepage publishes it as apiAuthToken in its own server-rendered data, at a stable URL — not inside a hash-named JS chunk. Extracting it and calling the API with it returns 200. So a rejection now triggers a read of the current key, a verification call, and a retry. Nothing is adopted before it has answered 200, which is what keeps a failed scrape equal to today's behaviour rather than worse than it. The recovered key is in-memory only and health stays degraded while it is in use: it is a recovery, not a second place to configure the key. Closes #112 Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
ChrisonSimtian
added
the
skip-changelog
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.
Four changes since v0.5.0.
SONARR_URL/SONARR_API_KEY(andRADARR_*) on first boot, so a compose deployment arrives wired up.:edge→:develop, on both registries. Breaking for anyone pulling:edge: the old tag is not deleted, it just stops being updated.dockerhubenvironment holds its credentials.Minor bump: the tag rename is breaking, and there are two new capabilities.
Merge by fast-forward, not the button —
git merge --ff-only develop && git push origin main.