Skip to content

feat(registry): add convex package definition - #149

Merged
moshest merged 1 commit into
neuledge:mainfrom
Gohans1:feat/add-convex-definition
Sep 21, 2026
Merged

moshest merged 1 commit into
neuledge:mainfrom
Gohans1:feat/add-convex-definition

Conversation

@Gohans1

@Gohans1 Gohans1 commented Sep 12, 2026

Copy link
Copy Markdown
Contributor

Adds the package documentation definition for Convex (npm/convex) to the community registry.

Convex (get-convex/convex-backend) maintains its official documentation in the monorepo under npm-packages/docs. This unversioned definition tracks the documentation directly from the tip.

Build Verification

Tested locally using the registry test tools:

  • pnpm --filter @neuledge/registry test-registry test convex
    • Sections: 1,329
    • Tokens: 315,852
  • pnpm --filter @neuledge/registry registry build convex
    • Result: dist-packages/npm-convex@latest.db built with 0 errors

Add Convex (https://github.com/get-convex/convex-backend) documentation package definition to the npm registry.

Tested locally with test-registry and registry build (1329 sections, 315852 tokens).
@changeset-bot

changeset-bot Bot commented Sep 12, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 395039e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@moshest moshest left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution! Your CI runs are gated because this is your first PR here, so I built the definition locally to check it:

Building npm/convex@latest...
  Sections: 1088
  Tokens:   312514

That's a healthy build — npm-packages/docs in get-convex/convex-backend is the right path, and that repo is the canonical Convex upstream (not a fork or mirror). The file shape matches neighbours like hono.yaml and drizzle-orm.yaml, the filename matches the name: field, and it correctly avoids the versions:/min_version: form. Looks good, I'll merge it.


Generated by Claude Code

@moshest
moshest merged commit 07cd387 into neuledge:main Sep 21, 2026
moshest pushed a commit that referenced this pull request Sep 22, 2026
Releases @neuledge/context 1.2.4 -> 1.2.5 (patch).

Consumed one changeset, .changeset/tidy-manual-examples.md, declared as a
patch on @neuledge/context and added by #137: preserve code formatting in
HTML documentation that uses bare preformatted blocks, including systemd's
rendered DocBook manuals. It was the only changeset on main, it names the
published package only, and a patch bump is the right size for it.

@neuledge/registry 0.0.17 -> 0.0.18 is the automatic dependent bump that
changesets emits for the workspace:* dependency. It is "private": true, is
not published, appears in no changeset, and matches the shape of the last
release PR (#129).

Cross-checked recently merged work: #133, #149 and #150 add registry YAML
definitions only and #136 changes the private registry package only, so
none of them warrants a changeset. No user-facing packages/context change
merged without one.

Verified against npm before merging: dist-tags.latest for @neuledge/context
is 1.2.4 and 1.2.5 is absent from the published version list, so the new
version is strictly greater and does not collide.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NBQQpA86yYzwJUiVz8ph2R
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.

2 participants