dependabot / dependabot-core

🤖 Dependabot's core logic for creating update PRs.
https://docs.github.com/en/code-security/dependabot
MIT License
4.72k stars 1.02k forks source link

[npm] Missing PR description #10435

Open Araxeus opened 3 months ago

Araxeus commented 3 months ago

Is there an existing issue for this?

Package ecosystem

npm

Package manager version

bun (versioning-strategy: 'increase')

Language version

not specified

Manifest location and content before the Dependabot update

https://github.com/Araxeus/vendorfiles/blob/e297a22ece7ac2608c5e5ab2a0f742a3f5244643/package.json

dependabot.yml content

https://github.com/Araxeus/vendorfiles/blob/e297a22ece7ac2608c5e5ab2a0f742a3f5244643/.github/dependabot.yml

Updated dependency

   "devDependencies": {
     "@biomejs/biome": "^1.8.3",
     "@types/make-fetch-happen": "^10.0.4",
-    "@types/node": "^22.1.0",
+    "@types/node": "^22.2.0",
     "@types/parse-json": "^4.0.2",
     "cpy-cli": "^5.0.0",
     "del-cli": "^5.1.0",
-    "type-fest": "^4.23.0",
+    "type-fest": "^4.24.0",
     "typescript": "^5.5.4"
   },

What you expected to see, versus what you actually saw

expected: a description + changelog in the PR description

got:

image

Images of the diff or a link to the PR, issue, or logs

Here is the PR discussed in this issue: https://github.com/Araxeus/vendorfiles/pull/86

here is the workflow that triggered this PR: https://github.com/Araxeus/vendorfiles/actions/runs/10358579887/job/28673109563

Smallest manifest that reproduces the issue

I don't even know how this happened - last week it worked fine, see https://github.com/Araxeus/vendorfiles/pull/85

Araxeus commented 3 months ago

There seems to be a bug with your issue-labeler action - it added a L:go:modules tag to this issue after I edited the issue and wrote the wrote got

https://github.com/dependabot/dependabot-core/blob/3ce1165574ada0627fdf058156954848ca8293df/.github/issue-labeler.yml#L25-L26

this seems to match any text with go in it in any shape or form?

Araxeus commented 2 months ago

This bug started on the week of ~14 august 2024 and has been occurring since