Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: Previous merge did not trigger release #210

Merged
merged 1 commit into from
Jan 21, 2025
Merged

fix: Previous merge did not trigger release #210

merged 1 commit into from
Jan 21, 2025

Conversation

danielpanzella
Copy link
Contributor

No description provided.

@danielpanzella danielpanzella requested a review from a team as a code owner January 21, 2025 18:31
zacharyblasczyk
zacharyblasczyk approved these changes Jan 21, 2025
View reviewed changes
Copy link
Contributor

@zacharyblasczyk zacharyblasczyk left a comment

Choose a reason for hiding this comment

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

🚀

@danielpanzella danielpanzella merged commit 205e332 into main Jan 21, 2025
7 checks passed
@danielpanzella danielpanzella deleted the danielpanzella-patch-1 branch January 21, 2025 18:32
@zacharyblasczyk
Copy link
Contributor

🚢

jsbroks pushed a commit that referenced this pull request Jan 21, 2025
@semantic-release-bot
chore(release): version 8.0.3 [skip ci]
cae4397 
### [8.0.3](v8.0.2...v8.0.3) (2025-01-21)

### Bug Fixes

* Prevent diffs appearing when nothing has changed in PSC configs ([#209](#209)) ([60597e4](60597e4))
* Previous merge did not trigger release ([#210](#210)) ([205e332](205e332))
@jsbroks
Copy link
Member

jsbroks commented Jan 21, 2025

This PR is included in version 8.0.3 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@zacharyblasczyk zacharyblasczyk zacharyblasczyk approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@danielpanzella @zacharyblasczyk @jsbroks