Skip to content

ci: Automate Dependabot configuration generation#9188

Merged
tekton-robot merged 2 commits intotektoncd:mainfrom
vdemeester:8572-dependabot-per-branch
Apr 24, 2026
Merged

ci: Automate Dependabot configuration generation#9188
tekton-robot merged 2 commits intotektoncd:mainfrom
vdemeester:8572-dependabot-per-branch

Conversation

@vdemeester
Copy link
Copy Markdown
Member

Changes

  • Generate the dependabot configuration to handle LTS branches in
    order to prevent release branches dependencies drift and reduce manual
    effort in maintaining per-branch dependency updates
  • For release branches, only bump dependencies on patch versions
  • Enable weekly automated checks with PR creation on changes

Signed-off-by: Vincent Demeester vdemeest@redhat.com

/kind misc
/area automation

Closes #8572

Submitter Checklist

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

  • Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
  • Has Tests included if any functionality added or changed
  • pre-commit Passed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

@tekton-robot tekton-robot added kind/misc Categorizes issue or PR as a miscellaneuous one. release-note-none Denotes a PR that doesnt merit a release note. labels Nov 28, 2025
@tekton-robot tekton-robot added the area/automation Issues that are related to automation aspects of the website or other projects. label Nov 28, 2025
@tekton-robot tekton-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Nov 28, 2025
@vdemeester vdemeester force-pushed the 8572-dependabot-per-branch branch 2 times, most recently from aa84d12 to 0e0a14c Compare November 28, 2025 13:11
Copy link
Copy Markdown
Member

@afrittoli afrittoli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this. Perhaps for some ecosystems (like GHA), we could setup auto merge if CI passes on release branches, otherwise it will become a lot of work only to approve all the PRs for the various branches 😅

@vdemeester
Copy link
Copy Markdown
Member Author

Thanks for this. Perhaps for some ecosystems (like GHA), we could setup auto merge if CI passes on release branches, otherwise it will become a lot of work only to approve all the PRs for the various branches 😅

Agreed 👼🏼 But note that we would only update patch dependencies, and it would only do it for the LTSes branches, so it shouldn't be that bad I guess/hope.

Also, we could do it today, by applying the labels (lgtm and approved) directly when creating the pull-request 🧌

@tekton-robot tekton-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 19, 2025
@vdemeester vdemeester force-pushed the 8572-dependabot-per-branch branch from 0e0a14c to 934cc29 Compare January 30, 2026 15:12
@tekton-robot tekton-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 30, 2026
@vdemeester
Copy link
Copy Markdown
Member Author

/retest

Copy link
Copy Markdown
Member

@waveywaves waveywaves left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

anticipating this to be opened on Monday !

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 27, 2026
@tekton-robot
Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: waveywaves

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 27, 2026
@tekton-robot tekton-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 17, 2026
@vdemeester vdemeester force-pushed the 8572-dependabot-per-branch branch from 934cc29 to 11d6202 Compare March 27, 2026 11:16
@tekton-robot tekton-robot removed lgtm Indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Mar 27, 2026
@vdemeester vdemeester force-pushed the 8572-dependabot-per-branch branch from 11d6202 to aa2afc4 Compare March 27, 2026 11:19
Comment on lines +18 to +22
release-branches:
- release-v1.9.x
- release-v1.6.x
- release-v1.3.x
- release-v1.0.x
Copy link
Copy Markdown
Member

@aThorp96 aThorp96 Apr 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be be automatically updated I think, it should be coming from a source of truth elsewhere

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, for now, the only "source of truth" is the release.md markdown, but not necessarily easy to parse. For now I thought it would make sense to have a post release checklist item for this.. but agreeing that mid/long term it needs to be automated.

Copy link
Copy Markdown
Member

@aThorp96 aThorp96 Apr 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmmm, yeah that's not super clean to parse as the source of truth. It could be done using an awk oneliner but it's a little ugly/archaic so not a blocker

E.g. this awk script searches for any 3rd-level heading under ## Release (stops searching at the next 2nd-level heading) which match the regex ### \d+\.\d+, then rewrites the \d\.\d version into the branch name.

 $ awk '/^## Release$/{found=1; next} found && /^## /{exit} found && /^### v[0-9]+\.[0-9]+/{sub(/^### /, "release-"); sub(/( \(LTS\))?\s*$/, ".x"); print}' releases.md
release-v1.11.x
release-v1.9.x
release-v1.6.x
release-v1.3.x
release-v1.0.x

Note though that regex doesn't check for \(LTS\)$ so it lists release-v1.11.x which is not included in this PR's list.

If we want to leave this list as hardcoded can we update the post-release checklist in this same PR?

Comment thread hack/generate-dependabot.sh Outdated
Comment thread hack/generate-dependabot.go Outdated
Comment thread hack/generate-dependabot.sh
@vdemeester vdemeester force-pushed the 8572-dependabot-per-branch branch from aa2afc4 to 8372e7b Compare April 23, 2026 07:14
@vdemeester vdemeester force-pushed the 8572-dependabot-per-branch branch from 8372e7b to 66588c2 Compare April 23, 2026 07:14
Copy link
Copy Markdown

@github-advanced-security github-advanced-security AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

zizmor found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.

- Generate the dependabot configuration to handle LTS branches in
  order to prevent release branches dependencies drift and reduce manual
  effort in maintaining per-branch dependency updates
- For release branches, only bump dependencies on patch versions
- Enable weekly automated checks with PR creation on changes
- Generate release-branches list dynamically from releases.md

Closes tektoncd#8572

Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
@vdemeester vdemeester force-pushed the 8572-dependabot-per-branch branch from 66588c2 to 4b9f4dd Compare April 23, 2026 07:17
- Add persist-credentials: false to checkout step
- Move all ${{ }} expressions from run: blocks to env: blocks
  to prevent template injection vulnerabilities

Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
@vdemeester
Copy link
Copy Markdown
Member Author

/retest

@afrittoli
Copy link
Copy Markdown
Member

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 24, 2026
@tekton-robot tekton-robot merged commit 42b30d4 into tektoncd:main Apr 24, 2026
39 of 41 checks passed
@vdemeester vdemeester deleted the 8572-dependabot-per-branch branch April 24, 2026 09:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/automation Issues that are related to automation aspects of the website or other projects. kind/misc Categorizes issue or PR as a miscellaneuous one. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

No open projects
Status: Todo

Development

Successfully merging this pull request may close these issues.

Dependabot for *active* release branches

6 participants