-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto building a new release isn't occurring (maybe I'm presumptive of the new configuration, new Transmission is out..) #2848
Comments
The Any commits subsequent to that, on master or dev, will cause the ^ this is due to be updated in #2843 to work properly |
Gotcha. Closing this thread. I just thought it would have promptly built and released a new build w/ latest Transmission. |
For I will look at adding something to the |
Is there a pinned issue for this?
Is there an existing or similar issue/discussion for this?
Is there any comment in the documentation for this?
Is this related to a provider?
Are you using the latest release?
Have you tried using the dev branch latest?
Docker run config used
N/A
Current Behavior
Currently, the release has not been updated to include the latest Transmission (4.0.6). I was going to open a PR to push an update to the latest tar.gz from the Transmission github release page. The new code for this project appears to have a set of tasks that query for the latest Transmission and update accordingly. https://github.com/transmission/transmission/releases/tag/4.0.6
Expected Behavior
Based upon my understanding of the new workflows that I just skimmed it would make sense that something should be triggering a new release to build auto-magically with the latest Transmission since there is no longer a reliance on manually editing the tar.gz path and building from there. https://github.com/haugene/docker-transmission-openvpn/blob/master/.github/workflows/check-transmission-releases.yml
How have you tried to solve the problem?
N/A
Log output
N/A
HW/SW Environment
Anything else?
Happy to help with PRs when I can. Not sure how to be of value in this instance.
The text was updated successfully, but these errors were encountered: