Skip to content

Remove unnecessary dependency#821

Merged
gbanasiak merged 2 commits intoelastic:masterfrom
gbanasiak:catalog-dependency-cleanup
Jul 16, 2025
Merged

Remove unnecessary dependency#821
gbanasiak merged 2 commits intoelastic:masterfrom
gbanasiak:catalog-dependency-cleanup

Conversation

@gbanasiak
Copy link
Contributor

Follow-up to #809.

@gbanasiak gbanasiak requested a review from fressi-elastic July 16, 2025 07:16
@gbanasiak gbanasiak requested a review from a team July 16, 2025 19:42
Comment on lines -54 to -55
provider_settings:
trigger_mode: none
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was one step too far in #809 it seems.

@gbanasiak
Copy link
Contributor Author

@gbanasiak
Copy link
Contributor Author

I'm bypassing rules as pending tests, i.e. rally-tracks-compat and rally-tracks-it-serverless are not related.

@gbanasiak gbanasiak merged commit 37a20a8 into elastic:master Jul 16, 2025
10 of 12 checks passed
@gbanasiak gbanasiak deleted the catalog-dependency-cleanup branch July 16, 2025 20:11
@esbenchmachine
Copy link
Collaborator

💚 All backports created successfully

Status Branch Result
8.15

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

esbenchmachine added a commit that referenced this pull request Jul 18, 2025
(cherry picked from commit 37a20a8)

Co-authored-by: Grzegorz Banasiak <grzegorz.banasiak@elastic.co>
@esbenchmachine esbenchmachine added the backport pending Awaiting backport to stable release branch label Dec 19, 2025
@esbenchmachine
Copy link
Collaborator

@gbanasiak
A backport is pending for this PR. Please add all required vX.Y version labels.

  • If it is intended for the current Elasticsearch release version, apply the corresponding version label.
  • If it also supports past released versions, add those labels too.
  • If it only targets a future version, wait until that version label exists and then add it.
    (Each rally-tracks version label is created during the feature freeze of a new Elasticsearch branch).

Backporting entails:

  1. Ensure the correct version labels exist in this PR.
  2. Ensure backport PRs have backport label and are passing tests.
  3. Merge backport PRs (you can approve yourself and enable auto-merge).
  4. Remove backport pending label from this PR once all backport PRs are merged.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport pending Awaiting backport to stable release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments