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.

Sign up for GitHub

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

Jump to bottom

Use ElasticSearch 6.8.23 in our local setup #4446

Merged
merged 2 commits into from
Feb 10, 2025
Merged

Use ElasticSearch 6.8.23 in our local setup #4446

merged 2 commits into from
Feb 10, 2025

Conversation

supersven
Copy link
Contributor

@supersven supersven commented Feb 7, 2025 •
edited
Loading

This version is deployed on Ci, staging and prod.

I've executed TASTY_PATTERN=Search make ci-safe package=brig (was green) to ensure our backend can talk to the changed ElasticSearch image.

Checklist

  • Add a new entry in an appropriate subdirectory of changelog.d
  • Read and follow the PR guidelines

@supersven
Use ElasticSearch 6.8.23 in our local setup
f5f7325 
This version is deployed on Ci, staging and prod.
@supersven
Add changelog entry
cefb494
@zebot zebot added the ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist label Feb 7, 2025
@supersven supersven merged commit 273ec4f into develop Feb 10, 2025
5 checks passed
@supersven supersven deleted the supersven/docker-compose-elasticsearch-6 branch February 10, 2025 10:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@akshaymankar akshaymankar akshaymankar approved these changes

Assignees
No one assigned
Labels
ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@supersven @akshaymankar @zebot