mirror of
https://github.com/getsentry/sentry-for-ai.git
synced 2026-09-14 14:28:22 +08:00
Evan Purkhiser
89c55f0d3d
Add the Craft release pipeline so packages/installer can be published to npm as @sentry/ai. - .craft.yml configures a single npm target (public scoped access) with a tarball-name guard. There is deliberately no github target, so a release creates no git tags and no GitHub releases -- nothing repo-wide implying the skills/plugins are versioned by it. - The release branch is scoped to `release-installer/<version>` via releaseBranchPrefix, so it reads as a package release. craft creates it during prepare and deletes it after publish, so it is transient. - changelogPolicy is `simple` (matching sentry-javascript) and the changelog lives with the package at packages/installer/CHANGELOG.md. The entry is written by hand before releasing; `auto` would sweep this repo's skill-drift and plugin churn into the installer changelog. - release.yml runs `craft prepare` via the Sentry release bot App token. It must be an App token rather than GITHUB_TOKEN so the pushed release branch triggers release-build.yml, which packs the tarball and uploads it as the SHA-named artifact Craft's GitHub provider expects. - The package gains `files: ["dist", "CHANGELOG.md"]`, publishConfig.access public, and an explicit LICENSE so the published tarball is complete without relying on pnpm copying the root LICENSE. Publishing runs from getsentry/publish after a team lead approves the release issue; this repo only prepares the release and builds the artifact.