[Bug] 插件市场不会重新解析仓库的 metadata.yaml
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- yaml
- Domain
- backend
Research direction
The payload is an issue tracker with no source files, so the code that reads metadata.yaml during publish lives in another repository and is not named here. Start by finding where the marketplace parses that file and caches the plugin's author and description, then check whether re-publishing or refreshing a version re-reads it. Done means the reproduction steps show the new author and description after a re-publish, or the maintainers have documented that deletion is required. The maintainers have not yet chosen between a re-sync feature and a docs change, so confirm that choice first.
Written by the indexing model from the issue text.
Description
问题概述 / Summary
插件市场不会重新解析仓库的 metadata.yaml:作者名和简介停留在首次发布时,改仓库、刷新页面、重新发布都改不掉。
复现步骤 / Steps to reproduce
- 发布插件(v0.2.0),
metadata.yaml里author: A、旧desc - 修改仓库
metadata.yaml:
同时更新-author: c1overzz & Alterssss (AstrBot port) +author: momo-OwO-qwqshort_desc/desc,新增support_platforms,版本号升到 0.2.0 - 合并到
main,确认 GitHub 上的metadata.yaml已是新值 - 打开
https://cloud.astrbot.app/profile/momo-owo-qwq→ 插件卡片仍显示旧作者c1overzz & Alterssss (AstrBot port)和旧简介 - 刷新页面、清缓存、重新发布都不生效
期望行为 / Expected behavior
仓库 main 的 metadata.yaml 变更后,插件市场展示的 author / desc / short_desc / support_platforms 应该同步更新(至少重新发布或刷新版本后生效)。
如果设计上元数据只在首次发布时读取,希望:
- 发布页提供「重新同步元数据」能力,或者
- 在文档里明确写出「修改 author/desc 必须删除插件后重新发布」,避免作者卡在旧名字上
实际行为 / Actual behavior
作者名永远停留在第一次发布时的值,无法通过任何界面操作更正。
相关页面或资源链接 / Related URL
No response
AstrBot Cloud 版本或环境 / Version or environment
No response
日志、截图或其他上下文 / Logs, screenshots, or context
No response
提交前确认 / Checklist
- 我已搜索现有 issue,确认没有重复反馈。 / I searched existing issues and found no duplicate.
- 我已移除反馈中的密码、Token、Cookie 等敏感信息。 / I removed passwords, tokens, cookies, and other sensitive information.
- Dominant language
- No language data
- Stars
- 6
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 AstrBotDevs/astrbot-cloud-issues
-
[Bug]Openbug
Difficulty 3/5 1-2 days Newbie friendliness 46/100
-
[Bug] 自动安全检查失败Openbug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
给我解封吧求求了,我再也不乱发插件了Open
Difficulty 1/5 Under an hour Newbie friendliness 5/100
AstrBotDevs/astrbot-cloud-issues#32 · 2 comments ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 15/100
All issues in AstrBotDevs/astrbot-cloud-issues
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
progress-deadline annotation accepts "0s" although validation says it must be positivePossibly taken @BahaaMattar claimed this today. Openarea/API kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mailcow/mailcow-dockerized#7677 · 1 comment ·
Maintainers usually reply within 1 day
-
area:plugins kind:perf priority:p3 ready
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
api cleanup
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day