Repository navigation
fix(harp): require HaRP 0.4.8 in the version check - #1149
Conversation
1a35ccc to
e3003d0
Compare
ba20398 to
ce31091
Compare
ce31091 to
cae695c
Compare
Findings
|
Signed-off-by: Oleksandr Piskun <oleksandr2088@icloud.com>
Signed-off-by: Oleksandr Piskun <oleksandr2088@icloud.com>
Signed-off-by: Oleksandr Piskun <oleksandr2088@icloud.com>
cae695c to
c3fbf87
Compare
There was a problem hiding this comment.
Actionable comments posted: 1

Review info
-
Run configuration-
- Source mode: Auto
- Repository: Unavailable
- Branch: Unavailable
- File: No configuration file from this repository applied
- Commit: Unavailable
- Layers: Organization UI
- Review profile: CHILL
- Plan: Advanced
- Run ID:
22684b0e-db79-4ef2-bb56-77a6105873db
Files selected for processing: 2-
lib/SetupChecks/HarpVersionCheck.phptests/php/SetupChecks/HarpVersionCheckTest.php
Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 0 remain after this review.
-
AppAPI's setup check warns when a HaRP daemon is older than
MINIMUM_HARP_VERSION, which is still 0.3.0. HaRP 0.4.8 checks the HTTP method of requests to ExApps against the route verbs that AppAPI sends since #1138, so admins on older HaRP versions should be told to update.The check also caches the version of each daemon for a week, so an admin who had updated HaRP kept seeing the warning for up to a week.
Changes
MINIMUM_HARP_VERSIONis 0.4.8.