Skip to content

chore(release): 0.4.31.2 — Teams Graph SSRF-guard hardening (#178) + NOTICE #181

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
patrick-chinchill merged 1 commit into from
Sep 2, 2026
Merged

chore(release): 0.4.31.2 — Teams Graph SSRF-guard hardening (#178) + NOTICE #181

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
8 changes: 6 additions & 2 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,12 @@
# Changelog

## Unreleased
## 0.4.31.2

- **Docs/licensing:** added `NOTICE` reproducing Vercel Chat's MIT copyright notice — this package is a derivative (port) of `vercel/chat`, and the notice now ships in the sdist and in the wheel's `dist-info/licenses/`. No code changes.
Python-only fixes on top of `4.31.0` (`UPSTREAM_PARITY` unchanged at `4.31.0`).

- **Teams: Graph SSRF / token-leak guard hardening** (#178, security). `call_teams_graph_api` decided absolute-vs-relative URLs with a case-sensitive `startswith("http")`, so `HTTPS://evil.example/x`, `HtTpS://…` or the scheme-relative `//evil.example/x` fell into the relative-path branch, where `urljoin` still resolved to the attacker host and the Graph-scoped bearer token was attached without consulting `is_trusted_graph_url`. Routing now uses the same scheme-insensitive parse as the allowlist, so every absolute or scheme-relative target goes through the trust check. Regression tests cover the mixed-case and scheme-relative forms.
- **Tests:** the Teams skip-auth fixture survives the SDK's flag rename (#180). No runtime change.
- **Docs/licensing:** added `NOTICE` reproducing Vercel Chat's MIT copyright notice — this package is a derivative (port) of `vercel/chat`, and the notice now ships in the sdist and in the wheel's `dist-info/licenses/` (#179). No code changes.

## 0.4.31.1

Expand Down
1 change: 1 addition & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,7 @@ Our version embeds the upstream Vercel Chat version: `0.{upstream_major}.{upstre
- `0.4.30` = synced to upstream `4.30.0`
- `0.4.31` = synced to upstream `4.31.0`
- `0.4.31.1` = Python-only fixes on top of `4.31.0` (Slack #138/#95)
- `0.4.31.2` = Python-only fixes on top of `4.31.0` (Teams Graph SSRF-guard hardening #178, NOTICE)
- `UPSTREAM_PARITY` constant in `__init__.py` = programmatic access

## Architecture
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 @@ -7,7 +7,7 @@

Multi-platform async chat SDK for Python. Port of [Vercel Chat](https://github.com/vercel/chat) (MIT, © Vercel, Inc. — see [NOTICE](NOTICE)).

> **Status: 0.4.31.1 — synced to [Vercel Chat 4.31.0](https://github.com/vercel/chat)** (`UPSTREAM_PARITY = "4.31.0"`). See [CHANGELOG.md](CHANGELOG.md).
> **Status: 0.4.31.2 — synced to [Vercel Chat 4.31.0](https://github.com/vercel/chat)** (`UPSTREAM_PARITY = "4.31.0"`). See [CHANGELOG.md](CHANGELOG.md).

## Why chat-sdk?

Expand Down
2 changes: 1 addition & 1 deletion pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[project]
name = "chat-sdk"
version = "0.4.31.1"
version = "0.4.31.2"
description = "Multi-platform async chat SDK for Python — port of Vercel Chat"
keywords = [
"chat",
Expand Down
Loading