chore(deps-dev): bump the dependencies group with 2 updates
Merged
DE
14d ago+8+8+0123456789-8-8-0123456789
Bumps the dependencies group with 2 updates: @types/node and pm-ops.
Updates @types/node from 26.6.2 to 26.6.3
Commits
- See full diff in compare view
Updates pm-ops from 2026.9.28 to 2026.9.29
Release notes
Sourced from pm-ops's releases.
pm-ops v2026.09.29
Changelog
2026.9.29 - 2026-09-29
Fixed
- Release completeness audit fails a release it just created because the GitHub Release list lags creation (ops-eys5)
2026.9.28 - 2026-09-28
Fixed
- Hoisted broken pm-ops can bypass merge-driver install guard (ops-jzp5)
2026.9.26 - 2026-09-26
Fixed
- A publish that npm accepts late is reported as failed and the GitHub Release is skipped on bun mirror lag (ops-ssnr)
- The guarded launcher template reads a pm-ops directory without package.json as an omit-dev install and skips the merge drivers (ops-eyi8)
Other
- Certify pm CLI 2026.9.23 and adopt the guarded pm-ops merge-driver launcher (ops-me3v)
2026.9.18 - 2026-09-18
Added
- Ship canonical strict ESLint and duplication gates from pm-ops (ops-4phd)
- Ship the merge-driver install step as the canonical pm-ops/merge-driver export (ops-crgk)
Fixed
- pm CLI 2026.9.11 drops every pm-ops command, because its new core ops group collides at group level (ops-k9iv)
Other
- Certify pm CLI 2026.9.17 (ops-xz9q)
2026.9.11 - 2026-09-11
Added
- Publish the canonical lifecycle policy contract every fleet repo enforces (ops-xgdt)
Fixed
- A retroactive completeness contract induced twelve placeholder evidence fields and then locked them in (ops-utza)
... (truncated)
Changelog
Sourced from pm-ops's changelog.
2026.9.29 - 2026-09-29
Fixed
- Release completeness audit fails a release it just created because the GitHub Release list lags creation (ops-eys5)
Commits
5ea8406Release pm-ops v2026.09.2920f6060Release pm-ops v2026.09.28-102de8a5Merge pull request #130 from unbraind/fix/release-audit-confirms-new-releases...90480daTreat a by-tag release read that names another tag as unreadable, and name pm...bdc647aConfirm a release the GitHub list has not caught up with before calling it mi...- See full diff in compare view
Dependabot 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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions
Summary by cubic
Bumps dev dependencies @types/node to 26.6.3 and pm-ops to 2026.9.29. The pm-ops update fixes the release completeness audit failing a release it just created when the GitHub Release list hasn't caught up yet.