jenkinsci / jenkinsci/implied-labels-plugin
Dependency Dashboard
- Dominant language
- Java
- Stars
- 5
- Forks
- 10
- Avg merge
- 1h 46m
- Merged PRs (30d)
- 1
Description
This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
The parent configuration is located in [jenkinsci/renovate-config](https://redirect.github.com/jenkinsci/renovate-config); Renovate logs for debug [here](https://developer.mend.io/github/jenkinsci/implied-labels-plugin).
## Awaiting Schedule
The following updates are awaiting their schedule. To get an update now, click on a checkbox below.
- [ ] Update dependency org.jenkins-ci.plugins:plugin to v6.2236.v12dd4c483242
## PR Closed (Blocked)
The following updates are blocked by an existing closed PR. To recreate the PR, click on a checkbox below.
- [ ] [Update dependency io.jenkins.tools.bom:bom-2.528.x to v6607](../pull/366)
## Detected Dependencies
github-actions (5)
.github/workflows/auto-merge-safe-deps.yml (1)
- `jenkins-infra/github-reusable-workflows v1@c2470861b1ad94810dc0d207b011e0b57bb91bbb`
.github/workflows/cd.yaml (1)
- `jenkins-infra/github-reusable-workflows v1@c2470861b1ad94810dc0d207b011e0b57bb91bbb`
.github/workflows/close-bom-if-passing.yml (1)
- `jenkins-infra/github-reusable-workflows v1@c2470861b1ad94810dc0d207b011e0b57bb91bbb`
.github/workflows/jenkins-security-scan.yml (1)
- `jenkins-infra/jenkins-security-scan v2@da7438f10fecc21e40174d420ef34daae0874122`
.github/workflows/labeler.yml (1)
- `actions/labeler v7@bf12e9b00b37c5c0ca2b87b79b2daf7891dbda13`
maven (2)
.mvn/extensions.xml (1)
- `io.jenkins.tools.incrementals:git-changelist-maven-extension 1.13`
pom.xml (2)
- `org.jenkins-ci.plugins:plugin 6.2221.va_045130417c9` → [Updates: `6.2236.v12dd4c483242`]
- `io.jenkins.tools.bom:bom-2.528.x 6210.v69ea_fd8a_f010` → [Updates: `6607.v3ed3d8ddfed8`]
renovate-config (1)
.github/renovate.json
---
- [ ] Check this box to trigger a request for Renovate to run again on this repository
Contributor guide
Research direction
Start with the Dependency Dashboard documentation, then inspect the dependency entries in pom.xml and the listed GitHub Actions workflow files. Use the dashboard checkbox or update the specified dependency, and consider the work done when the awaiting or blocked update is handled without unresolved dashboard entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, java
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100