🐸 Versioned release (#98)

<a href="https://bumpy.varlock.dev"><img
src="https://raw.githubusercontent.com/dmno-dev/bumpy/main/images/frog-clipboard.png"
alt="bumpy-frog" width="60" align="left" style="image-rendering:
pixelated;" title="Hi! I'm bumpy!" /></a>

This PR was created and will be kept in sync by
[bumpy](https://bumpy.varlock.dev) based on your bump files (in
`.bumpy/`). Merge it when you are ready to release the packages listed
below:
<br clear="left" />

### <a href="https://bumpy.varlock.dev" title="Minor releases"><img
src="https://raw.githubusercontent.com/dmno-dev/bumpy/main/images/frog-minor.png"
alt="minor" width="52" style="image-rendering: pixelated;" align="right"
/></a> Minor releases

#### `@varlock/bumpy` 1.12.0 → **1.13.0**
<sub>[CHANGELOG.md](https://github.com/dmno-dev/bumpy/pull/98/changes#diff-4172fac00a078eb9cef75fbac6f1df8320cd5bf3d45ed733e055f7567d8d0e29)</sub>

- Recommend `pull_request_target` for the `bumpy ci check` workflow so
fork PRs receive release-plan comments. Previously, fork PRs running
under `pull_request` got a read-only token, so the check would fail red
with no helpful comment — a bad first impression for OSS projects.
`bumpy ci check` now recognizes the `pull_request_target` event when
reading the PR number from `GITHUB_EVENT_PATH`, and emits a clearer
warning that links to the new docs when comment posting fails on a fork
PR. See the updated [GitHub Actions
docs](https://bumpy.varlock.dev/docs/github-actions) for the new
workflow (the version is resolved from the base branch's `package.json`,
so no version pinning duplication). ([bump
file](https://github.com/dmno-dev/bumpy/pull/98/changes#diff-df977e016f2253821894c8863fbd475c20ddc616ad6afaef181d7f317fdd06d2))

Co-authored-by: bumpy-bot <276066384+bumpy-bot@users.noreply.github.com>

Author: bumpy-bot

.bumpy/pull-request-target-check-workflow.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 1.13.0
+
+<sub>2026-06-03</sub>
+
+- [#97](https://github.com/dmno-dev/bumpy/pull/97) _(minor)_ - Recommend `pull_request_target` for the `bumpy ci check` workflow so fork PRs receive release-plan comments. Previously, fork PRs running under `pull_request` got a read-only token, so the check would fail red with no helpful comment — a bad first impression for OSS projects. `bumpy ci check` now recognizes the `pull_request_target` event when reading the PR number from `GITHUB_EVENT_PATH`, and emits a clearer warning that links to the new docs when comment posting fails on a fork PR. See the updated [GitHub Actions docs](https://bumpy.varlock.dev/docs/github-actions) for the new workflow (the version is resolved from the base branch's `package.json`, so no version pinning duplication).
+
 ## 1.12.0
 
 <sub>2026-06-03</sub>

packages/bumpy/CHANGELOG.md

@@ -1,6 +1,6 @@
 {
   "name": "@varlock/bumpy",
-  "version": "1.12.0",
+  "version": "1.13.0",
   "description": "Modern monorepo versioning and changelog tool",
   "keywords": [
     "bump",