Skip to content

chore(main): release 0.2.0#544

Open
github-actions[bot] wants to merge 1 commit intomainfrom
release-please--branches--main--components--expert
Open

chore(main): release 0.2.0#544
github-actions[bot] wants to merge 1 commit intomainfrom
release-please--branches--main--components--expert

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions bot commented Apr 2, 2026

🤖 I have created a release beep boop

0.2.0 (2026-04-10)

Features

  • expert: allow setting file log level via configuration (#563) (eeb6628), closes #541

Bug Fixes

  • don't connect to the epmd daemon (#553) (292ed7a)
  • engine: stop double applying alias suffix when prefix is aliased (#545) (9de53c2)
  • engine: unify import lookup to correctly resolve local calls (#547) (728b76e)
  • expert: add no-op handler for $/setTrace (#564) (4f425a2)
  • handle LSP supported invalid configuration values (#551) (e973cfc)
  • hang at startup if .bashrc contains exec call (#527) (73b8d28)

This PR was generated with Release Please. See documentation.

@github-actions github-actions bot force-pushed the release-please--branches--main--components--expert branch 5 times, most recently from 7217d06 to 4460912 Compare April 9, 2026 21:28
@github-actions github-actions bot changed the title chore(main): release 0.1.1 chore(main): release 0.2.0 Apr 10, 2026
@github-actions github-actions bot force-pushed the release-please--branches--main--components--expert branch from 4460912 to f62b8ab Compare April 10, 2026 09:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

Production release logging is too verbose

0 participants