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.

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

fix!: corrected broken lockfile #339

Merged
merged 1 commit into from
Feb 11, 2025
Merged

fix!: corrected broken lockfile #339

merged 1 commit into from
Feb 11, 2025

Conversation

iFaxity
Copy link
Owner

@iFaxity iFaxity commented Feb 11, 2025

Corrected broken lockfile after a merge conflict.

BREAKING CHANGE: previous pr made an api change

Corrected broken lockfile after a merge conflict.

BREAKING CHANGE: previous pr made an api change
@iFaxity iFaxity merged commit 213cd65 into next Feb 11, 2025
5 checks passed
@iFaxity iFaxity deleted the bugfix/fix-lockfile branch February 11, 2025 23:04
Copy link
Contributor

🎉 This PR is included in version 7.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@bmulholland
Copy link

bmulholland commented Feb 18, 2025

What's the breaking change here? This refers to a previous PR in some way, but there's no link to which PR and it's not clear... does this revert back to the original behaviour, undoing the previous PR? What had changed there? What action is needed now, if any, and in which circumstances?

@iFaxity
Copy link
Owner Author

iFaxity commented Feb 18, 2025

Hi @bmulholland.

There was an api change in a previous pr that incorrectly missed to be specified as a breaking change . Therefore to fix the error this pr was instead pushed as a braking change. Sorry for not making that clearer.

@bmulholland
Copy link

@iFaxity got it -- thank you! Which PR was that?

@iFaxity
Copy link
Owner Author

iFaxity commented Feb 18, 2025

@bmulholland This one #212

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants