Skip to content

chore(master): release 0.42.0 - #2076

Merged
aeppling merged 1 commit into
masterfrom
release-please--branches--master--components--rtk
May 24, 2026
Merged

aeppling merged 1 commit into
masterfrom
release-please--branches--master--components--rtk

Conversation

@rtk-release-bot

@rtk-release-bot rtk-release-bot Bot commented May 24, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.42.0 (2026-05-24)

Features

  • hook: add pi agent support (805caf7)

Bug Fixes

  • honor explicit -n N limit for git log on merge commits (26c8890)

This PR was generated with Release Please. See documentation.

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@rtk-release-bot

Copy link
Copy Markdown
Contributor Author

Automatic message from CI checks : It seems like this branch is targeting the wrong branch, any contribution should target develop branch.

See CONTRIBUTING.md for details.

@rtk-release-bot rtk-release-bot Bot added the wrong-base PR targets master instead of develop label May 24, 2026
@aeppling
aeppling merged commit 39583cf into master May 24, 2026
12 of 13 checks passed
@rtk-release-bot

Copy link
Copy Markdown
Contributor Author

Automatic message from CI checks : It seems like this branch is targeting the wrong branch, any contribution should target develop branch.

See CONTRIBUTING.md for details.

@rtk-release-bot

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

Labels

autorelease: tagged wrong-base PR targets master instead of develop

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants