Add nightly dependency bump workflow #479
Conversation
|
I just realized: I updated main build so that it also triggers when pushes are made to the |
This reverts commit 076e529.
| - OpenTelemetry Python: ${{ steps.get_versions.outputs.otel_python_version }} | ||
| - OpenTelemetry Contrib: ${{ steps.get_versions.outputs.otel_contrib_version }} | ||
| - [opentelemetry-sdk-extension-aws](https://pypi.org/project/opentelemetry-sdk-extension-aws/${{ steps.get_versions.outputs.opentelemetry_sdk_extension_aws_version }}/): ${{ steps.get_versions.outputs.opentelemetry_sdk_extension_aws_version }} | ||
| - [opentelemetry-propagator-aws-xray](https://pypi.org/project/opentelemetry-propagator-aws-xray/${{ steps.get_versions.outputs.opentelemetry_propagator_aws_xray_version }}/): ${{ steps.get_versions.outputs.opentelemetry_propagator_aws_xray_version }} |
There was a problem hiding this comment.
Can we add links to OpenTelemetry Python/Contrib?
| print("Error: OTEL_PYTHON_VERSION and OTEL_CONTRIB_VERSION environment variables required") | ||
| sys.exit(1) | ||
|
|
||
| pyproject_path = "aws-opentelemetry-distro/pyproject.toml" |
There was a problem hiding this comment.
I was wrong about contract tests, we do need it for mock-collector.
For aws-otel-python-instrumentation/lambda-layer/src/tests/requirements.txt - reach out to @wangzlei to confirm if these should be kept up to date. We can do this as a backlog item though.
There was a problem hiding this comment.
No, new job update-pr should always() run, but we should include the status of main-build run in the PR. It's easier to work with the PRs that way.
2 participants
Issue #, if available:
Description of changes:
Add a workflow
nightly-build.ymlwith following actions:nightly-dependency-updatesbranchExample nightly build PR: #526
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.