#1052 chore(release): prepare SDK v0.29.1

Prepares SDK v0.29.1 with make bump VERSION=0.29.1. The tag follows once this merges.

Why 0.29.1, not 0.29.0

v0.29.0 was published only to RubyGems and as the Swift tag. Its Go release failed on a flaky test (TestCache_EntryNeverPairsOneResponsesETagWithAnothersBody, fixed in #1051), so Go, npm, PyPI, crates.io and Maven never shipped it and there is no GitHub Release for it. Those four pending publishes (TypeScript, Python, Kotlin, Rust) have been rejected so nothing ships 0.29.0 later; the v0.29.0 tag stays in place. v0.29.1 is the release to use in every language.

Release scope since v0.28.1

Everything v0.29.0 carried, plus the test fix:

• #1044: the Go event-feed connector renews a ticket stream in band before its token expires (see #1050 for the detail). It's what makes this a minor release over v0.28.1; nothing breaks.
• #1046, #1047, #1048: Dependabot bumps (oxlint in TypeScript, tokio in Rust and its conformance runner).
• #1051: the ETag cache race test waits for both writers before checking they overlapped. Test only; no SDK code changes.

For Ruby and Swift consumers already on 0.29.0, 0.29.1 has no library changes. MIGRATING.md has no Unreleased section, so this version ships without migration notes, as v0.29.0 and v0.28.1 did.

The diff

19 files, 22 lines changed each way, every one a version substitution (0.29.0 to 0.29.1) in the 11 version files and 8 lockfiles, the same files #1050 touched. As in #1050, the local npm (10.9.3) also dropped the libc fields from both TypeScript lockfiles; I reverted that and kept only the three version lines.

make release VERSION=0.29.1 passes every check on this branch, including rs-publish-check's cargo publish --dry-run, and then stops at the branch guard, as it should.

Not related to this release

Known-defect tracking issues are open is still red on main and isn't required. No release workflow runs it.