Nextcloud release not being picked up as a n+1 version #158

New Issue

decentral1se · 2021-05-03T07:42:37Z

decentral1se commented

2021-05-03 07:42:37 +00:00

➜  nextcloud (main) ✔ abra recipe nextcloud release
SUCCESS: All compose files updated; new version is 21.0.1
Commit your changes to git? (y/[n])?

Should be 21.0.1_1?

``` ➜ nextcloud (main) ✔ abra recipe nextcloud release SUCCESS: All compose files updated; new version is 21.0.1 Commit your changes to git? (y/[n])? ``` Should be `21.0.1_1`?

decentral1se added this to the Beta release milestone 2021-05-03 07:42:37 +00:00

decentral1se added the

bug

versioning

labels 2021-05-03 07:42:37 +00:00

3wordchant commented

2021-05-04 07:22:54 +00:00

I think this is because the 21.0.1 version isn't yet in apps.json.

If you re-run bin/app-json.py (I cheated and edited my local apps.json manually to define the new version) and then try abra recipe nextcloud release, you get 21.0.1_1 as expected.

I think this is because the 21.0.1 version isn't yet in `apps.json`. If you re-run `bin/app-json.py` (I cheated and edited my local `apps.json` manually to define the new version) and _then_ try `abra recipe nextcloud release`, you get `21.0.1_1` as expected.

👍 1

3wordchant closed this issue

2021-05-04 07:22:54 +00:00

3wordchant commented

2021-05-04 07:24:16 +00:00

Oh, maybe the close was over-hasty – I'm gonna reply over in #159 about the underlying versioning logic question, but if you think there's still some UI / doc change necessary here after that dust settles then pls reopen 🙏

👍 1

This repo is archived. You cannot comment on issues.