v0.6.1

The README explains how to create your own GitHub App: helpers4-bot only works for the helpers4 and baxyz repositories.

A crate that crates.io does not know stops the release before it writes, like an unknown npm package: the message lists
the steps, and the new crates-token input can publish it once. The README explains the first release of a project.

Features

• preflight: ✨ stop on a crate crates.io does not know, and list the steps of a first release

Documentation

• docs: 📝 explain how to create your own GitHub App for the release

v0.6.0

Features

• action: ✨ leave the GitHub Release as a draft with publish-release: false

Reverts

• action: ⏪ remove the publish-release input

v0.5.2

The refusal to move the branch now also points at a classic branch protection, which rulesets hide and which
the action cannot read (it needs the administration permission). The README also explains the order of a first release across npm, crates.io and JSR.

Bug fixes

• commit: 📝 point at a classic branch protection when the branch refuses the release commit

v0.5.1

Bug fixes

• commit: 🐛 report why GitHub refuses to move the branch

v0.5.0

Features

• config: ✨ publish the npm packages a build generates (npm: dir/*)
• verify: ✨ stop before writing on an npm package that does not exist yet

Bug fixes

• since: 🐛 keep @SInCE next on a prerelease

v0.4.4

Features

• action: ✨ report what a dry run found

v0.4.3

Features

• publish: ✨ publish the crates of a workspace together

v0.4.2

Bug fixes

• publish: 🐛 check the version the registry tool will publish
• version: 💬 say how to release when there is no commit since the last one
• changelog: 🐛 give a release with no change notes instead of an empty body

v0.4.1

Bug fixes

• publish: 🐛 never publish a manifest that does not carry the version of the release

v0.4.0

Breaking changes

• action: 💥 take the configuration as inputs, with no .github/release.yml