Fit the description into the Marketplace limit, and check it in the pipeline - #9
Merged
Merged
Conversation
…ipeline. The Marketplace form rejected the action with "Description must be less than 125 characters." - it was 127. The description now names the namespace instead of spelling out "a GitHub organisation or user account", and is 108 characters. 'CheckMarketplaceMetadata.yml' is a local reusable workflow validating the metadata on every push, so the next such defect is a red pipeline on 'dev' rather than a rejection at publish time: the metadata file at the repository root, a name, a description below the limit, a branding icon, one of the eight accepted branding colours, and a public repository. Publishing itself is deliberately not automated - there is no API for it. Co-Authored-By: Patrick Lehmann <Paebbels@gmail.com> Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RnpaXYDwfNwnJrQew78j3f
Paebbels
reviewed
Sep 11, 2026
Paebbels
reviewed
Sep 11, 2026
Merged
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
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.
Bug Fixes
The action's description was 127 characters; the Marketplace allows fewer than 125. That is the first of the two
errors:
108 characters, and it says the same thing — "a GitHub organisation or user account" is what a namespace is, and
the parameter documentation still spells it out where there's room.
New Features
CheckMarketplaceMetadata.yml— a local reusable workflow, run by the pipeline on every push, so the nextsuch defect is a red pipeline on
devrather than a rejection at publish time. It checks:action.yml/action.yamlat the repository rootnamepresentdescriptionpresent and shorter than the limitbranding.iconpresent and shaped like a Feather namebranding.colorone of white, yellow, blue, green, orange, red, purple, gray-darkThe values are read with the YAML parser, not with
grep, so a folded or quoted description is measured as theMarketplace measures it. The limit is an input, defaulting to 125.
The three release jobs
needs:it, so a release can't be tagged with metadata the Marketplace would reject.The icon is checked for shape, not membership. The accepted set is a subset of Feather, long and subject to
change, so hard-coding it here would go stale silently; the check says so rather than implying more than it
verifies.
Documentation
Unit Tests
Nine cases against the extracted step, all passing: valid metadata; the exact 127-character description the
Marketplace rejected, reported as
'description' is 127 characters; the Marketplace requires fewer than 125.; amissing colour;
turquoise; a malformed icon; an empty description; a missing metadata file; invalid YAML; and aprivate repository.
One of those found a defect in the check itself, which is why it's worth having:
action.get("description", "")returns
Nonefor a key present with an empty value, andstr(None)is the four-character string"None"— sodescription:with nothing after it would have passed as a four-character description. It readsor ""now.The other two harnesses still pass unchanged: 23 for the action, 10 for the version-branch workflow.
Related Issues and Pull-Requests
v1.0.1release pull-request follows this one.🤖 Generated with Claude Code