-
Notifications
You must be signed in to change notification settings - Fork 3
Fix CI error #2
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
Comments
MongoDB 6.0 was released just today. I think that's the reason. Dockerfile uses the latest mongodb image. I'll check what are the breaking changes. EDIT: This has most likely broken the tests for mongoose-adapter as well. EDIT2: Mongo image does not seem to have mongo command line function, so entry-point.sh scripts fail. docker-library/mongo#558 |
* ci(docker-entrypoint.sh): change mongo commands into mongosh docker-library/mongo#558 fix #2 * test(watcher.test.ts): add callbackStreamCloseEvent attribute to a test
Hmmph. Tests complete before. I guess the semantic-release does not have access to the cluster anymore.. Should the release script run the tests anyway at this point? |
@Sefriol refer to other repos: https://github.com/node-casbin |
Other repos do not seem to have husky configured, but it seems that it should be ignored when semantic-release does the release commit. It seems that I should just disable husky in CI. EDIT: Yep: https://typicode.github.io/husky/#/?id=disable-husky-in-cidockerprod |
* ci(main.yml): disable husky in CI https://typicode.github.io/husky/#/?id=with-env-variables fix #2 * docs(readme.md): fix badge urls
See: https://github.com/node-casbin/mongo-changestream-watcher/actions/runs/2927758423
The text was updated successfully, but these errors were encountered: