Doing release-planning in rivet (assigning a release: field per artifact and querying readiness as "how many of release vX.Y are verified"), I hit a gap: rivet list --format json does not include the artifact fields dict, so I can't query/group by a custom field like release from the CLI — I had to parse the YAML files directly to build the per-release burn-down.
Repro
rivet modify FEATURE-004 --set-field release=v0.1.0
rivet list --format json | jq '.[] | select(.fields.release)' # fields not present in output
Impact
Release readiness ("is v0.X cuttable = all its artifacts verified") is meant to be a query, but custom fields aren't exposed in JSON, so it can't be expressed natively.
Suggested fix (any one)
- include the
fields map in rivet list --format json output; or
- add
rivet list --field release=v0.1.0 (filter by a field value); or
- a small
rivet release <vX.Y> / burndown view that groups a release's scope by status.
Happy to test against jess's release-tagged artifacts. Thanks!
Doing release-planning in rivet (assigning a
release:field per artifact and querying readiness as "how many of release vX.Y are verified"), I hit a gap:rivet list --format jsondoes not include the artifactfieldsdict, so I can't query/group by a custom field likereleasefrom the CLI — I had to parse the YAML files directly to build the per-release burn-down.Repro
Impact
Release readiness ("is v0.X cuttable = all its artifacts verified") is meant to be a query, but custom fields aren't exposed in JSON, so it can't be expressed natively.
Suggested fix (any one)
fieldsmap inrivet list --format jsonoutput; orrivet list --field release=v0.1.0(filter by a field value); orrivet release <vX.Y>/ burndown view that groups a release's scope by status.Happy to test against jess's release-tagged artifacts. Thanks!