Skip to content

Release pm-github v2026.11.01 - #207

Merged
github-actions[bot] merged 1 commit into
mainfrom
release/2026.11.01
Nov 1, 2026
Merged

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

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 1, 2026 •

Copy link
Copy Markdown
Contributor

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

Summary by Sourcery

Enhancements:

  • Update pm-github release metadata to version 2026.11.1 across the changelog and package manifests.

@greptile-apps

greptile-apps Bot commented Nov 1, 2026

Copy link
Copy Markdown

PR author is in the excluded authors list.

@sourcery-ai

sourcery-ai Bot commented Nov 1, 2026 •

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

Reviewer's Guide

This release-only PR updates pm-github from 2026.10.31 to 2026.11.1 across the changelog, runtime extension metadata, and npm package manifests; no functional code changes are included.

File-Level Changes

Change Details Files
Bump the extension release version consistently across source metadata and package manifests.
  • Update the changelog release heading and date.
  • Set the new version in the extension definition, manifest, and package metadata.
  • Regenerate the lockfile version metadata.
CHANGELOG.md
index.ts
manifest.json
package-lock.json
package.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

@coderabbitai

coderabbitai Bot commented Nov 1, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

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

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 99ddeb1d-2932-4583-81ce-2bc29a3f4e24

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

@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 found 1 issue

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="package.json" line_range="3" />
<code_context>
 {
   "name": "pm-github",
-  "version": "2026.10.31",
+  "version": "2026.11.1",
   "description": "GitHub Issues + Projects v2 integration. Imports issues as pm items (`pm github import`), exports pm items as GitHub issues, syncs issue state, and bidirectionally syncs pm items with a GitHub Projects v2 board (`pm github project import/sync/list/fields`) — mapping pm status to the board Status column with idempotent, no-data-loss provenance.",
   "author": "@unbraind",
</code_context>
<issue_to_address>
**Release workflows reject the package version**

When the release tag is `v2026.11.01`, the closeout and sync workflows derive `2026.11.01` from the tag and compare it literally with the installed package version, `2026.11.1`; validation fails and callers cannot complete either workflow.

Make the package version match the version derived from the release tag, or normalize the versions before comparing them.
</issue_to_address>

Sourcery assessment

Approval pending. 1 finding to address first.

Blocking findings: package.json:3


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

Comment thread package.json Resolved
@github-actions
github-actions Bot merged commit 282dbd6 into main Nov 1, 2026
11 checks passed
@github-actions
github-actions Bot deleted the release/2026.11.01 branch November 1, 2026 17:07
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.

1 participant