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

Update JamesIves/github-pages-deploy-action action to v4.3.0 #18

Merged
merged 1 commit into from
Apr 8, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 4, 2022

WhiteSource Renovate

This PR contains the following updates:

Package Type Update Change
JamesIves/github-pages-deploy-action action minor v4.2.5 -> v4.3.0

Release Notes

JamesIves/github-pages-deploy-action

v4.3.0

Compare Source

Changes

  • Implements a new option available behind a flag, force. If set to false the action will no longer force push, instead attempting 3 times to resolve rejected commits when making parallel/subsequent deployments. In a future version false will be set as the default. Massive thanks to @​rossjrw for this feature addition.
  • Modified the Node version which the action is developed/tested against from 14 to 16.

Minor Changes

  • Third-party dependency updates.
  • Test coverage improvements.

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@Im-Fran Im-Fran merged commit 4cb0d5a into master Apr 8, 2022
@Im-Fran Im-Fran deleted the renovate/jamesives-github-pages-deploy-action-4.x branch April 8, 2022 00:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants