Skip to content

fix: memos 0.27.0 support#352

Merged
mudkipme merged 1 commit into
mainfrom
fix/memos-0-27
Apr 20, 2026
Merged

fix: memos 0.27.0 support#352
mudkipme merged 1 commit into
mainfrom
fix/memos-0-27

Conversation

@mudkipme
Copy link
Copy Markdown
Owner

No description provided.

@mudkipme mudkipme merged commit 2171252 into main Apr 20, 2026
@mudkipme mudkipme deleted the fix/memos-0-27 branch April 20, 2026 15:26
@Heart1010
Copy link
Copy Markdown

Heart1010 commented Apr 21, 2026

Can not use MoeMemos anymore now...
I'm using latest canary docker image

services:
  memos:
    image: neosmemo/memos:canary
...

which shows this version number in memos Version: vcanary - MoeMemos doesn't let me connect to it anymore 🤔

@mudkipme
Copy link
Copy Markdown
Owner Author

Guess it's caused by usememos/memos@f8a304b

Moe Memos currently checks the version strictly when using the V1 API format (not 0.21.0 or Mortis). It only supports versions 0.27.0 and 0.27.1, and it shows a warning when using a version above 0.27.1. Since canary can't be parsed into a version number, it should be treated as a "future release" and show a warning instead of being marked as unsupported.

You can use Mortis to workaround for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants