Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ggj] docs: remove pre-release references in DEVELOPMENT.md #699

Merged
merged 1 commit into from Mar 19, 2021

Conversation

miraleung
Copy link
Contributor

No description provided.

@miraleung miraleung requested a review from a team as a code owner March 18, 2021 17:38
@google-cla google-cla bot added the cla: yes This human has signed the Contributor License Agreement. label Mar 18, 2021
@codecov
Copy link

codecov bot commented Mar 18, 2021

Codecov Report

Merging #699 (c950187) into master (ac6f5ad) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #699   +/-   ##
=======================================
  Coverage   92.47%   92.47%           
=======================================
  Files         124      124           
  Lines       13347    13347           
  Branches      952      952           
=======================================
  Hits        12342    12342           
  Misses        761      761           
  Partials      244      244           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ac6f5ad...c950187. Read the comment docs.

@miraleung miraleung changed the title docs: remove pre-release references in DEVELOPMENT.md [ggj] docs: remove pre-release references in DEVELOPMENT.md Mar 19, 2021
@miraleung miraleung merged commit fc7e637 into master Mar 19, 2021
@miraleung miraleung deleted the miraleung-patch-1 branch March 19, 2021 03:54
suztomo pushed a commit that referenced this pull request Mar 21, 2023
🤖 I have created a release *beep* *boop*
---


### Updating meta-information for bleeding-edge SNAPSHOT release.

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
suztomo pushed a commit that referenced this pull request Mar 21, 2023
…699)

[![WhiteSource Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [com.google.protobuf:protobuf-bom](https://developers.google.com/protocol-buffers/) ([source](https://togithub.com/protocolbuffers/protobuf)) | `3.19.3` -> `3.19.4` | [![age](https://badges.renovateapi.com/packages/maven/com.google.protobuf:protobuf-bom/3.19.4/age-slim)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://badges.renovateapi.com/packages/maven/com.google.protobuf:protobuf-bom/3.19.4/adoption-slim)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://badges.renovateapi.com/packages/maven/com.google.protobuf:protobuf-bom/3.19.4/compatibility-slim/3.19.3)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://badges.renovateapi.com/packages/maven/com.google.protobuf:protobuf-bom/3.19.4/confidence-slim/3.19.3)](https://docs.renovatebot.com/merge-confidence/) |

---

### Release Notes

<details>
<summary>protocolbuffers/protobuf</summary>

### [`v3.19.4`](https://togithub.com/protocolbuffers/protobuf/releases/v3.19.4)

[Compare Source](https://togithub.com/protocolbuffers/protobuf/compare/v3.19.3...v3.19.4)

### Python

-   Make libprotobuf symbols local on OSX to fix issue [#&#8203;9395](https://togithub.com/protocolbuffers/protobuf/issues/9395) ([#&#8203;9435](https://togithub.com/protocolbuffers/protobuf/issues/9435))

### Ruby

-   Fixed a data loss bug that could occur when the number of `optional` fields in a message is an exact multiple of 32. ([#&#8203;9440](https://togithub.com/protocolbuffers/protobuf/issues/9440)).

### PHP

-   Fixed a data loss bug that could occur when the number of `optional` fields in a message is an exact multiple of 32. ([#&#8203;9440](https://togithub.com/protocolbuffers/protobuf/issues/9440)).

</details>

---

### Configuration

📅 **Schedule**: At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by [WhiteSource Renovate](https://renovate.whitesourcesoftware.com). View repository job log [here](https://app.renovatebot.com/dashboard#github/googleapis/java-core).
suztomo pushed a commit that referenced this pull request Mar 21, 2023
🤖 I have created a release *beep* *boop*
---


## [2.5.0](googleapis/java-core@v2.4.0...v2.5.0) (2022-02-02)


### Features

* add limit support to ReadChannel ([#688](googleapis/java-core#688)) ([9543eb2](googleapis/java-core@9543eb2))


### Bug Fixes

* **java:** Initialize AsyncSSLPrivateKeyMethod (a grpc netty class) at run-time ([#702](googleapis/java-core#702)) ([af1c9b3](googleapis/java-core@af1c9b3))


### Dependencies

* update dependency com.google.api:gax-bom to v2.12.0 ([#698](googleapis/java-core#698)) ([34bbad8](googleapis/java-core@34bbad8))
* update dependency com.google.protobuf:protobuf-bom to v3.19.4 ([#699](googleapis/java-core#699)) ([9e2f077](googleapis/java-core@9e2f077))

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant