Release process to be automated

- Make sure your local main branch is up-to-date

- `git checkout main`
- `git fetch upstream`
- `git reset --hard upstream/main`

- Decide the version number of your next release, depending on the commits included:

- a patch version `X.X.(n+1)` when the release includes only bug fixes or small new features
- a minor version `X.(n+1).0` when the release includes notable new features
- a major version `(n+1).0.0` when the release introduces breaking changes / major refactoring or changes

- Package the action with `npm run all`
- Git add the changes of the `dist/` directory with `git add -u`
- Bump the package version with `npm version -f X.Y.Z` with the version decided before
- Publish to Github! `git push --tags upstream main`
- Update the “Major” version sliding tag `vN`

- `git tag -d vN`
- `git tag vN main`
- `git push upstream vN --force`

- Create a new GitHub release with a comprehensive changelog on https://github.com/bump-sh/github-action/releases/new