Bump version number so code with AWS token support can be identified in npm #33
Open
shafdog wants to merge 1 commit intoWantworthy:masterfrom
Open
Bump version number so code with AWS token support can be identified in npm #33shafdog wants to merge 1 commit intoWantworthy:masterfrom
npm #33shafdog wants to merge 1 commit intoWantworthy:masterfrom
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
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.
Not sure if the lack of session token support in the
npmpublished version is intentional. But suggest that at least the version be updated after some recent commits for AWS session/temp credential support, so it's clear ifdynodehas AWS token support.Looking at the commits, seems the AWS token changes did not also bump the
package.jsonversion.