Repository navigation
Release v0.2.40 - #3290
Merged
Merged
Release v0.2.40#3290
Conversation
Mechanical daily release: patch bump 0.2.39 → 0.2.40. CHANGELOG.md section for 0.2.40, version in core/package.json, core/package-lock.json and patches/ds-bot/0007-version-and-tooling.patch, and the six changelog.d/ fragments that went into the section, deleted.
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 v0.2.40
Mechanical daily release under the standing approval in AGENTS.md: patch
bump 0.2.39 → 0.2.40. No PASS and no human approval is required for a
mechanical release PR;
risk:T3is expected and does not stop it.Changed files:
CHANGELOG.md(new## [0.2.40] - 2026-11-22sectionand its link definition),
core/package.json,core/package-lock.json(root and
packages[""]),patches/ds-bot/0007-version-and-tooling.patch, and the 6changelog.d/fragments below deleted.Entries in v0.2.40
Fixed
key,token,secret,auth,password,passwd,credential,signature,cookie,session,bearer, andpatas a whole segment —X-Github-Patyes,X-Patch-Idno) is masked before the reason is stored, longest value first so one credential is never left as a surviving tail, so it can no longer be printed into the Bot's system prompt every turn (#3275).command/args(the next token, the--flag=valueform, or aNAME=valuetoken), and the value of a header or environment name such assig,hmacorpass— withsigandpassmatched as whole segments, soassign,compassandbypasskeep their values — is masked with[hidden]before the stored reason is cut at 300 characters, longest value first and a value under six characters left alone, so a failed server's own error line can no longer print that credential into the Bot's system prompt every turn (#3278).command, or a credential value that begins with-: acommandcontaining a space or a tab is read as a command line and its tokens go through the same rules asargs— the token after a credential-looking flag, the--flag=valueform and aNAME=valuetoken are masked with[hidden]— and the token after a credential-looking flag is its value even when it begins with-, so--api-key --verbosestores--api-key [hidden]and a second--api-keyis masked as a value too. Acommandthat is one bare token without whitespace stays unmasked, because it cannot be told from a program name, the same limit as a bareargstoken; the stored reason is still one line of at most 300 characters with the mask applied before the cut, longest value first and a value under six characters left alone, so a failed server's own error line can no longer print that credential into the Bot's system prompt every turn (#3281).workflow/assignreports a refused start as a failed answer (ok: falsewitherror.codebot/refusedanderror.detailsnaming the node) instead of a value inside the success envelope, so a caller cannot mistake a failed dispatch for a started run (#3282).Written-by: Release