fix: backward compatibility #540
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Tymek
approved these changes
Nov 27, 2023
renovate bot
added a commit
to Unleash/unleash
that referenced
this pull request
Dec 5, 2023
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [unleash-client](https://togithub.com/Unleash/unleash-client-node) | [`5.0.0` -> `5.3.0`](https://renovatebot.com/diffs/npm/unleash-client/5.0.0/5.3.0) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>Unleash/unleash-client-node (unleash-client)</summary> ### [`v5.3.0`](https://togithub.com/Unleash/unleash-client-node/releases/tag/v5.3.0) [Compare Source](https://togithub.com/Unleash/unleash-client-node/compare/v5.2.0...v5.3.0) #### What's Changed - fix: backward compatibility by [@​gastonfournier](https://togithub.com/gastonfournier) in [Unleash/unleash-client-node#540 **Full Changelog**: Unleash/unleash-client-node@v5.2.0...v5.3.0 ### [`v5.2.0`](https://togithub.com/Unleash/unleash-client-node/releases/tag/v5.2.0) [Compare Source](https://togithub.com/Unleash/unleash-client-node/compare/v5.1.0...v5.2.0) #### What's Changed - chore(deps): update dependency [@​types/semver](https://togithub.com/types/semver) to v7.5.5 by [@​renovate](https://togithub.com/renovate) in [Unleash/unleash-client-node#527 - feat: Backoff based on HTTP statuses by [@​chriswk](https://togithub.com/chriswk) in [Unleash/unleash-client-node#537 **Full Changelog**: Unleash/unleash-client-node@v5.1.0...v5.2.0 ### [`v5.1.0`](https://togithub.com/Unleash/unleash-client-node/releases/tag/v5.1.0) [Compare Source](https://togithub.com/Unleash/unleash-client-node/compare/v5.0.0...v5.1.0) #### What's Changed - feat: variant feature status - client specification update by [@​Tymek](https://togithub.com/Tymek) in [Unleash/unleash-client-node#536 **Full Changelog**: Unleash/unleash-client-node@v5.0.0...v5.1.0 </details> --- ### Configuration 📅 **Schedule**: Branch creation - "after 7pm every weekday,before 5am every weekday" in timezone Europe/Madrid, Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/Unleash/unleash). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy44MS4zIiwidXBkYXRlZEluVmVyIjoiMzcuODEuMyIsInRhcmdldEJyYW5jaCI6Im1haW4ifQ==--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
](https://renovatebot.com){kind=link}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
About the changes
5.1.0 and 5.2.0 accidentally released a major breaking change with 5.0.0. It's unlikely that you'll be affected by it because the change happened in an internal part of the SDK that should not be used by customers.
This PR makes sure we keep backward compatibility with the previous version as well as mark as deprecated the parts that will be removed in next major release.
This is how this PR compares to 5.0: v5.0.0...fix/backward-compatibility and we can see the expand pattern emerging