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.

Sign up for GitHub

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

Jump to bottom

chore(main): release 1.0.1 #318

Merged
merged 3 commits into from
Sep 21, 2022
Merged

chore(main): release 1.0.1 #318

merged 3 commits into from
Sep 21, 2022

Conversation

release-please[bot]
Copy link
Contributor

@release-please release-please bot commented May 26, 2022 •
edited
Loading

🤖 I have created a release beep boop

1.0.1 (2022-09-21)

Bug Fixes

Dependencies

  • Update dependency com.google.cloud:google-cloud-pubsublite-parent to v1.6.1 (#331) (03281fd)
  • Update dependency com.google.cloud:google-cloud-pubsublite-parent to v1.6.3 (#336) (7f8673b)
  • Update dependency com.google.cloud:google-cloud-pubsublite-parent to v1.7.0 (#340) (06a376e)
  • Update dependency org.apache.kafka:kafka-clients to v3.1.0 (#226) (578af21)
  • Version bump kafka to the latest version (#341) (a2875bc)

This PR was generated with Release Please. See documentation.

@release-please release-please bot requested review from a team as code owners May 26, 2022 17:32
@product-auto-label product-auto-label bot added size: s Pull request size is small. api: pubsublite Issues related to the googleapis/java-pubsublite-kafka API. labels May 26, 2022
@anguillanneuf anguillanneuf added the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label May 26, 2022
@anguillanneuf
Copy link
Contributor

Good to wait for the next commit to main because #226 is actually updating deps in the samples/ directory.

@release-please release-please bot force-pushed the release-please--branches--main branch from fd7d5f2 to a416f42 Compare June 9, 2022 16:40
@release-please release-please bot force-pushed the release-please--branches--main branch 2 times, most recently from 0861fd3 to b190aba Compare June 30, 2022 02:22
@blakeli0 blakeli0 added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jul 1, 2022
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jul 1, 2022
@blakeli0 blakeli0 added the automerge Merge the pull request once unit tests and other checks pass. label Jul 1, 2022
@release-please release-please bot force-pushed the release-please--branches--main branch from b190aba to d1b775e Compare July 1, 2022 21:12
@gcf-merge-on-green
Copy link

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Jul 1, 2022
@release-please release-please bot force-pushed the release-please--branches--main branch from d1b775e to f652036 Compare July 8, 2022 20:04
@alicejli
Copy link
Contributor

@anguillanneuf Is it okay to remove the donotmerge label given that #226 has been merged?

@release-please release-please bot force-pushed the release-please--branches--main branch 2 times, most recently from 4f40bbb to 0102d40 Compare July 13, 2022 19:36
@alicejli alicejli added kokoro:force-run Add this label to force Kokoro to re-run the tests. automerge Merge the pull request once unit tests and other checks pass. labels Jul 14, 2022
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jul 14, 2022
@gcf-merge-on-green
Copy link

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Jul 14, 2022
@release-please release-please bot force-pushed the release-please--branches--main branch from 0102d40 to df0bbaf Compare July 19, 2022 13:36
@release-please release-please bot force-pushed the release-please--branches--main branch from df0bbaf to ed418c8 Compare August 16, 2022 16:42
@release-please release-please bot force-pushed the release-please--branches--main branch from ed418c8 to 90e140d Compare September 12, 2022 13:33
@anguillanneuf anguillanneuf removed the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Sep 21, 2022
@release-please release-please bot force-pushed the release-please--branches--main branch from 90e140d to 2365ee2 Compare September 21, 2022 16:47
@anguillanneuf anguillanneuf added the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Sep 21, 2022
@release-please release-please bot force-pushed the release-please--branches--main branch from 2365ee2 to fae6c59 Compare September 21, 2022 16:48
@anguillanneuf anguillanneuf removed the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Sep 21, 2022
@release-please release-please bot force-pushed the release-please--branches--main branch from fae6c59 to 740692a Compare September 21, 2022 16:54
@anguillanneuf anguillanneuf added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Sep 21, 2022
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Sep 21, 2022
@anguillanneuf anguillanneuf added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Sep 21, 2022
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Sep 21, 2022
@anguillanneuf anguillanneuf added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Sep 21, 2022
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Sep 21, 2022
@anguillanneuf anguillanneuf merged commit 4d7782e into main Sep 21, 2022
@anguillanneuf anguillanneuf deleted the release-please--branches--main branch September 21, 2022 18:15
@release-please
Copy link
Contributor Author

🤖 Release is at https://github.com/googleapis/java-pubsublite-kafka/releases/tag/v1.0.1 🌻

@release-tool-publish-reporter
Copy link

The release build has started, the log can be viewed here. 🌻

@release-tool-publish-reporter
Copy link

🥚 You hatched a release! The release build finished successfully! 💜

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@alicejli alicejli alicejli approved these changes

@anguillanneuf anguillanneuf anguillanneuf approved these changes

@blakeli0 blakeli0 blakeli0 approved these changes

Assignees
No one assigned
Labels
api: pubsublite Issues related to the googleapis/java-pubsublite-kafka API. autorelease: published size: s Pull request size is small.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@anguillanneuf @alicejli @blakeli0 @yoshi-kokoro