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

chore: release main #82

Merged
merged 1 commit into from
Dec 22, 2021
Merged

chore: release main #82

merged 1 commit into from
Dec 22, 2021

Conversation

release-please[bot]
Copy link
Contributor

@release-please release-please bot commented Oct 27, 2021

🤖 I have created a release *beep* *boop*

bucket-blueprint: 0.4.2

Bug Fixes

  • Remove pre-v1 setter from bucket blueprint (#81) (d32d5de)
gitops-blueprint: 0.4.1

Bug Fixes

  • updates function name foe remove-annotated-resources (#85) (1632e00)
gke-blueprint: 0.4.0

Features

  • Change cluster and node pool defaults (#89) (32918a5)
landing-zone-blueprint: 0.5.0

Features

  • Implement landing-zone-lite and fix some issues in the existing LZ blueprints (#93) (bdd20a5)
iam-foundation-blueprint: 0.1.0

Features

Bug Fixes

  • add release-please config for IAM blueprint (#91) (817b459)

This PR was generated with Release Please. See documentation.

@google-oss-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: release-please[bot]
To complete the pull request process, please assign karlkfi after the PR has been reviewed.
You can assign the PR to them by writing /assign @karlkfi in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@google-oss-robot
Copy link
Collaborator

Hi @release-please[bot]. Thanks for your PR.

I'm waiting for a GoogleCloudPlatform member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@release-please release-please bot force-pushed the release-please/branches/main branch from 3fcf735 to 06c2cfc Compare December 22, 2021 22:50
@bharathkkb bharathkkb merged commit 7ee2731 into main Dec 22, 2021
@release-please
Copy link
Contributor Author

@release-please
Copy link
Contributor Author

@release-please
Copy link
Contributor Author

@release-please
Copy link
Contributor Author

@release-please
Copy link
Contributor Author

@google-oss-prow
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bharathkkb, release-please[bot]

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants