Skip to content
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

Cannot read property 'data' of undefined #221

Open
UebelAndre opened this issue Mar 18, 2022 · 3 comments
Open

Cannot read property 'data' of undefined #221

UebelAndre opened this issue Mar 18, 2022 · 3 comments

Comments

@UebelAndre
Copy link

I ran into the following error in a recent github action

Error: Cannot read property 'data' of undefined

The step is defined here: https://github.com/bazelbuild/rules_rust/blob/635da93206c2761d9db58ed82e194d2af053faf6/.github/workflows/release.yaml#L134-L143

@Locietta
Copy link

Locietta commented Apr 9, 2022

Any update about this issue?
I'm running into the same problem, and unfortunately rerun the workflow doesn't resolve it.

There is the action log, wierd thing is that the exact same .yml file works perfectly in previous releases.

@oblivioncth
Copy link

I ran this action on a test repository and had it complete successfully early today, I then moved the workflow over to my actual repo, from which the test was mirrored. I made some unrelated changes, then ran it and got the same error (Cannot read property 'data' of undefined) on what was nearly the same repository.

I thought this might have been because the real repository didn't have any release at all yet and I have generate_release_notes on, as perhaps the GitHub API doesn't handle when there is nothing to compare to elegantly, but based on the other two comments that doesn't seem to be the case.

@oblivioncth
Copy link

Just wanted to report back that it turns out I actually did have an indentation issue with .github/release.yml, as I tried to use the UI to generate the notes for a manual release after my last release workflow failure (which unfortunately failed due to a typo this time and not because of the title issue).

I redid a release after correcting that file and this time the action worked correctly.

So if you use auto generated release notes or any other GitHub based mechanism, you may just want to go through everything with a fine-toothed comb and make sure it all checks out.

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

No branches or pull requests

3 participants