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

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

Merged
merged 1 commit into from
May 18, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 18, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
JamesIves/github-pages-deploy-action action patch v4.6.0 -> v4.6.1

Release Notes

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

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


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 has been generated by Mend Renovate. View repository job log here.


PR-Codex overview

This PR updates the GitHub Pages deploy action to version 4.6.1 in the workflows for EBNF and LOC badge.

Detailed summary

  • Updated GitHub Pages deploy action to v4.6.1 in .github/workflows/ebnf.yml
  • Updated GitHub Pages deploy action to v4.6.1 in .github/workflows/loc-badge.yml

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@@ -76,7 +76,7 @@ jobs:
cp "${p}.png" gh-pages/ebnf
cp "${p}.svg" gh-pages/ebnf
done
- uses: JamesIves/github-pages-deploy-action@v4.6.0
- uses: JamesIves/github-pages-deploy-action@v4.6.1
with:
branch: gh-pages
folder: gh-pages

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code diff you've provided shows a change made to the version of the github-pages-deploy-action used in a GitHub Actions workflow. The version was updated from v4.6.0 to v4.6.1. There don't appear to be any syntax errors or irregularities in this code snippet, it seems to be a standard minor version upgrade.

However, please note that whether this change is correct and appropriate depends on changes made between versions v4.6.0 and v4.6.1 of the github-pages-deploy-action. If important changes were introduced with version v4.6.1 that impact your application, or if there are significantly changed usage instructions or breaking changes, review might be necessary.

As of my last training data up until September 2021, the specific details about this version of the github-pages-deploy-action would not have been available. Therefore, you should consult the action's release notes or changelog for specifics about what changed in v4.6.1 and how it might affect your project.

@@ -38,7 +38,7 @@ jobs:
debug: true
directory: .
badge: target/loc-badge.svg
- uses: JamesIves/github-pages-deploy-action@v4.6.0
- uses: JamesIves/github-pages-deploy-action@v4.6.1
with:
branch: gh-pages
folder: target

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The provided diff shows a change from version 4.6.0 to 4.6.1 of the JamesIves/github-pages-deploy-action in a GitHub Actions workflow.

As an AI model, I'm unable to access real-time Internet data or databases to confirm the latest version or existence of this action as of your current date. However, the change appears valid assuming version 4.6.1 exists and no specific features of version 4.6.0 are required by your project.

In general, when updating dependencies, it's important to review the release notes or change logs for the new version to ensure there are no breaking changes or behavior modifications that could potentially impact your workflow. It's also recommended to test your code thoroughly after updates.

@yegor256
Copy link
Member

@rultor please, try to merge, since 22 checks have passed

@rultor
Copy link
Contributor

rultor commented May 18, 2024

@rultor please, try to merge, since 22 checks have passed

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor rultor merged commit cf31d50 into master May 18, 2024
23 checks passed
@rultor
Copy link
Contributor

rultor commented May 18, 2024

@rultor please, try to merge, since 22 checks have passed

@yegor256 Done! FYI, the full log is here (took me 22min)

@renovate renovate bot deleted the renovate/jamesives-github-pages-deploy-action-4.x branch May 18, 2024 14:58
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.

None yet

2 participants