chore(master): release 1.8.2

[github-actions]

🤖 I have created a release beep boop

1.8.2 (2026-03-05)

Bug Fixes

• restore npx installs for published package (107bc14)

---

This PR was generated with Release Please. See documentation.

[github-actions]

🤖 Created releases:

• v1.8.2

🌻

[greptile-apps]

Greptile Summary

This is an automated Release Please PR bumping the package from v1.8.1 to v1.8.2, capturing the bug fix that restores npx/npm exec install support for the published package.

Changes:

• package.json: version field updated 1.8.1 → 1.8.2
• .release-please-manifest.json: manifest version updated 1.8.1 → 1.8.2
• CHANGELOG.md: new 1.8.2 entry prepended with the single bug fix entry

Issues found:

• A pre-existing ## [Unreleased] section (lines 83–135 of CHANGELOG.md) was not removed as part of this release. Its first entry ("restore npx / npm exec installs") describes the same fix being published here, creating redundancy and potential reader confusion. This should be cleaned up alongside the release.

Confidence Score: 5/5

• This PR is safe to merge — it contains only automated version bumps and a changelog entry with no logic changes.
• All three files are internally consistent (same version 1.8.2), the changes are entirely mechanical (version string updates + changelog prepend), and no source code is modified. The only minor issue is a stale [Unreleased] changelog section, which is a documentation concern and does not affect correctness or safety.
• No files require special attention — the stale [Unreleased] section in CHANGELOG.md is worth cleaning up but is not a blocker.

Important Files Changed

Filename	Overview
.release-please-manifest.json	Version bumped from 1.8.1 to 1.8.2 — consistent with package.json, no issues.
package.json	Version bumped from 1.8.1 to 1.8.2 — no other changes, consistent with manifest.
CHANGELOG.md	New 1.8.2 entry prepended correctly, but a stale [Unreleased] section (lines 83–135) containing the same npx bug fix was not cleaned up during this release.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A([Release Please bot triggers]) --> B[Bump version in package.json\n1.8.1 → 1.8.2]
    B --> C[Bump .release-please-manifest.json\n1.8.1 → 1.8.2]
    C --> D[Prepend 1.8.2 entry to CHANGELOG.md]
    D --> E{All 3 files consistent?}
    E -- Yes --> F([PR ready to merge & publish])

Loading

Comments Outside Diff (1)

1. CHANGELOG.md, line 83-135 (link)

   Stale [Unreleased] section not cleaned up

   The ## [Unreleased] section (lines 83–135) still exists in the changelog and its very first entry ("restore npx / npm exec installs") describes exactly the bug fix being shipped in this 1.8.2 release. Having this section linger after the release creates duplicate/conflicting documentation — readers may be confused about whether [Unreleased] refers to something yet to come or something already shipped.

   Consider removing (or archiving) the ## [Unreleased] block as part of this release PR so the changelog accurately reflects released vs. unreleased work.

_{Last reviewed commit: f6d4c93}