OG versions (0.10.15 & 1.0.0) incorrectly show updates to DB 2.0.1
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start by tracing the update-check flow reached through Settings > General > Check for update and compare it with the Homebrew update path for OG 0.10.15 and 1.0.0. Confirm that both paths offer only OG-track releases and never DB 2.0.1, then exercise the listed versions on macOS.
Written by the indexing model from the issue text.
Description
Search first
- I searched and no similar issues were found
What Happened?
As of today, both my long‑running Logseq OG 0.10.15 installation and a fresh install of Logseq OG 1.0.0 are prompting me to update to Logseq 2.0.1. My understanding is that OG users must avoid updating to DB as they are now separate versions for markdown and DB.
Reproduce the Bug
-
Via Homebrew, observe Homebrew wanting to upadte Logseq version 0.10.15 to version 2.01.
-
Within the app:
Settings>General>Check for update
Observe the update prompt for version 2.0.1.
Expected Behavior
Logseq OG should only show update notifications for OG‑track releases, not DB releases.
Screenshots
No response
Desktop or Mobile Platform Information
macos
Logseq OG versions tested: 0.10.15, 1.0.0
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
- I'm willing to submit a PR (Thank you!)
- Dominant language
- Clojure
- Stars
- 316
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from logseq/og
-
Difficulty 4/5 3-5 days Newbie friendliness 62/100
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Podman documentation is out of datePossibly taken @troyvit claimed this 1 day ago. Open.Needs Triage Priority:P3 Type:New Feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
metabase/metabase#83625 · 1 comment ·
Maintainers usually reply within 1 day
-
bug: MCP server rejects request bodies over 100kb (express.json default) with PayloadTooLargeErrorOpenneeds triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day