Avoid allocation of new path when resolving path ambiguities (#2904) #16134
Annotations
3 warnings
|
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-java@v2, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "Jmh_Main_CachedDateHeaderBenchmark", "Jmh_Main_CookieDecodeBenchmark", "Jmh_Main_EndpointBenchmark", "Jmh_Main_HttpCollectEval", "Jmh_Main_HttpCombineEval", "Jmh_Main_HttpNestedFlatMapEval", "Jmh_Main_HttpRouteTextPerf", "Jmh_Main_ProbeContentTypeBenchmark", "Jmh_Main_SchemeDecodeBenchmark", "Jmh_Main_ServerInboundHandlerBenchmark", "Jmh_Main_UtilBenchmark".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
This job succeeded
Loading