gh-pages

Developer Tools

Publishes a directory to a GitHub Pages branch.

Latest v6.3.0 · by Tim SchaubWebsitetschaub/gh-pages

Changelog

v6.3.0

Latest
Added 1
  • Support filenames starting with `-
Changed 5
  • Bump chai from 4.3.10 to 4.5.0
  • Bump mocha from 10.7.3 to 10.8.2
  • Bump mocha from 10.8.2 to 11.0.1
  • Bump eslint-config-tschaub from 14.1.2 to 15.1.0
  • Bump commander from 11.1.0 to 13.0.0

From gh-pages

What's Changed
New Contributors

Full Changelog: https://github.com/tschaub/gh-pages/compare/v6.2.0...v6.3.0

View originalPermalink
How v6.3.0 went

v6.2.0

Changed 1
  • Update globby
Fixed 1
  • Update instruction for next.js

From gh-pages

What's Changed
New Contributors

Full Changelog: https://github.com/tschaub/gh-pages/compare/v6.1.1...v6.2.0

View originalPermalink
How v6.2.0 went

v6.1.1

Fixed 1
  • Add missing cname option not passed to the config

From gh-pages

Fixes
Dependency Updates
New Contributors

Full Changelog: https://github.com/tschaub/gh-pages/compare/v6.1.0...v6.1.1

View originalPermalink
How v6.1.1 went

v6.1.0

Added 1
  • Add --nojekyll and --cname options

From gh-pages

What's Changed

Full Changelog: https://github.com/tschaub/gh-pages/compare/v6.0.0...v6.1.0

View originalPermalink
How v6.1.0 went

v6.0.0

Added 1
  • Add error message when --dist is not specified
Removed 1
  • Drop support for Node 14

From gh-pages

This release drops support for Node 14. Otherwise, there are no special upgrade considerations.

What's Changed
New Contributors

Full Changelog: https://github.com/tschaub/gh-pages/compare/v5.0.0...v6.0.0

View originalPermalink
How v6.0.0 went

v5.0.0

Changed 2
  • The publish method now always returns a promise, including in error cases where it previously did not
  • Minimum Node version for tests is now 14, though the library should still work on Node 12

From gh-pages

Potentially breaking change: the publish method now always returns a promise. Previously, it did not return a promise in some error cases. This should not impact most users.

Updates to the development dependencies required a minimum Node version of 14 for the tests. The library should still work on Node 12, but tests are no longer run in CI for version 12. A future major version of the library may drop support for version 12 altogether.

What's Changed
New Contributors

Full Changelog: https://github.com/tschaub/gh-pages/compare/v4.0.0...v5.0.0

View originalPermalink
How v5.0.0 went

v4.0.0

Changed 1
  • Updated development dependencies and formatting

From gh-pages

This release doesn't include any breaking changes, but due to updated development dependencies, tests are no longer run on Node 10.

What's Changed

Full Changelog: https://github.com/tschaub/gh-pages/compare/v3.2.3...v4.0.0

View originalPermalink
How v4.0.0 went

v3.2.3

Changed 2
  • Update glob-parent
  • Switch from filenamify-url to filenamify

From gh-pages

View originalPermalink
How v3.2.3 went

v3.0.0

Added 1
  • Allow custom script before git add with beforeAdd option
Changed 2
  • Development dependencies updated to address security warnings
  • Tests no longer run on Node versions below 10
Fixed 1
  • Fix remove not working properly

From gh-pages

Breaking changes:

None really. But tests are no longer run on Node < 10. Development dependencies were updated to address security warnings, and this meant tests could no longer be run on Node 6 or 8. If you still use these Node versions, you may still be able to use this library, but be warned that tests are no longer run on these versions.

All changes:

View originalPermalink
How v3.0.0 went

v2.2.0

Added 2
  • Allow an absolute path as dist directory
  • Add --no-history flag to not preserve deploy history
Changed 1
  • Update dependencies

From gh-pages

View originalPermalink
How v2.2.0 went
View all

Discussion

If you publish gh-pages, you can claim this product by proving you administer its repository.