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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update jamesives/github-pages-deploy-action action to v4.7.2 #112

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

chore(deps): update jamesives/github-pages-deploy-action action to v4.7.2 #112

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 25, 2024 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
JamesIves/github-pages-deploy-action action minor v4.5.0 -> v4.7.2

Release Notes

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

v4.7.2

Compare Source

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

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.

@cloudflare-workers-and-pages Cloudflare Workers and Pages
Copy link

cloudflare-workers-and-pages bot commented Jul 25, 2024 •
edited
Loading

Deploying portfolio with  Cloudflare Pages  Cloudflare Pages

Latest commit: 9df0aa6
Status:🚫  Build failed.

View logs

@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from fb09e68 to 2761189 Compare September 2, 2024 16:08
@renovate renovate bot changed the title chore(deps): update jamesives/github-pages-deploy-action action to v4.6.3 chore(deps): 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 2761189 to 6d37436 Compare September 27, 2024 18:15
@renovate renovate bot changed the title chore(deps): update jamesives/github-pages-deploy-action action to v4.6.4 chore(deps): update jamesives/github-pages-deploy-action action to v4.6.6 Sep 27, 2024
@renovate renovate bot changed the title chore(deps): update jamesives/github-pages-deploy-action action to v4.6.6 chore(deps): 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 2 times, most recently from c0f8cc8 to c397e83 Compare September 29, 2024 18:28
@renovate renovate bot changed the title chore(deps): update jamesives/github-pages-deploy-action action to v4.6.7 chore(deps): update jamesives/github-pages-deploy-action action to v4.6.8 Sep 29, 2024
@renovate renovate bot changed the title chore(deps): update jamesives/github-pages-deploy-action action to v4.6.8 chore(deps): 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 c397e83 to 02b6ca8 Compare November 9, 2024 22:35
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from 02b6ca8 to c4a7b14 Compare November 28, 2024 15:26
@renovate renovate bot changed the title chore(deps): update jamesives/github-pages-deploy-action action to v4.6.9 chore(deps): update jamesives/github-pages-deploy-action action to v4.7.1 Nov 28, 2024
@renovate renovate bot changed the title chore(deps): update jamesives/github-pages-deploy-action action to v4.7.1 chore(deps): 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 c4a7b14 to 9df0aa6 Compare December 3, 2024 19:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants