Skip to content

Update backend dependencies: Symfony

Alex requested to merge update-symfony-dependencies into master

What does this MR do?

Minor version updates of symfony/* backend dependencies.

How confident are you it won't break things if deployed?

Seems to work. The minor versions shouldn't break anything. Let's say 90%

How to test

  1. Checkout branch locally
  2. Run ./scripts/composer update symfony
  3. Run ./scripts/seed (depends on symfony/console)
  4. Login as foodsaver
  5. Check that everything works as usual, especially:
    • create a forum thread, update a working group's description (depends on symfony/validator, symfony/form)
    • anything that requires a call to the rest api, e.g. login, writing messages, ... (depends on symfony/http-kernel, symfony/http-foundation)
    • check the links in the infos menu, e.g. "Blog" and "Mission" (depends on symfony/routing)

Checklist

  • added a test, or explain why one is not needed/possible...
  • no unrelated changes
  • asked someone for a code review
  • set a "for:" label to indicate who will be affected by this change
  • added to the next milestone (see https://gitlab.com/foodsharing-dev/foodsharing/-/milestones, unless it has a "for:Dev" label)
  • added an entry to CHANGELOG.md
  • added a short text that can be used in the release notes
  • Once your MR has been merged, you are responsible to create a testing issue in the Beta Testing forum: https://foodsharing.de/?page=bezirk&bid=734&sub=forum. Please change the MRs label to "state:Beta testing".
    • Consider writing a detailed description in German.
    • Describe in a few sentences, what should be tested from a user perspective.
    • Also mention different settings (e.g. different browsers, roles, ...) how this change can be tested.
    • Be aware, that also non technical people should understand.

Release notes text in German

Merge request reports