chore: release 3.0.1 - #60
Merged
Merged
Conversation
Ship the upstream rclone v1.75.0 binary from #56 in a tagged release. The fix has been on master since #56 but nothing consumes master: the ownCloud Server 11 distribution assembles its apps from tagged GitHub releases, and the pinned v3.0.0 still carries the old custom rclone fork build (v1.67.0-beta, Go 1.22.4) with 23 HIGH/CRITICAL findings. Releasing 3.0.1 is what lets the Server 11 image stop reporting them. Roll the rclone-1.75.0 changelog fragment into changelog/3.0.1_2026-08-20/, regenerate CHANGELOG.md with calens, and bump appinfo/info.xml to 3.0.1 - the release workflow refuses to build when the tag and info.xml version disagree. Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com> Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com>
phil-davis
approved these changes
Aug 20, 2026
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
2 participants
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.
Cuts the 3.0.1 patch release, which ships the upstream rclone v1.75.0 binary from #56.
Why now: the ownCloud Server 11 distribution assembles its apps from tagged GitHub releases (
owncloud/server-releasespecs pinmigrate_to_ocis: v3.0.0). The rclone fix has been on master since #56, but nothing consumes master — so the image still bundles v3.0.0 with the old custom rclone fork build (v1.67.0-beta, Go 1.22.4) and its 23 HIGH/CRITICAL findings. Tagging 3.0.1 is the prerequisite for clearing those CVEs from the image.Changes
changelog/unreleased/rclone-1.75.0intochangelog/3.0.1_2026-08-20/CHANGELOG.mdwith calensappinfo/info.xmlto3.0.1— the release workflow hard-fails when the tag andinfo.xmlversion disagreePatch level: the only user-visible change is the replaced bundled binary. No API, config, or dependency-range change; the oc11 range stays
min-version="11" max-version="11"..trivyignore.yamlis untouched — its eight accepted Go-stdlib findings are against rclone v1.75.0 itself, which is still the newest rclone release (no build with Go >= 1.26.6 exists yet), and they expire 2026-11-01.Verification
Local
make distwith the G2 store produces a correctly signed tarball:appinfo/signature.jsonpresent, schemav: 2,alg: ecdsa-p384-sha384migrate_to_ocis<version>3.0.1</version>bin/rclone_linux_amd64reportsrclone v1.75.0make test-php-styleclean. PHPUnit/PHPStan need a core checkout, so they run here in CI.Follow-up
Once v3.0.1 is released, bump the pin to
v3.0.1inowncloud/server-release(specs/11.0.0-complete.yaml,specs/11.0.0-complete-qa.yaml).🤖 Generated with Claude Code