ship

To automate creating a pull request after updating the changelog and bumping the version, you can use a release workflow that merges the base branch, runs tests, updates VERSION and CHANGELOG files, commits, pushes, and opens the PR automatically.

The best way to ensure your branch is ready to ship is to execute a release workflow that merges the base branch, runs the project test suite, and reviews the diff to prevent shipping accidental or broken changes before opening a pull request.

Merging the base branch before running tests prevents release workflow errors by integrating the latest upstream changes into your working branch, ensuring the test suite executes against the current codebase before you bump the version and push.

Yes, you can automatically bump the VERSION and update the CHANGELOG when pushing code by triggering a workflow that performs these updates, commits the changes, pushes to your branch, and creates a pull request to merge into main.

You do not need a specific CI pipeline to run tests and review the diff before deploying; a local release workflow can execute the test suite, inspect the diff, bump the version, and generate the pull request directly from your working branch.

An automated release workflow fails when the base branch is not merged first because unmerged upstream changes can cause test failures or conflicts during the diff review, preventing a clean version bump and pull request creation.