Skip to content

chore(deps-dev): bump pm-ops from 2026.8.8 to 2026.8.10 - #37

Merged
unbraind merged 1 commit into
mainfrom
dependabot/npm_and_yarn/pm-ops-2026.8.10
Aug 15, 2026
Merged

chore(deps-dev): bump pm-ops from 2026.8.8 to 2026.8.10#37
unbraind merged 1 commit into
mainfrom
dependabot/npm_and_yarn/pm-ops-2026.8.10

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps pm-ops from 2026.8.8 to 2026.8.10.

Release notes

Sourced from pm-ops's releases.

pm-ops v2026.08.10

Changelog

2026.8.10 - 2026-08-10

Fixed

  • The docstring gate scanned installed extension artifacts, so it disagreed with itself across machines (ops-x8fk)

2026.8.8 - 2026-08-08

Added

  • Adopt pm CLI 2026.8.7 merge fences and release tooling (ops-8wyb)
  • Raise pm-ops enforced source coverage to 100/100/100/100 (ops-q6ki)

2026.8.7 - 2026-08-07

Fixed

  • Gate durable PM project health in CI on pm CLI 2026.8.6 (ops-54ed)

Other

  • Clear author-attribution health warning for _workspace history event (ops-whzj)

2026.8.5 - 2026-08-05

Other

  • Declare renderer ownership so the host enforces scoping the package only applied at runtime (ops-rozk)

2026.8.4 - 2026-08-04

Other

  • Resolve pm-changelog to the release that derives release dates in UTC (ops-70qk)

2026.8.1 - 2026-08-01

Added

  • Docstring coverage gate: a lexer-backed, fail-closed documentation gate the fleet can share (ops-073p)

Fixed

  • Brace-ending initializers consume following ASI declarations and members (ops-cqyv)
  • Prevent symlink cycles during docstring source traversal (ops-hkxb)
  • Semicolon-free exported variables consume following declarations (ops-aun4)
  • Sanitize Node test-runner context before release verification (ops-hq5u)

... (truncated)

Changelog

Sourced from pm-ops's changelog.

2026.8.10 - 2026-08-10

Fixed

  • The docstring gate scanned installed extension artifacts, so it disagreed with itself across machines (ops-x8fk)
Commits
  • 94e0bf6 Fix release publish-before-protected-main-push ordering (#43)
  • b5ee156 Reconcile the manifest with the 2026.8.10 already published to npm (#42)
  • f23f06b fix(test): make the throughput fixtures relative so the gate stops measuring ...
  • 25b700f fix(docstrings): never scan installed extension artifacts under .agents (#40)
  • See full diff in compare view

@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-ops 2026.8.8 → 2026.8.10 bump: it is a genuine update versus main's lock (currently 2026.8.8), 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 like a clean path forward. One note worth surfacing given the standing rule on clone-local CI state: the primary fix in this bump (ops-x8fk) is precisely the kind of problem that rule targets — the docstring gate was scanning installed artifacts under .agents, which are clone-local, making its results machine-dependent. The 2026.8.10 fix excludes those paths, so the gate should now be stable on a fresh runner checkout. Your plan of running npm ci + npm run release:check on a clean runner is the right validation step to confirm the fix holds in CI before merging.

@unbraind

unbraind commented Aug 15, 2026

Copy link
Copy Markdown
Owner

@dependabot rebase

Rebase needed for the same reason as #39: this branch is based on 36e66f63, predating main's release commit 0f65909 (v2026.08.15) and 11062c1 (#42), so changelog:check fails only because the committed ## Unreleased heading predates the release that re-titled it. Bumping pm-ops resolves pm-changelog to 2026.8.9 transitively in the lock, which is expected and fine; the gate failure is the stale base alone. Will re-run gates on the rebased branch and merge when green.

@dependabot
chore(deps-dev): bump pm-ops from 2026.8.8 to 2026.8.10
2651bf7 
Bumps [pm-ops](https://github.com/unbraind/pm-ops) from 2026.8.8 to 2026.8.10.
- [Release notes](https://github.com/unbraind/pm-ops/releases)
- [Changelog](https://github.com/unbraind/pm-ops/blob/main/CHANGELOG.md)
- [Commits](unbraind/pm-ops@v2026.08.08...v2026.08.10)

---
updated-dependencies:
- dependency-name: pm-ops
  dependency-version: 2026.8.10
  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-ops-2026.8.10 branch from adf5b04 to 2651bf7 Compare August 15, 2026 15:27
@unbraind
unbraind merged commit da77b35 into main Aug 15, 2026
5 checks passed
@unbraind
unbraind deleted the dependabot/npm_and_yarn/pm-ops-2026.8.10 branch August 15, 2026 15:47
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