Bump CommunityToolkit.Maui.Markup and Microsoft.Maui.Controls #344
dependabot[bot]maui.yml
on: pull_request
Build_Android
1m 39s
Build_iOS
2m 6s
Build_MacCatalyst
1m 31s
Build_Windows
5m 22s
Annotations
18 errors and 4 warnings
|
Build_MacCatalyst
Process completed with exit code 1.
|
|
Build_MacCatalyst:
src/HotChocolateGraphQL.Mobile/Pages/BasePage.cs#L11
'Page.SetUseSafeArea(IPlatformElementConfiguration<iOS, Page>, bool)' is obsolete: 'Use SafeAreaEdges attached property instead for per-edge safe area control.'
|
|
Build_MacCatalyst:
src/HotChocolateGraphQL.Mobile/Pages/BasePage.cs#L11
'Page.SetUseSafeArea(IPlatformElementConfiguration<iOS, Page>, bool)' is obsolete: 'Use SafeAreaEdges attached property instead for per-edge safe area control.'
|
|
Build_Android
Process completed with exit code 1.
|
|
Build_Android:
src/HotChocolateGraphQL.Mobile/Pages/BasePage.cs#L11
'Page.SetUseSafeArea(IPlatformElementConfiguration<iOS, Page>, bool)' is obsolete: 'Use SafeAreaEdges attached property instead for per-edge safe area control.'
|
|
Build_Android:
src/HotChocolateGraphQL.Mobile/Pages/BasePage.cs#L11
'Page.SetUseSafeArea(IPlatformElementConfiguration<iOS, Page>, bool)' is obsolete: 'Use SafeAreaEdges attached property instead for per-edge safe area control.'
|
|
Build_iOS
Process completed with exit code 1.
|
|
Build_iOS:
src/HotChocolateGraphQL.Mobile/Pages/BasePage.cs#L11
'Page.SetUseSafeArea(IPlatformElementConfiguration<iOS, Page>, bool)' is obsolete: 'Use SafeAreaEdges attached property instead for per-edge safe area control.'
|
|
Build_iOS:
src/HotChocolateGraphQL.Mobile/Pages/BasePage.cs#L11
'Page.SetUseSafeArea(IPlatformElementConfiguration<iOS, Page>, bool)' is obsolete: 'Use SafeAreaEdges attached property instead for per-edge safe area control.'
|
|
Build_Windows
Process completed with exit code 1.
|
|
Build_Windows:
src/HotChocolateGraphQL.Mobile/Pages/BasePage.cs#L11
'Page.SetUseSafeArea(IPlatformElementConfiguration<iOS, Page>, bool)' is obsolete: 'Use SafeAreaEdges attached property instead for per-edge safe area control.'
|
|
Build_Windows:
src/HotChocolateGraphQL.Mobile/Pages/BasePage.cs#L11
'Page.SetUseSafeArea(IPlatformElementConfiguration<iOS, Page>, bool)' is obsolete: 'Use SafeAreaEdges attached property instead for per-edge safe area control.'
|
|
Build_Windows:
src/HotChocolateGraphQL.Mobile/Pages/BasePage.cs#L11
'Page.SetUseSafeArea(IPlatformElementConfiguration<iOS, Page>, bool)' is obsolete: 'Use SafeAreaEdges attached property instead for per-edge safe area control.'
|
|
Build_Windows:
src/HotChocolateGraphQL.Mobile/Pages/BasePage.cs#L11
'Page.SetUseSafeArea(IPlatformElementConfiguration<iOS, Page>, bool)' is obsolete: 'Use SafeAreaEdges attached property instead for per-edge safe area control.'
|
|
Build_Windows:
src/HotChocolateGraphQL.Mobile/Pages/BasePage.cs#L11
'Page.SetUseSafeArea(IPlatformElementConfiguration<iOS, Page>, bool)' is obsolete: 'Use SafeAreaEdges attached property instead for per-edge safe area control.'
|
|
Build_Windows:
src/HotChocolateGraphQL.Mobile/Pages/BasePage.cs#L11
'Page.SetUseSafeArea(IPlatformElementConfiguration<iOS, Page>, bool)' is obsolete: 'Use SafeAreaEdges attached property instead for per-edge safe area control.'
|
|
Build_Windows:
src/HotChocolateGraphQL.Mobile/Pages/BasePage.cs#L11
'Page.SetUseSafeArea(IPlatformElementConfiguration<iOS, Page>, bool)' is obsolete: 'Use SafeAreaEdges attached property instead for per-edge safe area control.'
|
|
Build_Windows:
src/HotChocolateGraphQL.Mobile/Pages/BasePage.cs#L11
'Page.SetUseSafeArea(IPlatformElementConfiguration<iOS, Page>, bool)' is obsolete: 'Use SafeAreaEdges attached property instead for per-edge safe area control.'
|
|
Build_MacCatalyst
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/setup-dotnet@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/
|
|
Build_Android
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/setup-dotnet@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/
|
|
Build_iOS
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/setup-dotnet@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/
|
|
Build_Windows
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/setup-dotnet@v4, actions/setup-java@v2. 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/
|