docs: update harperdb references to harper for v5#32
Merged
Conversation
Replace all v4 `harperdb` CLI commands, package imports, and path references with `harper` to align with the v5 release. Also bumps the example devDependency version from ^4.7.20 to ^5.0.0. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
dawsontoth
approved these changes
May 21, 2026
|
🎉 This PR is included in version 1.4.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
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
harperdbCLI command references (harperdb deploy_component,harperdb run) withharperfrom 'harperdb') tofrom 'harper'node_modules/harperdb/schema.graphqlpath references tonode_modules/harper/schema.graphqlharperdb-config.yamlreference toharper-config.yaml"harperdb": "^4.7.20"to"harper": "^5.0.0"Files changed
harper-best-practices/AGENTS.mdand 10 rules files underharper-best-practices/rules/.The only remaining
harperdbstring in the repo is thesupport@harperdb.iocontact email inpackage.json, which was intentionally left unchanged.Test plan
harperdbpackage/CLI references remain:grep -r "harperdb" harper-best-practices/from 'harper'harper deploy_componentandharper run🤖 Generated with Claude Code