fix: mark the HTTP/2 support as stable #401
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
google-cla
bot
added
the
cla: yes
gcf-owl-bot
bot
removed
the
owlbot:run
bcoe
approved these changes
Jul 7, 2021
gcf-merge-on-green bot
pushed a commit
that referenced
this pull request
Jul 7, 2021
🤖 I have created a release \*beep\* \*boop\* --- ### [5.0.3](https://www.github.com/googleapis/nodejs-googleapis-common/compare/v5.0.2...v5.0.3) (2021-07-07) ### Bug Fixes * mark the HTTP/2 support as stable ([#401](https://www.github.com/googleapis/nodejs-googleapis-common/issues/401)) ([1e0735b](https://www.github.com/googleapis/nodejs-googleapis-common/commit/1e0735baa4a9df24e4a9323cfbba6a82ce2e738b)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
1 task
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.
The API is now over a year old, and we've had no complaints on the surface. There are many tests, and it seems to work great.