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.7.3 #78

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 16, 2022

This PR contains the following updates:

Package Type Update Change
JamesIves/github-pages-deploy-action action minor v4.2.3 -> v4.7.3

Release Notes

JamesIves/github-pages-deploy-action (JamesIves/github-pages-deploy-action)

v4.7.3

Compare Source

v4.7.2

Compare Source

What's Changed

Bug Fixes 🐝
Build 🔧

Full Changelog: JamesIves/github-pages-deploy-action@v4.7.1...v4.7.2

v4.7.1

Compare Source

What's Changed

Features ✨

New Contributors

Full Changelog: JamesIves/github-pages-deploy-action@v4.6.6...v4.7.1

v4.7.0

Compare Source

What's Changed

Features ✨
Build 🔧

New Contributors

Full Changelog: JamesIves/github-pages-deploy-action@v4.6.6...v4.7.0

v4.6.9

Compare Source

What's Changed

Dependencies 🤖
  • chore(deps): mass bump dependencies
  • chore(deps): switch to using .node-version instead of .nvmrc for Node dependency management.
  • chore(deps): updated node version to 22.11.0 for development

Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.6.9

v4.6.8

Compare Source

What's Changed

Bug Fixes 🐝
  • fix: 🐛 Added the temp deployment directory created by the action to the git safe directory list. This resolves an issue in certain circumstances where the deployment would fail depending on the types of files moved around by the workflow - #​1694.
  • fix: Resolved a rare deployment error where the action would complain that origin/${branch_name} is not a commit and a branch cannot be created from it. The action will continue to attempt to track the origin branch, but if this step fails, it will create a new untracked branch to continue the deployment from. - #​1689.
Testing 🧪
  • test: 🧪 Improved the integration test suite so it now runs immediately post-release to ensure that any issues do no longer in the major version tag (ie @​v4). This was done to combat problems raised by #​1697.

Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.6.8

v4.6.7

Compare Source

What's Changed

Bug Fixes 🐝
  • fix: resolved an issue where main.js was not found in the v4 major tag.

v4.6.6

Compare Source

What's Changed

Bug Fixes 🐝
  • revert: reverts a prior change that unsets safe directories to prevent dubious ownership, this change will be re-visited later.

v4.6.5

Compare Source

What's Changed

What's Changed

Bug Fixes 🐝
  • fix: resolved an issue where the full working directory was not properly getting added to the safe directory list, preventing deployments in certain circumstances.

Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.6.5

v4.6.4

Compare Source

What's Changed
What's Changed
Bug Fixes 🐝
  • fix: resolved an issue where the default config was not being applied to the non-action version of the project.
Build 🔧

Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.6.4

v4.6.3

Compare Source

What's Changed
Build 🔧
  • Consolidated a number of build scripts to make publishing easier.

Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.6.3

v4.6.2

Compare Source

What's Changed
Dependencies 🤖

Full Changelog: JamesIves/github-pages-deploy-action@v4.6.1...v4.6.2

v4.6.1

Compare Source

What's Changed

Fixes
  • Resolved an issue where workflows were suddenly failing due to a worktree in use error. The action will now attempt to create a temp branch name if the existing branch name is already checked out by a prior to step to ensure it can occur. This issue was only occurring in a handful of workflows, and likely stemmed from a git version change on the official GitHub runners. The actual root cause is still somewhat unknown.
Dependencies

Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.6.1

v4.6.0

Compare Source

What's Changed

New Contributors

Full Changelog: JamesIves/github-pages-deploy-action@v4.5.0...v4.6.0

v4.5.0

Compare Source

What's Changed

New Contributors

Full Changelog: JamesIves/github-pages-deploy-action@v4.4.3...v4.5.0

v4.4.3

Compare Source

What's Changed

Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.4.3

v4.4.2

Compare Source

What's Changed

  • Dependency updates

Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.4.2

v4.4.1

Compare Source

What's Changed

Changelog

New Contributors

Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.4.1

v4.4.0

Compare Source

What's Changed

New Contributors

Sponsors ❤️

github  

Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.4.0

v4.3.4

Compare Source

Minor Changes

  • The branch parameter is no longer required. It now defaults to gh-pages.
  • Linting scripts have been updated to ensure that everything across the repo gets picked up.
  • Numerous dependency updates.

New Contributors

Sponsors ❤️

github  

Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.3.4

v4.3.3

Compare Source

Changes

  • Resolves an issue in some workflows that were caused by a recent change to permission handling.

v4.3.2

Compare Source

Changes

  • Resolves an issue with folder permissions that causes an issue in container workflows when rsync attempts to run.

v4.3.1

Compare Source

Changes

  • Resolves an issue caused by Git 2.36 when running the action within a container.
    • The working directory is now added to the safe.directory global directory.
    • Integration tests have been updated so one of the samples run in a Docker container so this gets picked up by integration tests in the future.

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.

v4.2.5

Compare Source

Minor Changes

  • Corrects an issue in the publishing pipeline that was causing workflow failures.

v4.2.4

Compare Source

Minor Changes


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title Update JamesIves/github-pages-deploy-action action to v4.2.4 Update JamesIves/github-pages-deploy-action action to v4.2.5 Feb 16, 2022
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from 3ed7ea5 to 4814002 Compare February 16, 2022 16:11
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@renovate renovate bot changed the title Update JamesIves/github-pages-deploy-action action to v4.2.5 Update JamesIves/github-pages-deploy-action action to v4.3.0 Apr 4, 2022
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from 4814002 to bad33b7 Compare April 4, 2022 14:13
@renovate renovate bot changed the title Update JamesIves/github-pages-deploy-action action to v4.3.0 Update JamesIves/github-pages-deploy-action action to v4.3.2 Apr 25, 2022
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from bad33b7 to 2a4a46d Compare April 25, 2022 02:18
@renovate renovate bot changed the title Update JamesIves/github-pages-deploy-action action to v4.3.2 Update JamesIves/github-pages-deploy-action action to v4.3.3 May 16, 2022
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from 2a4a46d to 3c9fa90 Compare May 16, 2022 02:03
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from 3c9fa90 to f401613 Compare September 25, 2022 18:30
@renovate renovate bot changed the title Update JamesIves/github-pages-deploy-action action to v4.3.3 Update JamesIves/github-pages-deploy-action action to v4.4.0 Sep 25, 2022
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from f401613 to 5c3cbfb Compare November 20, 2022 17:05
@renovate renovate bot changed the title Update JamesIves/github-pages-deploy-action action to v4.4.0 Update JamesIves/github-pages-deploy-action action to v4.4.1 Nov 20, 2022
@renovate renovate bot changed the title Update JamesIves/github-pages-deploy-action action to v4.4.1 Update JamesIves/github-pages-deploy-action action to v4.4.2 May 28, 2023
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from 5c3cbfb to 17fab01 Compare May 28, 2023 12:19
@renovate renovate bot changed the title Update JamesIves/github-pages-deploy-action action to v4.4.2 Update JamesIves/github-pages-deploy-action action to v4.4.3 Jul 12, 2023
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from 17fab01 to afa230b Compare July 12, 2023 03:05
@renovate renovate bot changed the title Update JamesIves/github-pages-deploy-action action to v4.4.3 Update JamesIves/github-pages-deploy-action action to v4.5.0 Nov 28, 2023
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from afa230b to 4f2ca23 Compare November 28, 2023 04:42
@renovate renovate bot changed the title Update JamesIves/github-pages-deploy-action action to v4.5.0 Update JamesIves/github-pages-deploy-action action to v4.6.0 Apr 17, 2024
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from 4f2ca23 to 67429ae Compare April 17, 2024 14:44
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from 67429ae to 51409c2 Compare May 18, 2024 15:51
@renovate renovate bot changed the title Update JamesIves/github-pages-deploy-action action to v4.6.0 Update JamesIves/github-pages-deploy-action action to v4.6.1 May 18, 2024
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from 51409c2 to 456ad5d Compare July 5, 2024 16:06
@renovate renovate bot changed the title Update JamesIves/github-pages-deploy-action action to v4.6.1 Update JamesIves/github-pages-deploy-action action to v4.6.3 Jul 5, 2024
@renovate renovate bot changed the title Update JamesIves/github-pages-deploy-action action to v4.6.3 Update JamesIves/github-pages-deploy-action action to v4.6.4 Sep 2, 2024
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from 456ad5d to 87a1d45 Compare September 2, 2024 19:50
@renovate renovate bot changed the title Update JamesIves/github-pages-deploy-action action to v4.6.4 Update JamesIves/github-pages-deploy-action action to v4.6.6 Sep 27, 2024
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from 87a1d45 to b0e7068 Compare September 27, 2024 20:03
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from b0e7068 to 4ff7c7e Compare September 28, 2024 12:56
@renovate renovate bot changed the title Update JamesIves/github-pages-deploy-action action to v4.6.6 Update JamesIves/github-pages-deploy-action action to v4.6.7 Sep 28, 2024
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from 4ff7c7e to 13c32c7 Compare September 29, 2024 19:24
@renovate renovate bot changed the title Update JamesIves/github-pages-deploy-action action to v4.6.7 Update JamesIves/github-pages-deploy-action action to v4.6.8 Sep 29, 2024
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from 13c32c7 to 46218e4 Compare November 9, 2024 22:15
@renovate renovate bot changed the title Update JamesIves/github-pages-deploy-action action to v4.6.8 Update JamesIves/github-pages-deploy-action action to v4.6.9 Nov 9, 2024
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from 46218e4 to 976dd46 Compare November 28, 2024 17:29
@renovate renovate bot changed the title Update JamesIves/github-pages-deploy-action action to v4.6.9 Update JamesIves/github-pages-deploy-action action to v4.7.1 Nov 28, 2024
@renovate renovate bot changed the title Update JamesIves/github-pages-deploy-action action to v4.7.1 Update JamesIves/github-pages-deploy-action action to v4.7.2 Dec 3, 2024
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from 976dd46 to f2f5da3 Compare December 3, 2024 20:41
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from f2f5da3 to dc5d530 Compare February 19, 2025 16:44
@renovate renovate bot changed the title Update JamesIves/github-pages-deploy-action action to v4.7.2 Update JamesIves/github-pages-deploy-action action to v4.7.3 Feb 19, 2025
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.

0 participants