Guess what?!
A new upstream version of composer/semver is now available: 3.2.5.
Description
Description
Details
Details
Related Changes in Gerrit:
Related Objects
Related Objects
Event Timeline
Comment Actions
@Legoktm Is this because LibUp doesn't know what to do with "composer/semver": "^1.7.2|^3.2.4",?
Comment Actions
LibUp's upstream monitoring functionality is very dumb and doesn't actually look at what the repo has configured, just files tasks when it sees a new version based on the configured tags: https://gerrit.wikimedia.org/r/plugins/gitiles/labs/libraryupgrader/config/+/refs/heads/master/monitoring.json#15
We could remove Parsoid from there if you'd like, with the expectation that whenever a 4.x comes out, a human will tag Parsoid in the task that LibUp files.
Comment Actions
We could remove Parsoid from there if you'd like, with the expectation that whenever a 4.x comes out, a human will tag Parsoid in the task that LibUp files.
No, it's fine. Was just wondering how it compared to something like dependabot that would send a pull request instead
Comment Actions
Change 734396 had a related patch set uploaded (by Arlolra; author: Arlolra):
[mediawiki/services/parsoid@master] Bump some dependencies to match upstream
Comment Actions
Change 734396 merged by jenkins-bot:
[mediawiki/services/parsoid@master] Bump some dependencies to match upstream
Comment Actions
Change 734972 had a related patch set uploaded (by Subramanya Sastry; author: Subramanya Sastry):
[mediawiki/vendor@master] Bump remex-html to 3.0.0 and parsoid to 0.15.0-a6
Comment Actions
Change 734972 merged by jenkins-bot:
[mediawiki/vendor@master] Bump remex-html to 3.0.0 and parsoid to 0.15.0-a6