docs: mark Temporal buildId, selectAllActive and selectUnversioned as removed in 2.21 - #1840
Open
omkar619-dev wants to merge 1 commit into
Open
Conversation
✅ Deploy Preview for keda ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Thank you for your contribution! 🙏 We will review your PR as soon as possible.
Learn more about:
|
… removed in 2.21 Signed-off-by: Omkar Shendge <omkarshendge619@gmail.com>
omkar619-dev
force-pushed
the
docs/temporal-remove-deprecated-buildid-selectors
branch
from
August 17, 2026 13:10
86da000 to
82c7bba
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is a follow-up to kedacore/keda#7985, which makes
buildId,selectAllActiveandselectUnversionedfail at parse time in the Temporal scaler as of v2.21. @rickbrouwer asked for a matching docs change there.The 2.21 Temporal page currently still presents all three as usable options, so someone whose ScaledObject breaks on upgrade lands here and finds nothing explaining why.
Three changes:
workerDeploymentName/workerDeploymentBuildId. I kept the entries rather than deleting them so that anyone searching after hitting the parse error still finds an explanation.buildId,selectAllActive, andselectUnversioned" from theworkerDeploymentNameentry, since mutual exclusivity no longer means anything once those keys cannot be set at all.That last one wasn't in the original review comment, I just noticed it while making the other edits.