chore: update changelog#13911
Conversation
|
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. |
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
DeepDiver1975
left a comment
There was a problem hiding this comment.
Automated maintainer review (Claude Code review agent).
This is a owncloud-calens-bot changelog regeneration. The diff touches only CHANGELOG.md and purely assembles/regenerates changelog content from already-merged PR fragments (new [unreleased] compare base v12.4.1...master, plus the 12.4.1 and additional 12.4.0 sections for #13907, #13844, #13822, #13826, #13827, #13834, #13843, #13867, #13877, #13759, #13769, #13795, #13802, #13803). No source code, config, or build changes. Content looks consistent with the referenced PRs/issues.
Two notes:
- This PR is the changelog update itself (bot-generated), so
changelog=present— nothing to add. - PR #13910 has the same head SHA (
e334b3b) and same branch (chore/changelog-update) — it appears to be a duplicate of this PR. One of the two should be closed to avoid confusion.
Not approving/merging via the agent: mergeStateStatus is BLOCKED and the security/snyk check is failing (8 tests). Auto-merge requires all checks green and a mergeable state, so this is left for a human to merge once the branch is unblocked.
e334b3b to
bea84e9
Compare
f373698 to
4a25abb
Compare
DeepDiver1975
left a comment
There was a problem hiding this comment.
Automated maintainer review (Claude Code agent).
LGTM — this is a calens-generated changelog regeneration. The diff touches only CHANGELOG.md: it adds the [12.4.1] (2026-06-18) release section assembled from the existing unreleased fragments (plus a backfill of the [12.4.0] section) and updates the compare link. No source code, config, or fragment files are modified, so there is no functional risk — the content is mechanically derived from fragments already merged on this branch.
- mergeable=MERGEABLE, mergeStateStatus=BLOCKED (awaiting required checks/review — expected).
- changelog: this PR is the changelog update (present / n-a).
Note on the duplicate: PR #13910 carries the identical head SHA (4a25abb) and head branch (chore/changelog-update) but targets master. A 12.4.1 release changelog belongs on the release line, so #13911 (base stable-12.4) is the canonical PR; #13910 looks like a mis-based duplicate of the same regeneration and should likely be closed (or re-based) to avoid landing the 12.4.1 release section onto master.
No merge action taken (review-only).
4a25abb to
cd0e3fd
Compare
|
DeepDiver1975
left a comment
There was a problem hiding this comment.
Automated maintainer review (Claude Code review agent).
Scope verified — changelog-only. This PR touches exactly one file, CHANGELOG.md (+187/-3), regenerating the rendered changelog for the 12.4.2 release (and backfilling the 12.4.1 / 12.4.0 sections) from calens fragments. No source/code changes, no behavioral risk. This is the expected calens-bot output and the changelog content is correct → changelog present.
Mergeability. mergeable=MERGEABLE, mergeStateStatus=BLOCKED. The BLOCK is from the security/snyk check reporting failures (8 pre-existing dependency tests) — unrelated to this changelog-only diff; functional checks (build, check-tests-passed, changelog generation, SonarCloud, CLA, semantic-commit validation) are green. Base branch is correctly stable-12.4.
Duplicate pair note. PR #13910 carries the same head SHA (cd0e3fd) but is based on master instead of stable-12.4, and is CONFLICTING / DIRTY (84 changed files, +1111/-370) — the mis-based, non-mergeable duplicate. #13911 (this PR, base stable-12.4) is the canonical, mergeable one; #13910 should be closed in favor of this one.
Verdict: looks good as a changelog regeneration. Leaving merge to a human maintainer.



Automated changelog update via Calens. This pull request is updated on each push to
stable-12.4— merging it will close it and a fresh one will be opened on the next change.