ci(release): Switch from action-prepare-release to Craft

[BYK]

Summary

This PR migrates from the deprecated action-prepare-release to the new Craft GitHub Actions.

Changes

• Migrated .github/workflows/release.yml to Craft reusable workflow
• Updated .craft.yml with versioning.policy: calver

Documentation

See https://getsentry.github.io/craft/github-actions/ for more information.

[github-actions]

Semver Impact of This PR

🟢 Patch (bug fixes)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

New Features ✨

Uptime

• Assertion failure data now contains the assertion by klochek in #459
• Add a config to disable assert evaluation by klochek in #457

Build / dependencies / internal 🔧

• (release) Switch from action-prepare-release to Craft by BYK in #463

---

_{🤖 This preview updates automatically when you update the PR.}

[sentry]

Bug: During scheduled runs, ${{ inputs.version }} will be empty, which may cause the craft action to fail as it might not accept an empty version string.
_{Severity: CRITICAL}

🔍 Detailed Analysis

The release.yml workflow is triggered on a schedule and by workflow_dispatch. For scheduled runs, the inputs context is empty. Consequently, the version and force parameters passed to the craft action will be empty strings. While the PR adds a versioning: policy: calver configuration, which might be intended to handle this, there is a risk that the craft action does not interpret an empty string as a request for auto-versioning and will instead fail, as it's documented to reject empty version inputs. This would cause all scheduled releases to fail.

💡 Suggested Fix

Provide a default value for the version and force inputs to handle scheduled runs where the inputs context is empty. For example: version: ${{ inputs.version || 'auto' }} and force: ${{ inputs.force || false }}.

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: .github/workflows/release.yml#L37-L38

Potential issue: The `release.yml` workflow is triggered on a schedule and by
`workflow_dispatch`. For scheduled runs, the `inputs` context is empty. Consequently,
the `version` and `force` parameters passed to the `craft` action will be empty strings.
While the PR adds a `versioning: policy: calver` configuration, which might be intended
to handle this, there is a risk that the `craft` action does not interpret an empty
string as a request for auto-versioning and will instead fail, as it's documented to
reject empty `version` inputs. This would cause all scheduled releases to fail.

_{Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 8427358}

[sentry]

Bug: On scheduled runs, inputs.version and inputs.force will be empty strings, which may cause the getsentry/craft action to fail if it doesn't handle empty inputs.
_{Severity: HIGH}

🔍 Detailed Analysis

The GitHub workflow is configured to run on a schedule. During a scheduled run, the inputs context is empty, causing ${{ inputs.version }} and ${{ inputs.force }} to be passed as empty strings to the getsentry/craft@v2 action. If this action does not gracefully handle empty string values for these parameters, the scheduled release process will fail. While it is plausible the action is designed to handle this, as its author wrote this workflow, the behavior is unconfirmed and could lead to a failure in the automated release pipeline.

💡 Suggested Fix

To ensure the workflow is robust, add a fallback value for the version parameter. For example, use ${{ inputs.version || 'auto' }} to explicitly use the 'auto' versioning feature during scheduled runs, assuming this is the intended default behavior for the Craft action.

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: .github/workflows/release.yml#L37-L38

Potential issue: The GitHub workflow is configured to run on a schedule. During a
scheduled run, the `inputs` context is empty, causing `${{ inputs.version }}` and `${{
inputs.force }}` to be passed as empty strings to the `getsentry/craft@v2` action. If
this action does not gracefully handle empty string values for these parameters, the
scheduled release process will fail. While it is plausible the action is designed to
handle this, as its author wrote this workflow, the behavior is unconfirmed and could
lead to a failure in the automated release pipeline.

_{Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 8473281}