Version Packages - #95
Merged
Merged
Conversation
|
PR author is in the excluded authors list. |
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@propgate/sdk@0.6.0
Minor Changes
#94
7c2c4e5Thanks @joaopcm! - Add@propgate/sdk: the propgate API from Node, with a method for every routeexcept signup.
new Propgate(apiKey)and thenpropgate.domains.check(id). Every call returns{ data, error, meta }and none of them throw, so the failure branch istype-checked rather than an
unknownfrom acatch.listAllwalks a cursor tothe end; retries cover connection failures, timeouts and rate limits, and
deliberately never repeat a
POSTthat may already have been applied.apps/api/src/sdk-coverage.spec.tsreads the API's own router, so a route addedwithout a method to reach it fails there rather than in an integration.