Skip to content

Release pm-github v2026.08.18 - #47

Merged
github-actions[bot] merged 1 commit into
mainfrom
release/2026.08.18
Aug 18, 2026
Merged

github-actions[bot] merged 1 commit into
mainfrom
release/2026.08.18

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 18, 2026 •

Copy link
Copy Markdown
Contributor

Automated daily release metadata for v2026.08.18. The release gate passed before this PR was created; npm publication and tagging remain blocked until this protected PR is merged.

Summary by Sourcery

Chores:

  • Update release metadata and changelog for the 2026.8.18 release.

Summary by cubic

Bumps pm-github from v2026.8.17 to v2026.8.18 and advances the changelog to the new release. No runtime changes; merging unblocks npm publication and tagging for this release.

  • Verify the version is 2026.8.18 in index export, manifest.json, package.json, and package-lock.json.

  • Confirm CHANGELOG.md now has “2026.8.18 - 2026-08-18”.

  • Upon merge, proceed with npm publish and tag creation; no config or data migrations required.

Written for commit 060847e. Summary will update on new commits.

Review in cubic

@greptile-apps

greptile-apps Bot commented Aug 18, 2026

Copy link
Copy Markdown

PR author is in the excluded authors list.

@sourcery-ai

sourcery-ai Bot commented Aug 18, 2026 •

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Daily release prep for pm-github v2026.8.18: promote changelog entry from Unreleased to a dated release and consistently bump the extension/package version from 2026.8.17 to 2026.8.18 across source and metadata files.

Flow diagram for pm-github version bump to 2026.8.18

flowchart TD
  Release_start[Daily release prep]
  Changelog_unreleased[CHANGELOG.md section Unreleased]
  Changelog_released[CHANGELOG.md section 2026.8.18 - 2026-08-18]

  Version_old[index.ts, manifest.json, package.json version 2026.8.17]
  Version_new[index.ts, manifest.json, package.json version 2026.8.18]

  Release_start --> Changelog_unreleased
  Changelog_unreleased --> Changelog_released

  Release_start --> Version_old
  Version_old --> Version_new

  Version_new --> Release_complete[Release metadata ready for npm publication and tagging]
Loading

File-Level Changes

Change Details Files
Promote the changelog from an Unreleased section to a dated 2026.8.18 release entry.
  • Rename the top-level changelog section header from Unreleased to 2026.8.18 - 2026-08-18
  • Keep existing Fixed subsection content under the new dated release header
CHANGELOG.md
Bump the pm-github extension runtime version to 2026.8.18.
  • Update the exported extension definition version string from 2026.8.17 to 2026.8.18
index.ts
Align manifest and npm metadata versions with the new 2026.8.18 release.
  • Update manifest.json version field from 2026.8.17 to 2026.8.18
  • Update package.json version field from 2026.8.17 to 2026.8.18
  • Regenerate or update package-lock.json to reflect the 2026.8.18 version (diff not shown)
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

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@github-actions
github-actions Bot merged commit 92b9a00 into main Aug 18, 2026
4 checks passed
@github-actions
github-actions Bot deleted the release/2026.08.18 branch August 18, 2026 04:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants