Repository navigation
fix: restore queue scope, Zammad actor and mobile navigation guards - #306
Merged
stefan-ernst merged 2 commits intoOct 2, 2026
Merged
Conversation
This was referenced Oct 2, 2026
Contributor
|
thanks for noticing! main is currently in heavy development, did not even catch that one |
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.
I fixed four regressions:
Regression tests live in the companion core-tests PR. The queue scope tests pass with SQLite and PostgreSQL, including concurrent writes. The public quick suite passed. I also updated DOMPurify to 3.4.16 and the resolved devalue dependency to 5.9.4; npm audit reports no known vulnerabilities in the frontend dependency tree.