v0.8.27 tag: embedded Version constant still reads v0.8.26

[arreyder]

What

In the v0.8.27 git tag, pkg/sdk/version.go still has:

```go
const Version = "v0.8.26"
```

The previous "Update SDK version to v0.8.X" commits before each release tag (e.g. 52acb60 for v0.8.26, 772a94b for v0.8.25) appear to have been skipped between v0.8.26 and v0.8.27 — the v0.8.27 tag was placed directly on the feat(expand): periodic mid-expansion progress log commit (a2bdd0c) without first bumping the constant.

Impact

Anything that reports the SDK version at runtime — including baton-sdk's own version subcommand and any downstream service log/metric that uses sdk.Version for diagnostics — will report v0.8.26 even when v0.8.27 is the actually-loaded module version. Cosmetic but confusing during incident triage.

Found via

A code-review bot caught this while bumping ConductorOne/c1 from v0.8.23 → v0.8.27 (ductone/c1#17081). The vendored content is correct (matches the tag); only the embedded constant is stale.

Suggested fix

Either:

1. Cut a v0.8.28 with the constant updated to v0.8.28, or
2. Move the v0.8.27 tag to a commit that bumps the constant to v0.8.27.

Option 1 is safer (no force-tag).

[ggreer]

Yeah, the github action that updates the version runs after a release is tagged, so it's always one behind the real version.