-
Notifications
You must be signed in to change notification settings - Fork 0
fix(python): upgrade pydantic to 2.12 for Python 3.14 compatibility #421
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,48 @@ | ||
| steps: | ||
| - name: gcr.io/k8s-skaffold/pack | ||
| args: | ||
| - build | ||
| - >- | ||
| $_AR_HOSTNAME/$_AR_PROJECT_ID/$_AR_REPOSITORY/$REPO_NAME/$_SERVICE_NAME:$COMMIT_SHA | ||
| - '--builder=gcr.io/buildpacks/builder:google-24' | ||
| - '--network=cloudbuild' | ||
| - '--path=src/python' | ||
| id: Buildpack | ||
| entrypoint: pack | ||
| - name: gcr.io/cloud-builders/docker | ||
| args: | ||
| - push | ||
| - '--all-tags' | ||
| - $_AR_HOSTNAME/$_AR_PROJECT_ID/$_AR_REPOSITORY/$REPO_NAME/$_SERVICE_NAME | ||
| id: Push | ||
| - name: gcr.io/google.com/cloudsdktool/cloud-sdk:slim | ||
| args: | ||
| - run | ||
| - services | ||
| - update | ||
| - $_SERVICE_NAME | ||
| - >- | ||
| --image=$_AR_HOSTNAME/$_AR_PROJECT_ID/$_AR_REPOSITORY/$REPO_NAME/$_SERVICE_NAME:$COMMIT_SHA | ||
| - >- | ||
| --update-labels=managed-by=gcp-cloud-build-deploy-cloud-run,gcb-trigger-id=$_TRIGGER_ID,gcb-trigger-region=$LOCATION,commit-sha=$COMMIT_SHA,gcb-build-id=$BUILD_ID | ||
| - '--region=$_DEPLOY_REGION' | ||
| - '--quiet' | ||
| id: Deploy | ||
| entrypoint: gcloud | ||
| images: | ||
| - >- | ||
| $_AR_HOSTNAME/$_AR_PROJECT_ID/$_AR_REPOSITORY/$REPO_NAME/$_SERVICE_NAME:$COMMIT_SHA | ||
| options: | ||
| requestedVerifyOption: VERIFIED | ||
| substitutionOption: ALLOW_LOOSE | ||
| logging: CLOUD_LOGGING_ONLY | ||
| substitutions: | ||
| _DEPLOY_REGION: europe-west1 | ||
| _AR_HOSTNAME: europe-west1-docker.pkg.dev | ||
| _AR_REPOSITORY: cloud-run-source-deploy | ||
| _AR_PROJECT_ID: lamp-control-469416 | ||
| _SERVICE_NAME: python-lamp-control-api | ||
| _TRIGGER_ID: e4522704-3279-49da-b701-63621b89eb67 | ||
| tags: | ||
| - gcp-cloud-build-deploy-cloud-run | ||
| - python-lamp-control-api | ||
Oops, something went wrong.
Oops, something went wrong.
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.
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.
This PR adds a new
src/python/cloudbuild.yaml(Cloud Build/Cloud Run deployment config), but the PR description only mentions dependency/lockfile updates. Please update the PR description (or add an inline comment) to explain why this file is being introduced and how it’s intended to be used (e.g., new trigger, replacing an existing build config, etc.).