Properly publish this recipe 🙃 #9

New Issue

2024-12-09T15:44:03Z

basebuilder commented

2024-12-09 15:44:03 +00:00

Upon the realization that this recipe is not properly published, I just tried using abra recipe sync for the first time and it produced the follow FATA error:

$:~/.abra/recipes/parasol-static-site$ abra recipe sync parasol-static-site

You need to make a decision about what kind of an update this new recipe
version is. If someone else performs this upgrade, do they have to do some
migration work or take care of some breaking changes? This can be signaled in
the version you specify on the recipe deploy label and is called a semantic
version.

The latest published version is v0.1.0.

Here is a semver cheat sheet (more on https://semver.org):

    major: new features/bug fixes, backwards incompatible (e.g 1.0.0 -> 2.0.0).
           the upgrade won't work without some preparation work and others need
           to take care when performing it. "it could go wrong".

    minor: new features/bug fixes, backwards compatible (e.g. 0.1.0 -> 0.2.0).
           the upgrade should Just Work and there are no breaking changes in
           the app and the recipe config. "it should go fine".

    patch: bug fixes, backwards compatible (e.g. 0.0.1 -> 0.0.2). this upgrade
           should also Just Work and is mostly to do with minor bug fixes
           and/or security patches. "nothing to worry about".

? select recipe version increment type minor
WARN[0020] no existing label found, automagic insertion not supported yet 
FATA[0020] add '- "coop-cloud.${STACK_NAME}.version=v0.2.0+1.25.3-alpine"' manually to the 'app' service in /home/user/.abra/recipes/parasol-static-site/compose.yml

While I created the repo parasol-static-site and it was my idea of how to weave these pieces together @decentral1ze did the heavy lifting and I have not read the Packaging Handbook properly so I assume this error has to do with something I did not do properly to finish this off.

Upon the realization that this recipe is not properly published, I just tried using `abra recipe sync` for the first time and it produced the follow `FATA` error: ``` $:~/.abra/recipes/parasol-static-site$ abra recipe sync parasol-static-site You need to make a decision about what kind of an update this new recipe version is. If someone else performs this upgrade, do they have to do some migration work or take care of some breaking changes? This can be signaled in the version you specify on the recipe deploy label and is called a semantic version. The latest published version is v0.1.0. Here is a semver cheat sheet (more on https://semver.org): major: new features/bug fixes, backwards incompatible (e.g 1.0.0 -> 2.0.0). the upgrade won't work without some preparation work and others need to take care when performing it. "it could go wrong". minor: new features/bug fixes, backwards compatible (e.g. 0.1.0 -> 0.2.0). the upgrade should Just Work and there are no breaking changes in the app and the recipe config. "it should go fine". patch: bug fixes, backwards compatible (e.g. 0.0.1 -> 0.0.2). this upgrade should also Just Work and is mostly to do with minor bug fixes and/or security patches. "nothing to worry about". ? select recipe version increment type minor WARN[0020] no existing label found, automagic insertion not supported yet FATA[0020] add '- "coop-cloud.${STACK_NAME}.version=v0.2.0+1.25.3-alpine"' manually to the 'app' service in /home/user/.abra/recipes/parasol-static-site/compose.yml ``` While I created the repo `parasol-static-site` and it was my idea of how to weave these pieces together @decentral1ze did the heavy lifting and I have *not* read the [Packaging Handbook](https://docs.coopcloud.tech/maintainers/handbook/) properly so I assume this error has to do with something I did not do properly to finish this off.

basebuilder self-assigned this 2024-12-09 15:44:03 +00:00

ammaratef45 referenced this issue from toolshed/organising

2024-12-09 15:56:24 +00:00

Support automagic insertion in packaging #655

ammaratef45 commented

2024-12-09 15:56:42 +00:00

toolshed/organising#655

https://git.coopcloud.tech/toolshed/organising/issues/655

ammaratef45 referenced this issue from a commit

2024-12-10 03:07:10 +00:00

#9 adding coop-cloud version label

ammaratef45 commented

2024-12-10 03:09:25 +00:00

? current: v0.1.0, new: v0.2.0+1.25.3-alpine, correct? Yes
? Release Note (leave empty for no release note)
? publish new release? Yes
INFO[0017] new release published: https://git.coopcloud.tech/coop-cloud/parasol-static-site/src/tag/v0.2.0+1.25.3-alpine

``` ? current: v0.1.0, new: v0.2.0+1.25.3-alpine, correct? Yes ? Release Note (leave empty for no release note) ? publish new release? Yes INFO[0017] new release published: https://git.coopcloud.tech/coop-cloud/parasol-static-site/src/tag/v0.2.0+1.25.3-alpine ```

decentral1se commented

2024-12-10 10:30:11 +00:00

From #9 (comment)

FATA[0020] add '- "coop-cloud.${STACK_NAME}.version=v0.2.0+1.25.3-alpine"' manually to the 'app' service in /home/user/.abra/recipes/parasol-static-site/compose.yml

I assume that was what was done to get #9 (comment) out the door.

Thanks all, seems we can close!

From https://git.coopcloud.tech/coop-cloud/parasol-static-site/issues/9#issue-4360 > FATA[0020] add '- "coop-cloud.${STACK_NAME}.version=v0.2.0+1.25.3-alpine"' manually to the 'app' service in /home/user/.abra/recipes/parasol-static-site/compose.yml I assume that was what was done to get https://git.coopcloud.tech/coop-cloud/parasol-static-site/issues/9#issuecomment-21830 out the door. Thanks all, seems we can close!

👍 1

decentral1se closed this issue

2024-12-10 10:30:11 +00:00

decentral1se referenced this issue from toolshed/organising

2024-12-10 10:31:28 +00:00

Support automagic insertion in packaging #655

Sign in to join this conversation.

3 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/parasol-static-site#9