fix(deps): update dependency unleash-server to v5.10.0 #129
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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
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.
This PR contains the following updates:
5.9.6->5.10.0Release Notes
unleash/unleash (unleash-server)
v5.10.0Compare Source
New Features
Schedule configuration changes
Change requests that have been approved can now be scheduled for a delayed application. Scheduled change requests can be rescheduled, applied immediately, or rejected.
Cleanup users / manual flow
You can now see users that have not been active (not logged in or used a token in last 6 months) and delete them in bulk
Bug: Project Privilege escalation
Users allowed to assign roles can now only assign roles they can access themselves. This locks down our permission system to prevent users from granting themselves roles they should not have
Enhance change request overview with deleted strategy info
When you delete a strategy in a change request, you'll now be able to see the strategy configuration in its entirety before applying it. This makes it easier to see exactly what you'll be deleting by applying a change request.
Improve conflict handling in CR
If a strategy, segment, or environment-level variant that's being updated in a change request has been changed since the change request had its relevant changes added, Unleash will now give a you a little heads up on the change request overview. You'll be able to see what the current configuration is and what it would be after applying your change request. Additionally, Unleash will suspend any scheduled change requests if it detects that a strategy, segment, or environmen-level variant has been updated after the change request was scheduled. All of this is to make it clearer to the user when a change request would introduce potentially unexpected changes.
Strategy configuration updates
Strategy configuration is now broken up into 3 sections: General, Targeting and Variants. This is to make it easier to have an overview over strategy configuration and to keep each section clean and uncluttered.
Thank you for your continued support and feedback. We hope you enjoy these new features and improvements.
Full log:
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
This PR has been generated by Mend Renovate. View repository job log here.