Skip to content

chore(release/v0.13): release 0.13.1-SNAPSHOT#348

Merged
marythought merged 2 commits intorelease/v0.13from
release-please--branches--release/v0.13
Apr 10, 2026
Merged

chore(release/v0.13): release 0.13.1-SNAPSHOT#348
marythought merged 2 commits intorelease/v0.13from
release-please--branches--release/v0.13

Conversation

@opentdf-automation
Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.13.1-SNAPSHOT

Updating meta-information for bleeding-edge SNAPSHOT release.


This PR was generated with Release Please. See documentation.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 9, 2026

marythought added a commit that referenced this pull request Apr 9, 2026
## Summary

- Adds `release/v0\.\d+` regex pattern to the allowed scopes in the PR
title validation workflow
- Fixes `Validate PR title` check failing on release-please PRs
targeting release branches (e.g. #348, #315, #289)

Release-please uses the pattern `chore(${branch}): release ${version}`
for PR titles, which produces scopes like `release/v0.13` for release
branch PRs. These scopes were not in the allowed list, causing CI to
fail.

## Test plan

- [x] Verify this PR's own `Validate PR title` check passes
- [ ] Confirm #348 passes after this merges (or re-run its check)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Chores**
* Enhanced pull request validation workflow to recognize and properly
handle release automation processes.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Signed-off-by: Mary Dickson <mary.dickson@virtru.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
marythought
marythought previously approved these changes Apr 9, 2026
## Summary

- Adds `release/v0\.\d+` regex pattern to the allowed scopes in the PR
title validation workflow
- Fixes `Validate PR title` check failing on release-please PRs
targeting release branches (e.g. #348, #315, #289)

Release-please uses the pattern `chore(${branch}): release ${version}`
for PR titles, which produces scopes like `release/v0.13` for release
branch PRs. These scopes were not in the allowed list, causing CI to
fail.

## Test plan

- [x] Verify this PR's own `Validate PR title` check passes
- [ ] Confirm #348 passes after this merges (or re-run its check)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Chores**
* Enhanced pull request validation workflow to recognize and properly
handle release automation processes.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Signed-off-by: Mary Dickson <mary.dickson@virtru.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud bot commented Apr 9, 2026

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 9, 2026

Copy link
Copy Markdown
Contributor

@marythought marythought left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

@marythought marythought merged commit 426b98e into release/v0.13 Apr 10, 2026
18 checks passed
@marythought marythought deleted the release-please--branches--release/v0.13 branch April 10, 2026 17:56
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.

2 participants