chore: move the aptos smoke workflow back to develop by cawthorne · Pull Request #417 · smartcontractkit/chainlink-aptos

cawthorne · 2026-04-02T12:47:58Z

Summary

switch the Aptos smoke workflow back to chainlink develop by default
explicitly opt the generated core TOML into mock-streams-trigger@1.0.0 so the existing workflow smoke path still works with gated core registration
make the PR-body override accept the documented core_ref:<ref>; syntax
remove the stale README note that said develop could not work yet

bash .github/actions/get-core-ref/test_get_core_ref.sh
parsed integration-tests/templates/core.toml through the chainlink TOML types from feature/aptos-develop-mock-trigger
full smoke run is still blocked locally in this session because the Docker daemon is not running

cawthorne had a problem deploying to integration April 2, 2026 12:48 — with GitHub Actions Error

chore: move aptos smoke workflow back to develop

c44e7a7

cawthorne force-pushed the feature/aptos-off-aptos-init branch from 6b228fd to c44e7a7 Compare April 2, 2026 13:07

cawthorne had a problem deploying to integration April 2, 2026 13:08 — with GitHub Actions Failure

fix: point aptos smoke at paired core branch

1a8c132

cawthorne had a problem deploying to integration April 2, 2026 14:10 — with GitHub Actions Failure

fix: preserve mock trigger config in smoke harness

106c06a

cawthorne temporarily deployed to integration April 2, 2026 15:26 — with GitHub Actions Inactive