publish: getsentry/replay-debugger@0.0.1

[sentry-release-bot]

Requested by: @limbonaut

Merge target: (default)

Quick links:

• View changes
• View check runs

Assign the accepted label to this issue to approve the release.
To retract the release, the person requesting it must leave a comment containing #retract on a line by itself under this issue.

Targets

• github
• registry

Checked targets will be skipped (either already published or user-requested skip). Uncheck to retry a target.

---

📋 Changelog

Bug Fixes 🐛

Ci

• Add dynamic path resolution in bump-version script by @limbonaut in #14
• Add CHANGELOG.md by @billyvg in #13
• Specify minVersion: 2.14.0 for craft by @billyvg in #12
• Bump craft action sha by @billyvg in #11

Build / dependencies / internal 🔧

• Avoid macOS-specific SED syntax in bump-version script by @limbonaut in #16
• Use pull_request_target for changelog preview by @BYK in #15

[github-actions]

Publishing: run#21179434855

[github-actions]

Failed to publish. (run logs)

Bad branch? You can delete with ease and start over.

[BYK]

@limbonaut -- this is the error:

• This branch must not contain merge commits.

This is caused by branch protection rules not playin well with Craft merging the release branch back into the main branch. I'll see if I can get a fix in to make sure it doesn't do a merge commit but in the meantime you can relax the branch protection rules to finalize your release.

[limbonaut]

I don't have access to repo settings, @BYK.
Let's ask @billyvg - he's the maintainer.

[billyvg]

@BYK Do you know what user role Craft uses? Is it via the Sentry Release bot? I could add a bypass

[BYK]

@billyvg yup, it's that one.