Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changelogs in Forge update checker #921

Open
Gaming32 opened this issue May 22, 2024 · 0 comments
Open

Changelogs in Forge update checker #921

Gaming32 opened this issue May 22, 2024 · 0 comments
Labels
enhancement For issues suggesting enhancements to existing features

Comments

@Gaming32
Copy link

Gaming32 commented May 22, 2024

Is your suggested enhancement related to a problem? Please describe.

Forge and NeoForge support changelogs in their update.json files. Labrinth's generated forge_update.json files do not include this information.

Describe the solution you'd like

It would be useful to support this information.

Describe alternatives you've considered

No response

Additional context

The full format of update.json files is as follows:

{
  "homepage": "<homepage url>",
  "promos": {
    "<mc version 1>-recommended": "<version 1>",
    "<mc version 1>-latest": "<version 2>",
    "<mc version 2>-recommended": "<version 3>",
    "<mc version 2>-latest": "<version 4>"
  },
  "<mc version 1>": {
    "<version 1>": "<changelog for version 1>",
    "<version 2>": "<changelog for version 2>"
  },
  "<mc version 2>": {
    "<version 3>": "<changelog for version 3>",
    "<version 4>": "<changelog for version 4>"
  }
}

Currently Labrinth only provides the homepage and promos fields.

@Gaming32 Gaming32 added the enhancement For issues suggesting enhancements to existing features label May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement For issues suggesting enhancements to existing features
Development

No branches or pull requests

1 participant