Skip to content

chore(main): release 0.3.0 - #7

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--muse-code-acp
Closed

github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--muse-code-acp

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 12, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.3.0 (2026-09-12)

Features

  • close Muse ACP sessions cleanly (#4) (0aa9979)
  • forward ACP prompt content to Muse (#3) (3beeee8)
  • resume Muse ACP sessions without replay (#5) (dfc1d31)

This PR was generated with Release Please. See documentation.

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--muse-code-acp branch from 86314ab to 5f6c625 Compare September 12, 2026 08:50
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--muse-code-acp branch from 5f6c625 to df515b4 Compare September 12, 2026 08:53
@puncsky

puncsky commented Sep 12, 2026

Copy link
Copy Markdown
Member

Closing this release proposal as premature. The preceding 0.2.0 publish failed at npm upload with E404 / no permission to publish @bex-co/muse-code-acp: https://github.com/bex-co/muse-code-acp/actions/runs/34683759586 . This PR only updates the version and changelog; it does not address that publishing-access failure. Merging it now would create another release while npm delivery remains unresolved. The image, close, and resume changes are already merged and retained on main. Reopen/regenerate the release PR after the npm publishing identity/trusted-publisher configuration is repaired and verified.

@puncsky puncsky closed this Sep 12, 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.

1 participant