fix(deps): bump node-halopsa to @wyre-ai scope 1.1.0 - #91
Merged
Merged
Conversation
…@wyre-technology name) The Aug 25 org migration (6fa7cc2) deliberately left the SDK dependency on the old @wyre-technology/node-halopsa name because node-halopsa hadn't republished under @WYRE-AI yet. It has now (1.1.0, which includes the node-halopsa#78 fix: a 400 from a resource endpoint no longer gets mislabeled as HaloPsaAuthenticationError with an "invalid credentials" message). Since halopsa-mcp was still pinned to the old package name, npm never had a newer version to resolve within that name's published history — the ^1.0.9 range was irrelevant; it's a different package name entirely as far as npm dependency resolution is concerned. This had been silently stuck on 1.0.10 since before the migration, missing every fix since (1.0.11 through 1.1.0). Renamed the dependency and every import (src/utils/client.ts, src/card.builder.ts, and the test mock in src/__tests__/client.test.ts) from @wyre-technology/node-halopsa to @wyre-ai/node-halopsa, bumped the version floor to ^1.1.0, and regenerated package-lock.json. .npmrc already mapped both scopes to the same registry, so no registry config changes were needed. Verified: typecheck, full test suite (147/147), lint, and build all clean. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JgXg1NhHo6DvvAqoPowppi
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (6)
Included review availability: Your plan provides up to 10 included reviews per hour; 6 remain after this review. 📝 WalkthroughWalkthroughThe project replaces ChangesHaloPSA package migration
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This updates the HaloPSA SDK package and version consistently across runtime wiring, tests, and documentation. The migration is ready to merge with no identified current-head risk. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
|
🎉 This PR is included in version 1.7.14 🎉 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
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
@wyre-technology/node-halopsaname, sincenode-halopsahadn't republished under@wyre-aiyet at the time.@wyre-ai/node-halopsa1.1.0, WYRE-AI/node-halopsa#79), which includes the fix for #78 — a 400 from a resource endpoint no longer gets mislabeled asHaloPsaAuthenticationErrorwith an "invalid credentials" message.halopsa-mcpwas still pinned to the old package name, npm had no newer version to resolve within that name's history —^1.0.9was irrelevant, since it's a different package name entirely as far as dependency resolution goes. This repo had been silently stuck on node-halopsa 1.0.10 since before the migration, missing every fix released since (1.0.11 through 1.1.0).src/utils/client.ts,src/card.builder.ts, test mock insrc/__tests__/client.test.ts, plus two doc comments) from@wyre-technology/node-halopsato@wyre-ai/node-halopsa, bumped the floor to^1.1.0, regeneratedpackage-lock.json..npmrcalready mapped both scopes to the same registry, so no registry config changes needed.Test plan
npm run typecheck— cleannpm test— 147/147 passingnpm run lint— cleannpm run build— clean🤖 Generated with Claude Code
https://claude.ai/code/session_01JgXg1NhHo6DvvAqoPowppi
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is enabled.Summary by CodeRabbit
@wyre-ai/node-halopsapackage.^1.1.0.