Repository navigation
chore: update the FRP client to 0.71.1 - #72
Merged
Merged
Conversation
Signed-off-by: Oleksandr Piskun <oleksandr2088@icloud.com>
15 of 17 tasks
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.
The skeleton image bundles frpc 0.61.1, and ExApps generated from it copy that version. HaRP now ships frps 0.71.1 (nextcloud/HaRP#135), and frp only guarantees client/server compatibility within eight minor versions, so 0.61.1 works today but is outside that window.
Changes
FRP_VERSION0.61.1 -> 0.71.1, with both checksums taken from the release'sfrp_sha256_checksums.txt.frpc 0.71.1 connects to the frps of current and older HaRP releases alike (checked against frps 0.65.0 and 0.71.1, with FRP TLS on and off). The image builds and reports frpc 0.71.1; the published image changes only when the publish workflow is run.