Repository navigation
docs: permanent links to the latest release (#42) - #47
Merged
Merged
Conversation
All three READMEs, in "Download": - a "Permanent links" section: the one release, latest, titled "VTesse <version>", rebuilt from every push to main; a table of its 12 files with what each is and its releases/latest/download/<file> link (only the VTun server's name follows the VTun version); a download with the checksum check that also works with BusyBox sha256sum; - the release badge and every download link use the releases/latest form (the install commands used releases/download/latest, which works the same). Checked: all 12 links answer 200; the example verifies vtesse-arm32 in alpine:3.22 (BusyBox). Closes #42
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can see how risky a PR is at a glance with blast radius labels |
PR Summary by QodoDocument permanent links to the latest release
AI Description
Diagram
High-Level Assessment
Files changed (3)
|
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.
Closes #42.
All three READMEs (same structure), section "Download":
latest, titledVTesse <version>, rebuilt from every push tomain, no versioned releases; a table of all 12 release files — what each one is and itshttps://github.com/OpenIPC/vtesse/releases/latest/download/<file>link (onlyvtund-<VTun version>-x86_64follows the VTun version, a third-party component); a download example with the checksum check (grep ' vtesse-arm32$' SHA256SUMS | sha256sum -c -, which also works with BusyBoxsha256sum).releases/latest/…form (the install commands usedreleases/download/latest/…, which serves the same files).Checked: all 12 links answer 200; the example verifies
vtesse-arm32inalpine:3.22(BusyBox). Docs only: no version bump, no release.