Skip to content

chore: publish the Crabbox Zed package in the extension registry #1157

Description

@zozo123

Context

The first-party Zed package lives under integrations/zed, but it has never been submitted to https://github.com/zed-industries/extensions. Registry code search and open/closed pull request search have no Crabbox entry, so users can install only through Zed development-extension flow.

#1155 fixes the package file associations and documents the exact publication state. Wait for that change to merge so the registry submodule can pin a commit reachable from openclaw/crabbox.

Publication follow-up

  • Fork and update zed-industries/extensions.
  • Add https://github.com/openclaw/crabbox.git as extensions/crabbox in .gitmodules.
  • Pin the submodule to the merged Crabbox commit.
  • Add this entry to extensions.toml and run the registry sorter:
[crabbox]
submodule = "extensions/crabbox"
version = "0.1.0"
path = "integrations/zed"

The package already has its own MIT license, manifest, pinned YAML grammar, static validation, official compiler packaging, and controlled task E2E coverage.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Low-risk cleanup, docs, polish, ergonomics, or speculative feature.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🌊 off-meta tidepoolIssue quality rating does not apply to this item.

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions