feat: 0.5 migration guide (#166) #115

	name: Deploy to GitHub Pages

	on:
	push:
	branches:
	- main
	# Review gh actions docs if you want to further define triggers, paths, etc
	# https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#on

	jobs:
	deploy:
	name: Deploy to GitHub Pages
	runs-on: ubuntu-latest
	steps:
	- uses: actions/checkout@v4
	- uses: actions/setup-node@v4
	with:
	node-version: 18.x
	cache: yarn

	# ignore scripts as indy-sdk will try to build and we don't have libindy
	- name: Install dependencies
	run: yarn install --frozen-lockfile --ignore-scripts
	- name: Build website
	run: yarn build

	# Popular action to deploy to GitHub Pages:
	# Docs: https://github.com/peaceiris/actions-gh-pages#%EF%B8%8F-docusaurus
	- name: Deploy to GitHub Pages
	uses: peaceiris/actions-gh-pages@v3
	with:
	github_token: ${{ secrets.GITHUB_TOKEN }}
	# Build output to publish to the `gh-pages` branch:
	publish_dir: ./build
	cname: credo.js.org
	# The following lines assign commit authorship to the official
	# GH-Actions bot for deploys to `gh-pages` branch:
	# https://github.com/actions/checkout/issues/13#issuecomment-724415212
	# The GH actions bot is used by default if you didn't specify the two fields.
	# You can swap them out with your own user credentials.
	user_name: github-actions[bot]
	user_email: 41898282+github-actions[bot]@users.noreply.github.com

Provide feedback