chore(main): release 3.10.0 (#102) #185
pull-request.yml
on: push
macos-latest
2m 23s
swift-lint
30s
Annotations
12 warnings
|
swift-lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|
|
swift-lint:
FlagsmithClient/Tests/CustomerCacheUseCaseTests.swift#L243
Empty Enum Arguments Violation: Arguments can be omitted when matching enums with associated values if they are not used (empty_enum_arguments)
|
|
swift-lint:
FlagsmithClient/Tests/CustomerCacheUseCaseTests.swift#L84
Empty Enum Arguments Violation: Arguments can be omitted when matching enums with associated values if they are not used (empty_enum_arguments)
|
|
swift-lint:
FlagsmithClient/Tests/CustomerCacheUseCaseTests.swift#L81
Empty Enum Arguments Violation: Arguments can be omitted when matching enums with associated values if they are not used (empty_enum_arguments)
|
|
swift-lint:
FlagsmithClient/Tests/CustomerCacheUseCaseTests.swift#L72
Empty Enum Arguments Violation: Arguments can be omitted when matching enums with associated values if they are not used (empty_enum_arguments)
|
|
swift-lint:
FlagsmithClient/Tests/CustomerCacheUseCaseTests.swift#L342
Colon Spacing Violation: Colons should be next to the identifier when specifying a type and next to the key in dictionary literals (colon)
|
|
swift-lint:
FlagsmithClient/Tests/CustomerCacheUseCaseTests.swift#L341
Colon Spacing Violation: Colons should be next to the identifier when specifying a type and next to the key in dictionary literals (colon)
|
|
swift-lint:
FlagsmithClient/Tests/CustomerCacheUseCaseTests.swift#L34
Colon Spacing Violation: Colons should be next to the identifier when specifying a type and next to the key in dictionary literals (colon)
|
|
swift-lint:
FlagsmithClient/Tests/CustomerCacheUseCaseTests.swift#L33
Colon Spacing Violation: Colons should be next to the identifier when specifying a type and next to the key in dictionary literals (colon)
|
|
swift-lint:
FlagsmithClient/Tests/APIErrorCacheFallbackEdgeCaseTests.swift#L46
Non-optional String -> Data Conversion Violation: Prefer non-optional `Data(_:)` initializer when converting `String` to `Data` (non_optional_string_data_conversion)
|
|
swift-lint:
Example/FlagsmithClient/SwiftUIView.swift#L15
Type Body Length Violation: Struct body should span 250 lines or less excluding comments and whitespace: currently spans 251 lines (type_body_length)
|
|
macos-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|