chore: bump version to 2.3.5 - #371
Merged
Merged
Conversation
Release the two access-token audience checks on the ownCloud 10 line. #356 shipped on the oc11 line in v2.4.1 but never reached 2.3, so v2.3.5 is the first 10.x release carrying either half of the check. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: Thomas Müller <323649642+oc-tmueller@users.noreply.github.com>
This was referenced Sep 11, 2026
phil-davis
approved these changes
Sep 11, 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.
Prepares the ownCloud 10 security release. Replaces #369, which had to be abandoned - see the note at the bottom.
appinfo/info.xml:2.3.4→2.3.5. Theowncloud min-version="10.12" max-version="10"/php min-version="7.4"block is untouched.CHANGELOG.md: new## [2.3.5]section under### Security- the heading this branch's own 2.3.4 entry established - plus the[2.3.5]compare link and the bumped[Unreleased]link, following what the 2.3.4 release did.Both entries are first releases of the fix on the 10.x line, not backport housekeeping: #356 shipped on the oc11 line in v2.4.1 but never reached 2.3, so the whole 10.x line stayed exposed to OC10-115 as well as OC10-147 until this release.
The date is set to today (2026-09-11) - adjust it if the merge slips.
release.ymlrefuses to release unless the tag minusvequals<version>, so this has to merge beforev2.3.5is tagged.Stack
release-2.3.4as its parents merge)Why not #369
#369 used the branch name
release/2.3.5, which the org ruleset matches as a protected release branch:deletion,non_fast_forward,required_signaturesandpull_requestall apply, so no further commit could be pushed to it - not even a fast-forward. Renamed tochore/bump-2.3.5, which is unprotected and therefore still reviewable. Same tree, one commit.release/2.3.5andrelease/2.4.2cannot be deleted either (the ruleset blocks that too), so they will linger as stale branches until someone with bypass rights removes them.Follow-ups, not in this PR
openidconnect.tar.gz