Repository navigation
chore: release v0.78.0 - #155
francoischalifour merged 2 commits into
Conversation
|
Reviewed db93d7f: the 20-file diff is release metadata only. All seven package versions, internal dependency pins, lockfile entries, manifest and versioned starter links consistently advance to 0.77.1; the changelog points to merged #154. The merged source matches the reviewed #154 tree and its main checks pass. No checks are reported on this release branch, so I have not approved it. |
f9c6817 to
0aa7b43
Compare
|
The current 0.78.0 release is blocked by the packed-consumer setup, not a missing publication that should be retried: the Bun adapter now depends on Fixed in #158. I reproduced the current |
ff0dece to
a4bf966
Compare
## Fix Keep the Bun adapter's new manifest dependency on this release's packed archive in the copied starter, Bun-only consumer and both preview installations. The isolated Bun install also pins that archive through its override. This fixes the packed gate blocking #155. It changes verification tooling only, not the published dependency contract or product runtime. ## Verification - Before: reproduced #155's current `ff0dece1` failure locally: npm resolves `@altertable/data-app-manifest@0.78.0` from the registry and fails with `ETARGET` because the coordinated release is not published yet ([CI failure](https://github.com/altertable-ai/data-app/actions/runs/44134754105/job/134221349922)). - After: the complete packed-package gate passes against the same **unpublished 0.78.0 release**, including seven archives, the copied starter, exports/declarations/tree-shaking, and both npm and Bun-isolated preview launcher lifecycle checks. - Rebased the one-file fix onto current main and ran `bun run check:static` successfully with Bun 1.4.4. `git diff --check` passes. Human merge and release publication remain pending. No CI rerun or package publication was triggered.
ce3c325 to
d8d58c6
Compare
|
The packaging blocker is resolved: #158 was human-merged, and the updated release head ce3c325 passes its packed-package check. One release-note gap remains: the 0.78.0 changelog omits merged #150 entirely. That change introduces registered query IDs, changes the hosted Current release head |
721ac05 to
3ca0315
Compare
e639fea to
8df5e1a
Compare
|
🤖 Created releases: 🌻 |
|
Verified npm publication of all seven This confirms package availability, not deployment of the companion frontend #3005/backend #5056 changes; their integration remains unverified here. The previously reported #150 migration-note omission remains in the release notes (finding). |
🤖 I have created a release beep boop
0.78.0 (2026-11-19)
⚠ BREAKING CHANGES
Features
Bug Fixes
Code Refactoring
This PR was generated with Release Please. See documentation.