Update ghcr.io/usememos/memos Docker tag to v26 #72
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/ghcr.io-usememos-memos-26.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
0.31.0→26.11.1@demophoon
Release Notes
usememos/memos (ghcr.io/usememos/memos)
v26.11.1Compare Source
Memos 26.11.1 adds Markup for drawings and image annotations, a full emoji reaction picker, and a refreshed interface. Attachment browsing, editing reliability, and sign-in forms also improve.
Highlights
Fixes and polish
Administration and integrations
Cache-Control: no-store, preventing caches from retaining those 404 responses after a deployment. (static asset caching)UploadAttachmentSpec.replace_attachmentreplaces an owned attachment's content while keeping its name, memo, and creation time. Administrators may also replace attachments; external links and motion-photo parts cannot be replaced. (#6533)Upgrade notes
InstanceSetting.MemoRelatedSetting,memo_related_setting, and theMEMO_RELATEDkey are removed. Before upgrading, removeinstance/settings/MEMO_RELATEDandmemoRelatedSettingdeclarations from configuration files, including references inlifecycleorremoved. Files containing them are rejected. The next configuration apply releases the old ownership record automatically; stored reactions are preserved. API clients must stop using the removed setting. (reaction setting removal)--background,--primary, andtext-muted-foreground, need to target the new--mu-*variables andmu-classes. (#6528)New Contributors
Full Changelog: https://github.com/usememos/memos/compare/26.11.0...26.11.1
v26.11.0Compare Source
Memos 26.11.0 fixes typing Japanese and Korean in Safari and makes attachment failures visible instead of opaque. The server cache and upgrades from v0.31 deployment files are also more reliable.
Fixes and polish
Administration and integrations
/etc/secrets(memos-idp-*.json,memos-instance-setting-*.json) are no longer read. Startup now logs a warning naming any that are still present, so settings they used to provide, such as an S3 storage or an identity provider, do not revert silently. Move them into the configuration directory (/etc/memos/config) as described in the 26.10.0 upgrade notes. (startup warning, legacy filenames, #6515)New Contributors
Full Changelog: https://github.com/usememos/memos/compare/26.10.0...26.11.0
v26.10.0Compare Source
Memos 26.10.0 adds a rich editor that shows a memo as it will look while you write, per-user usage limits, and declarative configuration for operators. Browsing, Markdown rendering, sign-in, security, and the server improve throughout, and releases now use calendar versions.
Highlights
has_attachmentsandhas_imageselect memos with files or pictures, in Views, Quick Find, and the API. (#6492)Fixes and polish
<ruby>renders again, collapsible sections and heading sizes are consistent between editing and reading, and Bilibili players embed. Check all and Uncheck all reach tasks inside quotes and nested lists. (tables and footnotes, quotes and callouts, inline HTML, #6364, disclosure spacing, Markdown layout, #6404, #6490, #6508)%,?, or#download and share correctly. (#6414, #6448, preview navigation, #6496, #6401, HTTP attachments, #6506)has_task_list == falsematches memos without the property, constant operands no longer shift later filter conditions, deleting a memo removes its whole comment thread, and blurred content stays out of the detail sidebar. (#6369, pin ordering, #6451, #6457, #6382, folded operands, #6424, #6494)Administration and integrations
/etc/memos/config(--config-dir,MEMOS_CONFIG_DIR). The server applies the directory at startup, ormemos config validate | plan | apply | statedoes it from the command line, so a fresh instance is usable without a browser and staging can match production. Resources the files manage show "Managed by configuration" in Settings and cannot be changed through the UI or API until the file releases them; secrets come from${env:NAME}and${file:/path}. (#6507, linked identities)/healthzreports database outages, the admin's username is hidden from anonymous requests, outbound fetches refuse the CGNAT range, token store failures no longer appear as 401, authorization errors are JSON, hidden paths such as/.well-known/return 404, and MariaDB works. Go and gRPC are updated for CVE-2026-78669 and CVE-2026-84445. (#6475, #6454, #6491, #6256, #6461, #6504, hidden paths, #6497, #6462, #6453)ListAttachmentsuses the shared opaque page token and returns one only when more results exist. The MCP reaction tool no longer shows a redundantparentargument beside its path. (#6452, page token, MCP reaction tool)YY.MM.N, such as26.10.0, with-rc.Kfor candidates and novprefix. Stable images also publish the month tag (26.10) andstable; candidates publish only their own tag. (#6362, #6469, development versions)Upgrade notes
0.31.0once before installing this release if you are on anything older. Versions before0.22go through0.25.3first.0.31.0,26.10-rc.1, and26.10.0-rc.2upgrade directly; fresh installs need nothing. (#6362)/etc/secretsis no longer read: The deployment configuration files introduced in 0.31.0 (memos-idp-*.json,memos-instance-setting-*.json) are ignored, and the database values they overrode take effect again. Move those resources into a configuration directory asmemos.api.Configurationdocuments, keep the same identity provider UID so linked accounts keep working, and runmemos config planto preview before the first start. (#6507)ExportMemosAPI is removed. Administrators download any account's archive; the archive content and the import flow are unchanged. (#6514)has_task_list && has_incomplete_tasks), and the Move to Space action (use the audience menu) are removed. The editor opens in rich mode; turn on Markdown mode under Settings › Editor to keep writing raw Markdown, as the old per-browser choice is not carried over. (device preferences, #6466, Tasks View, audience menu, #6512)Breaking API changes
UserService.ExportMemosandExportMemosRequestare removed. Export is an instance-administrator download atGET /file/users/{username}/export, authenticated like attachments (Bearer header or session cookie), streaming thearchive with
Content-Disposition. One export runs at a time per instance; a second request receives429. Membersask an administrator for their archive.
ImportMemosis unchanged.an administrator password reset. Pre-upgrade access tokens are also rejected; clients must refresh them or sign in
again. The browser session that changes its own password can still refresh; other refresh sessions are revoked.
StorageSetting.upload_size_limit_mband
MemoRelatedSetting.content_length_limitare removed and old values are not migrated. The limits are theUSAGE_LIMITSinstance setting,instance/settings/USAGE_LIMITS, an ordered list of entries read and replaced wholethrough
GetInstanceSettingandUpdateInstanceSetting; the first entry naming a user applies, the last entryapplies to all users. The
usageLimits/{usage_limit}resource and its five RPCs do not exist.UserUsagereturnsthe limit set in effect as
limitspluslimit_index. Exceeding a limit returnsRESOURCE_EXHAUSTEDwith reasonQUOTA_EXCEEDEDand metadatametric,limit, andusage.MemoRelatedSetting.enable_double_click_editis removed; double-click editing is now a per-browser preference inthe web client and is no longer an instance setting.
MemoRelatedSettingkeeps the single fieldreactions = 1./etc/secrets(memos-idp-*.json,memos-instance-setting-*.json)introduced in v0.31.0 are no longer read, and the stored values they overrode take effect again. Identity providers,
instance settings, bootstrap users, and their linked identities are declared instead as
memos.api.Configurationdocuments in the configuration directory (
--config-dirorMEMOS_CONFIG_DIR, default/etc/memos/config), appliedat startup unless
--config-apply=off, or throughmemos config planandmemos config apply. Keep an identityprovider's UID when moving it so linked accounts keep working. An API write that changes a field a file manages
returns
FAILED_PRECONDITIONwithErrorInfo{reason: MANAGED_BY_CONFIGURATION}naming the file and fields;GET /api/instance/configuration(administrators) lists what is managed.CreateIdentityProviderandUpdateIdentityProvidervalidate the provider as it will be stored and returnINVALID_ARGUMENTwhen it has no title, an invalididentifier_filter, noclient_id, a non-absolute or non-HTTP(S)auth_url,token_url, oruser_info_url, an empty scope entry, or nofield_mapping.identifier. A request thatomitted
configorfield_mappingpreviously failed withINTERNAL.UpdateInstanceSettingforSTORAGErequires every new or changed S3 storage to haveendpoint,region,bucket,access_key_id, andaccess_key_secret(an empty secret still keeps the stored one). ForGENERAL,week_start_day_offsetmust be between -1 and 6.BASICcannot be written. Notification validation errors namefields in proto form (
smtp_host,use_tls).v1version marker. Every client must update its paths:/api/v1/...to/api/...(for exampleGET /api/memos). Server-sent events move from/api/v1/sseto/api/sse.memos.api.v1is nowmemos.api, so Connect and gRPC procedures move from/memos.api.v1.<Service>/<Method>to/memos.api.<Service>/<Method>.memos.api.v1/<Type>tomemos.api/<Type>.domainofgoogle.rpc.ErrorInfodetails is nowmemos.api./api/v1/...and/memos.api.v1.*return410 Gonewith anUNIMPLEMENTEDerror that points here. The next release removes these routes.
reservedranges are removed.JSON field names are unchanged; clients that use the binary protobuf encoding must regenerate from the new schema.
User.Role(ADMIN = 1,USER = 2) andUserSetting.Key(GENERAL = 1,WEBHOOKS = 2,TAGS = 3). Clients that send numeric enum values must update them.MemoService:ListMemoAttachments,ListMemoRelations,ListMemoComments,CreateMemoComment,ListMemoReactions, andUpsertMemoReactiontakeparentinstead ofname(REST path variable{parent=memos/*}).ListMemoCommentsResponse.memosis nowcomments. The nestedMemoRelation.Memotype isnow
MemoRelation.MemoRef. TheMemoShareresource singular/plural is nowmemoShare/memoShares.UserService.ListAllUserStatsis nowListUserStats. It requires aparent:users/-for all users (RESTGET /api/users/-/statsinstead ofGET /api/users:stats) orusers/{user}for one user. The response fieldstatsis nowuser_stats.BatchGetUsersRequest.usernamesis nownamesand takes resource names (users/{user}), not bare usernames.PersonalAccessToken.created_at,expires_at, andlast_used_atare nowcreate_time,expire_time, andlast_use_time.LinkedIdentity.idp_nameandextern_uidare nowidentity_providerandexternal_uid;CreateLinkedIdentityRequest.idp_nameis nowidentity_provider.MemoViewandUserNotificationresource singulars are nowmemoViewanduserNotification.UserStats.tag_countis nowtag_counts.MemoImportPlan,MemoImportReport, andMemoImportIssueare nowImportMemosPlan,ImportMemosReport, andImportMemosIssue.ImportMemosPlan.memosandattachmentsare nowmemo_countandattachment_count;ImportMemosIssue.memois nowmemo_uid.UserNotification.SpaceInvitationPayload.Stateis nowInvitationState.UpdateUserSettingRequest.settingandListUserSettingsResponse.settingsare nowuser_settinganduser_settings;UpdateInstanceSettingRequest.settingandBatchGetInstanceSettingsResponse.settingsare nowinstance_settingandinstance_settings.SignInResponse.access_token_expires_atandRefreshTokenResponse.expires_atare both nowaccess_token_expire_time.SignInRequest.SSOCredentialsis nowSsoCredentials, and itsidp_nameis nowidentity_provider.New Contributors
Full Changelog: https://github.com/usememos/memos/compare/v0.31.0...26.10.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.
f4b7504c7etoadebde6cfcadebde6cfctoa1147a0a14