-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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(main): release 0.75.0 #1497
Conversation
3ccbb21
to
3107fa0
Compare
3107fa0
to
007309b
Compare
007309b
to
55eba78
Compare
55eba78
to
f1dbf1d
Compare
f1dbf1d
to
32083d1
Compare
32083d1
to
5c14094
Compare
5c14094
to
f5da87e
Compare
f5da87e
to
970c410
Compare
970c410
to
9271f69
Compare
9271f69
to
0d62a3e
Compare
@quartzmo @codyoss This release is broken with the Cloud Run v2 API unfortunately. On 95e21aa#diff-16788947c954af9dfca293168fd213c4ddf0557d861974463e34f62036dc8cbe When using the new version with the renamed field, it results in an error now: {
"@type": "type.googleapis.com/google.rpc.BadRequest",
"fieldViolations": [
{
"description": "Invalid JSON payload received. Unknown name \"instances\" at 'service.template.volumes[0].cloud_sql_instance': Cannot find field.",
"field": "service.template.volumes[0].cloud_sql_instance"
}
]
} |
Opened #1519 in case closed issues don't tend to get visibility |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hellou
🤖 I have created a release beep boop
0.75.0 (2022-04-20)
Features
This PR was generated with Release Please. See documentation.