Skip to content

chore(deps-dev): bump pm-changelog from 2026.8.6 to 2026.8.12 - #39

Merged
unbraind merged 2 commits into
mainfrom
dependabot/npm_and_yarn/pm-changelog-2026.8.9
Aug 15, 2026
Merged

chore(deps-dev): bump pm-changelog from 2026.8.6 to 2026.8.12#39
unbraind merged 2 commits into
mainfrom
dependabot/npm_and_yarn/pm-changelog-2026.8.9

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 14, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps pm-changelog from 2026.8.6 to 2026.8.12.

Release notes

Sourced from pm-changelog's releases.

pm-changelog v2026.8.12

2026.8.12 - 2026-08-12

Fixed

  • Classifier misroutes Issues with CLI command-name titles (update/change) to Changed not Fixed (pmc-874d)

Other

  • Prove classifier precedence across every weak title signal (pmc-hscf)
  • Adopt pm-cli 2026.8.11 for current history verification (pmc-ypbc)

pm-changelog v2026.8.9

2026.8.9 - 2026-08-10

Fixed

  • Node 22 exact branch coverage is nondeterministic across identical CI reruns (pmc-v18w)
  • Repository-local pm 2026.8.6 prepare removes the 2026.8.7 extension merge fence (pmc-rdc3)
  • Propagate the docstring gate entry guard fix (pmc-g5f7)
  • changelog:check verified in prepend mode against a replace-mode CHANGELOG, making the gate unsatisfiable (pmc-s2bk)
  • The release merge-wait read branch protection which the workflow token can never read (pmc-o58h)
  • Retire the vendored docstring gate for the canonical pm-ops analyzer (pmc-j0dx)
  • Self-referential release-context test freezes the package version the release bump mutates (pmc-iygx)
  • Node-CLI acceptance test assumes pmc-or-pm item prefixes and leaks the invoking PM tracker (pmc-femy)

Other

  • Cover pm-changelog cli.ts and extension.ts to reach the 100/100/100 aggregate (pmc-p5l1)

pm-changelog v2026.8.7

2026.8.7 - 2026-08-07

Other

  • Gate CI on strict tracked pm project health (pmc-vm22)
Changelog

Sourced from pm-changelog's changelog.

2026.8.12 - 2026-08-12

Fixed

  • Classifier misroutes Issues with CLI command-name titles (update/change) to Changed not Fixed (pmc-874d)

Other

  • Prove classifier precedence across every weak title signal (pmc-hscf)
  • Adopt pm-cli 2026.8.11 for current history verification (pmc-ypbc)

2026.8.9 - 2026-08-10

Fixed

  • Node 22 exact branch coverage is nondeterministic across identical CI reruns (pmc-v18w)
  • Repository-local pm 2026.8.6 prepare removes the 2026.8.7 extension merge fence (pmc-rdc3)
  • Propagate the docstring gate entry guard fix (pmc-g5f7)
  • changelog:check verified in prepend mode against a replace-mode CHANGELOG, making the gate unsatisfiable (pmc-s2bk)
  • The release merge-wait read branch protection which the workflow token can never read (pmc-o58h)
  • Retire the vendored docstring gate for the canonical pm-ops analyzer (pmc-j0dx)
  • Self-referential release-context test freezes the package version the release bump mutates (pmc-iygx)
  • Node-CLI acceptance test assumes pmc-or-pm item prefixes and leaks the invoking PM tracker (pmc-femy)

Other

  • Cover pm-changelog cli.ts and extension.ts to reach the 100/100/100 aggregate (pmc-p5l1)

2026.8.7 - 2026-08-07

Other

  • Gate CI on strict tracked pm project health (pmc-vm22)

2026.8.4 - 2026-08-04

Fixed

  • Handle SDK CompletionTimestampResolution unresolved arm and upgrade pm-cli pin to 2026.8.3 (pmc-5hho)

2026.8.3 - 2026-08-03

Added

  • Docstring coverage gate: a parser-backed, self-scanning mandatory check (pmc-kdm1)

Fixed

  • sync-version could silently restamp the wrong version literal during a release (pmc-vbft)

... (truncated)

Commits
  • 9d272d4 Release pm-changelog v2026.8.12
  • 55c4201 Keep ambiguous Issue titles out of Added and Changed (#138)
  • fb16325 Harden release merge wait against mergeStateStatus deadlock (#137)
  • 9888ddc Propagate the docstring gate entry guard fix so an unresolvable entry cannot ...
  • 7314c41 Release pm-changelog v2026.8.9 (#133)
  • 8263ed5 Close the release merge-wait item, now that the fix has shipped (#135)
  • bc98fda Wait for required checks before merging the release PR, so the daily release ...
  • fcc2875 fix(pm): correct two release identifiers that blocked the 2026.8.9 release
  • 918ffc9 Release pm-changelog v2026.8.9
  • 4bcf99b Retire the vendored docstring gate for the canonical pm-ops analyzer, which f...
  • Additional commits viewable in compare view
Install script changes

This version modifies prepare script that runs during installation. Review the package contents before updating.

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 14, 2026
@greptile-apps

greptile-apps Bot commented Aug 14, 2026

Copy link
Copy Markdown

PR author is in the excluded authors list.

@unbraind

unbraind commented Aug 15, 2026

Copy link
Copy Markdown
Owner

@greptile-apps — 👍 on the status note: Greptile is configured to exclude Dependabot-authored PRs, so this PR carries no Greptile findings and there is nothing advisory to triage from your side. My disposition for this pm-changelog 2026.8.6 → 2026.8.9 bump: it is a genuine update versus main's lock (currently 2026.8.6), so I am running this repo's own gates (npm ci + npm run release:check) on the branch and will squash-merge it if they are green, per the fleet's normal Dependabot procedure.

@greptile-apps

greptile-apps Bot commented Aug 15, 2026

Copy link
Copy Markdown

Sounds good — npm ci + npm run release:check on the branch is the right gate for a tooling-only bump like this. Nothing to flag on my end; proceed when green.

@unbraind

unbraind commented Aug 15, 2026

Copy link
Copy Markdown
Owner

@dependabot rebase

Rebase needed: this branch is based on 36e66f63, which predates main's 0f65909 (Release pm-github v2026.08.15, CHANGELOG regenerated with the new 2026.8.15 heading) and 11062c1 (#42). The local release:check gate fails changelog:check purely from that stale base — the committed ## Unreleased heading vs today's date-derived ## 2026.8.15 heading — with a one-line generated diff that main's release commit already reconciled. Regenerating the changelog on the stale base instead would duplicate what the release machinery already did, so rebase is the correct fix. I'll re-run the gates on the rebased branch and merge when green.

@unbraind unbraind mentioned this pull request Aug 15, 2026
Merged
@dependabot dependabot Bot changed the title chore(deps-dev): bump pm-changelog from 2026.8.6 to 2026.8.9 chore(deps-dev): bump pm-changelog from 2026.8.6 to 2026.8.12 Aug 15, 2026
@dependabot
chore(deps-dev): bump pm-changelog from 2026.8.6 to 2026.8.12
9204027 
Bumps [pm-changelog](https://github.com/unbraind/pm-changelog) from 2026.8.6 to 2026.8.12.
- [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.8.6...v2026.8.12)

---
updated-dependencies:
- dependency-name: pm-changelog
  dependency-version: 2026.8.9
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/pm-changelog-2026.8.9 branch from a41fe93 to 9204027 Compare August 15, 2026 15:27
pi-agent
chore(deps): regenerate CHANGELOG.md with pm-changelog 2026.8.9
b3a407d 
pm-changelog 2026.8.9 classifies pm-github-px45 (CHANGELOG omissions and
mislabelled Unreleased work) under Fixed instead of Added, which is the more
accurate section for that item. This regenerates CHANGELOG.md with the bumped
generator so changelog:check passes; content change is that one entry move.
@unbraind

unbraind commented Aug 15, 2026

Copy link
Copy Markdown
Owner

Follow-up after the rebase: Dependabot refreshed this PR's target to pm-changelog 2026.8.6 → 2026.8.12 (lockfile-only; the ^2026.8.6 manifest range already admits it), superseding the 2026.8.9 references in my earlier comments above.

The rebased branch then failed changelog:check because pm-changelog 2026.8.12 classifies the historical item pm-github-px45 under Fixed instead of Added — a generator improvement (that item describes fixing CHANGELOG omissions/mislabelling, so Fixed is the more accurate section). Fix applied on this branch per the fleet procedure: committed b3a407d regenerates CHANGELOG.md with the bumped generator; the content change is exactly that one entry moving sections (verified: 1 insertion, 1 deletion). Full npm ci + release:check (typecheck, build, docstring, coverage, prod audit, pack dry-run, changelog check) passes locally with the regenerated file. One correction to that commit message: it says 'with pm-changelog 2026.8.9' — the generator actually in effect is 2026.8.12 (the version this PR now installs); the verified diff is identical either way. Not amending the pushed commit to avoid history rewrite; this comment is the authoritative correction.

Reviews re-triggered by this push: Greptile reviews new pushes automatically (though Dependabot-authored PRs are excluded by its config, per its status notice above), Sourcery remains rate-limited this week, semgrep/CI re-run on push. Will merge once CI is green.

@unbraind
unbraind merged commit 8fea71e into main Aug 15, 2026
4 checks passed
@unbraind
unbraind deleted the dependabot/npm_and_yarn/pm-changelog-2026.8.9 branch August 15, 2026 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@unbraind