build: add release and artifact upload to contracts build CI#146
Merged
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
vicentevieytes
changed the title
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR replaces the existing contracts build workflow with an enhanced version that adds artifact packaging and release functionality. The new workflow builds contracts, runs tests, packages the output, and creates GitHub releases for main branch commits.
- Replaced the simple build workflow with a comprehensive build-test-release pipeline
- Added change detection to optimize CI runs by only executing when contracts or workflow files change
- Integrated artifact upload and GitHub release creation with SHA-based tagging
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| .github/workflows/contracts-build.yml | Removes the original simple build workflow |
| .github/workflows/contracts-build-test-release.yml | Adds new comprehensive workflow with change detection, packaging, and release functionality |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
vicentevieytes
commented
Sep 2, 2025
patricios-space
previously approved these changes
Sep 2, 2025
krebernisak
reviewed
Sep 3, 2025
| name: TON Contracts Build (${{ steps.get_sha.outputs.short_sha }}) | ||
| draft: false | ||
| prerelease: false | ||
| files: | |
Collaborator
There was a problem hiding this comment.
Why do we actually need this?
Can't we just:
- During active development, run
TON_CONTRACTS_DIR=$(nix build 'git+https://github.com/smartcontractkit/chainlink-ton#contracts' --print-out-paths)will get you the latest from anywhere (e.g., core repo, cld repo) - Once we have a stable version, we make a release, and pin it where we need it
TON_CONTRACTS_DIR=$(nix build 'git+https://github.com/smartcontractkit/chainlink-ton?ref=v0.1.1#contracts' --print-out-paths)
Not sure why we need custom releases on every commit for this.
Collaborator
Author
There was a problem hiding this comment.
Yeah I agree this is not the cleanest
krebernisak
reviewed
Sep 3, 2025
krebernisak
reviewed
Sep 5, 2025
… vv/publish-contracts-build
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
Updates the TON - Contracts workflow to publish a release with the build artifacts after merging to main.
Example: https://github.com/smartcontractkit/chainlink-ton/releases/tag/ton-contracts-build-3e7567f120be
Description
The workflow now only runs when there are changes to the contracts/** files and filters out artifacts compiled with the
exampleprefix.