release: prepare v1.5.1 GitHub Marketplace launch - #40
Merged
Conversation
paladini
marked this pull request as ready for review
July 26, 2026 09:53
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.
Summary
Prepare Harness Score v1.5.1 for its initial GitHub Marketplace Action release.
1.5.1instead oflatest@mainusage with the stable@v1reference across the root README, Action README, and all localized guidesWhy
GitHub's Marketplace release form rejected the existing 205-character Action description. The audit also found that consumers were directed to a mutable branch, the Action executed the mutable npm
latesttag by default, Action inputs were interpolated directly into Bash, and CI did not exercise the packaged Action itself. The release workflow also publishes npm, GitHub Packages, and JSR for every GitHub Release, so all version surfaces need to stay aligned for the Marketplace release.User impact
After the release is published and the
v1tag is created, users can consumepaladini/harness-score@v1with reproducible default scanner behavior, safer input handling, and CI-backed Action packaging. Existingaction/consumers remain compatible because the legacy metadata stays byte-for-byte aligned with the root entrypoint.Marketplace fields
Validation
npm test— 20 files, 268 tests passednpm run lint— passed; 18 pre-existing CSS warnings, no errorsnpm run docs:build— passednpm run scan -- --min-level 4— L4, 108/108npm run plugins:sync-check— passedactionlintv1.7.12 — passednpm audit --omit=dev— 0 vulnerabilitiesnpm pack -w harness-score --dry-run --json—harness-score@1.5.1, 11 filesgit diff --check— passedRelease boundary
This PR does not publish a GitHub Release, list the Action in Marketplace, or create/move the
v1tag. Those steps remain gated on merge and a successful release workflow.