Skip to content

chore(ENG-000): release defender 0.6.1#54

Merged
hiskudin merged 1 commit intomainfrom
chore/release-as-0.6.1
Apr 21, 2026
Merged

chore(ENG-000): release defender 0.6.1#54
hiskudin merged 1 commit intomainfrom
chore/release-as-0.6.1

Conversation

@hiskudin
Copy link
Copy Markdown
Collaborator

@hiskudin hiskudin commented Apr 21, 2026

Summary

Overrides release-please's automatic bump. The squash-merge of #52 used a feat: prefix, which made release-please compute 0.7.0 (minor bump). Intended release for that PR is a patch — 0.6.1, not 0.7.0.

This empty commit carries a Release-As: 0.6.1 footer that release-please picks up and uses to pin the version.

Follow-up

Once merged, release-please will regenerate #53 targeting 0.6.1.

Test plan


Summary by cubic

Pins the defender release to 0.6.1 using a Release-As: 0.6.1 empty commit so release-please publishes a patch. Fixes an unintended 0.7.0 minor bump from a prior feat: squash-merge; no code changes.

Written for commit df91815. Summary will update on new commits.

Release-As: 0.6.1
Copilot AI review requested due to automatic review settings April 21, 2026 09:18
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot wasn't able to review any files in this pull request.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@hiskudin hiskudin changed the title chore: release defender 0.6.1 chore(ENG-xxx): release defender 0.6.1 Apr 21, 2026
@hiskudin hiskudin changed the title chore(ENG-xxx): release defender 0.6.1 chore(ENG-000): release defender 0.6.1 Apr 21, 2026
@hiskudin hiskudin merged commit 3611f4b into main Apr 21, 2026
3 of 6 checks passed
@hiskudin hiskudin deleted the chore/release-as-0.6.1 branch April 21, 2026 09:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants