docs: Add instructions to update the honeycomb_version field inside the package.json
#87
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
… the package.json
RobertGemmaJr
requested review from
digicosmos86,
hetd54,
anna-murphy and
broarr
RobertGemmaJr
commented
Nov 14, 2023
RobertGemmaJr
commented
Nov 14, 2023
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.
My thinking here is that if they don't follow the quick start than most likely the
versiontag will be the Honeycomb version they used. I don't foresee a lab updating theversionfield and not touchinghoneycomb_versionCoincides with this PR in honeycomb.