chore(main): release brepjs-verify 0.10.0#1337
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
4f143aa to
fdc23ae
Compare
Greptile SummaryRelease Please automation bumping
Confidence Score: 5/5Safe to merge — purely mechanical version bookkeeping generated by Release Please with no logic changes. All three changed files are Release Please artifacts: a manifest JSON, a changelog prepend, and a version field in No files require special attention. Important Files Changed
Reviews (10): Last reviewed commit: "chore(main): release brepjs-verify 0.10...." | Re-trigger Greptile |
fdc23ae to
881f218
Compare
881f218 to
07096b5
Compare
07096b5 to
d0ecfa8
Compare
d0ecfa8 to
1af3996
Compare
1af3996 to
a7aaf84
Compare
a7aaf84 to
45a97e7
Compare
45a97e7 to
8cf4f34
Compare
8cf4f34 to
cc59c2b
Compare
cc59c2b to
82fc8c6
Compare
#1350) ## Why The Vercel preview deploy for the `brepjs-verify` release-please PR (e.g. #1337) only ever fails — the docs/playground site doesn't depend on the (unpublished) `brepjs-verify` package, so building a site preview for its release is pointless and just adds a red check. ## What Adds a Vercel **Ignored Build Step** (`ignoreCommand` in `vercel.json`): ```sh case "$VERCEL_GIT_COMMIT_REF" in *components--brepjs-verify) exit 0 ;; *) exit 1 ;; esac ``` Vercel skips the deploy when the command exits 0 and proceeds when it exits 1, so this skips previews on any release-please branch for the `brepjs-verify` component and builds normally for every other branch. Takes effect once release-please next regenerates its branch from `main` (it rebases on merge), so future `brepjs-verify` releases won't trigger a failing preview. Easily extended to other package-only release components by adding more patterns to the `case`.
5e08cd7 to
6560cfb
Compare
ade0658 to
f34bf01
Compare
f34bf01 to
bb3a48c
Compare
🤖 I have created a release beep boop
0.10.0 (2026-06-14)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.