build: use stellar.expert verified build workflow#10
Merged
Conversation
Collaborator
|
Yesterday I created https://github.com/stellar-registry/actions. This action was a copy/paste of the linked one. The big difference was that we use scaffold stellar to build so that we can embed the other metadata. |
chadoh
force-pushed
the
feat/stellar-expert-verified-build
branch
from
199c463 to
a17c580
Compare
Member
Author
|
@willemneal and I discussed on a call and decided we will use the Stellar.Expert workflow for now, with a modified Stellar Registry workflow slated for Q3 |
willemneal
approved these changes
Jul 6, 2026
willemneal
approved these changes
Jul 6, 2026
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
2 participants
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.
Copying the approach used by https://github.com/Consulting-Manao/tansu/blob/main/.github/workflows/contract-release.yml