v2.0.2

What's Changed

• Update node version from 14 to 16 by @yucheng11122017 in #8
• Replace deprecated set-output with GITHUB_OUTPUT by @yucheng11122017 in #10
• Upgrade setup-node to v3 from v2 by @yucheng11122017 in #13
• Update MarkBind Action node version to 18 by @gerteck in #17

New Contributors

• @yucheng11122017 made their first contribution in #8
• @gerteck made their first contribution in #17

Full Changelog: v2.0.1...v2.0.2

v2.0.1

markbind-action

Features

• Add reusable workflows (#4)

Dependencies

• Update Node.js version to v14 after MarkBind v4 release (#7)

v2.0.0

markbind-action

Breaking Changes

Update markbind-action to enhance existing features (#1)

A number of inputs have now changed both in terms of how they are specified in the workflow and the details of the inputs.

Migrating

If you are unsure where to start, first have a look at the README.md. It may be easier to look at the available options and choose
the relevant optional inputs to build your workflow.

A basic example for building and deploying to GitHub Pages is as follows:

name: MarkBind Action

on:
  push:
    branches:
      - main

jobs: 
  build_and_deploy:
    runs-on: ubuntu-latest
    steps:
      - name: Build & Deploy MarkBind site
        uses: MarkBind/markbind-action@v2
        with:
          token: ${{ secrets.GITHUB_TOKEN }}
          version: '3.1.1'
          baseUrl: '/repoName'

Enhancements

Build with specified version (including the latest developmental version) of MarkBind (#1)
Build with files that are not at the root level of the repository (#1)
Option to keep files or discard before push to gh-pages branch (#1)

Features

Deploy to Surge.sh (#1)
PR preview for PRs made within the same repository (#1)

Documentation

Update readme to fix errors and improve readability (#3)

Initial release

1.0.0

Update README.md