Sync the non-npm manifests to 4.5.1 (one-time, unblocks the release)

[brentrager]

What happened

The release that bumped package.json to 4.5.1 ran from the commit before the version-sync fix (#186) landed, so it used the old plain changeset version with no sync. The next release run then hit the new guard and stopped:

check-versions: FAILED — manifests disagree with package.json (4.5.1)
- python/pyproject.toml is at 4.5.0, expected 4.5.1 (package.json)
- python/uv.lock is at 4.5.0, expected 4.5.1 (package.json)
- rust/logger/Cargo.toml is at 4.5.0, expected 4.5.1 (package.json)
- rust/logger/Cargo.lock is at 4.5.0, expected 4.5.1 (package.json)
- go/version.go is at 4.5.0, expected 4.5.1 (package.json)
- dotnet/src/SmooAI.Logger/SmooAI.Logger.csproj is at 4.5.0, expected 4.5.1 (package.json)

That is the guard doing its job, not a regression.main genuinely carries a package.json bump that never reached the other five manifests — the exact defect #186 exists to stop, caught on the last bump the old flow could produce.

This is a one-time transition. From here pnpm run version is changeset version && node scripts/sync-versions.mjs, and changesets/action commits the whole working tree after the version command, so the synced manifests ride along inside the bump commit.

Why no changeset

4.5.1 was never published — the failing guard skipped every publish step (npm, PyPI, crates.io, the Go tag, NuGet were all skipped). Merging this lets the release finish 4.5.1 consistently across all five registries.

Adding a changeset would bump to 4.5.2 and strand 4.5.1 in the changelog with nothing published under it. No code changes here, only version metadata.

Verification

• node scripts/check-versions.mjs → OK (all manifests at 4.5.1)
• uv sync --locked --group dev clean (this is why uv.lock had to be in the synced set — it errors outright on a stale lock)
• cargo check --locked clean, so cargo publish --locked will be too

🤖 Generated with Claude Code

https://claude.ai/code/session_0152bbE1veqfG1SVJdyLCBxC

[changeset-bot]

⚠️ No Changeset found

Latest commit: cdfda8a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[brentrager]

What happened

The release that bumped package.json to 4.5.1 ran from the commit before the version-sync fix (#186) landed, so it used the old plain changeset version with no sync. The next release run then hit the new guard and stopped:

check-versions: FAILED — manifests disagree with package.json (4.5.1)
- python/pyproject.toml is at 4.5.0, expected 4.5.1 (package.json)
- python/uv.lock is at 4.5.0, expected 4.5.1 (package.json)
- rust/logger/Cargo.toml is at 4.5.0, expected 4.5.1 (package.json)
- rust/logger/Cargo.lock is at 4.5.0, expected 4.5.1 (package.json)
- go/version.go is at 4.5.0, expected 4.5.1 (package.json)
- dotnet/src/SmooAI.Logger/SmooAI.Logger.csproj is at 4.5.0, expected 4.5.1 (package.json)

That is the guard doing its job, not a regression.main genuinely carries a package.json bump that never reached the other five manifests — the exact defect #186 exists to stop, caught on the last bump the old flow could produce.

This is a one-time transition. From here pnpm run version is changeset version && node scripts/sync-versions.mjs, and changesets/action commits the whole working tree after the version command, so the synced manifests ride along inside the bump commit.

Why no changeset

4.5.1 was never published — the failing guard skipped every publish step (npm, PyPI, crates.io, the Go tag, NuGet were all skipped). Merging this lets the release finish 4.5.1 consistently across all five registries.

Adding a changeset would bump to 4.5.2 and strand 4.5.1 in the changelog with nothing published under it. No code changes here, only version metadata.

Verification

• node scripts/check-versions.mjs → OK (all manifests at 4.5.1)
• uv sync --locked --group dev clean (this is why uv.lock had to be in the synced set — it errors outright on a stale lock)
• cargo check --locked clean, so cargo publish --locked will be too

🤖 Generated with Claude Code

https://claude.ai/code/session_0152bbE1veqfG1SVJdyLCBxC

[changeset-bot]

⚠️ No Changeset found

Latest commit: cdfda8a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[brentrager]

What happened

The release that bumped package.json to 4.5.1 ran from the commit before the version-sync fix (#186) landed, so it used the old plain changeset version with no sync. The next release run then hit the new guard and stopped:

check-versions: FAILED — manifests disagree with package.json (4.5.1)
- python/pyproject.toml is at 4.5.0, expected 4.5.1 (package.json)
- python/uv.lock is at 4.5.0, expected 4.5.1 (package.json)
- rust/logger/Cargo.toml is at 4.5.0, expected 4.5.1 (package.json)
- rust/logger/Cargo.lock is at 4.5.0, expected 4.5.1 (package.json)
- go/version.go is at 4.5.0, expected 4.5.1 (package.json)
- dotnet/src/SmooAI.Logger/SmooAI.Logger.csproj is at 4.5.0, expected 4.5.1 (package.json)

That is the guard doing its job, not a regression.main genuinely carries a package.json bump that never reached the other five manifests — the exact defect #186 exists to stop, caught on the last bump the old flow could produce.

This is a one-time transition. From here pnpm run version is changeset version && node scripts/sync-versions.mjs, and changesets/action commits the whole working tree after the version command, so the synced manifests ride along inside the bump commit.

Why no changeset

4.5.1 was never published — the failing guard skipped every publish step (npm, PyPI, crates.io, the Go tag, NuGet were all skipped). Merging this lets the release finish 4.5.1 consistently across all five registries.

Adding a changeset would bump to 4.5.2 and strand 4.5.1 in the changelog with nothing published under it. No code changes here, only version metadata.

Verification

• node scripts/check-versions.mjs → OK (all manifests at 4.5.1)
• uv sync --locked --group dev clean (this is why uv.lock had to be in the synced set — it errors outright on a stale lock)
• cargo check --locked clean, so cargo publish --locked will be too

🤖 Generated with Claude Code

https://claude.ai/code/session_0152bbE1veqfG1SVJdyLCBxC

[changeset-bot]

⚠️ No Changeset found

Latest commit: cdfda8a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[brentrager]

What happened

The release that bumped package.json to 4.5.1 ran from the commit before the version-sync fix (#186) landed, so it used the old plain changeset version with no sync. The next release run then hit the new guard and stopped:

check-versions: FAILED — manifests disagree with package.json (4.5.1)
- python/pyproject.toml is at 4.5.0, expected 4.5.1 (package.json)
- python/uv.lock is at 4.5.0, expected 4.5.1 (package.json)
- rust/logger/Cargo.toml is at 4.5.0, expected 4.5.1 (package.json)
- rust/logger/Cargo.lock is at 4.5.0, expected 4.5.1 (package.json)
- go/version.go is at 4.5.0, expected 4.5.1 (package.json)
- dotnet/src/SmooAI.Logger/SmooAI.Logger.csproj is at 4.5.0, expected 4.5.1 (package.json)

That is the guard doing its job, not a regression.main genuinely carries a package.json bump that never reached the other five manifests — the exact defect #186 exists to stop, caught on the last bump the old flow could produce.

This is a one-time transition. From here pnpm run version is changeset version && node scripts/sync-versions.mjs, and changesets/action commits the whole working tree after the version command, so the synced manifests ride along inside the bump commit.

Why no changeset

4.5.1 was never published — the failing guard skipped every publish step (npm, PyPI, crates.io, the Go tag, NuGet were all skipped). Merging this lets the release finish 4.5.1 consistently across all five registries.

Adding a changeset would bump to 4.5.2 and strand 4.5.1 in the changelog with nothing published under it. No code changes here, only version metadata.

Verification

• node scripts/check-versions.mjs → OK (all manifests at 4.5.1)
• uv sync --locked --group dev clean (this is why uv.lock had to be in the synced set — it errors outright on a stale lock)
• cargo check --locked clean, so cargo publish --locked will be too

🤖 Generated with Claude Code

https://claude.ai/code/session_0152bbE1veqfG1SVJdyLCBxC

[changeset-bot]

⚠️ No Changeset found

Latest commit: cdfda8a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[brentrager]

What happened

The release that bumped package.json to 4.5.1 ran from the commit before the version-sync fix (#186) landed, so it used the old plain changeset version with no sync. The next release run then hit the new guard and stopped:

check-versions: FAILED — manifests disagree with package.json (4.5.1)
- python/pyproject.toml is at 4.5.0, expected 4.5.1 (package.json)
- python/uv.lock is at 4.5.0, expected 4.5.1 (package.json)
- rust/logger/Cargo.toml is at 4.5.0, expected 4.5.1 (package.json)
- rust/logger/Cargo.lock is at 4.5.0, expected 4.5.1 (package.json)
- go/version.go is at 4.5.0, expected 4.5.1 (package.json)
- dotnet/src/SmooAI.Logger/SmooAI.Logger.csproj is at 4.5.0, expected 4.5.1 (package.json)

That is the guard doing its job, not a regression.main genuinely carries a package.json bump that never reached the other five manifests — the exact defect #186 exists to stop, caught on the last bump the old flow could produce.

This is a one-time transition. From here pnpm run version is changeset version && node scripts/sync-versions.mjs, and changesets/action commits the whole working tree after the version command, so the synced manifests ride along inside the bump commit.

Why no changeset

4.5.1 was never published — the failing guard skipped every publish step (npm, PyPI, crates.io, the Go tag, NuGet were all skipped). Merging this lets the release finish 4.5.1 consistently across all five registries.

Adding a changeset would bump to 4.5.2 and strand 4.5.1 in the changelog with nothing published under it. No code changes here, only version metadata.

Verification

• node scripts/check-versions.mjs → OK (all manifests at 4.5.1)
• uv sync --locked --group dev clean (this is why uv.lock had to be in the synced set — it errors outright on a stale lock)
• cargo check --locked clean, so cargo publish --locked will be too

🤖 Generated with Claude Code

https://claude.ai/code/session_0152bbE1veqfG1SVJdyLCBxC

[changeset-bot]

⚠️ No Changeset found

Latest commit: cdfda8a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[brentrager]

What happened

The release that bumped package.json to 4.5.1 ran from the commit before the version-sync fix (#186) landed, so it used the old plain changeset version with no sync. The next release run then hit the new guard and stopped:

check-versions: FAILED — manifests disagree with package.json (4.5.1)
- python/pyproject.toml is at 4.5.0, expected 4.5.1 (package.json)
- python/uv.lock is at 4.5.0, expected 4.5.1 (package.json)
- rust/logger/Cargo.toml is at 4.5.0, expected 4.5.1 (package.json)
- rust/logger/Cargo.lock is at 4.5.0, expected 4.5.1 (package.json)
- go/version.go is at 4.5.0, expected 4.5.1 (package.json)
- dotnet/src/SmooAI.Logger/SmooAI.Logger.csproj is at 4.5.0, expected 4.5.1 (package.json)

That is the guard doing its job, not a regression.main genuinely carries a package.json bump that never reached the other five manifests — the exact defect #186 exists to stop, caught on the last bump the old flow could produce.

This is a one-time transition. From here pnpm run version is changeset version && node scripts/sync-versions.mjs, and changesets/action commits the whole working tree after the version command, so the synced manifests ride along inside the bump commit.

Why no changeset

4.5.1 was never published — the failing guard skipped every publish step (npm, PyPI, crates.io, the Go tag, NuGet were all skipped). Merging this lets the release finish 4.5.1 consistently across all five registries.

Adding a changeset would bump to 4.5.2 and strand 4.5.1 in the changelog with nothing published under it. No code changes here, only version metadata.

Verification

• node scripts/check-versions.mjs → OK (all manifests at 4.5.1)
• uv sync --locked --group dev clean (this is why uv.lock had to be in the synced set — it errors outright on a stale lock)
• cargo check --locked clean, so cargo publish --locked will be too

🤖 Generated with Claude Code

https://claude.ai/code/session_0152bbE1veqfG1SVJdyLCBxC

[changeset-bot]

⚠️ No Changeset found

Latest commit: cdfda8a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[brentrager]

What happened

The release that bumped package.json to 4.5.1 ran from the commit before the version-sync fix (#186) landed, so it used the old plain changeset version with no sync. The next release run then hit the new guard and stopped:

check-versions: FAILED — manifests disagree with package.json (4.5.1)
- python/pyproject.toml is at 4.5.0, expected 4.5.1 (package.json)
- python/uv.lock is at 4.5.0, expected 4.5.1 (package.json)
- rust/logger/Cargo.toml is at 4.5.0, expected 4.5.1 (package.json)
- rust/logger/Cargo.lock is at 4.5.0, expected 4.5.1 (package.json)
- go/version.go is at 4.5.0, expected 4.5.1 (package.json)
- dotnet/src/SmooAI.Logger/SmooAI.Logger.csproj is at 4.5.0, expected 4.5.1 (package.json)

That is the guard doing its job, not a regression.main genuinely carries a package.json bump that never reached the other five manifests — the exact defect #186 exists to stop, caught on the last bump the old flow could produce.

This is a one-time transition. From here pnpm run version is changeset version && node scripts/sync-versions.mjs, and changesets/action commits the whole working tree after the version command, so the synced manifests ride along inside the bump commit.

Why no changeset

4.5.1 was never published — the failing guard skipped every publish step (npm, PyPI, crates.io, the Go tag, NuGet were all skipped). Merging this lets the release finish 4.5.1 consistently across all five registries.

Adding a changeset would bump to 4.5.2 and strand 4.5.1 in the changelog with nothing published under it. No code changes here, only version metadata.

Verification

• node scripts/check-versions.mjs → OK (all manifests at 4.5.1)
• uv sync --locked --group dev clean (this is why uv.lock had to be in the synced set — it errors outright on a stale lock)
• cargo check --locked clean, so cargo publish --locked will be too

🤖 Generated with Claude Code

https://claude.ai/code/session_0152bbE1veqfG1SVJdyLCBxC

[changeset-bot]

⚠️ No Changeset found

Latest commit: cdfda8a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[brentrager]

What happened

The release that bumped package.json to 4.5.1 ran from the commit before the version-sync fix (#186) landed, so it used the old plain changeset version with no sync. The next release run then hit the new guard and stopped:

check-versions: FAILED — manifests disagree with package.json (4.5.1)
- python/pyproject.toml is at 4.5.0, expected 4.5.1 (package.json)
- python/uv.lock is at 4.5.0, expected 4.5.1 (package.json)
- rust/logger/Cargo.toml is at 4.5.0, expected 4.5.1 (package.json)
- rust/logger/Cargo.lock is at 4.5.0, expected 4.5.1 (package.json)
- go/version.go is at 4.5.0, expected 4.5.1 (package.json)
- dotnet/src/SmooAI.Logger/SmooAI.Logger.csproj is at 4.5.0, expected 4.5.1 (package.json)

That is the guard doing its job, not a regression.main genuinely carries a package.json bump that never reached the other five manifests — the exact defect #186 exists to stop, caught on the last bump the old flow could produce.

This is a one-time transition. From here pnpm run version is changeset version && node scripts/sync-versions.mjs, and changesets/action commits the whole working tree after the version command, so the synced manifests ride along inside the bump commit.

Why no changeset

4.5.1 was never published — the failing guard skipped every publish step (npm, PyPI, crates.io, the Go tag, NuGet were all skipped). Merging this lets the release finish 4.5.1 consistently across all five registries.

Adding a changeset would bump to 4.5.2 and strand 4.5.1 in the changelog with nothing published under it. No code changes here, only version metadata.

Verification

• node scripts/check-versions.mjs → OK (all manifests at 4.5.1)
• uv sync --locked --group dev clean (this is why uv.lock had to be in the synced set — it errors outright on a stale lock)
• cargo check --locked clean, so cargo publish --locked will be too

🤖 Generated with Claude Code

https://claude.ai/code/session_0152bbE1veqfG1SVJdyLCBxC

[changeset-bot]

⚠️ No Changeset found

Latest commit: cdfda8a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR