feat: release 11.0.0 - #41768
Merged
Merged
Conversation
Bump version.php to 11.0.0 and materialize the changelog for the final release of the 11.0 line, after three release candidates (11.0.0-rc1 2026-06-29, rc2 2026-07-23, rc3 2026-07-29). The RC tags were all cut without materializing changelog/unreleased/, so the entire 11.0.0 cycle — 47 fragments — was still filed under [unreleased]. Move them into changelog/11.0.0_2026-07-30/ and regenerate CHANGELOG.md with calens, producing one combined 11.0.0 section (compare link v10.16.4...v11.0.0). unreleased/ is left empty, ready for the next cycle. $OC_Version stays [11, 0, 0, 0]: the 4th digit is the internal DB-upgrade patch level, not the public version, and it is unchanged across an RC-to-final transition (v10.16.0RC1 -> v10.16.0 likewise kept [10, 16, 0, 0]). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com>
|
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
phil-davis
approved these changes
Jul 30, 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
owncloud/corefor the final 11.0.0 tag, after three release candidates (rc1 2026-06-29, rc2 2026-07-23, rc3 2026-07-29).version.php$OC_VersionString11.0.0-rc3→11.0.0.$OC_Versionstays[11, 0, 0, 0]: the 4th digit is the internal DB-upgrade patch level, not the public version, and it does not change across an RC-to-final transition —v10.16.0RC1→v10.16.0likewise kept[10, 16, 0, 0].Changelog
All three RC tags were cut without materializing
changelog/unreleased/, so the entire 11.0.0 cycle — 47 fragments — was still filed under[unreleased], and no 11.x changelog folder existed at all.This moves them into
changelog/11.0.0_2026-07-30/(viagit mv, all 47 at 100% similarity) and regeneratesCHANGELOG.mdwith calens, producing one combined 11.0.0 section.unreleased/keeps its.gitkeepand is now empty, ready for the next cycle. None of the 47 overlapped any existing released folder.The
CHANGELOG.mddiff is intentionally small (4 lines): the entries were already being rendered, under the[unreleased]heading. What changes is the heading, the date, and the compare link:Same shape as
852062dd("feat: release 10.16.4"), which did the changelog and version bump in one commit.Once merged,
v11.0.0gets tagged on the merged commit and the release bundles are built and published fromowncloud/server-release.🤖 Generated with Claude Code