Community plugin dashboard cannot detect a valid release; Preview Scan returns GitHub API 401 “Bad credentials”

Basement
1

image
image1092×525 39 KB

image
image844×401 12.7 KB

image
image839×505 27.5 KB

Hi,

I am trying to publish an update for my existing Community plugin, HanMark, but the Community developer dashboard cannot retrieve the repository correctly.

Plugin information

Errors shown by the dashboard

The dashboard has shown the following errors in sequence:

  1. We couldn't read manifest.json from your repository's default branch.

  2. No release matches your manifest version.

  3. Preview Branch Scan now returns:

    GitHub API error: 401 Unauthorized — {"message":"Bad credentials","documentation_url":"https://docs.github.com/rest","status":"401"}

The Preview Branch Scan fails even when the branch field is left blank to use the default branch.

Repository checks

I verified the repository and release independently:

  • The default branch is exactly 2.5.5.
  • The root manifest.json is publicly accessible:
    https://raw.githubusercontent.com/laguna821/hanmark/HEAD/manifest.json
  • Its version is exactly 2.5.5.
  • The GitHub Release tag is exactly 2.5.5, without a v prefix.
  • The Release is public and marked as Latest.
  • It is neither a draft nor a pre-release.
  • The Release contains the required uploaded assets:
    • main.js
    • manifest.json
    • styles.css
  • The tag and default branch point to the same commit.
  • The root manifest and Release asset manifest are byte-identical and contain no BOM or hidden characters.
  • All raw files, Release pages, and asset download URLs return HTTP 200 without authentication.

Troubleshooting attempted

  • Disconnected and reconnected my GitHub account in the Obsidian Community profile.
  • Confirmed that the connected GitHub account is laguna821.
  • Signed out and back into the Community dashboard.
  • Retried both the New Release Check and Preview Branch Scan.

The Preview Scan still returns 401 Bad credentials.

Because the repository is public and all release requirements are satisfied, this appears to be an expired or invalid GitHub credential stored by the Community dashboard rather than a repository or release configuration problem.

Could someone please reset or refresh the stored GitHub authorization and repository metadata for my Community account or the HanMark listing?

I have attached screenshots of all three errors. I have not recreated the tag or Release because the existing 2.5.5 Release is valid and publicly accessible.

Thank you.

2

It is also happening to me today when I was trying to test a test branch for muy plugin.

3

Same for me

4

We are aware of this problem and we are working ok a fix

5

Same symptoms here (plugin neurovim), but I want to add a data point that I think is more serious than the dashboard errors: this is not only failing scans — plugins are being delisted.

community-plugins.json in obsidianmd/obsidian-releases is a mirror of the backend, so the removals are visible in the commit history. Six mirror runs today:

Time (UTC) Commit Plugins
08:09:30 a3ddaff5 −9 / +4
10:14:59 2b56629d −23 / +0
11:58:24 62c868d4 −19 / +0
13:58:48 7f3b42d2 −18 / +0
15:00:24 ec386ba9 −7 / +0
15:55:09 e6492a09 −11 / +0

That is 87 plugins removed and 4 added, and as of writing none of the 87 has come back. Together they account for ~1.8M downloads per community-plugin-stats.json. The largest ones are long-established plugins:

  • obsidian-day-planner — 839,318 downloads
  • notebook-navigator — 790,057
  • obsidian-bible-reference — 57,310
  • voice — 34,057
  • karpathywiki — 24,793

Mine was removed in 7f3b42d2 at 13:58:48 UTC:

-  { "id": "neurovim", "name": "NeuroVim", "repo": "johannes-kaindl/neurovim-obsidian" },

This also explains why the dashboard message changes over time, which several of us have seen: once a plugin is delisted, “No release matches your manifest version” replaces the earlier “couldn’t read manifest.json” — the scanner no longer has a listing to match against.

There’s a second signal in community-plugin-stats.json: my entry has download counts up to 0.7.1 and none for 0.7.2, 0.7.3 or 0.7.4, even though 0.7.2 was live in the store from 2026-07-27. So the scanner had stopped processing this plugin days before it was delisted — the 401s look like the visible symptom of something that started earlier.

@WhiteNoise — glad to hear a fix is underway. Could you confirm whether it also covers re-listing the affected plugins? A scanner fix alone would leave the 87 entries missing from community-plugins.json, which means users can’t install or update them even once scanning works again. Happy to provide the full list of removed IDs if that’s useful.

For the record, my releases check out (verified anonymously, i.e. what an unauthenticated client sees): repo public, default branch main, contents/manifest.json → HTTP 200 with 0.7.4, release tag 0.7.4 without v, not a draft, all three assets uploaded, versions.json covering it.

6

this should be fixed now