Skip to content

chore: merge main into dev - #174

Merged
TitusKirch merged 30 commits into
devfrom
main
Nov 13, 2026
Merged

TitusKirch merged 30 commits into
devfrom
main

Conversation

@TitusKirch

Copy link
Copy Markdown
Member

Brings dev up to main after the v0.14.1 release. dev carries nothing main lacks, so this merges cleanly.

What dev gains:

Merge with a merge commit, not a squash, so the release commits keep their identity on both branches.

TitusKirch and others added 30 commits October 29, 2026 03:35
release-me v0.5.0 refuses the configuration the next channel accepted:
the pre-release type switches now live under labels.prerelease, and a
component names its changelog with changelog-path. The release run on
main failed parsing release-me.yaml before doing anything. With both
keys renamed, release-me next on main computes 0.14.1 for every
package, as the closed release pull request #170 did.
GHSA-4m76-xfj5-7975, GHSA-h7mg-cq63-vhpq and GHSA-3gg2-335m-rxc6 were
published against hono 4.13.15 and older, which the MCP SDK and
@hono/node-server resolved to 4.13.13. Their ranges already admit the
fix, so only the lockfile moves, to 4.13.17: 4.13.18 is still inside
the release cooldown.
@TitusKirch
TitusKirch merged commit 85346c0 into dev Nov 13, 2026
41 of 44 checks passed

This branch was successfully deployed

2 active deployments
production — 14502648 Deployed Nov 13, 2026 by kirchdev-release[bot] via Publish www #84
npm — 14502648 Deployed Nov 13, 2026 by TitusKirch via Publish duxt-wiki@v0.14.1 #56
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