Skip to content

chore: release v0.78.0 - #155

Merged
francoischalifour merged 2 commits into
mainfrom
release-please--branches--main--components--data-app
Nov 19, 2026
Merged

francoischalifour merged 2 commits into
mainfrom
release-please--branches--main--components--data-app

Conversation

@altertable-release

@altertable-release altertable-release Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.78.0 (2026-11-19)

⚠ BREAKING CHANGES

  • apps: unify local setup with shared app declarations (#159)
  • run embedded page actions from the host (#151)

Features

  • improve data app starters and chart exploration (#162) (c57a557)
  • run embedded page actions from the host (#151) (8e496b8)
  • show horizontal grids by default on Cartesian charts (#157) (bfd12a7)

Bug Fixes

  • correct comparison math, date range edge cases, and stale docs (#154) (6ec7c6b)
  • polish component states, focus rings, and alignment (#161) (202074e)
  • resolve packed manifest dependency before publication (#158) (75f57eb)
  • stacked bar tooltip inspection across sparse hourly data (#156) (e917ff0)

Code Refactoring

  • apps: unify local setup with shared app declarations (#159) (dec99a2)

This PR was generated with Release Please. See documentation.

@albert20260301

Copy link
Copy Markdown
Contributor

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. @altertable/data-app-react on npm is still 0.77.0; the fixes are merged, not yet verified as published. Human release merge/publication remains pending.

@altertable-release altertable-release Bot changed the title chore: release v0.77.1 chore: release v0.78.0 Nov 17, 2026
@altertable-release
altertable-release Bot force-pushed the release-please--branches--main--components--data-app branch 3 times, most recently from f9c6817 to 0aa7b43 Compare November 17, 2026 17:13
@albert20260301

Copy link
Copy Markdown
Contributor

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 @altertable/data-app-manifest, but several consumers do not receive its local release archive and npm tries the unpublished registry version.

Fixed in #158. I reproduced the current ETARGET locally before the patch, then passed the entire packed gate against the same unpublished 0.78.0 release, including both npm and Bun-isolated preview launchers. Main-branch static checks also pass. Human merge and fresh release-branch checks are still needed; no CI rerun or publication triggered.

@altertable-release
altertable-release Bot force-pushed the release-please--branches--main--components--data-app branch from ff0dece to a4bf966 Compare November 18, 2026 13:47
francoischalifour pushed a commit that referenced this pull request Nov 18, 2026
## 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.
@altertable-release
altertable-release Bot force-pushed the release-please--branches--main--components--data-app branch 2 times, most recently from ce3c325 to d8d58c6 Compare November 18, 2026 14:22
@albert20260301

albert20260301 commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

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 data:query/lakehouse adapter contract, and removes the server-run operation HTTP mode. Please include that breaking migration and the coordinated frontend #3005/backend #5056 rollout prerequisite in the user-facing release notes before publication. The current breaking-change entry only mentions #151. The version and internal dependency pins are consistent; publication and companion deployment remain unverified here.

Current release head e639fea8: the packed-package check passes, but required Tests (4/4) fails in apps-embedding.test.ts:369 waiting for Echo requests to become 1 (it stays 0). I built that exact release head and all three focused foreign-window/stale-session scenarios pass locally; no source regression is established by that result. Required CI is still red, so this is not an approval. No workflow rerun triggered.

@altertable-release
altertable-release Bot force-pushed the release-please--branches--main--components--data-app branch from 721ac05 to 3ca0315 Compare November 18, 2026 17:36
@altertable-release
altertable-release Bot force-pushed the release-please--branches--main--components--data-app branch from e639fea to 8df5e1a Compare November 19, 2026 10:48
@francoischalifour
francoischalifour merged commit 093bac3 into main Nov 19, 2026
13 checks passed
@francoischalifour
francoischalifour deleted the release-please--branches--main--components--data-app branch November 19, 2026 10:54
@altertable-release

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

@albert20260301

Copy link
Copy Markdown
Contributor

Verified npm publication of all seven @altertable/data-app* packages at 0.78.0. Downloaded archives match registry integrity hashes; versions, internal pins, licenses and declared export targets are present. The merged fixes from #149, #150, #151 and #154 are now in the published SDK release.

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants