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): bump JamesIves/github-pages-deploy-action from 4.1.5 to 4.2.5 #129

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 21, 2022

Bumps JamesIves/github-pages-deploy-action from 4.1.5 to 4.2.5.

Release notes

Sourced from JamesIves/github-pages-deploy-action's releases.

v4.2.5

Minor Changes

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

v4.2.4

Minor Changes

  • Modified how workflow notices get displayed. (#1033 Thanks to @​hemberger)
  • Dependency upgrades.

v4.2.3

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

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/github-pages-deploy-action@v4.2.2 for instance. Dependabot should pick up this change automatically.

4.2.1

Minor Changes

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

4.2.0

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.

4.1.9

Minor Changes

  • Dependency/security updates from third parties.

4.1.8

... (truncated)

Commits
  • 830e6a4 Deploy Production Code for Commit 340091a9f3b338991f3995d53fd5be82651fc553 🚀
  • 340091a v4.2.4 (#1037)
  • b36f842 Deploy Production Code for Commit 0752a8c57b6c10ab57484898a6bf14c27eb97b18 🚀
  • 0752a8c Merge branch 'dev' into releases/v4
  • 91d4e8f Part 1: Logging Improvements (#1022)
  • cdd72ba Bump nowactions/update-majorver from 1.1.0 to 1.1.2 (#1021)
  • 92429b8 Update production.yml
  • 0332481 Update build.yml
  • 424cd9d Bump @​types/node from 17.0.12 to 17.0.13 (#1020)
  • 5a8b8e4 Bump node-fetch from 2.6.1 to 2.6.7 (#1018)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update Github_actions code labels Feb 21, 2022
Bumps [JamesIves/github-pages-deploy-action](https://github.com/JamesIves/github-pages-deploy-action) from 4.1.5 to 4.2.5.
- [Release notes](https://github.com/JamesIves/github-pages-deploy-action/releases)
- [Commits](JamesIves/github-pages-deploy-action@4.1.5...v4.2.5)

---
updated-dependencies:
- dependency-name: JamesIves/github-pages-deploy-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/github_actions/JamesIves/github-pages-deploy-action-4.2.5 branch from 2155a8c to 802cd55 Compare April 3, 2022 19:57
@dermatologist dermatologist merged commit cbeab33 into develop Apr 3, 2022
@dermatologist dermatologist deleted the dependabot/github_actions/JamesIves/github-pages-deploy-action-4.2.5 branch April 3, 2022 20:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file github_actions Pull requests that update Github_actions code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant