Release pm-github v2026.10.19

[github-actions]

Automated daily release metadata for v2026.10.19, rebuilt from current main. The release gate passed before refresh; publication and tagging wait for the protected PR.

Summary by Sourcery

Release pm-github version 2026.10.19.

Build:

• Update package metadata and lockfile to version 2026.10.19.

Chores:

• Mark the 2026.10.19 release in the changelog.

[greptile-apps]

PR author is in the excluded authors list.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This release-only PR synchronizes the pm-github version from 2026.10.16 to 2026.10.17 across runtime and package metadata, with no functional code changes.

File-Level Changes

Change	Details	Files
Bump the extension release version consistently across source metadata, package metadata, and lockfile metadata.	Update the runtime extension version to 2026.10.17. Update manifest and npm package versions to 2026.10.17. Regenerate the corresponding package-lock version entries.	index.ts manifest.json package.json package-lock.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 00f23729-d4ba-45d1-9056-35277153f191

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Approved.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

[unbraind]

Exact-head CI evidence for 8a31fe00f0257db5798ac28b1d47aa2e530f60e5 (pm-github@2026.10.17): both Node 22 and Node 26 fail at npm run changelog:check after 903/903 tests, authored-source coverage and package checks pass.

Expected: the release candidate's committed changelog agrees with the canonical generator, as required by pm-github-l1ot. Actual: both job logs show exactly this heading difference:

• committed: ## Unreleased
• generated: ## 2026.10.17 - 2026-10-17

The complete tree comparison with main 68e7b8993e1974bf0d21b49dcfd7ce1322ac5138 changes only version metadata in index.ts, manifest.json, package.json and package-lock.json; CHANGELOG.md remains identical to main. The merge brought in main's changelog while retaining this PR's release version. The canonical generator deliberately uses --release-version-from-package --date-from-version.

Impact: this exact release candidate remains CI-blocked; the earlier release-gate receipt in the PR description does not certify this merged head. This is hosted execution evidence plus exact-tree inspection, not a fresh local full-suite run or an importer regression claim. It is separate from the original l1ot status-filter mismatch, and can stay with that existing refresh work rather than a duplicate issue.

Acceptance: rebuild/refresh the candidate through the existing canonical release path, regenerate the changelog for its selected version, and require changelog:check plus both exact-head Node jobs to pass without weakening the checks. Preserve the existing protected merge/publication and separately authorized caller-adoption boundaries.