Skip to content

7.17 reached EoL#48364

Merged
v1v merged 2 commits into
elastic:mainfrom
v1v:feature/-remove-support-7.17
Jan 14, 2026
Merged

7.17 reached EoL#48364
v1v merged 2 commits into
elastic:mainfrom
v1v:feature/-remove-support-7.17

Conversation

@v1v

@v1v v1v commented Jan 9, 2026

Copy link
Copy Markdown
Member

Proposed commit message

7.17 reached EoL, therefore remove any scheduler or references to 7.17 in the automation.
I kept some 7.17 references in some commented code in the catalog-info and avoided removing any BK pipelines from the catalog-info.yaml to avoid issues with the wildness terrazzo - probably that's something we could potentially do in the future if we want to remove unused BK pipelines.

Besides I replace 8.* for 8.19 - that's the new LTS and no other minor 8.x will be available.

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
  • I have added tests that prove my fix is effective or that my feature works. Where relevant, I have used the stresstest.sh script to run them under stress conditions and race detector to verify their stability.
  • I have added an entry in ./changelog/fragments using the changelog tool.

Disruptive User Impact

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

@v1v v1v self-assigned this Jan 9, 2026
@v1v v1v added backport-7.17 Automated backport to the 7.17 branch with mergify backport-active-8 Automated backport with mergify to all the active 8.[0-9]+ branches skip-changelog labels Jan 9, 2026
@botelastic botelastic Bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jan 9, 2026
@botelastic

botelastic Bot commented Jan 9, 2026

Copy link
Copy Markdown

This pull request doesn't have a Team:<team> label.

@github-actions

github-actions Bot commented Jan 9, 2026

Copy link
Copy Markdown
Contributor

🤖 GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@v1v v1v marked this pull request as ready for review January 12, 2026 15:49
@v1v v1v requested a review from a team as a code owner January 12, 2026 15:49
@v1v v1v requested a review from pierrehilbert January 12, 2026 16:48

@fr4nc1sc0-r4m0n fr4nc1sc0-r4m0n left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

@v1v v1v merged commit 7e90e2c into elastic:main Jan 14, 2026
16 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

@Mergifyio backport 8.19

@mergify

mergify Bot commented Jan 14, 2026

Copy link
Copy Markdown
Contributor

backport 8.19

✅ Backports have been created

Details

mergify Bot pushed a commit that referenced this pull request Jan 14, 2026
(cherry picked from commit 7e90e2c)

# Conflicts:
#	.github/workflows/bump-golang.yml
#	.github/workflows/updatecli.d/bump-golang-7.17.yml
#	catalog-info.yaml
@mergify mergify Bot mentioned this pull request Jan 14, 2026
6 tasks
mergify Bot pushed a commit that referenced this pull request Jan 14, 2026
(cherry picked from commit 7e90e2c)

# Conflicts:
#	.github/workflows/bump-golang.yml
#	.github/workflows/updatecli.d/bump-golang-7.17.yml
@mergify mergify Bot mentioned this pull request Jan 14, 2026
6 tasks
v1v pushed a commit that referenced this pull request Jan 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-7.17 Automated backport to the 7.17 branch with mergify backport-active-8 Automated backport with mergify to all the active 8.[0-9]+ branches needs_team Indicates that the issue/PR needs a Team:* label skip-changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants