Skip to content

Bump YamlDotNet from 17.1.0 to 18.0.0 #76

Bump YamlDotNet from 17.1.0 to 18.0.0

Bump YamlDotNet from 17.1.0 to 18.0.0 #76

Triggered via pull request May 22, 2026 12:28
Status Success
Total duration 2m 49s
Artifacts

test.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

12 warnings
build-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-java@v3, android-actions/setup-android@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-test
Failed to post or update PR comment (status 403: Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment). Falling back to the step summary instead.
build-test: src/Darp.Ble.Hci/HciDevice.cs#L247
File name must match type name (class AttResponseMessageSinkProvider), expected file name: 'AttResponseMessageSinkProvider' (https://github.com/meziantou/Meziantou.Analyzer/blob/main/docs/Rules/MA0048.md)
build-test: src/Darp.Ble.Hci/AttResponse.cs#L7
AttResponse should override the equality (==) and inequality (!=) operators (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1815)
build-test: src/Darp.Ble.Hci/AttResponse.cs#L7
AttResponse should override Equals (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1815)
build-test: src/Darp.Ble.Hci/AclPacketQueue.cs#L140
File name must match type name (class ConnectionState), expected file name: 'ConnectionState' (https://github.com/meziantou/Meziantou.Analyzer/blob/main/docs/Rules/MA0048.md)
build-test: src/Darp.Ble.Hci/AclPacketQueue.cs#L9
File name must match type name (interface IAclPacketQueue), expected file name: 'IAclPacketQueue' (https://github.com/meziantou/Meziantou.Analyzer/blob/main/docs/Rules/MA0048.md)
build-test: src/Darp.Ble.Hci/AclConnection.cs#L207
File name must match type name (class AclConnectionSubscription), expected file name: 'AclConnectionSubscription' (https://github.com/meziantou/Meziantou.Analyzer/blob/main/docs/Rules/MA0048.md)
build-test: src/Darp.Ble.Hci/AclConnection.cs#L21
File name must match type name (record struct AclConnectionParameters), expected file name: 'AclConnectionParameters' (https://github.com/meziantou/Meziantou.Analyzer/blob/main/docs/Rules/MA0048.md)
build-test: src/Darp.Ble.Hci/HciPacketInFlightHandler.cs#L80
TODO What do we do if a response is received after a timeout was hit? Will this trigger the next query? (https://github.com/meziantou/Meziantou.Analyzer/blob/main/docs/Rules/MA0026.md)
build-test: tools/AssignedNumbersCrawler/Program.cs#L138
Exception type System.Exception is not sufficiently specific (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2201)