Version Packages - #97
Open
github-actions[bot] wants to merge 1 commit into
Open
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
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.7.0
Minor Changes
#96
a80bbf7Thanks @joaopcm! - ExportPROPGATE_ERROR_CODES, the runtime listPropgateErrorCodeis derivedfrom — the same shape as
CHECK_KINDSandWEBHOOK_EVENTSelsewhere.A union alone exists only at compile time, so nothing could check that the
documented table of codes covers what a consumer can actually receive. The docs
now assert exactly that against this array.
Also exports
MAX_RETRY_WAIT_MS: it decides whether a rate limit is ridden outinside a call or handed back as
retryAfterSeconds, so it is a number a callerschedules around, and the documented worst case is now computed from it rather
than typed out.