Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating #1

Open
wants to merge 427 commits into
base: master
Choose a base branch
from
Open

Updating #1

wants to merge 427 commits into from

Conversation

shuklaalok7
Copy link
Member

Update from the base

@shuklaalok7 shuklaalok7 self-assigned this Aug 6, 2016
dmitraver and others added 29 commits October 12, 2017 12:06
- Add sections on email stats and setting up domain white labels
Add "viewing request body" section to troubleshooting
twilio-ci and others added 29 commits April 1, 2020 19:04
* signature-verification: verify signature from event webhook

* signature-verification: code review

* signature-verification: add an example

* signature-verification: package renaming and updated examples

* signature-verification: code review updates

* signature-verification: consistent sample data across SDKs
Using a version range like this results in maven attempting to get SNAPSHOT information for the dependency since it's possible a SNAPSHOT release would match the version range. It's not a big deal, but there are better approaches. The idea was we want to pick up the latest 4.X version of java-http-client, but even a version range does not guarantee this. It only guarantees that a 4.X version will be used (not necessarily the latest release). What we really want is the latest non-snapshot, minor version release for all dependencies, not just java-http-client. Also note that Maven version ranges perform basic string comparison so even it they were capable of getting the latest release for a dependency, it might not actually be the latest release if proper semver is used.
#637)

The "Kitchen Sink" example and other mail-send examples were out-of-date. This change updates them to use the latest package version.
We have similar examples in other languages and they provide a clear distinction between the two use cases.
We don't do this in any of the other libraries and it only guards against a specific secret. Multiple customers indicate this check is overly sensitive to legitimate use cases.
@thinkingserious thinkingserious deleted the master branch August 13, 2020 21:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.