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.

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

Add GitHub Action to run composer outdated and composer audit #597

Closed
mrdavidburns opened this issue Jun 26, 2024 · 3 comments
Closed

Add GitHub Action to run composer outdated and composer audit #597

mrdavidburns opened this issue Jun 26, 2024 · 3 comments

Comments

@mrdavidburns
Copy link
Member

We have noticed on some projects that Renovate is not picking up major version upgrades or we have pinned versions that are not getting new releases. We would like to have a GitHub action that we can run on a weekly or monthly basis so that anyone with access to the logs of that job can identify these packages then we can create tickets to get those packages updated.

@justafish
Copy link
Member

@mrdavidburns is this not fixable by changing renovate's configuration?

@mrdavidburns
Copy link
Member Author

@justafish Yes, and we do have that configured for things like Drupal core major and point releases.
I created this when reviewing all our LSM projects and was running those 2 commands to determine if anything was being missed. It doesn't take long to checkout the latest code and run these commands manually. I was thinking this could be helpful to avoid having to do that step, but agree it probably isn't needed for all projects using Drainpipe.

Closing.

@YesCT
Copy link
Contributor

YesCT commented Aug 20, 2024

There have been cases where renovate did not alert us. I'll share a slack link in our internal devops channel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants