Skip to content

chore(main): release 1.9.1 - #126

Open
github-actions[bot] wants to merge 3 commits into
mainfrom
release-please--branches--main--components--altertable-cli
Open

github-actions[bot] wants to merge 3 commits into
mainfrom
release-please--branches--main--components--altertable-cli

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 1, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.9.1 (2026-10-02)

Changed

  • Update generated and upgraded data apps to @altertable/data-app 0.65.0.

This PR was generated with Release Please. See documentation.

Verification: ./scripts/verify.sh --quick passed (763 unit tests and 79 black-box tests).

@albert20260301 albert20260301 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The v1.9.0 tag already points to the merged release commit and is published on npm, but this generated v1.10.0 PR has no commits newer than that tag. Its changelog repeats the historical features and fixes that were released before v1.9.0, so merging it would publish an incorrect minor release.

@francoischalifour please investigate the Release Please state and regenerate it only from commits after v1.9.0 (or suppress the PR if there are none).

# Conflicts:
#	CHANGELOG.md
The previous proposal repeated changes already shipped in v1.9.0. Release v1.9.1 instead, containing only the generated and upgraded data-app runtime update merged in #127.
@francoischalifour francoischalifour changed the title chore(main): release 1.10.0 chore(main): release 1.9.1 Oct 2, 2026
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