View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009921 | Taler | release | public | 2025-05-09 16:12 | 2025-05-09 17:58 |
| Reporter | sebasjm | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | confirmed | Resolution | open | ||
| Target Version | post-1.0 | ||||
| Summary | 0009921: improve check-prebuilt | ||||
| Description | we should not depend on the spa dev to update the contrib folder we can improve this by adding some standardization to the process: * ./contrib/check-prebuilt check - verify that the local .lock file match the prebuilt git folder (already implemented) - fetch the latest updates from prebuilt folder - verify that there is no missing update - report a soft warning if it found that a new version is available, don't fail * ./contrib/check-prebuilt update - update the local brach of the `prebuilt` folder to the remote branch `prebuilt` * ./contrib/check-prebuilt upgrade - update the local lock file to the current version of the `prebuilt` folder * ./contrib/check-prebuilt check-latest (useful to check before creating a release) - same as check but fail if is not the latest * ./contrib/check-prebuilt commit-id (useful to check what changed in the spa, or what's missing) - report the commit id of the released version from the source repo - search the local history of the contrib folder when was the latest change of the project folder - the commit message shoud be something like "built from commit xxxx" - return XXXX * rename to ./contrib/check-$PROJECT-prebuilt | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-05-09 16:12 | sebasjm | New Issue | |
| 2025-05-09 17:58 | Christian Grothoff | Status | new => confirmed |
