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

Update JamesIves/github-pages-deploy-action action to v4 #3

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

Update JamesIves/github-pages-deploy-action action to v4 #3

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 5, 2023 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
JamesIves/github-pages-deploy-action action major 3.7.1 -> v4.6.9

Release Notes

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

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

v4.2.3

Compare Source

Minor Changes

  • Improved action logging. This is part 1 or 2 updates that will make the logs easier to traverse. Warnings and notices are now provided so you don't need to expand the logs to get the termination message.
  • Dependency bumps across the board.

v4.2.2

Compare Source

Minor Changes

  • Introduces major version tags. You can now point your workflow to JamesIves/github-pages-deploy-action@v4 if you'd like to always have the most cutting edge changes outside of using the release branch directly.
  • The version tags for this project now include a v to be consistent with other officially provided actions by GitHub. You can use JamesIves/[email protected] for instance. Dependabot should pick up this change automatically.

v4.2.1

Compare Source

Minor Changes

  • Resolves an issue where the operating system warning was showing incorrectly.

v4.2.0

Compare Source

Happy New Year 2022!

London

Minor Changes

  • Implements a warning if you're using an unsupported operating system. This will occur if the workflow runs within MacOS or Windows. The workflow will not be cancelled.
  • The action is now case insensitive, allowing you to make casing changes to files so long as you commit them using the git mv command prior to the workflow running. (#​895)
  • Fixes an issue that was causing single-commit to fail when using repository-name if the branch name was equal from the origin to destination. (#​665)
  • Enabled Dependabot updates for the GitHub Actions that are used as part of the projects integration tests.
  • Made improvements to the issue template.
  • Modified the dev container so it now properly runs on Node 14 when used within GitHub Codespaces.
  • Modified the default exclude list to use an enum value to ensure accuracy.
  • Dependency upgrades.

v4.1.9

Compare Source

Minor Changes

  • Dependency/security updates from third parties.

v4.1.8

Compare Source

Minor Changes

  • Library dependency and security bumps.
  • README modifications.

New Contributors

Full Changelog: JamesIves/github-pages-deploy-action@4.1.7...4.1.8

v4.1.7

Compare Source

Minor Changes

  • Dependency upgrades
  • Modified README examples to use npm ci instead of npm install in examples by @​bananer in https://github.com/JamesIves/github-pages-deploy-action/pull/934
  • Modified the git-config-email option again. If you wish to omit this field entirely you must now provide <> in the field instead of an empty string. This is due to the fact that GitHub Actions defaults all undefined fields to an empty string, causing the default behavior to not work when you don't provide a git-config-email parameter at all. You can find an example of this below.
name: Build and Deploy
on: [push]
jobs:
  build-and-deploy:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout 🛎️
        uses: actions/[email protected]

      - name: Install and Build 🔧
        run: |
          npm install
          npm run build

      - name: Deploy 🚀
        uses: JamesIves/[email protected]
        with:
          branch: gh-pages
          folder: build
          git-config-email: <>

New Contributors

Full Changelog: JamesIves/github-pages-deploy-action@4.1.6...4.1.7

v4.1.6

Compare Source

Minor Changes

  • Resolves an issue that was causing a permission error on the cleanup job. This error was caused by other actions changing directory permissions that prevented a worktree removal step from executing correctly. #​922
  • Migrated the project to Node version 14 across all integration tests, nvm file, etc.
  • Numerous third party dependency updates/fixes.
  • The git-config-email option now accepts an empty string as a valid value in a workflow. This will allow the email part of the commit signature to empty, for example Author Name <>. You can find an example of how to utilize this below. #​868
name: Build and Deploy
on: [push]
jobs:
  build-and-deploy:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout 🛎️
        uses: actions/[email protected]

      - name: Install and Build 🔧
        run: |
          npm install
          npm run build

      - name: Deploy 🚀
        uses: JamesIves/[email protected]
        with:
          branch: gh-pages
          folder: build
          git-config-email: ''

v4.1.5

Compare Source

Minor Changes

  • Resolves a bug that was causing the usage of the clean and single commit options together to fail.
  • Numerous dependency and security bumps.

v4.1.4

Compare Source

Minor Changes

  • Resolves an issue with the buffer length causing issues with very large repos (thanks to @​garazdawi)
  • Lots of dependency updates across the board.
  • Minor README adjustments.

v4.1.3

Compare Source

Minor Changes

  • Resolves a false positive error that was caused by a build cleanup step.

v4.1.2

Compare Source

Minor Changes

  • Fixed an issue that prevented you from deploying if you had a similarly named branch, ie docs and ci/docs.
  • Resolved an issue that prevents you from deploying a second time in the same workflow job. The action will now correctly cleanup branch artifacts after it's done deploying.
  • Standardized ESLint configuration, now using typescript-eslint as opposed to the GitHub configuration.
  • Documentation change/cleanup for some parts.
  • Added sponsorship automation for people who donate via GitHub Sponsors.

v4.1.1

Compare Source

Minor Changes

  • Dependency/security updates provided through Dependabot.
  • Minor tooling changes, format is now lint:format for consistency.
  • Removed ^ keyword in all dependencies within package.json.

v4.1.0

Compare Source

Major Changes

  • This action now supports self-hosted GitHub instances such as GitHub Enterprise. The GitHub Actions runner passes down the server url of the GitHub instance it's running on which is what the deployment step will use going forward to determine where it needs to make requests to. If you have any issues with this feature please create an issue. For more details about how to use an open source action on GitHub Enterprise please refer to the official GitHub documentation.

Minor Changes

  • Dependency updates across the board.

v4.0.0: 🎉

Compare Source

🎉 Version 4 is here! Please refer to the migration guide for information on breaking changes if you were previously using version 3. 🎉

Spaced

Major Changes ⚡

  • All inputs should are now kebab case/lowercase as opposed to snake case.
  • GITHUB_TOKEN is no longer required, if you rely on the default authentication method you can simply remove this field.
  • If you rely on an ACCESS_TOKEN to make your deployments you now need to use the token input. Please refer to the migration guide for more information.
  • SSH is now ssh-key and can accept either true or a private SSH key. Please refer to the README or/and migration guide for more details about how this works in this version.
  • The LFS option is now deprecated.
  • The PRESERVE option is no longer needed and is now deprecated.
  • CLEAN_EXCLUDE has a different syntax, please refer to the README or/and migration guide for more details.
  • Integration tests now run on every pull request.

Minor Changes 📜

  • You can now use the dry-run input to verify compatibility in your workflow without pushing to the branch. Check out the README for additional details.
  • ESlint is now enabled for unit tests.
  • CodeQL is now enabled on all incoming pull requests.
  • Release branch based dependencies are now automatically generated on a commit to a releases/* branch using GitHub Actions.
  • Integration tests now point to version 4.
  • Security documentation has been updated.
  • [GitHub Codespaces](https://redirect.gith

Configuration

📅 Schedule: Branch creation - "after 11pm every weekday,before 7am every weekday,every weekend" in timezone Europe/Brussels, 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 force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from cb24fce to 25f2158 Compare September 5, 2023 12:53
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from 25f2158 to 37a599b Compare November 28, 2023 05:03
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from 37a599b to 6754951 Compare April 17, 2024 14:05
@mauromorales
Copy link
Member

there are breaking changes between v3 and v4, so worth double checking before merging

@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from 6754951 to 594b0a7 Compare May 18, 2024 11:57
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from 594b0a7 to 51d181c Compare July 5, 2024 16:54
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from 51d181c to cf94656 Compare September 2, 2024 18:17
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch 4 times, most recently from 2218fe0 to d29ec4d Compare September 29, 2024 16:16
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from d29ec4d to 873977e Compare November 9, 2024 21:12
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.
1 participant
@mauromorales