One thing I overlooked at #56 is that events triggered by the GITHUB_TOKEN will not create a new workflow run (as stated here). This means that the build workflow will not be triggered when the check-for-new-cascadia workflow creates a new tag because GITHUB_TOKEN was used to create it. This limitation also means that Workflow Dispatch would also require a personal access token to dispatch other workflows (it is a required input for the action).
This fixes the problem by combining the two workflows together so that you do not need to call the other workflow which requires your token.
Truly resolves #48.
One thing I overlooked at #56 is that events triggered by the
GITHUB_TOKEN
will not create a new workflow run (as stated here). This means that thebuild
workflow will not be triggered when thecheck-for-new-cascadia
workflow creates a new tag becauseGITHUB_TOKEN
was used to create it. This limitation also means that Workflow Dispatch would also require a personal access token to dispatch other workflows (it is a required input for the action).This fixes the problem by combining the two workflows together so that you do not need to call the other workflow which requires your token.