chore(cli): release v0.1.30, release node-sdk v0.0.7 - #574
Merged
Conversation
updateEmailProviderAction was calling updateEmailProvider (temps-email's transactional email provider PATCH) instead of the notifications endpoint updateNotificationEmailProvider, so 'temps notifications update --type email' silently hit the wrong resource. Also update the repository sync success message to match the async RepositorySyncStartedResponse shape (no more total_count/synced_at).
📓 Changelog previewThis is what your commits will add to the generated ## [Unreleased]
### Documentation
- **skill:** Pin temps-cli skill to @temps-sdk/cli v0.1.30
### Fixed
- **cli:** Route email-provider updates to the notifications endpoint
### Miscellaneous
- **cli:** Release v0.1.29, release node-sdk v0.0.6
- **cli:** Release v0.1.30, release node-sdk v0.0.7 |
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
temps notifications update --type emailwas callingupdateEmailProvider(the transactional email-provider endpoint fromtemps-email) instead ofupdateNotificationEmailProvider(the actual notifications endpoint) — wrong resource entirelyproviders syncreferencedtotal_count/synced_atonRepositorySyncStartedResponse, which no longer exist now that sync is async ({connection_id, started_at, syncing})@temps-sdk/cli0.1.28 → 0.1.30,@temps-sdk/node-sdk0.0.5 → 0.0.7 (published to npm)skills/temps-clito the published v0.1.30 artifact + its registry integrity hashTest plan
bunx tsc --noEmitclean inapps/temps-cli(aside from an unrelated devDep-only codegen config script excluded from the shipped bundle)bun run buildsucceeds forapps/temps-clitsc -p tsconfig.build.jsonclean forsdks/node/packages/node-sdkbun run buildsucceeds forsdks/node/packages/node-sdknpm view