Skip to content

Prepare 1.3.0 for release#88

Open
onelxj wants to merge 4 commits into
mainfrom
onelxj.release_1_3_0
Open

Prepare 1.3.0 for release#88
onelxj wants to merge 4 commits into
mainfrom
onelxj.release_1_3_0

Conversation

@onelxj

@onelxj onelxj commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Also contains a small fix, check a separate commit.

@aviator-app

aviator-app Bot commented Jul 13, 2026

Copy link
Copy Markdown

Current Aviator status

Aviator will automatically update this comment as the status of the PR changes.
Comment /aviator refresh to force Aviator to re-examine your PR (or learn about other /aviator commands).

This pull request is currently open (not queued).

How to merge

To merge this PR, comment /aviator merge or add the mergequeue-ready label.


See the real-time status of this PR on the Aviator webapp.
Use the Aviator Chrome Extension to see the status of your PR within GitHub.

@onelxj onelxj requested review from benh, rileysdev and rjhuijsman July 13, 2026 23:50
@onelxj onelxj self-assigned this Jul 13, 2026
onelxj and others added 3 commits July 14, 2026 13:01
The frontend type-check tests for the bank-pydantic and kcdc-2025
examples overlaid the locally built @reboot-dev/reboot{,-api,-web,
-react} tarballs but resolved the @reboot-dev/reboot-std{,-api,-react}
packages from the npm registry. That only works when the version the
example pins is already published, so the tests break during release
preparation, when every pin points at the not-yet-published next
version. Overlay the std packages the same way bank-zod already does.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
… tests

bank-pydantic's frontend/package.json declares mobile as an npm
workspace, so an npm install run in frontend/mobile resolves the whole
workspace, including the web frontend's registry pins. Those pins are
resolved before the locally built tarballs given on the command line
are placed in the tree, so npm contacts the registry for them and the
install breaks during release preparation, when every pin points at
the not-yet-published next version.

Run the overlay install at the workspace root instead: command-line
specs there replace the root package.json pins outright, and the
mobile workspace member's pins then dedupe against the tarball
versions already placed in the tree. Also overlay the std packages,
which the web frontend (now part of the same install) depends on.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@onelxj onelxj force-pushed the onelxj.release_1_3_0 branch from 81d420b to a858392 Compare July 14, 2026 13:40
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