Merge release into master #5424
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
risk: nonprod
risk: nonprod
JIRA: LX-423 risk: low
feat: release saved filter views for public
Override feature hub to disable alerting and scheduling features for release 10.11.0. JIRA: F1-753
fix: disable alerting / scheduling
risk: nonprod
risk: nonprod
risk: nonprod
… master risk: nonprod
|
Job gooddata-ui-sdk-unit-tests at https://checklist.intgdc.com/job/gooddata-ui-sdk/job/gooddata-ui-sdk-unit-tests/21972/ finished with 'SUCCESS' status. |
|
Job gooddata-ui-sdk-cypress-tiger-isolated-zuul-pipeline at https://checklist.intgdc.com/job/gooddata-ui-sdk/job/gooddata-ui-sdk-cypress-tiger-isolated-zuul-pipeline/2540/ finished with 'SUCCESS' status. |
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 is created automatically by GitHub Actions from release into master via temporary branch release-to-master.
In case of conflicts, please resolve them.
Check out release-to-master locally and ensure the branch is up to date with the upstream.
Then call 'git merge upstream/master'.
Resolve conflicts and push release-to-master to upstream.