You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What you expected to see, versus what you actually saw
I am using cookiecutter templates that generate as well GitHub workflows that include some Jinja2 code.
Now that #6189 has been implemented, dependabot started to parse the cookiecutter workflow templates but it results in failures:
Dependabot can't parse your quality.yml
Dependabot failed to update your dependencies because there was an error parsing the quality.yml found at /{{cookiecutter.repo_name}}/.github/workflows/quality.yml.
Dependabot encountered the following error:
Dependabot::DependencyFileNotParseable
[Learn more](https://docs.github.com/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)
martinm82
changed the title
Dependabot throws error when scanning cookiecutter template folder
Workflow files containing Jinja2 code result in dependabot parsing errors
Nov 24, 2022
martinm82
changed the title
Workflow files containing Jinja2 code result in dependabot parsing errors
Workflows containing Jinja2 code result in dependabot parsing errors
Nov 24, 2022
Hmm... GitHub actions aren't python, and don't have native support for Jinja2. The error is correct that it's not actually a valid parsable actions file.
In other words, you're passing a template that can be processed into a valid file, but not a valid file. And we aren't going to add support for templates--there's too many possible templating languages and each language ecosystem has their own preferred one it seems.
To avoid the error I suggest instead not having Dependabot watch that directory of templates.
If your directory has a mixture of files, some valid and some template, then you may be interested in:
Is there an existing issue for this?
Package ecosystem
github-actions
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
No response
dependabot.yml content
Updated dependency
No response
What you expected to see, versus what you actually saw
I am using cookiecutter templates that generate as well GitHub workflows that include some Jinja2 code.
Now that #6189 has been implemented, dependabot started to parse the cookiecutter workflow templates but it results in failures:
Example workflow:
It seems that Jinja2 is supported but only for Python requirements files: #1537
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response
The text was updated successfully, but these errors were encountered: