Skip to content

CI/CD improvements - #302

Open
azkrishpy wants to merge 1 commit into
mainfrom
ci-cd
Open

CI/CD improvements#302
azkrishpy wants to merge 1 commit into
mainfrom
ci-cd

Conversation

@azkrishpy

@azkrishpy azkrishpy commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Issue #, if available:

N/A

Description of changes:

Adds CI/CD workflows mirroring awslabs/aws-c-common#1250:

  • check-abi.yml — ABI compliance check on PRs
  • release.yml — manual (workflow_dispatch) release with auto version bump + tag
  • block-needs-review.yml — gate merges labeled needs-review
  • VERSION file seeded from latest release tag
  • CMakeLists.txt: derive target VERSION from VERSION file via aws_get_version()

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@github-actions github-actions Bot added the patch ABI backward-compatible (patch release) label Aug 12, 2026
@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.91%. Comparing base (16c7289) to head (2fa2698).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #302   +/-   ##
=======================================
  Coverage   81.91%   81.91%           
=======================================
  Files          36       36           
  Lines        7144     7144           
=======================================
  Hits         5852     5852           
  Misses       1292     1292           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@azkrishpy
azkrishpy marked this pull request as ready for review August 12, 2026 20:02

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

somewhere, we need to document this.
Will it be a concern if multiple developer try to kick off the action?
can we do something to prevent the action to run when there is another one in progress?
the abi check will take time, and it needs to build the package, right?
What if the build fails or some random failure goes on (eg: pull deps fails)?
How will the dev find it out?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

somewhere, we need to document this.

There is a guidance doc available for cutting releases. Will update it with some last minute stuff but the core idea already of auto releases already exists.

Will it be a concern if multiple developer try to kick off the action?

Worst case scenario is two people try to run release at the same time, one person commits to main first and the other person's commit fails since we don't force push the branch. They would have to restart release.

ref: https://github.com/awslabs/aws-crt-builder/blob/0cb166b3cb3f3cee1b61e5139919e7d3a2adca51/.github/actions/auto-release/scripts/cut-release.sh#L94

the abi check will take time, and it needs to build the package, right?
What if the build fails or some random failure goes on (eg: pull deps fails)?
How will the dev find it out?

Release job provides logs: https://github.com/awslabs/aws-c-common/actions/runs/31543641609
the abi-check action uses the builder package to build, so if the CI passes, we should not really have any issues building for the ABI check. (https://github.com/awslabs/aws-crt-builder/blob/0cb166b3cb3f3cee1b61e5139919e7d3a2adca51/.github/actions/check-abi/scripts/build.sh#L91).
If the ABI check fails, the release fails and the dev would have to look through the logs to investigate.

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

Labels

patch ABI backward-compatible (patch release)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants