chore: bump version to 2.4.2 - #372
Open
oc-tmueller wants to merge 1 commit into
Open
oc-tmueller wants to merge 1 commit into
oc-tmueller wants to merge 1 commit into
Conversation
Releases the introspection-branch audience check from #365 on the ownCloud 11 line. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: Thomas Müller <323649642+oc-tmueller@users.noreply.github.com>
phil-davis
approved these changes
Sep 11, 2026
Contributor
Author
|
recheck |
jvillafanez
approved these changes
Sep 15, 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
3 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 11 security release for #365 (OC10-147), which is merged on
masterbut unreleased. Replaces #370 - see the note at the bottom.appinfo/info.xml:2.4.1→2.4.2CHANGELOG.md: promotes the## [Unreleased]entry into## [2.4.2] - 2026-09-11, keeping the empty[Unreleased]heading and adding the[2.4.2]compare link - same shape as chore: bump version to 2.4.1 #359 (the 2.4.1 bump)No code change. The date is set to today - adjust it if the merge slips.
release.ymlrefuses to release unless the tag minusvequals<version>, so this has to merge beforev2.4.2is tagged.The 10.x side
The same fix is being backported to the 2.3 line in #367 → #368 → #371. Worth knowing:
release-2.3.4had noverifyAudience()at all - #356 was never backported - so v2.3.5 is the first 10.x release to close OC10-115 as well as OC10-147, while this release only adds OC10-147 on top of v2.4.1.Tag
v2.3.5beforev2.4.2if both go out together, so the oc11 release ends up as GitHub's "Latest" (releases are ordered by date - today v2.3.4 holds that label).Why not #370
#370 used the branch name
release/2.4.2, which the org ruleset matches as a protected release branch (deletion,non_fast_forward,required_signatures,pull_request), so no further commit could be pushed to it - not even a fast-forward - which makes it useless for review. Renamed tochore/bump-2.4.2; same tree, same single commit.Follow-ups, not in this PR
openidconnect.tar.gz