Skip to content

fix: added secrets to workflow_call workflows #478

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 30, 2025

Conversation

lempira
Copy link
Contributor

@lempira lempira commented Jul 30, 2025

There are currently errors in the promote-to-prod workflow when running the release workflow. The release-desktop and release-web workflows are called from the release workflow, which means the secrets are passed automatically. The secrets were already being inherited but not imported by the workflow, so i added them.

These are some other updates

  • Added validation for missing release outputs that are needed crabnebula steps
  • Updated the conflict resolution in the sync-to-main job because it was failing on merge conflicts.

Copy link

Deploying algokit-lora with  Cloudflare Pages  Cloudflare Pages

Latest commit: 6b38e22
Status: ✅  Deploy successful!
Preview URL: https://383b3cd5.algokit-lora.pages.dev
Branch Preview URL: https://fix-secrets-inheritance-in-w.algokit-lora.pages.dev

View logs

@lempira lempira merged commit 3279acc into main Jul 30, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant