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.

Sign up for GitHub

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

Jump to bottom

Wrong supported values for Dependabot update types #35862

Closed
1 task done
pomier opened this issue Jan 8, 2025 · 2 comments · Fixed by #35818
Closed
1 task done

Wrong supported values for Dependabot update types #35862

pomier opened this issue Jan 8, 2025 · 2 comments · Fixed by #35818
Labels
code security Content related to code security content This issue or pull request belongs to the Docs Content team

Comments

@pomier
Copy link

pomier commented Jan 8, 2025

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/code-security/dependabot/working-with-dependabot/dependabot-options-reference#ignore--

What part(s) of the article would you like to see updated?

For the ignore -> update-types field of the dependabot.yml file, the article specifies as supported values sem-ver:minor, sem-ver:patch, and sem-ver:major. When using one of those, the parsing fails with the following message:

Your .github/dependabot.yml contained invalid details

Dependabot encountered the following error when parsing your .github/dependabot.yml:

The property '#/updates/0/ignore/0/update-types/0' value "sem-ver:major" did not match one of the following values: version-update:semver-major, version-update:semver-minor, version-update:semver-patch

The documentation should specific the correct values accepted.

Additional information

No response
@pomier pomier added the content This issue or pull request belongs to the Docs Content team label Jan 8, 2025
@welcome Welcome
Copy link

welcome bot commented Jan 8, 2025

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@pomier pomier mentioned this issue Jan 8, 2025
Closed
3 tasks
@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Jan 8, 2025
@nguyenalex836 nguyenalex836 added code security Content related to code security and removed triage Do not begin working on this issue until triaged by the team labels Jan 8, 2025
@nguyenalex836
Copy link
Contributor

@pomier Thank you for opening an issue and linking it to your PR! ✨

@mchammer01 mchammer01 mentioned this issue Jan 9, 2025
Merged
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
code security Content related to code security content This issue or pull request belongs to the Docs Content team
Projects
None yet
Milestone
No milestone
2 participants
@pomier @nguyenalex836