Update probot to the latest version 🚀 #12
Merged
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.
Version 7.1.0 of probot was just published.
The version 7.1.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of probot.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v7.1.0Improvements
If a webhook received from GitHub is not using the same value configured for
WEBHOOK_SECRET
you'll now see a more helpful error message telling you how to fix it. (#621, #647) @hiimbexBy default, installation tokens are cached for 59 minutes. You can now change that by setting
INSTALLATION_TOKEN_TTL
(#638) @tommilliganPRIVATE_KEY
can now be a base64 encoded string, which make it a little easier to set in some deployment environments (#624) @tcbyrdMany more improvements to our TypeScript support, including:
context.github.query()
(#667) @tcbyrdUpdate versions for a few dependencies:
Documentation:
Bring testing docs in line with probot/template (#627) @wilhelmklopp
Adding typescript option to
create-probot-app
command (#630) @mousavianAdd probot-messages (#657) @hiimbex
See full changelog
Commits
The new version differs by 38 commits.
9a09eaf
7.1.0
782707a
fix: Show friendly error when the webhook secret on GitHub does not match
WEBHOOK_SECRET
(#647)42d3d39
chore: Add template for release-drafter app (#666)
96b186a
chore: Convert resolver tests to TypeScript (#660)
84518e5
chore(package): update ts-jest to version 23.1.4 (#662)
c8d9f0a
chore(package): update bottleneck to version 2.8.0 (#661)
8a12f83
Convert logger test to Typescript (#656)
1820442
Add probot-messages (#657)
d8383d3
Rename event->name in docs (#631)
691d724
chore(package): update @types/node to version 10.7.0 (#659)
1351932
chore(package): update typedoc to version 0.12.0 (#658)
686232d
chore: Rename plugins to apps (#654)
59f924e
Add environment variable option to provide a base64 encoded key (#624)
4159d80
chore(tests): Convert graphql tests to TypeScript (#629)
4118f1d
Added env var INSTALLATION_TOKEN_TTL (#638)
There are 38 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴