chore: update changelog#13910
Conversation
[full-ci] chore: bump version to 12.4.0
…version chore: use whitelisted calens version
The MFA expiry worker and broadcast channel were initialized unconditionally at startup. Now they are lazily created only when the vault capability is enabled and a session duration is configured, preventing the expiry warning from firing when vault mode is off. Also replaced `self` with `globalThis` in the worker as SonarQube was flagging the deprecated `self` reference.
* fix(e2e): [OCISDEV-843] Use correct listType for search results after pressing Enter * fix(e2e): [OCISDEV-843] Keeps resourcePage.searchList as the correct listType * fix(e2e): [OCISDEV-843] Using the filesList fix for listType Co-authored-by: Deyan Zhekov <deyan.zhekov@kiteworks.com>
…ching and cancel button visibility (#13843) (#13861) Clear previous theme's custom properties before applying the new theme so old values don't persist. Treat empty token strings as unset by removing the property instead of setting it to blank. Also fix the cancel button in the password protected folder modal being invisible against the dark action bar background.
…3842) The topbar logo was not visible in Firefox because the SVG files lacked explicit `width` and `height` attributes. Firefox requires these attributes to establish intrinsic dimensions when loading SVGs via `<img>`; without them it renders the image as 0×0. Chrome infers the dimensions from `viewBox` alone. Signed-off-by: Lukas Hirt <info@hirt.cz>
When opening the vault for the first time, the user is redirected to an external IdP for 2FA. Upon returning, the OIDC callback URL contains no vault context, causing the regular theme to be applied instead of the vault theme. We now also check the stored post-login redirect URL during the OIDC callback to correctly detect vault mode. Signed-off-by: Lukas Hirt <info@hirt.cz>
* fix(web-pkg): [OCISDEV-911] pass vault=true param to capabilities endpoint
…gate-iframe-csrf fix(web-pkg): [OCISDEV-777] validate postMessage origin in embed mode…
Signed-off-by: Lukas Hirt <info@hirt.cz>
Signed-off-by: Lukas Hirt <info@hirt.cz>
Signed-off-by: Lukas Hirt <info@hirt.cz>
* chore: bump version to v12.4.1 Signed-off-by: Lukas Hirt <info@hirt.cz> * chore: create v12.4.1 changelog Signed-off-by: Lukas Hirt <info@hirt.cz> * chore: sync translations Signed-off-by: Lukas Hirt <info@hirt.cz> --------- Signed-off-by: Lukas Hirt <info@hirt.cz>
|
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 failed. 72 issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
…instead of hardcoded value (#13908)
8b31fa2 to
e334b3b
Compare
DeepDiver1975
left a comment
There was a problem hiding this comment.
Automated maintainer review (Claude Code review agent).
Duplicate detection: This PR (#13910) and #13911 share the same head commit e334b3b on the same branch chore/changelog-update, but target different base branches:
- #13910 (this PR) → base
master— shows 84 changed files and is CONFLICTING / DIRTY. The branch content belongs to thestable-12.4line, so diffing it against the divergedmasterproduces a large spurious diff and a merge conflict. This is not a clean changelog update againstmaster. - #13911 → base
stable-12.4— shows exactly 1 file (CHANGELOG.md), a clean calens changelog regen, and is MERGEABLE.
Conclusion: #13911 is the canonical changelog PR; #13910 appears to be a mis-based duplicate (correct branch, wrong base). I recommend closing #13910 (or re-basing it onto the intended branch if a master changelog update was actually wanted) and proceeding with #13911.
I am not approving or merging this PR: it is the non-canonical duplicate and is currently un-mergeable (conflicts against master). To avoid a duplicate-merge race, the changelog merge should go through #13911 only.
changelog: this PR is the changelog update (n/a — nothing to add).
bea84e9 to
83086ad
Compare
|
83086ad to
f373698
Compare
f373698 to
4a25abb
Compare
DeepDiver1975
left a comment
There was a problem hiding this comment.
🤖 Automated review by the Claude Code review agent (acting as maintainer).
Verdict: comment — recommend closing this PR as a non-canonical duplicate.
This calens changelog-regen PR (chore/changelog-update, head 4a25abb) shares the exact same head commit as #13911. The two differ only in base branch:
- This PR (#13910) targets
master. Because thechore/changelog-updatebranch is based on the release line, the diff againstmasterballoons to 80+ unrelated files (workflows,package.json, translations, components, …) and GitHub reports itCONFLICTING/DIRTY. This is the mis-based copy. - #13911 targets
stable-12.4, where the same head reduces to a clean single-fileCHANGELOG.mdupdate and isMERGEABLE. That is the canonical PR.
Recommendation: close #13910 and proceed with #13911. No changes needed to the changelog content itself — this is the changelog update (changelog=present), and the canonical PR carries it correctly.
4a25abb to
cd0e3fd
Compare
|
DeepDiver1975
left a comment
There was a problem hiding this comment.
Automated maintainer review (Claude Code agent).
This is a calens changelog regeneration on chore/changelog-update (head cd0e3fd) — the changelog update itself, so the changelog requirement is satisfied (this PR is the changelog).
However, #13910 and #13911 share the same head commit (cd0e3fd) and are duplicates. #13910 is based on master and currently reports mergeable: CONFLICTING / DIRTY — its diff is mis-based against master and pulls in unrelated changes (whole workflow files, etc.), so it cannot merge cleanly. #13911 is based on the correct release branch stable-12.4 and is MERGEABLE.
Recommendation: close this PR (#13910) as the non-canonical, mis-based duplicate and proceed with #13911 as the canonical changelog update. No code review concerns beyond the duplication/base mismatch.



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