Skip to content

chore(main): release 0.2.0#2

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

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

Conversation

@github-actions
Copy link
Copy Markdown

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

🤖 I have created a release beep boop

0.2.0 (2026-04-10)

🚀 Features

  • chat: add repository best practices (62fb7e7)
  • chat: extract chat system from oxidized-protocol (90ad318)
  • ci: add dev publish workflow (b639e32)

🐛 Bug Fixes

  • chat: remove [patch] section that breaks CI (d97b6f8)
  • chat: switch deps to crates.io versions with local patches (49385d9)
  • ci: add permissions to release-please caller (86c42ab)
  • ci: chain publish into release-please workflow (55c5128)
  • deny: use allow-org for git source allowlist (1da2cd5)
  • deps: switch from git to version deps for crates.io publishing (a26aec4)
  • release: switch to rust release-type for Cargo.toml versioning (573b21c)

🔨 Refactor

  • move [patch.crates-io] to meta-repo .cargo/config.toml (bc3caed)

This PR was generated with Release Please. See documentation.

@github-actions github-actions bot changed the title chore(main): release 0.1.1 chore(main): release 0.2.0 Apr 2, 2026
@github-actions github-actions bot force-pushed the release-please--branches--main--components--oxidized-chat branch 8 times, most recently from 98a1de2 to 9cab879 Compare April 5, 2026 11:13
@github-actions github-actions bot force-pushed the release-please--branches--main--components--oxidized-chat branch 3 times, most recently from 09b28c5 to 22f4611 Compare April 10, 2026 12:00
@github-actions github-actions bot requested a review from dodoflix as a code owner April 10, 2026 12:00
@github-actions github-actions bot force-pushed the release-please--branches--main--components--oxidized-chat branch from 22f4611 to dd042e4 Compare April 10, 2026 20:01
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.

0 participants