`craft` target for Unity

We’re setting up craft with the new Unity SDK.

CI is already configured in a way that we use the GitHub artifacts provider and craft prepare x.x.x already works as expected. Release registry has a new SDK: upm:sentry-unity and is configured already.

What we’re missing now is the target to get craft publish to work.

We’ve identified two tasks to do that:

1. The github target currently downloads the artifact, unzip it, and publish all files in that artifact to the github release. This isn’t the expected behavior for Unity, so ideally we’d just skip attaching anything to the github release altogether.

One alternative is to zip the files before adding as attachment. And having the target (see below) unzip to move to package

1. The actual ‘release’ for UPM is to replace all contents of a folder in the repository itself, and push it to the main branch. More context about the release process in this issue, and the contributing docs.

[BYK]

Closed via #209

[bruno-garcia]

To update this issue with the last comment from the pair “Unity Release” issue:

Currently the “upm target” is taken by these steps:

export release=0.0.6
export artifact=where/craft/downloaded/artifact
git checkout [e-mail]:getsentry/unity.git
cd unity
git rm -r .
unzip $artifact/package-release.zip -d .
git add .
git commit -m "release $release"
git tag $release
git push origin main --tags

It’s something that @bitsandfoxes is looking into to get into craft.