ci(release): release the tag's commit (forgejo-release's sha), so that a retry from main works #52
No reviewers
Labels
No labels
ansible
bug
ci
dependencies
digest
docker
documentation
duplicate
enhancement
fix
go
good first issue
help wanted
invalid
javascript
major
minor
patch
php
python
question
released
security
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
dawid/langchain-memvid!52
Loading…
Reference in a new issue
No description provided.
Delete branch "release-tag-commit"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
forgejo-release refuses a tag that points elsewhere than the commit it is given, by default the run's. A run started by hand from
mainwith the tag named (to retry a release) ran on main's commit and failed: the tag SHA … does not match the tag SHA that triggered the build (unbabelizer v1.3.1). The step collecting the release files now fetches the tag and passes its commit assha, as HomeLab's converter does now (dawid/HomeLab#81).After merging: a failed release is retried with Run workflow on
main, the tag in the field.forgejo-release refuses a tag that points elsewhere than the commit it is given, by default the run's: a run started by hand from main with the tag named ran on main's commit and failed ("the tag SHA ... does not match the tag SHA that triggered the build"). The step collecting the release files now fetches the tag and names its commit (as HomeLab's converter does now, #81).