Repository navigation
chore: release duxt v0.14.1, duxt-typesense v0.14.1, duxt-meilisearch v0.14.1, duxt-wiki v0.14.1 - #170
Closed
kirchdev-release[bot] wants to merge 1 commit into
Closed
chore: release duxt v0.14.1, duxt-typesense v0.14.1, duxt-meilisearch v0.14.1, duxt-wiki v0.14.1#170kirchdev-release[bot] wants to merge 1 commit into
kirchdev-release[bot] wants to merge 1 commit into
Conversation
… v0.14.1, duxt-wiki v0.14.1
kirchdev-release
Bot
added
the
autorelease: pending
Member
|
Closed: the release commit on this branch was not signed. Release-me is being updated to v0.5.0 on dev; the next release run recreates this pull request. |
TitusKirch
added a commit
that referenced
this pull request
Nov 13, 2026
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
added a commit
that referenced
this pull request
Nov 13, 2026
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release duxt v0.14.1, duxt-typesense v0.14.1, duxt-meilisearch v0.14.1, duxt-wiki v0.14.1
Changelog
duxt
v0.14.1 (2026-11-13)
Bug Fixes
Performance
duxt-typesense
v0.14.1 (2026-11-13)
Bug Fixes
duxt-meilisearch
v0.14.1 (2026-11-13)
Bug Fixes
duxt-wiki
v0.14.1 (2026-11-13)
Bug Fixes
Performance