@sgiehl
Description:
As our composer requirements are almost all configured to only allow minor or patch release updates, it should be fine to run this action weekly in order to check if any updates are available.
The first PR created after merging this might be a bit bigger, as we didn't update the dependencies for a while.
Updates to major version will still need to be done manually, as they require a change in composer.json
Review
- [ ] Functional review done
- [ ] Potential edge cases thought about (behavior of the code with strange input, with strange internal state or possible interactions with other Matomo subsystems)
- [ ] Usability review done (is anything maybe unclear or think about anything that would cause people to reach out to support)
- [ ] Security review done
- [ ] Wording review done
- [ ] Code review done
- [ ] Tests were added if useful/possible
- [ ] Reviewed for breaking changes
- [ ] Developer changelog updated if needed
- [ ] Documentation added if needed
- [ ] Existing documentation updated if needed
@Findus23
Maybe this could also run a composer outdated so that one can immediately see from the log if there is anything that needs major upgrades?
Maybe this could also run a composer outdated so that one can immediately see from the log if there is anything that needs major upgrades?
We need to find another process for major updates. Maybe another action could automatically create issues for packages that have a major update. See https://github.com/matomo-org/developer-documentation/pull/547
@github-actions[bot]
This issue is in "needs review" but there has been no activity for 7 days. ping @matomo-org/core-reviewers
This issue is in "needs review" but there has been no activity for 7 days. ping @matomo-org/core-reviewers