Skip to content

Commit f88c154

Browse files
committed
Test
1 parent bb16787 commit f88c154

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

.github/workflows/release_build.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ jobs:
125125
- name: Get SHA256 checksum of wheel file
126126
id: get_sha256
127127
run: |
128-
shasum -a 256 dist/${{ env.ARTIFACT_NAME }} > ${{ env.ARTIFACT_NAME }}.sha256
128+
shasum -a 256 dist/${{ env.ARTIFACT_NAME }} | sed "s|dist/||" > ${{ env.ARTIFACT_NAME }}.sha256
129129
130130
# Publish to GitHub releases
131131
- name: Create GH release

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ This project ensures compatibility with the following supported Python versions:
4040
### Note on Amazon CloudWatch Application Signals
4141
[Amazon CloudWatch Application Signals](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Application-Monitoring-Sections.html) components are designed to seamlessly work with all library instrumentations offered by [OpenTelemetry Python auto-instrumentation](https://github.com/open-telemetry/opentelemetry-python-contrib/blob/main/instrumentation/README.md). While upstream OpenTelemetry Python instrumentations are in beta, Application Signals components are stable, production ready and have also been tested for popular libraries/frameworks such as [Django, Boto3, and others](https://github.com/aws-observability/aws-otel-python-instrumentation/tree/main/contract-tests/images/applications). We will prioritize backward compatibility for Application Signals components, striving to ensure that they remain functional even in the face of potential breaking changes introduced by OpenTelemetry upstream libraries. Please [raise an issue](https://github.com/aws-observability/aws-otel-python-instrumentation/blob/main/CONTRIBUTING.md#reporting-bugsfeature-requests) if you notice Application Signals doesn't work for a particular OpenTelemetry supported library.
4242

43-
### Checksum Verification
43+
## Checksum Verification
4444
Artifacts released will include a `.sha256` file for checksum verification starting from v0.7.0
4545
To verify, run the command `shasum -a 256 -c <artifact_name>.sha256`
4646
It should return the output `<artifact_name>: OK` if the validation is successful

0 commit comments

Comments
 (0)