2024-08-06T00:56:08.345064Z INFO published krata-oci 0.0.14
in release
2024-08-06T00:56:47.593865Z ERROR failed to release package
Caused by:
0: Failed to create release
1: HTTP status client error (422 Unprocessable Entity) for url (https://api.github.com/repos/edera-dev/krata/releases)
Error: failed to release package
Caused by:
0: Failed to create release
1: HTTP status client error (422 Unprocessable Entity) for url (https://api.github.com/repos/edera-dev/krata/releases)
The workaround is to create the release manually (title vX.X.X), copy changelog entry from CHANGELOG.md into the release notes, but excluding the version. For example:
### Added
- *(oci)* use local index as resolution cache when appropriate, fixes [#289](https://github.com/edera-dev/krata/pull/289) ([#294](https://github.com/edera-dev/krata/pull/294))
### Fixed
- *(idm)* process all idm messages in the same frame and use childwait exit notification for exec (fixes [#290](https://github.com/edera-dev/krata/pull/290)) ([#302](https://github.com/edera-dev/krata/pull/302))
### Other
- init: mount /proc with hidepid=1 ([#277](https://github.com/edera-dev/krata/pull/277))
- update Cargo.toml dependencies
Then make sure it is the latest, set previous to the last release tag/release. Publish release. The release-assets workflow will start and will build the release assets.
The action log at https://github.com/edera-dev/krata/actions/runs/10258349344/job/28381026939#step:8:489 shows that release-plz is failing to make a release.
The workaround is to create the release manually (title vX.X.X), copy changelog entry from CHANGELOG.md into the release notes, but excluding the version. For example:
Then make sure it is the latest, set previous to the last release tag/release. Publish release. The release-assets workflow will start and will build the release assets.