Skip to content

chore(master): release 1.9.0#66

Merged
PatrickSys merged 1 commit intomasterfrom
release-please--branches--master--components--codebase-context
Mar 19, 2026
Merged

chore(master): release 1.9.0#66
PatrickSys merged 1 commit intomasterfrom
release-please--branches--master--components--codebase-context

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Mar 7, 2026

🤖 I have created a release beep boop

1.9.0 (2026-03-19)

Features

  • add workspace-aware multi-project routing (#67) (edb1350)

Bug Fixes

  • make exclude patterns recursive to prevent index pollution (#76) (a814b24)
  • prevent orphaned processes via stdin/ppid/onclose lifecycle guards (#77) (0b49d7a)
  • route MCP requests per project root (#65) (b0c2d04)

This PR was generated with Release Please. See documentation.

@greptile-apps
Copy link

greptile-apps bot commented Mar 7, 2026

Greptile Summary

This is an automated release PR generated by Release Please, bumping the package version from 1.8.2 to 1.8.3 to capture the MCP request routing bug fix landed in PR #65.

  • .release-please-manifest.json — version field updated from "1.8.2" to "1.8.3"
  • package.jsonversion field updated from "1.8.2" to "1.8.3"
  • CHANGELOG.md — new 1.8.3 section prepended, documenting the bug fix: route MCP requests per project root

All three changes are consistent and correct. No logic or configuration changes are introduced by this PR.

Confidence Score: 5/5

  • This PR is safe to merge — it is a purely automated version-bump and changelog update with no logic changes.
  • All three changed files are generated/automated artifacts (manifest, changelog, package version). The version is consistently bumped to 1.8.3 across all files, and the changelog entry correctly references the underlying bug-fix commit. There is no application logic at risk.
  • No files require special attention.

Important Files Changed

Filename Overview
.release-please-manifest.json Version bumped from "1.8.2" to "1.8.3" — standard Release Please manifest update, no issues.
CHANGELOG.md New 1.8.3 changelog entry added referencing the MCP request routing bug fix in PR #65; correctly formatted and prepended to the existing log.
package.json Package version field bumped from "1.8.2" to "1.8.3" to match the new release — no other changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR #65 merged\nroute MCP requests per project root] --> B[Release Please bot\ndetects fix commit]
    B --> C[Creates Release PR #66]
    C --> D1[.release-please-manifest.json\n1.8.2 → 1.8.3]
    C --> D2[package.json\nversion 1.8.2 → 1.8.3]
    C --> D3[CHANGELOG.md\nNew 1.8.3 section added]
    D1 & D2 & D3 --> E[Merge PR #66\npublish v1.8.3]
Loading

Last reviewed commit: 22573f4

@github-actions github-actions bot changed the title chore(master): release 1.8.3 chore(master): release 1.9.0 Mar 11, 2026
@github-actions github-actions bot force-pushed the release-please--branches--master--components--codebase-context branch from 22573f4 to d1d1162 Compare March 11, 2026 21:41
@github-actions github-actions bot force-pushed the release-please--branches--master--components--codebase-context branch from d1d1162 to 16a5dec Compare March 18, 2026 22:06
@github-actions github-actions bot force-pushed the release-please--branches--master--components--codebase-context branch from 16a5dec to ca6d4ca Compare March 19, 2026 22:09
@PatrickSys PatrickSys merged commit 260c61d into master Mar 19, 2026
1 check passed
@github-actions
Copy link
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant