Repository navigation
docs: add ownCloud Classic 11.1 and release notes for 11.1.0 and 10.16.7 - #174
Merged
Merged
Conversation
Copy content/server/11.0 to 11.1 unchanged except for the antora.yml version key, and make 11.1 the latest server version. 11.0 stays published. Register the new tree in go-redirect's PUBLISHED_VERSIONS and in the test's version loop, and record it in the manifest and the README. previous-server-version stays at 10.16, the previous maintained line. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
11.1.0 temporarily locks local accounts after repeated failed logins, enabled by default, and adds occ user:unlock to lift a lockout early. Add an Account Lockout page to the 11.1 security section, the user:unlock command to the user commands, and regenerate the 11.1 config.sample.php page from core master (11.1.0), which adds the four account_lockout.* keys. Bump the example version output in the occ pages to 11.1.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add the 11.1.0 and 10.16.7 sections to the release notes, keep the 11.0 page aliases now that latest moved to 11.1, and point the 10.16 docker installation page at the 10.16.7 image. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The 11.0 docker page took its image tag from the global latest-server-download-version, so moving latest to 11.1.0 told 11.0 readers to install 11.1. Pin it on the page, as 10.16 does; playbook attributes cannot be overridden per component. Make the lockout page match core: OpenID Connect accounts are auto-provisioned into the built-in backend and are counted, endpoints other than the login form and WebDAV report a lockout like a wrong password, unknown names only look like local accounts, and an email shared by several accounts is not resolved by occ user:unlock. Use the full user:unlock description in the occ list output, and move the 10.16.7 section to the 10.16 group of the release notes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
Thanks, will review tomorrow morning, 59k changes... |
The 11.1.0 and 10.16.7 release notes now cover the installer's app package signature verification (core#41955, #41959), which rejects unsigned or ambiguously packaged apps where code signing is enforced. The 11.0 and 11.1 Secure View links resolve within their own version. current-server-version is a playbook attribute and now points 11.0 at 11.1. The lockout page no longer says external backend accounts are never locked: a login name that is not the ownCloud user name, such as an LDAP email address, is counted like an unknown name. A successful login with the user name does not reset the email address counter. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Thomas Müller <323649642+oc-tmueller@users.noreply.github.com>
LukasHirt
reviewed
Nov 3, 2026
The 11.1 installation page and its dot.env example rendered the image tag from the global latest-server-download-version, so the next global bump would silently change the documented 11.1 image. Pin it with a page-local docker-image-version, as the 11.0 page already does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Thomas Müller <323649642+oc-tmueller@users.noreply.github.com>
LukasHirt
approved these changes
Nov 3, 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
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.
Summary
content/server/11.1: a copy of 11.0, nowlatest. 11.0 stays published. Registered ingo-redirect.jsPUBLISHED_VERSIONS, the go-redirect test loop,sync/manifest.ymland the README.previous-server-versionstays10.16, the previous maintained line.occ user:unlockin the user commands, andconfig_sample_php_parameters.adocregenerated from coremaster(11.1.0), which adds the fouraccount_lockout.*keys. The exampleoccversion output now shows 11.1.0.10.16.7. The 11.0 page now pins11.0.1as a page attribute: it used the globallatest-server-download-version, which moves to11.1.0, and playbook attributes cannot be overridden per component.Read the diff commit by commit: the first commit is the verbatim 11.0 → 11.1 copy, with only
antora.yml's version key changed.Merge only after the images exist
owncloud/server:11.1.0andowncloud/server:10.16.7are not on Docker Hub yet. They come from owncloud-docker/server#753 and #752. Until those are merged, the install pages point at tags that do not exist.Verification
npm run antora && npm test: 72 pass, 0 fail, 1 skip (it needs a prerelease server line, of which there is none).config-to-docsis a no-op on 11.0 againstv11.0.1. For 11.1 againstmaster, the diff is only theaccount_lockout.*block./server/latest/→ 11.1. The 11.0 docker page shows11.0.1everywhere, 11.1 shows11.1.0and 10.16 shows10.16.7. Every new xref and anchor resolves.AccountLockout,Sessionanduser:unlock.🤖 Generated with Claude Code