-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Clean up and soft-deprecate AsyncKit #106
Conversation
…g Vapor), clean up CI and DocC docs
…ault log level to the now-standard info
…darn thing, why should we spend forever testing it?)
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #106 +/- ##
==========================================
+ Coverage 95.63% 96.74% +1.10%
==========================================
Files 19 19
Lines 963 860 -103
==========================================
- Hits 921 832 -89
+ Misses 42 28 -14
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
These changes are now available in 1.19.0 |
This update starts the official soft-deprecation of AsyncKit. It should not be used in new code (although it will remain included in Vapor and Fluent 4 for compatibility). It is not expected to receive new updates other than security fixes.
Other changes in this update:
~
operator onEventLoopFuture
is nowpublic
as was intended (not that anyone noticed it wasn't 🙂)