Github Pages Deploy Action Versions Save

🚀 Automatically deploy your project to GitHub Pages using GitHub Actions. This action can be configured to push your production-ready code into any branch you'd like.

v4.6.0

2 weeks ago

What's Changed

New Contributors

Full Changelog: https://github.com/JamesIves/github-pages-deploy-action/compare/v4.5.0...v4.6.0

v4.5.0

5 months ago

What's Changed

New Contributors

Full Changelog: https://github.com/JamesIves/github-pages-deploy-action/compare/v4.4.3...v4.5.0

v4.4.3

9 months ago

What's Changed

Full Changelog: https://github.com/JamesIves/github-pages-deploy-action/compare/v4...v4.4.3

v4.4.2

11 months ago

What's Changed

  • Dependency updates

Full Changelog: https://github.com/JamesIves/github-pages-deploy-action/compare/v4...v4.4.2

v4.4.1

1 year ago

What's Changed

  • The action now fully runs on Node 16. (Thank you @nickmccurdy)

Changelog

New Contributors

Full Changelog: https://github.com/JamesIves/github-pages-deploy-action/compare/v4...v4.4.1

v4.4.0

1 year ago

What's Changed

New Contributors

Sponsors ❤️

  • Special thanks to @github for their generous sponsorship contributions.

github  

Full Changelog: https://github.com/JamesIves/github-pages-deploy-action/compare/v4...v4.4.0

v4.3.4

1 year ago

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 ❤️

  • Special thanks to @github for their generous sponsorship contributions.

github  

Full Changelog: https://github.com/JamesIves/github-pages-deploy-action/compare/v4...v4.3.4

v4.3.3

2 years ago

Changes

  • Resolves an issue in some workflows that were caused by a recent change to permission handling.

v4.3.2

2 years ago

Changes

  • Resolves an issue with folder permissions that causes an issue in container workflows when rsync attempts to run.

v4.3.1

2 years ago

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.