mirror of
https://github.com/getsentry/sentry-for-ai.git
synced 2026-09-14 14:28:22 +08:00
Evan Purkhiser
b4e096aa37
The plugins had no releases to speak of: one hand-edited version copied across four manifests, no tags in any distribution repo, and every merge rewriting each repo's main. Nothing separated "merged" from "shipped", and no ref named a version anyone could pin or roll back to. src/plugins/version.json is now the one version, stamped over the 0.0.0 placeholder in each manifest at build time, so the four plugins move in lockstep from a single bump. Deploys land on develop instead, leaving main to advance only when the Release plugins workflow cuts a version -- which tags this repo plugin/v<version> and each distribution repo v<version>. Consumers all resolve main today, so this is what makes shipping deliberate rather than a side effect of merging. Develop builds carry their distance from the last tag (1.2.1-dev.14.gdeadbee). The patch bump is load-bearing: semver ranks a prerelease below its release, so 1.2.0-dev.14 would compare older than the 1.2.0 it is fourteen commits ahead of, and build metadata is ignored in comparisons entirely.