Draft a new release of the project.
First, let's work on the following steps.
What's Changed, Contributors and Full Changelog are needed../tmp/release-notes/*.md will be used as the release notes.Then, from $ARGUMENTS, get the new version without v prefix, and assign it to $new_version. For example, if $ARGUMENTS is "v1.0.0", the new version is "1.0.0".
If $ARGUMENTS is empty, determine the new version automatically by performing the release-dry-run skill.
Let's resume the release process.
git pull.git checkout -b release/v${new_version}.getVersion() function to return the ${new_version} in src/cli/index.ts, and run pnpm cicheck. If the checks fail, fix the code until pass. Then, execute , and .git addgit commitgit pushpnpm version ${new_version} --no-git-tag-version.package.json will be modified, execute git commit and git push.getVersion() in src/cli/index.ts is updated to the ${new_version}.gh pr create to the main branch.gh release create v${new_version} --draft --title v${new_version} --notes-file ./tmp/release-notes/*.md command on the github.com/dyoshikawa/rulesync repository. This creates a draft release so that the publish-assets workflow can upload assets later.