adding a Makefile target that copies the files from the upstream dist folder for a given release (tag) (hard-code the release/tag in the Makefile)
adding a CL item to the upgrade issue that reminds operators to periodically check for a new release of Swagger UI and update to it if possible
adding a section to the operator manual, documenting the procedure of selecting an upstream release, as well as copying and testing it
The operator manual should mention that the message of the commit that updates the Swagger UI must reference the exact release/tag in the title, and the link to the release/tag in the body.
… and ensure it is kept up-to-date updated by:
adding a Makefile target that copies the files from the upstream dist folder for a given release (tag) (hard-code the release/tag in the Makefile)
adding a CL item to the upgrade issue that reminds operators to periodically check for a new release of Swagger UI and update to it if possible
adding a section to the operator manual, documenting the procedure of selecting an upstream release, as well as copying and testing it
The operator manual should mention that the message of the commit that updates the Swagger UI must reference the exact release/tag in the title, and the link to the release/tag in the body.