-
Notifications
You must be signed in to change notification settings - Fork 36
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
Incompatible with Probot v11 #58
Comments
What's your setup? Is your code open source? Do you see any deprecation warnings when you run your app with 10.19.0? |
The code is here and yes, I do have some warnings such as this one 👇
In terms of setup, it's just a simple probot app that I'm deploying as an AWS lambda with the serverless command line. It's configured with |
The deprecation warning is why it fails with the new version, this line here is the problem I'm currently working on creating an example app with deployment to AWS Lambda with Serverless. Once that's done I'll update the adapter. But the current app is not working, I don't know why, I'm not very familiar with Lambda/Serverless, could you have a look? probot/example-aws-lambda-serverless#1 See also the discussion at probot/probot#1467 (comment) |
In addition, Probot v11 incompatibilities concerns a custom GitHub URL endpoint (sample: GitHub Enterprise). Switching a probot app v10 (which is working) into v11, the GitHub Enterprise URL is not taken into account (default GitHub.com is used):
The It could perhaps be linked to new Probot constructor usage or new But was introduced in 10.17 and downgrade v11 to v10.19.0 is working fine for me 🤔. |
I've a pull request which will update this adapter to Probot v11, it also changes its APIs. Could you have a look? I'm not very familiar with the serverless framework. If you could check instructions in the README I'd appreciate it |
🎉 This issue has been resolved in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Got this error with probot
11.0.1
and11.0.5
. Downgrading to10.19.0
solved it.The text was updated successfully, but these errors were encountered: