[Fleet] Update spec.max to 3.4 #221544
Merged
[Fleet] Update spec.max to 3.4 #221544
+5
−11
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
botelastic
bot
added
the
Team:Fleet
|
Pinging @elastic/fleet (Team:Fleet) |
jsoriano
added
backport:prev-major
nchaulet
reviewed
May 26, 2025
jeramysoucy
approved these changes
May 27, 2025
There was a problem hiding this comment.
Approving to unblock. Only question I had was already asked by Nicolas here
nchaulet
approved these changes
May 27, 2025
jloleysens
approved these changes
Jun 3, 2025
jsoriano
added
ci:project-deploy-elasticsearch
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
|
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]
History
cc @jsoriano |
jsoriano
added
backport:version
jsoriano
added
backport:version
|
Starting backport for target branches: 8.19 https://github.com/elastic/kibana/actions/runs/15562543091 |
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
kibanamachine
added
the
backport missing
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
jsoriano
added a commit
that referenced
this pull request
Jun 12, 2025
# Backport This will backport the following commits from `main` to `8.19`: - [[Fleet] Update spec.max to 3.4 (#221544)](#221544) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jaime Soriano Pastor","email":"jaime.soriano@elastic.co"},"sourceCommit":{"committedDate":"2025-06-10T14:38:47Z","message":"[Fleet] Update spec.max to 3.4 (#221544)\n\nUpdates maximum supported spec version to 3.4.\n\n3.4 spec version released in\nhttps://github.com/elastic/package-spec/pull/896.\n\nCommon serverless settings are moved to the common file.","sha":"25b5ff2b83fbfed6298babd640b67c41b732de94","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","backport missing","Team:Fleet","ci:project-deploy-elasticsearch","ci:project-deploy-observability","ci:project-deploy-security","backport:version","8.19 candidate","v9.1.0","v8.19.0","ci:project-deploy-ai4soc"],"title":"[Fleet] Update spec.max to 3.4","number":221544,"url":"https://github.com/elastic/kibana/pull/221544","mergeCommit":{"message":"[Fleet] Update spec.max to 3.4 (#221544)\n\nUpdates maximum supported spec version to 3.4.\n\n3.4 spec version released in\nhttps://github.com/elastic/package-spec/pull/896.\n\nCommon serverless settings are moved to the common file.","sha":"25b5ff2b83fbfed6298babd640b67c41b732de94"}},"sourceBranch":"main","suggestedTargetBranches":["8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/221544","number":221544,"mergeCommit":{"message":"[Fleet] Update spec.max to 3.4 (#221544)\n\nUpdates maximum supported spec version to 3.4.\n\n3.4 spec version released in\nhttps://github.com/elastic/package-spec/pull/896.\n\nCommon serverless settings are moved to the common file.","sha":"25b5ff2b83fbfed6298babd640b67c41b732de94"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
kibanamachine
removed
the
backport missing
nickpeihl
pushed a commit
to nickpeihl/kibana
that referenced
this pull request
Jun 12, 2025
Updates maximum supported spec version to 3.4. 3.4 spec version released in elastic/package-spec#896. Common serverless settings are moved to the common file.
iblancof
pushed a commit
to iblancof/kibana
that referenced
this pull request
Jun 16, 2025
Updates maximum supported spec version to 3.4. 3.4 spec version released in elastic/package-spec#896. Common serverless settings are moved to the common file.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Updates maximum supported spec version to 3.4.
3.4 spec version released in elastic/package-spec#896.
Intended to be released in 9.1, 8.19 and Serverless.
Common serverless settings are moved to the common file. spec.max is removed as it is the same as the default.
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesIdentify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.