chore: add supported version to description #93
Merged
Conversation
This file contains 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
AWS-Samuel
force-pushed
the
samuel/add-version-installbuilder
branch
from
19b1613 to
16b817a
Compare
amarsjac
approved these changes
Feb 14, 2024
epmog
approved these changes
Feb 14, 2024
Signed-off-by: Samuel Anderson <[email protected]>
AWS-Samuel
force-pushed
the
samuel/add-version-installbuilder
branch
from
16b817a to
e6d9399
Compare
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.
What was the problem/requirement? (What/Why)
It was unclear at installation time what version(s) of the DCC the submitter will be available in.
What was the solution? (How)
Explicitly call out which version(s) of the DCC the submitter will be available in.
What is the impact of this change?
Less confusion when installing
How was this change tested?
Built an installer, confirmed wording appeared accurate:
Did you run the "Job Bundle Output Tests"? If not, why not? If so, paste the test results here.
No, this doesn't affect the integration.
Was this change documented?
No
Is this a breaking change?
No