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.1.7 #972

Closed

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 18, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Type Update Change
JamesIves/github-pages-deploy-action action patch 4.1.5 -> 4.1.7

Release Notes

JamesIves/github-pages-deploy-action

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 use "npm ci" instead of "npm install" in examples JamesIves/github-pages-deploy-action#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/checkout@v2.3.1

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

      - name: Deploy 🚀
        uses: JamesIves/github-pages-deploy-action@4.1.6
        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/checkout@v2.3.1

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

      - name: Deploy 🚀
        uses: JamesIves/github-pages-deploy-action@4.1.6
        with:
          branch: gh-pages
          folder: build
          git-config-email: ''

Configuration

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

🚦 Automerge: Disabled due to failing status checks.

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.

@renovate renovate bot changed the title Update JamesIves/github-pages-deploy-action action to v4.1.6 Update JamesIves/github-pages-deploy-action action to v4.1.7 Nov 26, 2021
@renovate renovate bot force-pushed the renovate/jamesives-github-pages-deploy-action-4.x branch from e82f06f to 52e44cf Compare November 26, 2021 14:49
@jgillich jgillich closed this Jan 23, 2022
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