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

Compatibility with OpenSearch 2.11.0 #113

Closed
3 of 4 tasks
AlexRuiz7 opened this issue Oct 20, 2023 · 2 comments · Fixed by #121
Closed
3 of 4 tasks

Compatibility with OpenSearch 2.11.0 #113

AlexRuiz7 opened this issue Oct 20, 2023 · 2 comments · Fixed by #121
Assignees
Labels

Comments

@AlexRuiz7
Copy link
Member

AlexRuiz7 commented Oct 20, 2023

Description

We need to ensure the UI compatibility with the next version of OpenSearch v2.11.0.
This update is still being discussed, but we need to be aware of potential issues.

For that, we need to:

  • Review opensearch and opensearch-dashboard latest stable changelog.
  • Identify improvements and potential impact on the UI.
  • Create new tracking and development branches.
  • Develop a testing environment to verify our components would work under this new build.

Issues

@JuanGarriuz

This comment was marked as outdated.

@AlexRuiz7
Copy link
Member Author

Note: listed here the interesting changes, followed by a comment of why it's interesting.

OpenSearch Dashboards 2.11.0 Release Notes

🛡 Security

  • [CVE-2022-25869] Remove AngularJS 1.8 (#5086)

🔩 Tests

  • [Functional][Doc Views] Remove angular code from plugin_functional and update tests (#5221)
  • Security fixes, including a CVE.
  • Removes AngularJS which is used in our plugins.
  • Changes in the test suite due to the removal of AngularJS

OpenSearch 2.11.0 Release Notes

Dependencies

  • Security fixes, including several CVEs.

@AlexRuiz7 AlexRuiz7 linked a pull request Nov 17, 2023 that will close this issue
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants