Skip to content

chore(main): release 1.10.0 - #128

Merged
utay merged 2 commits into
mainfrom
release-please--branches--main--components--altertable-cli
Oct 8, 2026
Merged

chore(main): release 1.10.0#128
utay merged 2 commits into
mainfrom
release-please--branches--main--components--altertable-cli

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 2, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.10.0 (2026-10-08)

Features

  • data-app: add commands to validate, publish, and update data apps from files (#131) (439444b)

Bug Fixes

  • data-app: upgrade CLI starter and fixtures to v0.66.0 (#130) (503ed70)

This PR was generated with Release Please. See documentation.

albert20260301
albert20260301 suggested changes Oct 2, 2026
View reviewed changes

@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.1 tag is published and v1.9.1...main has zero commits, but this PR proposes v1.10.0 and replays the historical changelog. Merging it would publish an incorrect release.

@francoischalifour please repair or suppress the Release Please state and regenerate only when there is at least one commit after v1.9.1. The previous correction to v1.9.1 did not prevent this successor PR from being created.

@github-actions github-actions Bot changed the title chore(main): release 1.10.0 chore(main): release 1.9.2 Oct 8, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--altertable-cli branch from 0415a3a to 286b642 Compare October 8, 2026 08:41
@github-actions github-actions Bot changed the title chore(main): release 1.9.2 chore(main): release 1.10.0 Oct 8, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--altertable-cli branch from 286b642 to ec6e3ac Compare October 8, 2026 13:18
@utay
utay enabled auto-merge (squash) October 8, 2026 13:30
@albert20260301

albert20260301 commented Oct 8, 2026

Copy link
Copy Markdown
Contributor

The v1.10.0 release branch fails one pre-existing help-output assertion solely because v1.10.0 makes the banner wrap between “from” and “the terminal.” I opened #133 with a test-only normalized-whitespace assertion; bun test src/lib/usage.test.ts and git diff --check pass.

@utay could you review and merge or incorporate #133, then rerun the release checks?

@utay utay mentioned this pull request Oct 8, 2026
Closed
@albert20260301
test(usage): allow wrapped version banner (#133)
947af53 
## Summary

Makes the help-banner assertion compare normalized whitespace, so it
verifies the complete versioned sentence whether the terminal renderer
wraps it or not.

## Impact

This is a test-only correction for the release branch. It restores
release verification for multi-digit version components without changing
CLI behavior or help rendering.

## Verification

- `bun test src/lib/usage.test.ts`
- `git diff --check`
@utay
utay merged commit 7e11731 into main Oct 8, 2026
12 checks passed
@utay
utay deleted the release-please--branches--main--components--altertable-cli branch October 8, 2026 14:46
@github-actions

github-actions Bot commented Oct 8, 2026

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

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

Reviewers

@utay utay utay approved these changes
+1 more reviewer
@albert20260301 albert20260301 albert20260301 approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

autorelease: tagged

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@albert20260301 @utay