chore/set the client version back to 0.11.0 and enable publishing #80
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
In order to publish again, let's have continuity with the npm versions. This change in gen.yaml will get picked up on the next regenerate.
awalker4
changed the title
awalker4
force-pushed
the
austin/publish-client
branch
from
11cb786 to
338cfc0
Compare
awalker4
force-pushed
the
austin/publish-client
branch
from
338cfc0 to
63eddb8
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.
In order to publish again, let's have continuity with the npm versions. This change in gen.yaml will get picked up on the next regenerate.
The actual publish will happen when we regenerate. We'll coordinate this to go with a docs update showing the new usage.