Skip to content

fix: ship @cobusgreyling/loop 0.1.1 (restore name)#378

Merged
cobusgreyling merged 2 commits into
mainfrom
fix/restore-loop-package-name
Jul 24, 2026
Merged

fix: ship @cobusgreyling/loop 0.1.1 (restore name)#378
cobusgreyling merged 2 commits into
mainfrom
fix/restore-loop-package-name

Conversation

@cobusgreyling

Copy link
Copy Markdown
Owner

Summary

  • @cobusgreyling/loop@0.1.0 is live on npm (initial 404 was registry propagation).
  • Reverts the temporary @cobusgreyling/loop-cli rename.
  • Bumps to 0.1.1 with main + stable bin.loop.

Verify

npx @cobusgreyling/loop@0.1.0 --help   # already works
# after tag:
npx @cobusgreyling/loop@0.1.1 --version

0.1.0 is live on npm (registry lag looked like a 404). Revert the
loop-cli rename, keep bin name loop, and publish 0.1.1 with main set.
@github-actions

Copy link
Copy Markdown
Contributor

Thanks @cobusgreyling for contributing a docs improvement — visible, reviewable PRs like this grow the reference for everyone.

What happens next

  • Maintainer aims for same-day review on story, adopter, and scoped docs/example PRs (CONTRIBUTING.md).
  • good first issue PRs: comment on the linked issue so we can assign and close on merge.

More ways to help

— loop-engineering maintainers

@github-actions

Copy link
Copy Markdown
Contributor

Loop Readiness Audit

Score: 100/100 (L3)

Strong loop readiness — good candidate for L3 with explicit gates.

Top suggestions

  • Loop Ready 80+: version this loop for a fleet — npx @cobusgreyling/loop-init . --with-fleet
  • Loop Ready 80+: version this loop's memory — npx @cobusgreyling/loop-init . --with-memory
  • Loop Ready 80+: version this loop as a harness — npx @cobusgreyling/loop-init . --with-foundry · showcase https://github.com/cobusgreyling/harness-foundry/blob/main/docs/showcase.md
  • Scaffold a harness: npx @cobusgreyling/loop-init . --with-foundry (or npx @cobusgreyling/harness-foundry init --from loop-engineering:daily-triage)
  • Scaffold memory tiers: npx @cobusgreyling/loop-init . --with-memory

Posted by audit.yml · loop-audit docs

1 similar comment
@github-actions

Copy link
Copy Markdown
Contributor

Loop Readiness Audit

Score: 100/100 (L3)

Strong loop readiness — good candidate for L3 with explicit gates.

Top suggestions

  • Loop Ready 80+: version this loop for a fleet — npx @cobusgreyling/loop-init . --with-fleet
  • Loop Ready 80+: version this loop's memory — npx @cobusgreyling/loop-init . --with-memory
  • Loop Ready 80+: version this loop as a harness — npx @cobusgreyling/loop-init . --with-foundry · showcase https://github.com/cobusgreyling/harness-foundry/blob/main/docs/showcase.md
  • Scaffold a harness: npx @cobusgreyling/loop-init . --with-foundry (or npx @cobusgreyling/harness-foundry init --from loop-engineering:daily-triage)
  • Scaffold memory tiers: npx @cobusgreyling/loop-init . --with-memory

Posted by audit.yml · loop-audit docs

@cobusgreyling
cobusgreyling merged commit 511f150 into main Jul 24, 2026
3 checks passed
@cobusgreyling
cobusgreyling deleted the fix/restore-loop-package-name branch July 24, 2026 08:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant