Skip to content

chore: bump version to 2.3.5 - #369

Closed
oc-tmueller wants to merge 1 commit into
backport/oc10-audience-checksfrom
release/2.3.5
Closed

oc-tmueller wants to merge 1 commit into
backport/oc10-audience-checksfrom
release/2.3.5

Conversation

@oc-tmueller

Copy link
Copy Markdown
Contributor

Prepares the ownCloud 10 security release.

  • appinfo/info.xml: 2.3.42.3.5. The owncloud 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. Both entries are first releases of the fix on the 10.x line, not backport housekeeping: fix: verify token audience to prevent cross-client account takeover #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.yml refuses to release unless the tag minus v equals <version>, so this has to merge before v2.3.5 is tagged.

Stack

  1. ci: run unit tests, code style and trivy on the 2.3.x line #367 - CI for this branch
  2. fix: verify the token audience on the ownCloud 10 line #368 - the backport (this PR is based on it; retarget to release-2.3.4 as its parents merge)
  3. this PR - the bump

Follow-ups, not in this PR

  • marketplace upload of the resulting openidconnect.tar.gz
  • a GHSA advisory, which has to cover both lines for OC10-115

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>
@oc-tmueller

Copy link
Copy Markdown
Contributor Author

Superseded by #371. The branch name release/2.3.5 matches the org ruleset as a protected release branch, so no further commit could be pushed to it - not even a fast-forward - which made it impossible to act on review feedback. #371 carries the identical tree on chore/bump-2.3.5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant