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

feat: raise errors when versions are not supported #31

Merged
merged 1 commit into from
Oct 1, 2024

Conversation

kylemellander
Copy link
Collaborator

There were scenarios where an upgrade was not compatible because of peerDependencies not being valid. This caused the version to be upgraded to a lower version than what we intended. Instead of allowing that to happen, we will now raise an error that communicates why we were not able to upgrade to the newer version.

Fixes #26

@kylemellander kylemellander requested review from danielma and a team September 30, 2024 16:49
@kylemellander kylemellander self-assigned this Sep 30, 2024
@kylemellander kylemellander requested a review from a team as a code owner September 30, 2024 16:49
There were scenarios where an upgrade was not compatible because of
peerDependencies not being valid.  This caused the version to be
upgraded to a lower version than what we intended.  Instead
of allowing that to happen, we will now raise an error that communicates
why we were not able to upgrade to the newer version.
@kylemellander kylemellander force-pushed the km/feat/version-allowed-detection branch from 4166011 to c981a82 Compare October 1, 2024 17:06
@kylemellander kylemellander merged commit 04c810d into main Oct 1, 2024
@kylemellander kylemellander deleted the km/feat/version-allowed-detection branch October 1, 2024 17:06
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.

Bug: mismatching version in description / yarn.lock / title
2 participants