Releases: toeverything/AFFiNE
Releases · toeverything/AFFiNE
2025.12.15-canary.908
feat(core): find todo list based on 'checkbox' search query (#13982) This feature enhances the /slash command by allowing users to search for 'checkbox' and have the to-do list item show up as a result. Users come from different systems and environments, and some may use the name 'checkbox' but be confused as they cannot find it in the search menu. This is achieved by adding a `searchAlias` property on the to-do list item block that contains the string `checkbox`. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added search-alias support for slash menu items so entries can be found by alternative terms. * To-do List entry now includes "checkbox" as an additional searchable alias to improve discoverability. * Slash menu search results updated to reflect alias-driven matches (additional item appears when searching). <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: DarkSky <[email protected]>
2025.12.14-canary.903
fix: title icon display (#14101) fix #14073
2025.12.13-canary.904
fix: roll back electron version to v35 (#14089) In electron v36, all workers do not work. The webpack configuration is too complicated, so go back first. If start a new project with [forge](https://www.electronforge.io/) and latest electron, the worker works well. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Downgraded the Electron development/runtime used for building and testing the desktop app from v36 to v35; this is a development-environment change with no functional or API changes affecting end users. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025.12.11-canary.906
feat(i18n): add Polish language support (#14080) It's my first time making a pull request to any repo. If there are any issues, let me know. ## Summary Adds Polish language support. Translation is 98% complete (10,447/10,646 words). ## Changes - Added `pl` to Language type - Added Polish to SUPPORTED_LANGUAGES with lazy loading The `pl.json` file already exists in the repo with good translation coverage. Some AI-related strings are not yet translated but will fall back to English. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added Polish language support to the application, including localized language name, native language name, and flag emoji. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai -->
0.25.7
What's Changed
- fix(editor): use onBlur for input handling in property menu by @lawvs in #14049
- fix(server): apple sign by @darkskygit in #14053
- feat(i18n): update FR translate & corrections by @Zegnos in #14052
- feat(native): native reader for indexer by @darkskygit in #14055
- fix(core): handle image-blob reduce errors more gracefully by @ddybing in #14056
- feat(server): improve oauth by @darkskygit in #14061
- chore: bump up nodemailer version to v7.0.11 [SECURITY] by @renovate[bot] in #14062
New Contributors
Full Changelog: v0.25.6...v0.25.7
0.25.7-beta.0
v0.25.7-beta.0 chore: bump version
2025.12.6-canary.903
v2025.12.6-canary.903 fix: lint
2025.11.28-canary.904
v2025.11.28-canary.904 fix(editor): one-time size mismatch during surface-block resize after…
2025.11.27-canary.904
fix: improved error description of proxy size limits (#14016) **Summary:** This PR improves the user feedback when encountering an HTTP 413 (_CONTENT_TOO_LARGE)_ error caused by a file size limit in the proxy / ingress controller in a self-hosted environment. **Example scenario:** A self-hosted environment serves AFFiNE through an nginx proxy, and the `client_max_body_size` variable in the configuration file is set to a smaller size (e.g. 1MB) than AFFiNE's own file size limit (typically 100MB). Previously, the user would get an error saying the file is larger than 100MB regardless of file size, as all of these cases resulted in the same internal error. With this fix, the _CONTENT_TOO_LARGE_ error is now handled separately and gives better feedback to the user that the failing upload is caused by a fault in the proxy configuration. **Screenshot of new error message** <img width="798" height="171" alt="1MB_now" src="https://github.com/user-attachments/assets/07b00cd3-ce37-4049-8674-2f3dcb916ab5" /> **Affected files:** 1. packages/common/nbstore/src/storage/errors/over-size.ts 2. packages/common/nbstore/src/impls/cloud/blob.ts I'm open to any suggestions in terms of the wording used in the message to the user. The fix has been tested with an nginx proxy. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Improved user-facing error messages for file upload failures. When an upload exceeds the file size limit, users now receive a clearer message indicating that the upload was stopped by the network proxy due to the size restriction, providing better understanding of why the upload was rejected. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025.11.16-canary.903
v2025.11.16-canary.903 chore: cleanup logs