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

[DO NOT MERGE] Adding Gemlock file from 8.18 to 9.0 #16992

Closed
wants to merge 1 commit into from

Conversation

mashhurs
Copy link
Contributor

Release notes

[rn:skip]

What does this PR do?

Copies Gemlock file (required for release) from 8.18 to 9.0 branch

Why is it important/What is the impact to the user?

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files (and/or docker env variables)
  • I have added tests that prove my fix is effective or that my feature works

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

@mashhurs mashhurs marked this pull request as ready for review January 30, 2025 15:07
@mashhurs mashhurs self-assigned this Jan 30, 2025
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

cc @mashhurs

@mashhurs mashhurs marked this pull request as draft January 30, 2025 17:43
@mashhurs mashhurs changed the title Adding Gemlock file from 8.18 to 9.0 [DO NOT MERGE] Adding Gemlock file from 8.18 to 9.0 Jan 30, 2025
@mashhurs
Copy link
Contributor Author

Covered with #16993

@mashhurs mashhurs closed this Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants