Add or update the Azure App Service build and deployment workflow config #1
erickorlandomaster_tiendabackend.yml
on: push
build
3m 33s
deploy
1m 14s
Annotations
7 warnings
|
build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-dotnet@v1, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
build
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build:
ECommerceWeb.Client/Pages/Home.razor#L52
Found markup element with unexpected name 'LoadingComponent'. If this is intended to be a component, add a @using directive for its namespace.
|
|
build:
ECommerceWeb.Client/Pages/Home.razor#L52
Found markup element with unexpected name 'LoadingComponent'. If this is intended to be a component, add a @using directive for its namespace.
|
|
build
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
|
deploy
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: azure/login@v1, actions/download-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: ".net-app".
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/
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
.net-app
Expired
|
48.4 MB |
|