Add the release-note-none to dependabot

[afrittoli]

Changes

Without the release label, dependabot PRs cannot be merged.
Altering the PR to add the label means that dependabot won't
be able to manage its PR anymore, so adding the release note
label by default.

Signed-off-by: Andrea Frittoli [email protected]

/kind misc

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• Docs included if any changes are user facing
• Tests included if any functionality added or changed
• Follows the commit message standard
• Meets the Tekton contributor standards (including
  functionality, content, code)
• Release notes block below has been filled in
  (if there are no user facing changes, use release note "NONE")

Release Notes

NONE

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dibyom

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [dibyom]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[pritidesai]

Setting the release note to NONE sounds good but it will be useful if the PR approver can document which dependency was upgraded from what version. Thoughts?

[pritidesai]

/lgtm

[afrittoli]

Setting the release note to NONE sounds good but it will be useful if the PR approver can document which dependency was upgraded from what version. Thoughts?

That would be in the PR description created by dependabot, or are you thinking of some other place we should document it?
We could include it in the release notes but we've not done it until now.

[pritidesai]

Setting the release note to NONE sounds good but it will be useful if the PR approver can document which dependency was upgraded from what version. Thoughts?

That would be in the PR description created by dependabot, or are you thinking of some other place we should document it? We could include it in the release notes but we've not done it until now.

Thanks @afrittoli

Yeah I was thinking of including it in the release notes.

So the dependabot PRs has the details in the PR title that its upgrading a package from one version to the other. If we can automatically capture the same details in the PR release notes such that the release manager (task) can list them in a separate section when creating a release.