Loading...
 
Skip to main content

composer.lock; automate the updates for each branch, from latest composer.json

  • Tracker item actions
Trackers
Items
Status
Closed
Subject
composer.lock; automate the updates for each branch, from latest composer.json
Category
  • Community projects
  • Feature request
Feature
Installer (profiles, upgrades and server-related issues)
Resolution status
Fixed or Solved
Submitted by
Marc Laporte
Lastmod by
Marc Laporte
Rating
(0)
Description

composer.lock needs to updated

  • when composer.json is updated
  • to get updates on any of our 100+ dependencies


Tiki developers sometimes waste time with this. Let's automate.

It should be ran with the right version of PHP (the lowest supported for that Tiki version)

Also, each branch needs to be run independently (you should't merge the results of one branch in another). So this should be excluded from the script at Semi-automatic merging period

We need a robot SourceForge user name. Ex: tikicibot


One example: (up for discussion):

  1. Check all changes on composer.json and update immediately composer.lock (because a dev working on something likely wants to see immediate results)
  2. Update composer.lock every 10 days on supported branches. So we get somewhat frequent updates. Since composer.json is set for semantic versioning, it should not cause regressions.


Also, there is some weirdness where the composer.tiki.org URLs are changed to the external sources like Github.
http://sourceforge.net/p/tikiwiki/code/68089
This automation should keep everything on composer.tiki.org

This should also be done by the release script

Importance
5
Easy to solve?
5
Priority
25
Demonstrate Bug on Tiki 19+
Demonstrate Bug (older Tiki versions)
Ticket ID
6881
Created
Wednesday 24 October, 2018 11:03:21 UTC
by Marc Laporte
LastModif
Sunday 08 March, 2020 11:03:35 UTC


Show PHP error messages