v2.2.* to v2.2.1 Upgrade Guide

Breaking Changes

• New ESI scope esi-search.search_structures.v1" needed (749c40f35f253946f4559c9533d3c0f6c1068fd0)
• Adjust .env file and replace the line beginning with CCP_ESI_SCOPES= with CCP_ESI_SCOPES="esi-location.read_online.v1,esi-location.read_location.v1,esi-location.read_ship_type.v1,esi-ui.write_waypoint.v1,esi-ui.open_window.v1,esi-universe.read_structures.v1,esi-corporations.read_corporation_membership.v1,esi-clones.read_clones.v1,esi-characters.read_corporation_roles.v1,esi-search.search_structures.v1"
• Adjust your application on developers.eveonline.com and add the scope esi-search.search_structures.v1

Upgrade Steps:

This guide assumes you are using our Pathfinder-Containers solution for running Pathfinder. If you are not then your upgrade path will be slightly different, but hopefully this gives a general outline of the steps required.

1. Follow all of the steps in the General Upgrade Guide.
2. If your project won't build (ie. docker-compose up --build or git stash apply fails, this could be due to merge conflicts in your docker-compose file. This will looks something like this:

<<<<<<< Updated upstream
      - "--certificatesresolvers.letsencrypt.acme.email=MYEMAIL@someemailprobablygmail.com"
=======
      - "--certificatesresolvers.letsencrypt.acme.storage=/letsencrypt/acme.json"
>>>>>>> Stashed changes

This block is asking you to keep one or the other. If you're unfamiliar with how to resolve these conflicts, and how significant-whitespace works in yml files, you might just want to paste over the whole file with the correct version with the staging letsencrypt lines removed.

3. When your users try to log their characters back in, PF may ask for additional character ESI scopes.