Rename dkg-hello-world npm package to @origintrail-official scope#1
Merged
branarakic merged 1 commit intomainfrom Apr 24, 2026
Merged
Rename dkg-hello-world npm package to @origintrail-official scope#1branarakic merged 1 commit intomainfrom
branarakic merged 1 commit intomainfrom
Conversation
Follow-up to OriginTrail/dkg-hello-world#1, which renamed the npm package from @origintrail/dkg-hello-world to @origintrail-official/dkg-hello-world so it lives in the same scope as the rest of the DKG ecosystem (@origintrail-official/dkg, -mcp, etc.). Updates install.package in the registry entry to match the new source of truth. Version stays at 0.1.0; `commit` pin stays at cb6af61 (the commit on main that added the publish workflow) and will be bumped to the rename-merge commit plus a re-published 0.1.0 in a follow-up once we've cut the first npm release under the new scope. Note on CI: `security-checks.mjs` will emit a "package not yet published" warning when validating this entry. That's expected — the package has never been published under either name. The warning doesn't block merge, and clears the moment we publish the first version. Made-with: Cursor
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.
Summary
Follow-up to OriginTrail/dkg-hello-world#1, which moves the npm package from `@origintrail/dkg-hello-world` → `@origintrail-official/dkg-hello-world` so it sits in the same scope as the rest of the DKG ecosystem (`@origintrail-official/dkg`, `-mcp`, etc.). The `@origintrail` scope on npm is owned by a different npm user, so publishing there would create an ownership ambiguity.
Change
Single field flip in `integrations/dkg-hello-world.json`:
```diff
```
`version` stays at `0.1.0`; `commit` pin stays at `cb6af61` (the commit on `main` that added the publish workflow). Both will be bumped in a tiny follow-up PR once we've cut the first npm release under the new scope.
CI note
`security-checks.mjs` will emit a "package not yet published" warning when validating this entry — that's expected, the package has never been published under either name. The warning is non-blocking (we made it non-blocking specifically so registry entries can land before their first npm release).
Ordering
Safe to merge in either order relative to the dkg-hello-world PR, since neither state corresponds to a published package yet. Recommended order:
Made with Cursor