Skip to content

chore(main): release 1.8.1 - #120

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

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

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.8.1 (2026-09-29)

Bug Fixes

  • release: include publication helper in recovery checkout (#123) (2a7b2dc)
  • release: recover assetless v1.8.0 release (#121) (bdf930f)

This PR was generated with Release Please. See documentation.

@github-actions github-actions Bot changed the title chore(main): release 1.9.0 chore(main): release 1.8.1 Sep 29, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--altertable-cli branch from 99d6f11 to 7c76876 Compare September 29, 2026 16:07
@albert20260301

Copy link
Copy Markdown
Contributor

Holding approval: the v1.8.0 recovery workflow reached asset upload but failed resolving @/lib/object.ts from .release-orchestration/cli/scripts/publish-release.ts, so npm publication never ran. I opened #122 with the run link and remediation details. Please fix and validate that path before merging this generated release PR; otherwise v1.8.1 will reproduce the failed publish step.

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--altertable-cli branch from 7c76876 to 6b827ed Compare September 29, 2026 17:05

@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 recovery import-resolution fix from #123 is included, carries an isolated sparse-checkout regression test, and all required validation is green. Approved the generated 1.8.1 release metadata; publishing still requires a maintainer merge or an explicit validated v1.8.0 recovery dispatch.

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.

1 participant