Skip to content

chore(release): prepare 0.5.0 #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
moonyue-w merged 1 commit into from
Oct 13, 2026
Merged

chore(release): prepare 0.5.0 #14

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,12 +5,14 @@ existing `0.1.0` release; earlier development prereleases are not listed.

## [Unreleased]

## [0.5.0]

### Added

- Forward admin and Identity SAT issuance and Forward SAT revocation, using explicit per-call SA Key authentication, typed issuance/revocation metadata, and no automatic retries. Existing platform credentials and PAT/SAT business authentication remain unchanged.

- Forward Realtime Beta: create Conversations with a stable idempotency key, connect over WebSocket using PAT/SAT or shared Credentials, exchange text and PCM16 audio, observe typed events and Work progress, report playback, interrupt, and confirm graceful closure.
- Realtime Conversation history with independent `before` pagination, persisted history IDs and preserved unknown event fields. Connections have separate stage timeouts, bounded receive queues, and explicit protocol failures; they do not follow redirects, reconnect, or replay input automatically.
- Realtime SA access requires a Forward-issued bound SAT and a Realtime-enabled Template; a platform SAT from `ServiceAccountCredential` alone does not establish the required Forward binding.

## [0.4.0] - 2026-10-12

Expand Down
2 changes: 1 addition & 1 deletion Makefile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ lint:
check-version:
@set -eu; version="$${VERSION:-}"; \
if test -z "$$version"; then \
echo "VERSION is required (for example: make check-version VERSION=0.4.0)" >&2; exit 1; \
echo "VERSION is required (for example: make check-version VERSION=0.5.0)" >&2; exit 1; \
fi; \
if ! printf '%s\n' "$$version" | grep -Eq '^(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)(-[0-9A-Za-z-]+(\.[0-9A-Za-z-]+)*)?$$'; then \
echo "VERSION must be canonical Go semver without a v prefix or build metadata: $$version" >&2; exit 1; \
Expand Down
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ The SDK ships two clients that share authentication, transport, retries, error h
## Installation

```sh
go get github.com/QoderAI/qoder-cloud-agents-sdk-go@v0.4.0
go get github.com/QoderAI/qoder-cloud-agents-sdk-go@v0.5.0
```

This SDK is pre-1.0, so pin a version explicitly and keep the version your build resolved in `go.mod` and `go.sum`.
Expand Down
2 changes: 1 addition & 1 deletion convention/version.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,4 +4,4 @@ package convention
// X-Qoder-Package-Version. It must match the released module tag, otherwise the
// server-side SDK version statistics describe a version that was never shipped.
// `make check-version VERSION=<version>` validates it before release.
const packageVersion = "0.4.0"
const packageVersion = "0.5.0"
Loading