Skip to content

chore: merge dev into main - #171

Merged
TitusKirch merged 2 commits into
mainfrom
dev
Nov 13, 2026
Merged

TitusKirch merged 2 commits into
mainfrom
dev

Conversation

@github-actions

Copy link
Copy Markdown

Automated rollup PR for changes accumulated on dev. Mark ready when you want it to land — and use a merge commit, not squash, so individual feat:/fix: commits stay visible to release-please.

The release pull request #170 could not be merged because its commit was
not signed. release-me v0.5.0 creates the release commit through the
GitHub API, so it is signed, and it is the first release carrying what
duxt needed from the next channel. The action now comes from
ostendorf-cloud/release-me, pinned by SHA like every other action, and
the floating exception is gone from action-pins.test.ts and the agent
files.
@TitusKirch
TitusKirch marked this pull request as ready for review November 13, 2026 00:07
The test hung past its 300 s limit on PR #171, where it normally takes
about 80 s, and vitest's timeout reported neither the request nor the
server's output. Every request to the built server now carries a 60 s
deadline unless it brings its own signal, fails with its method and
path, and a failure of any kind prints the requests still open and the
tail of the server output.
@TitusKirch
TitusKirch merged commit b8f58a7 into main Nov 13, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant