Repository navigation
chore: release main - #168
Open
github-actions[bot] wants to merge 5 commits into
Open
github-actions[bot] wants to merge 5 commits into
github-actions[bot] wants to merge 5 commits into
Conversation
github-actions
Bot
requested a review
from dg-coreylweathers
as a code owner
November 12, 2026 23:16
github-actions
Bot
requested review from
GregHolmes and
deepgram-kiley
as code owners
November 12, 2026 23:16
dg-coreylweathers
added a commit
that referenced
this pull request
Nov 12, 2026
PR #165 merged 97 feature/fix commits via a merge commit whose own title isn't conventional-commit-formatted, and release-please's commit walk doesn't descend into a nested merge inside that branch's own history (the internal main-into-release/0.5.0 sync merge). As a result release-please never saw any of #165's commits and proposed an empty patch bump (PR #168) instead of the real 0.5.0 minor release. This marker commit sits directly on main, outside any merge, so release-please will see it and regenerate #168 correctly: Features and fixes mean a minor release, so with bump-patch-for-minor-pre-major set, release-please would otherwise propose only a patch. Release-As: 0.5.0
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
November 12, 2026 23:35
33d0b76 to
352baf3
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
November 12, 2026 23:39
352baf3 to
37fa9a0
Compare
…istory release-please's commit walk doesn't descend into #165's own nested sync merge, so it only saw 3 trivial commits sitting after it. Two problems followed from that, now fixed by hand: 1. CHANGELOG.md's 0.5.0 entry only listed those 3 commits. Replaced with the full set of 71 visible commits (feat/fix/perf/docs) from the true v0.4.1..#165 range, correctly ordered and sectioned, plus a Behavior changes section for upgrade-note-worthy changes to defaults. 2. The empty marker commit used to force the Release-As trailer had no file changes, so release-please's path-splitting misattributed it to packages/deepctl-plugin-example (proposing a bogus 0.1.13 -> 0.5.0 jump for an independently-versioned, untouched package). Reverted its pyproject.toml and CHANGELOG.md, and fixed the manifest back to 0.1.13 for that component.
The release App token needed to push this repo's own automated re-pin (the "Push the re-pin with the release App" job) is missing, so that automation never ran. uv.lock was still pinning every first-party package at 0.4.1 while pyproject.toml had already moved to 0.5.0, which fails `uv sync --group testing --locked` in CI. Regenerated with uv 0.9.30 (matching the Docker gate image) and confirmed with check_dependency_floors.py and a --locked sync.
…rsion Review on 83dff0c/96b59c7 found: - The credential-precedence bullet claimed an order change that didn't happen (307e2c3's commit says precedence is unchanged); replaced with the two real changes from that commit (env placeholder detection, keyring timeout fallback). - The Behavior changes section was missing three changes that affect stdout/stdin/exit-status in agent or CI contexts (fb7f9ec, ab6ceb9, e4db87a), and the dg init bullet undersold what changed. - uv.lock had been locked with uv 0.9.30 (the Docker gate image's version), not the 0.13.6 the repo's own CI and release re-pin job pin, which silently downgraded the lockfile format (revision 5 -> 3) and added two dependency markers unrelated to this release. Re-locked from origin/main's original uv.lock with uv 0.13.6 inside python:3.12-slim; diff is now exactly the 30 version-line changes, confirmed with check_dependency_floors.py and a --locked sync.
Nit from re-review on 619c7ca: the bullet was accurate but broader than the code — it didn't mention the save only happens when the output format was auto-detected and stdout isn't a regular file or /dev/null, or the temp-directory fallback.
This branch has not been deployed
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.
🤖 I have created a release beep boop
0.5.0
0.5.0 (2026-11-12)
Features
Bug Fixes
Performance Improvements
Documentation
Behavior changes
Upgrading to 0.5.0 changes these:
-o/--outputis deprecated fordg speak's audio file; use--out-fileinstead (8f59531).dg initno longer runs a template's setup commands or starts the app without a person at a terminal: pass--yes(or, outside an AI agent session,--install) to run setup and--startto start the app; otherwise it exits 1 withconfirmation_required(8c50ae1).dg initclones only Deepgram-owned templates now (56dc618).dg listen's prerecorded-o jsonnow prints the server's response body as sent — keys the server omitted no longer appear asnull— and-o yamlprints that body instead of the table (setDEEPCTL_LISTEN_JSON=sdkto restore the old JSON shape) (6aa1795).dg listenresult over 64 KiB is now saved under~/.deepctl/results/(or a private temp directory) instead of printed, when the output format was auto-detected and stdout isn't a regular file or/dev/null; stdout gets a summary, and--full-outputrestores the full result (fb7f9ec).dg speakno longer reads stdin unless the text argument is-(otherwise it exits withE-SPEAK-NO-TEXT), and refuses to write audio to a pipe (E-SPEAK-NO-OUTPUT) (ab6ceb9).dg login's confirmations now returnconfirmation_required(exit 1) instead of "Login cancelled" (e4db87a).DEEPGRAM_API_KEY,DEEPGRAM_PROFILE,DEEPGRAM_PROJECT_IDorDEEPGRAM_BASE_URLthat still holds an unexpanded${...}placeholder is now ignored, with aW-ENV-PLACEHOLDERwarning; off a terminal, a keyring that doesn't answer within 2 s is skipped for the config file or environment, with aW-KEYRING-TIMEOUTwarning. Credential precedence itself is unchanged from 0.4.1 (307e2c3).dg debug networkno longer attaches~/.netrccredentials to its probe requests (it never sent your Deepgram key) (edc5243).This PR was generated with Release Please. See documentation.