abra recipe release fails without obvious reason #544

New Issue

iexos · 2023-12-19T18:07:17Z

iexos commented

2023-12-19 18:07:17 +00:00

I just did a hotfix for #543, just renaming the release notes and syncing patch version. Now releasing didn't work:

$ abra recipe release outline
WARN[0000] discovered 2.0.1+0.74.0 as currently synced recipe label
WARN[0000] previous git tags detected, assuming this is a new semver release
? current: 2.0.0+0.74.0, new: 2.0.1+0.74.0, correct? Yes
? publish new release? Yes
FATA[0012] failed to publish new release: already up-to-date

second try

> abra recipe release outline
WARN[0000] discovered 2.0.1+0.74.0 as currently synced recipe label
WARN[0000] previous git tags detected, assuming this is a new semver release
FATA[0000] latest git tag (2.0.1+0.74.0) and synced label (2.0.1+0.74.0) are the same?

I just did a hotfix for #543, just renaming the release notes and syncing patch version. Now releasing didn't work: ``` $ abra recipe release outline WARN[0000] discovered 2.0.1+0.74.0 as currently synced recipe label WARN[0000] previous git tags detected, assuming this is a new semver release ? current: 2.0.0+0.74.0, new: 2.0.1+0.74.0, correct? Yes ? publish new release? Yes FATA[0012] failed to publish new release: already up-to-date ``` second try ``` > abra recipe release outline WARN[0000] discovered 2.0.1+0.74.0 as currently synced recipe label WARN[0000] previous git tags detected, assuming this is a new semver release FATA[0000] latest git tag (2.0.1+0.74.0) and synced label (2.0.1+0.74.0) are the same? ```

iexos added the

bug

label 2023-12-19 18:07:17 +00:00

decentral1se commented

2023-12-19 19:26:08 +00:00

Seems like it got released: https://git.coopcloud.tech/coop-cloud/outline/releases/tag/2.0.1+0.74.0 👏

Seems like abra made the release commit and then when you hotfixed, it didn't have a change to commit. The release process is automated to expect unstaged changes which can be commited. Hard to understand more without --debug output, maybe you can pull that out the next time 🙏

Seems like it got released: https://git.coopcloud.tech/coop-cloud/outline/releases/tag/2.0.1+0.74.0 👏 Seems like `abra` made the release commit and then when you hotfixed, it didn't have a change to commit. The release process is automated to expect unstaged changes which can be commited. Hard to understand more without `--debug` output, maybe you can pull that out the next time 🙏

decentral1se added the

abra

label 2024-03-27 06:18:29 +00:00

Sign in to join this conversation.

No Milestone

No project

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/organising#544