We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello,
A few days ago my scheduled action failed with Error: Cannot read properties of undefined (reading 'data'), for details see https://github.com/qianbinbin/fdroid-priv-ext/actions/runs/5779647317/job/15662229381
Error: Cannot read properties of undefined (reading 'data')
It doesn't reproduce for now, and before that the action ran for months smoothly.
My simple script:
- name: Release id: release if: ${{ steps.create.outputs.VERSION != '' }} uses: softprops/action-gh-release@v1 with: tag_name: ${{ steps.create.outputs.VERSION }} body: ${{ steps.create.outputs.CHANGELOG }} files: build/*
The full version is here.
Any help is appreciated.
The text was updated successfully, but these errors were encountered:
same issue
Sorry, something went wrong.
It turns out the tag_name should follow certain convention, which means you have to add 'v' at the start. In my case, I only give 1.x.x.
Thanks for your reply, but if so why it ran for months very well?
My tag_name was like 20231205, without the starting v as well. It doesn't seem to be a compulsory convention.
20231205
v
We are facing the same problem.. job ran fine months ago, now getting the error. we use vX.X.X naming scheme
No branches or pull requests
Hello,
A few days ago my scheduled action failed with
Error: Cannot read properties of undefined (reading 'data')
, for details see https://github.com/qianbinbin/fdroid-priv-ext/actions/runs/5779647317/job/15662229381It doesn't reproduce for now, and before that the action ran for months smoothly.
My simple script:
The full version is here.
Any help is appreciated.
The text was updated successfully, but these errors were encountered: