Release #6

	name: Release

	on:
	workflow_dispatch:

	env:
	CARGO_TERM_COLOR: always

	jobs:
	release:
	if: github.repository == 'blue-build/cli'
	runs-on: ubuntu-latest
	permissions:
	id-token: write
	contents: write
	packages: write

	steps:
	- uses: actions/checkout@v4
	with:
	fetch-depth: 0

	- uses: chainguard-dev/actions/setup-gitsign@main

	- uses: actions/cache@v4
	with:
	path: \|
	target/
	~/.cargo/bin/
	~/.cargo/git/db/
	~/.cargo/registry/index/
	~/.cargo/registry/cache/
	key: ${{ runner.os }}-cargo-build-stable-${{ hashFiles('**/Cargo.toml') }}

	- name: Install cargo-release
	run: cargo install cargo-release

	- name: Git setup
	run: \|
	git config user.name github-actions
	git config user.email [email protected]

	# Leaving bevy comments here for us to discuss. Do we want to start tagging our pre-releases with `dev`?
	- name: Setup release
	run: \|
	# release: remove the dev suffix, like going from 0.X.0-dev to 0.X.0
	# --workspace: updating all crates in the workspace
	# --no-publish: do not publish to crates.io
	# --execute: not a dry run
	# --no-tag: do not push tag for each new version
	# --no-push: do not push the update commits
	# --dependent-version upgrade: change 0.X.0-dev in internal dependencies to 0.X.0
	# --exclude: ignore those packages
	cargo release release \
	--workspace \
	--no-publish \
	--execute \
	--no-tag \
	--no-confirm \
	--no-push \
	--dependent-version upgrade

	- name: Create PR
	uses: peter-evans/create-pull-request@v5
	with:
	delete-branch: true
	base: "main"
	title: "Preparing Next Release"
	body: \|
	Preparing next release
	This PR has been auto-generated

Provide feedback