Skip to content

Validate tokens before use, on non-dry runs #25

@MattSturgeon

Description

@MattSturgeon

It is possible to go through the CurseForge publish and then later discover that the Modrinth token has expired (or vice versa, if refactored).

E.g. https://github.com/MinecraftFreecam/Freecam/actions/runs/27571829697/job/81527688774

Maybe part of the early pre-run validation should check with the respective APIs that the tokens have access to the endpoints we need?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions