Too early 15.0 and 15.1 tags #104

Closed
opened 2026-08-09 13:12:27 +00:00 by ineiti · 1 comment
Owner

Hi @dannygroenewegen - I just realised that I pushed the 15.0 and 15.1 tags some weeks ago while testing ! Now I have no idea how many people are already on these tags. We can either:

  1. hope it's not too many, delete the tags, and replace with our own
  2. hurry up and release a 15.2.0 tag with all the pg-update changes

Sorry for that hickup!

Hi @dannygroenewegen - I just realised that I pushed the 15.0 and 15.1 tags some weeks ago while testing ! Now I have no idea how many people are already on these tags. We can either: 1. hope it's not too many, delete the tags, and replace with our own 2. hurry up and release a 15.2.0 tag with all the pg-update changes Sorry for that hickup!
Owner

Resolved, copy-paste from Matrix:

It is in the catalogue: https://recipes.coopcloud.tech/nextcloud

Looks like abra usually clones the main branch, and when running abra app upgrade it looks at the available tags in the local repo, so it won't find the 15... tags.

But abra app new nextcloud does use the catalogue. I was able to run abra app new nextcloud 15.1.1+34.0.1-fpm, but somehow this checkouts the main branch in recipes/nextcloud. But then when running deploy on the new app, it appears to get the tagged 15.1.1+34.0.1-fpm commit

It's probably best to remove the two 15 tags. Someone could have deployed those, but if they run upgrade there is no newer tag available so that doesn't break. And doesn't look like abra adds the prune argument when fetching, so the two 15... tags stay available in the local clone and will keep working.

Once we get to the actual 15 we release we should use a version number higher then these two tags so the upgrade works for anyone that has already did a new deploy of these faulty 15 tags.

Resolved, copy-paste from Matrix: > It is in the catalogue: https://recipes.coopcloud.tech/nextcloud > > Looks like abra usually clones the main branch, and when running `abra app upgrade` it looks at the available tags in the local repo, so it won't find the 15... tags. > > But `abra app new nextcloud` does use the catalogue. I was able to run `abra app new nextcloud 15.1.1+34.0.1-fpm`, but somehow this checkouts the main branch in recipes/nextcloud. But then when running deploy on the new app, it appears to get the tagged 15.1.1+34.0.1-fpm commit > > It's probably best to remove the two 15 tags. Someone could have deployed those, but if they run `upgrade` there is no newer tag available so that doesn't break. And doesn't look like abra adds the prune argument when fetching, so the two 15... tags stay available in the local clone and will keep working. > > Once we get to the actual 15 we release we should use a version number higher then these two tags so the upgrade works for anyone that has already did a new deploy of these faulty 15 tags.
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/nextcloud#104