Repository navigation
chore(deps-dev): bump pm-changelog from 2026.7.12 to 2026.7.15 - #2
Merged
Merged
Conversation
Bumps [pm-changelog](https://github.com/unbraind/pm-changelog) from 2026.7.12 to 2026.7.15. - [Release notes](https://github.com/unbraind/pm-changelog/releases) - [Changelog](https://github.com/unbraind/pm-changelog/blob/main/CHANGELOG.md) - [Commits](unbraind/pm-changelog@v2026.7.12...v2026.7.15) --- updated-dependencies: - dependency-name: pm-changelog dependency-version: 2026.7.15 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
PR author is in the excluded authors list. |
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Sorry @dependabot[bot], you have reached your weekly rate limit of 500000 diff characters.
Please try again later or upgrade to continue using Sourcery
dependabot
Bot
deleted the
dependabot/npm_and_yarn/pm-changelog-2026.7.15
branch
July 17, 2026 08:44
unbraind
added a commit
that referenced
this pull request
Jul 22, 2026
…dges (#9) * feat(import): --link-deps maps GitHub issue-body dependencies to pm edges Opt-in second pass over `pm github import` that parses dependency references from issue BODIES (`Blocked by #N`, `Depends on owner/repo#N`, `Blocks #N`) and materializes them as pm dependency edges between the imported items, resolved through the existing `gh:owner/repo#N` provenance tags. Agents get the real ready/blocked ordering (`pm next`, `pm deps`) instead of a flat list — project management = context management. Implementation (index.ts): - parseDependencyReferences (pure): case/hyphen/colon-tolerant phrase grammar; bare `#N` + explicit `owner/repo#N`; multi-ref runs (`#1, #2 and #3`); fenced/inline code-span stripping; in-body dedupe. "Blocked by"/"Depends on" → blocked_by; "Blocks" → blocks. - buildProvenanceIndexFromMetadata + planDependencyLinks (pure): resolve refs to concrete edges; skip self-references, unresolved targets (counted), and issues whose source item is absent; dedupe edges. - linkImportedDependencies: best-effort, idempotent (`pm update --dep` dedupes by id+kind), path-agnostic (runs after the normal AND --atomic import). Ordering cycles the mapped edges introduce are reported, not rejected, via the SDK `collectNewOrderingCycleWarnings` advisory over the workspace before/after the pass — restoring the advisory that the `commitItemMutations` atomic path drops (its outcome carries only {id,op}). Result surface gains linkedDependencies / unresolvedDependencyRefs / orderingCycleWarnings (+ dependencyLinkFailures when non-empty); a `--dry-run --link-deps` result reports wouldLinkDependencyCandidates. peerDependency floor unchanged (>=2026.7.20 already exports both SDK fns). Tests: 25 new (parser/planner/provenance units, hermetic DI orchestration, 3 real end-to-end runImport cases) — full suite 164 green, typecheck clean, audit --omit=dev clean, changelog:check up to date. Verified against a real private repo over live REST: 3 dependency-phrased issues → 3 edges, code-block `#999` correctly ignored, `pm next` gating confirmed. Tracks pm item pm-github-hdai. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(import): --link-deps infra failures never discard a committed import Adversarial review found the second-pass call sites awaited linkImportedDependencies without guarding SDK-load / snapshot / advisory errors. On a host whose CLI predates the required SDK exports (or on a transient workspace-read error), the items commit, then the pass throws and runImport rejects — the caller sees a FAILED command despite a fully successful import, contradicting the feature's best-effort contract. Fix: linkImportedDependencies now wraps (1) SDK resolution + pre-edge snapshot — a failure returns linked:0 with a 'dependency linking skipped' note instead of throwing; and (2) the after-snapshot + ordering-cycle detector — a failure preserves the edges already written and records an 'ordering-cycle advisory skipped' note. Per-edge failures were already captured. +2 tests (27 link-deps / 166 total, all green). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: SteveBot <1153461+unbraind@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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 pm-changelog from 2026.7.12 to 2026.7.15.
Release notes
Sourced from pm-changelog's releases.
Changelog
Sourced from pm-changelog's changelog.
... (truncated)
Commits
2eec8e9Release pm-changelog v2026.7.152ca739dtrack: close pmc-4nkr (release npm-guard hardening merged in #74)23e70c1ci(release): poll npm before failing GitHub-release creation (#74)7d45e26Release pm-changelog v2026.7.14-28d294f0fix(changelog): emit JSON on stdout for --format json without global --json (...8300854Release pm-changelog v2026.7.14-18c28117Retry transient package-install cleanup99c7c67Release pm-changelog v2026.7.145d3a5b1Harden protected release review pathsadb8bbdMake daily releases protected-branch safeDependabot 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)Summary by cubic
Upgrade
pm-changelogto 2026.7.15 to pull in fixes for GitHub release guard timing and JSON output. Dev-only; improves reliability of changelog and release tasks with no runtime impact.Written for commit eb82e4c. Summary will update on new commits.