Skip to content

chore: bump AltWebSocketSharp to 1.0.10 - #18

Merged
RobertPoienar merged 1 commit into
masterfrom
chore/bump-version-1.0.10
Nov 13, 2026
Merged

RobertPoienar merged 1 commit into
masterfrom
chore/bump-version-1.0.10

Conversation

@RobertPoienar

Copy link
Copy Markdown
Collaborator

Why

#17 fixed ClientWebSocket.Close() waiting the full 5 s close timeout. The C# AltDriver (Bindings~/dotnet/AltDriver/AltDriver.csproj in the Unity SDK) gets AltWebSocketSharp 1.0.9 from NuGet, so every AltDriver.Stop() still takes 5 s until a release with the fix is published.

Change

  • altwebsocket-sharp.csproj: VersionPrefix 1.0.9 → 1.0.10
  • release.yml: the hardcoded push path AltWebSocketSharp.1.0.9.nupkg → AltWebSocketSharp.1.0.10.nupkg

1.0.9 is the latest version on nuget.org, so 1.0.10 is free.

Testing

dotnet pack altwebsocket-sharp.csproj -c release (the same command release.yml runs) creates bin/release/AltWebSocketSharp.1.0.10.nupkg, which matches the new push path.

After merge

Publish a GitHub release (or run the release workflow manually) to push the package. Then bump AltDriver.csproj in the Unity SDK repos to 1.0.10.

🤖 Generated with Claude Code

Publishes the Close() fix from #17 to NuGet, so the C# AltDriver can
pick it up. release.yml pushes a hardcoded nupkg name, so it is bumped
alongside VersionPrefix.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@RobertPoienar
RobertPoienar merged commit d724c54 into master Nov 13, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants