Repository navigation
chore(deps): bump undici from 7.22.0 to 7.24.0 - #2
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [undici](https://github.com/nodejs/undici) from 7.22.0 to 7.24.0. - [Release notes](https://github.com/nodejs/undici/releases) - [Commits](nodejs/undici@v7.22.0...v7.24.0) --- updated-dependencies: - dependency-name: undici dependency-version: 7.24.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Contributor
Author
|
Superseded by #3. |
unbraind
added a commit
that referenced
this pull request
May 28, 2026
… validate guards, idempotent materialize no-op Followups to first-pass review on PR #78. CodeRabbit's 7 ".agents/pm files" comments were a false-positive (pm IS the system of record AND the files ARE tracked in git — that's the entire pm-cli design). Codex P2 #1: src/cli/commands/extension/scaffold.ts now emits the typed `defineExtension({...})` shape ONLY in package mode (peerDependencies on @unbrained/pm-cli make the import resolvable from the package's own node_modules). In extension-only mode there is no package.json with that dep, so the dynamic loader's `import(<file-url>)` would have raised ERR_MODULE_NOT_FOUND when the extension was actually loaded. The import-free shape from before is restored for that mode, decorated with a JSDoc @PARAM hint so editors that follow JSDoc still narrow the api parameter (matches the SDK type contract without a runtime dep). Codex P2 #2: src/sdk/cli-contracts.ts CLOSE_FLAG_CONTRACTS now lists `--resolution`, `--expected-result` (alias `--expected_result`), and `--actual-result` (alias `--actual_result`). `pm contracts --command close --json` now surfaces them; bootstrap flag normalization and the JSON help payload pick them up automatically. Gemini high #1+#2: src/cli/commands/validate.ts buildMetadataCheck adds optional-chain guards so a future settings shape with an unsupported field in `required_fields` falls back to 0 instead of throwing TypeError, and skips writing when the count-key / item-ids-key / truncated-key mapping is undefined. Gemini medium (idempotency): `pm plan materialize --steps all` now returns a successful no-op (exit 0) with `materialize_skipped` populated when every selected step is already completed or already materialized. Previously this threw NOT_FOUND, breaking agent/CI pipelines that re-invoke the same script. Explicit step-ref path keeps processing pending refs in the same call and recording skipped reasons. Test updated to assert the new exit-0 + materialize_skipped contract. Gemini medium (style): dropped the redundant `trimmed.length === 0` short-circuit in `normalizeDependencyKindInput` (update.ts) — the alias lookup with the trimmed key already returns the canonical value (or the trimmed input) safely. 1866 tests, 100% coverage (stmt/branch/func/line), typecheck, quality:static, quality:docs-skills, security:scan, changelog:check all green. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
unbraind
added a commit
that referenced
this pull request
May 29, 2026
…gv, schema
Gemini (case-insensitivity):
- mergeAdditiveTags / applyTagRemovals now normalize the existing baseTags to
canonical lowercase before merging/removing, so mixed-case legacy or
hand-edited tags ("Beta") dedupe against additions ("beta") and are removed
by lowercase selectors. Output stays sorted + deduped + lowercased.
- pm update skips a no-op tag write: an additive/subtractive-only mutation that
resolves to the existing set no longer pushes "tags" to changed_fields or
churns history/updated_at. Comparison uses the RAW original so a canonical
case normalization still counts as a real change (consistent with
update-many's buildTagMutationPlan).
Codex P2 #1 (JSON-array argv corruption):
- Dropped list:true from the --add-tags/--remove-tags flag contracts. These use
Commander's repeatable collector, so the bootstrap list-coalescer must not
comma-join repeated occurrences — it was turning
`--add-tags '["a","b"]' --add-tags c` into `["a","b"],c` and breaking the
documented JSON-array form. Each occurrence is now parsed independently.
Codex P2 #2 (published tool schema):
- Added addTags/removeTags to TOOL_CREATE/UPDATE_OPTION_CONTRACTS and
PM_TOOL_PARAMETER_PROPERTIES (+ descriptions) so the additionalProperties:false
MCP/SDK tool schema accepts them instead of rejecting schema-validated clients.
(--expected/--actual remain CLI-only sugar; MCP clients use expectedResult.)
New regression tests for case-insensitive merge/removal and the no-op skip.
1973 tests, 100% coverage, all gates green.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This was referenced Jun 10, 2026
pm context: Support --depth full and --fields customization for comprehensive project snapshots
#156
Closed
Owner
|
PM archive governance: pm-w2krlt. This item owns canonical reconstruction and verified comment linkage for historical artifacts that did not embed a live PM item ID. This comment records lineage only; it does not reopen or change this artifact. |
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.
Bumps undici from 7.22.0 to 7.24.0.
Release notes
Sourced from undici's releases.
... (truncated)
Commits
07a3906Bumped v7.24.0 (#4887)74495c6fix: reject duplicate content-length and host headers84235c6Fix websocket 64-bit length overflow77594f9fix: validate upgrade header to prevent CRLF injectioncb79c57fix: validate server_max_window_bits range in permessage-deflate4147ce2Merge commit '2ee00cb3'2ee00cbfix(websocket): add maxDecompressedMessageSize limit for permessage-deflate5890c7bfix(deduplicate): stream response chunks to waiting handlersfbda3c1Bumped v7.23.0 (#4884)07276c9fix: remove unused kSocketPath symbolDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.