chore: bump npm package versions for metadata discoverability updates#35
Merged
Merged
Conversation
- @cobusgreyling/loop-audit: 1.4.0 → 1.4.1 - @cobusgreyling/loop-init: 1.2.0 → 1.2.1 - @cobusgreyling/loop-cost: 1.0.1 → 1.0.2 Updated descriptions and keywords (from previous discoverability work) will now ship to npm on tag-triggered release. Also added changelog entry for loop-audit.
Contributor
Loop Readiness AuditScore: 100/100 (L3) Strong loop readiness — good candidate for L3 with explicit gates. No suggestions — looking good. Posted by |
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.
Bumps the three published packages to ship the improved descriptions and keywords from the recent discoverability work:
@cobusgreyling/loop-audit1.4.0 → 1.4.1@cobusgreyling/loop-init1.2.0 → 1.2.1@cobusgreyling/loop-cost1.0.1 → 1.0.2Changes
This is a metadata-only release (no behavior changes).
After this PR merges, the release tags will be pushed to trigger the GitHub Actions publish workflows (which use trusted publishing).
See: docs/RELEASE.md