[BUG] Publishing workflow does not generate GitHub releases anymore.

[mainrs]

Describe the bug
Although the APK file is available as a build artifact inside the publish-playstore workflow. The matching GitHub releases do not get created.

medito-app/.github/workflows/deploy_to_playstore.yml

Lines 100 to 109 in 5d26e6c

	- name: Create GH Release
	uses: softprops/action-gh-release@v1
	if: startsWith(github.ref, 'refs/tags/')
	with:
	body: |
	# Medito ${{ steps.release_version.outputs.version }}
	## What's New?
	NOTE: If you install Medito app using APK file, please make sure to verify that the APK file is signed by Medito Foundation. See [VERIFY_APK](VERIFY_APK.md) for more information.
	draft: true
	files: build/app/outputs/flutter-apk/medito-${{ steps.release_version.outputs.version }}.apk

The issue is that all updates seem to have failed before said action is executed. https://github.com/meditohq/medito-app/actions/runs/7645834161/job/20833316324. Tags have been published inside this repository. Meaning that the GH release step should have triggered. But it didn't.

It would be great if this can be fixed! Sadly, I am not familiar with flutter dev tools and fastlane, or else I would dig more into it.

[mainrs]

I investigated a little bit.

This is different from the one I can observse on workflows on GitHub. The newest, passing publish-playstore workflow actually triggers the GH release step, but the tag information is weird.

When I run the workflow locally using act, I do not even reach the GH release step, since the fastlane-deploy step fails (as expected).

[mainrs]

I also noticed this while investigating:
https://dcm.dev/blog/2023/06/06/announcing-dcm-free-version-sunset/