Releases: cerc-io/stack-orchestrator
Releases · cerc-io/stack-orchestrator
v1.1.0-09a1cbb-202404260545
Additional env configuration in graph-node stack (#812) Part of [Deploy v2 and updated v3 sushiswap subgraphs](https://www.notion.so/Deploy-v2-and-updated-v3-sushiswap-subgraphs-e331945fdeea487c890706fc22c6cc94) Reviewed-on: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/812 Co-authored-by: Prathamesh Musale <[email protected]> Co-committed-by: Prathamesh Musale <[email protected]>
v1.1.0-13ce521-202404232147
Fix config dir processing for external stacks (#810) Reviewed-on: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/810 Co-authored-by: David Boreham <[email protected]> Co-committed-by: David Boreham <[email protected]>
v1.1.0-6e4dae9-202404182123
Add external stack support (#806) Reviewed-on: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/806 Co-authored-by: David Boreham <[email protected]> Co-committed-by: David Boreham <[email protected]>
v1.1.0-7f84a45-202404151859
Switch repo to cerc-io org. (#804) Update stack to track moved repo. Reviewed-on: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/804 Reviewed-by: David Boreham <[email protected]>
v1.1.0-4126f2f-202404151220
Add --fqdn-policy option to deploy-webapp-from-registry. (#802) This add a new option `--fqdn-policy` to the `deploy-webapp-from-registry`. The default policy, `prohibit` means that `ApplicationDeploymentRequests` which specify a FQDN will be rejected. The `allow` policy will cause them to be processed. The `preexisting` policy will only process them if an existing `DnsRecord` exists in the registry with the correct ownership. The latter would be useful in conjunction with a pre-checking scheme in the UI (eg, that the DNS entry is properly configured, the domain is under the control of the requestor, etc.) Only after all the checks were successful would the `DnsRecord` be created, allowing for `ApplicationDeploymentRequests` to use it. Reviewed-on: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/802 Reviewed-by: David Boreham <[email protected]> Co-authored-by: Thomas E Lackey <[email protected]> Co-committed-by: Thomas E Lackey <[email protected]>
v1.1.0-87fffca-202404110321
fixturenet-plugeth Deneb/Cancun upgrade (#789) Updates fixturenet-plugeth stack for the Deneb fork based on Geth v1.13.x: - updates genesis generator tool, and simplifies the config: the default from `ethereum-genesis-generator` can be used for a from-genesis Merged chain. Reviewed-on: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/789 Reviewed-by: jonathanface <[email protected]> Reviewed-by: Thomas E Lackey <[email protected]>
v1.1.0-66b92df-202404081551
Merge pull request 'Blast stack' (#777) from blast-stack into main Reviewed-on: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/777
v1.1.0-9cd34ff-202404050828
Add Slack alerts for failures on CI workflows (#793) Part of https://www.notion.so/Alerting-for-failing-CI-jobs-d0183b65453947aeab11dbddf989d9c0 Reviewed-on: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/793 Co-authored-by: Prathamesh Musale <[email protected]> Co-committed-by: Prathamesh Musale <[email protected]>
v1.1.0-40f3625-202404050926
Run CI alert steps only on main (#797) Part of https://www.notion.so/Alerting-for-failing-CI-jobs-d0183b65453947aeab11dbddf989d9c0 - Run CI alert steps only on main to avoid alerts for in-progress PRs - The Slack alerts will be sent on a CI job failure if - A commit is pushed directly to main - A PR gets merged into main - A scheduled job runs on main Reviewed-on: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/797 Co-authored-by: Prathamesh Musale <[email protected]> Co-committed-by: Prathamesh Musale <[email protected]>
v1.1.0-515f6d1-202404041050
Fix laconic registry CLI tests (#792) Part of https://www.notion.so/Test-registry-cli-in-SO-fixturenet-laconicd-CI-ef1f497678264362931bd12643ba8a17 Reviewed-on: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/792 Co-authored-by: Prathamesh Musale <[email protected]> Co-committed-by: Prathamesh Musale <[email protected]>