Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump azure/webapps-deploy from 2.2.10 to 3.0.0 #467

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 16, 2023

Bumps azure/webapps-deploy from 2.2.10 to 3.0.0.

Release notes

Sourced from azure/webapps-deploy's releases.

Release version 3.0.0 🎉

Release v3

Moving from the older Zip Deploy API to Kudu Publish API for deploying your webapp via Github action webapps-deploy.

Reason for migration

The reason for this change is the Publish API /api/publish/ has many more features over the older /zipdeploy/ API and it is also currently used in the Azure CLI, plugins for Maven and Gradle, it would be consistent with other deployment providers.

What it means for the existing users

  • Users who are currently using the webapps-deploy@v2 can still use the same action without any change in the workflow file.
  • Users who want to shift to the new workflow can use the webapps-deploy@v3 to use the new Publish API features.

Features

  • New workflow parameter type - The type of the artifact being deployed, this sets the default target path and informs the web app how the deployment should be handled.
    • Allowed values: JAR, WAR, EAR, ZIP, Static
    • Ex: - type=war: Deploy a WAR package. By default, the WAR package is deployed to /home/site/wwwroot/app.war. The target path can be specified with parameter target-path.
  • New workflow parameter target-path - The absolute path to deploy the artifact to.
    • Allowed value: {string}
    • Ex: /home/site/wwwroot
  • New workflow parameter clean - Specifies whether to clean (delete) the target deployment before deploying the artifact there.
    • Allowed values: true/false
    • Ex: clean=true
  • New workflow parameter restart - By default, the API restarts the app following the deployment operation (restart=true). To deploy multiple artifacts, prevent restarts on all but the final deployment by setting restart=false.
    • Allowed values: true/false
    • Ex: restart=true

Example

- name: Deploy to Azure Web App
  id: deploy-to-webapp
  uses: azure/webapps-deploy@v3
  with:
    app-name: ${{ env.AZURE_WEBAPP_NAME }}
    publish-profile: ${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}
    package: '*.war'
    type: (jar, war, zip, static)
    clean: (true, false)
    target-path: (i.e. /home/site/wwwroot/test, /home/site/wwwroot/test.war)
    restart: (true, false)

What's Changed

New Contributors

Full Changelog: Azure/webapps-deploy@v2.2.11...v3.0.0

v2.2.11

What's Changed

... (truncated)

Commits
  • 145a068 update node_modules
  • 3dc06f7 Merge pull request #360 from dannysongg/enable-onedeploy
  • d3a151f Bump azure-actions-appservice-rest to 1.3.13
  • 5ac1116 Bump version to 3.0.0
  • c26b53a Resolving nits
  • 403feab Refactor logic for determining deployment type
  • 0f57d77 Migrate deployments to OneDeploy
  • 99c0cca Merge pull request #302 from benjaminmillhouse/patch-1
  • f613a60 Update action.yml
  • 24be858 Limit the length of commit message (#271)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [azure/webapps-deploy](https://github.com/azure/webapps-deploy) from 2.2.10 to 3.0.0.
- [Release notes](https://github.com/azure/webapps-deploy/releases)
- [Commits](Azure/webapps-deploy@v2.2.10...v3.0.0)

---
updated-dependencies:
- dependency-name: azure/webapps-deploy
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update Github_actions code labels Oct 16, 2023
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Oct 17, 2023

Looks like azure/webapps-deploy is up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this Oct 17, 2023
@dependabot dependabot bot deleted the dependabot/github_actions/azure/webapps-deploy-3.0.0 branch October 17, 2023 17:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file github_actions Pull requests that update Github_actions code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants