| |
between releases.
|
| |
|
| |
|
| + |
## Version 0.14.0, released 2025-03-24
|
| + |
|
| + |
Bug fixes:
|
| + |
|
| + |
* The Ci broker had a programming error where it would consider it a
|
| + |
fatal error if a CI event referred to a Git ref that was not a patch
|
| + |
or a branch. This would cause the CI broker to terminate, resulting
|
| + |
in no CI running, and the CI broker process having to be re-started.
|
| + |
This has been changed so that such Git refs are merely ignored. An
|
| + |
example of such a Git ref is an update to `sigrefs`, which is
|
| + |
fundamental to how Radicle works.
|
| + |
|
| + |
* When an event is picked from the event queue, it is removed at once.
|
| + |
This means if something goes wrong while processing the event
|
| + |
(running CI based on the event), the CI broker won't re-try the
|
| + |
event. This avoids a situation where something in the event causes
|
| + |
processing to always end due to an error, resulting in the CI broker
|
| + |
re-trying the same event over and over, forever. With the new
|
| + |
behavior, the event is tried only once, and if it fails, it's up to
|
| + |
humans to figure out what caused this and to make it not happen
|
| + |
again.
|
| + |
|
| + |
* Many problems in how Git references are handled have been fixed.
|
| + |
Radicle deals with at least three types of Git references: branch
|
| + |
names (`main`), qualified refs (`refs/heads/main`) and name spaced
|
| + |
refs (`refs/namespaces/$NID/refs/main`). The CI broker is now more
|
| + |
careful about keeping the different kinds apart. This results in the
|
| + |
`DefaultBranch` filter to work more reliably, when previously in
|
| + |
some cases it would not, because the plain branch name was compared
|
| + |
to a name spaced ref.
|
| + |
|
| + |
Other changes:
|
| + |
|
| + |
* Logging is now more systematic and consistent. For example, all log
|
| + |
messages are now structured, rather than just free form text. All
|
| + |
log messages now have a `kind` field. All CI broker worker threads
|
| + |
now emit a log message when they start and end, and if they end due
|
| + |
to an error, the error is included in the log message.
|
| + |
|
| + |
* The new `cibtool event filter --explain` explains why a filter
|
| + |
allows or denies an event.
|
| + |
|
| + |
* The RSS feeds produced by the CI broker now only contain up to ten
|
| + |
entries. Apparently some RSS feed readers only remember a limited
|
| + |
number of entries, and if the feed grows too long, they start
|
| + |
treating really old entries as new. This can be alarming to the
|
| + |
anxious developer who gets notified of failures in CI, only to later
|
| + |
realize that it happened six months ago.
|
| + |
|
| + |
The number ten is currently fixed. If need be, it can be made
|
| + |
configurable.
|
| + |
|
| + |
* The user guide now has a chapter on configuring the CI broker.
|
| + |
|
| |
## Version 0.13.1, released 2025-03-05
|
| |
|
| |
* The `NoneOf`, `AnyOf`, and `AllOf` aliases for CI event filters
|