Skip to content

Release request: include the UQUICConn session API required by uQUIC #426

Open

Description

@andre487

The latest tagged uTLS release, v1.8.2, cannot be used with refraction-networking/uquic at 837c7ce1b72bf07b2d29b3dabd5b45c60bec0f42: uQUIC calls UQUICConn.StoreSession, which is absent from that release.

Could you publish a release that includes the QUIC session API changes from 63aeec73c564 — feat: add quic changes from stdlib, together with any follow-up fixes required for a supported uQUIC pairing? Is there an expected timeframe for such a release?

Minimal reproduction

go.mod:

module example.com/utls-uquic-compat

go 1.26.3

require (
    github.com/refraction-networking/uquic v0.0.7-0.20260804184259-837c7ce1b72b
    github.com/refraction-networking/utls v1.8.2
)

main.go:

package main

import _ "github.com/refraction-networking/uquic"

func main() {}

Run:

go mod tidy
go build ./...

Reproduced with Go 1.27.0 on macOS arm64:

# github.com/refraction-networking/uquic/internal/handshake
internal/handshake/u_crypto_setup.go:228:17: h.conn.StoreSession undefined (type *"github.com/refraction-networking/utls".UQUICConn has no field or method StoreSession)

Version mismatch

uQUIC pins v1.7.4-0.20250521174854-63aeec73c564, which provides UQUICConn.StoreSession and forwards QUICConfig.EnableSessionEvents. In v1.8.2, that method is missing and UQUICClient does not forward EnableSessionEvents. Current master contains both pieces. This concerns UQUICConn, not the ordinary QUICConn, which has its own StoreSession method.

The pinned commit is not an ancestor of v1.8.2, so this is a release-line compatibility gap rather than a claim that v1.8.2 removed a previously released API. See the history comparison.

The same compilation blocker was mentioned in the additional context of #408, but that issue primarily concerned TLS session resumption and is closed. This request is specifically for a tagged release and a documented compatible uTLS/uQUIC version pair. We have not established that current master is fully runtime-compatible with uQUIC; the open UQUICConn fixes in #421, #424 and #425 may also be relevant to release readiness.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions