ci: gate action.yml Marketplace publishability#9
Merged
Conversation
Publishing the composite action to the GitHub Marketplace has fixed metadata requirements (name, description, branding.icon/color from an allowed set) that are easy to break in action.yml and only surface when someone tries to publish. Add a contract test that pins those requirements so a regression fails at `cargo test` time, alongside the existing release/schema contract tests. The publish button itself has no API and needs the Marketplace agreement accepted in the web UI, so document that one-time manual step (and the automatic per-release updates afterward) in the release checklist. Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
action.ymlalways stays in a publishable shape.tests/marketplace_action_contract.rs(runs under the existingcargo testCI job) that pins the Marketplace metadata requirements:name,description, abrandingblock withicon+color, the color from GitHub's allowed set, and an icon shaped like a valid Feather name (and not on GitHub's blocklist). Same "pin both sides / fail at test time" spirit as the release and schema contract tests.Test plan
cargo test --test marketplace_action_contractpasses (4 tests)cargo test+clippy -D warnings+fmt --checkclean