[Bug] 插件市场不会重新解析仓库的 metadata.yaml

Open
#23 1 comment 0 reactions 0 assignees View on GitHub

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

bug
问题概述 / Summary

插件市场不会重新解析仓库的 metadata.yaml:作者名和简介停留在首次发布时,改仓库、刷新页面、重新发布都改不掉。

复现步骤 / Steps to reproduce
  1. 发布插件(v0.2.0),metadata.yaml 里 author: A、旧 desc
  2. 修改仓库 metadata.yaml:
    -author: c1overzz & Alterssss (AstrBot port)
    +author: momo-OwO-qwq
    
    同时更新 short_desc / desc,新增 support_platforms,版本号升到 0.2.0
  3. 合并到 main,确认 GitHub 上的 metadata.yaml 已是新值
  4. 打开 https://cloud.astrbot.app/profile/momo-owo-qwq → 插件卡片仍显示旧作者 c1overzz & Alterssss (AstrBot port) 和旧简介
  5. 刷新页面、清缓存、重新发布都不生效
期望行为 / 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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AstrBotDevs/astrbot-cloud-issues

All issues in AstrBotDevs/astrbot-cloud-issues

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.