Sync Optimisarr 0.2.9 metadata to dev - #52
Merged
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.
What changed
0.2.9ondev0.2.9changelog section as releasedWhy
The
v0.2.9release metadata was committed on the release branch and reachedmain, but was not synchronized back todev. As a result, the currentghcr.io/jellman86/optimisarr:devimage contains the latest development codewhile
/api/healthstill reports version0.2.8.Merging this PR lets the normal
devbranch workflow rebuild and publish thetag from the correct source state.
Validation
dotnet build Optimisarr.slnx --configuration Release --warnaserrorpython3 scripts/check_openapi.py --configuration Release --no-buildpython3 scripts/check_docs.py