@@ -14,7 +14,7 @@ description: >
1414through uvx with this version range; it matches the flags and report schema described here:
1515
1616``` bash
17- uvx --from ' release-scope>=0.9 ,<0.10 ' release-scope --help
17+ uvx --from ' release-scope>=0.11 ,<0.12 ' release-scope --help
1818```
1919
2020## Check the settings
@@ -58,7 +58,7 @@ run and only saves requests:
5858``` bash
5959out=" ${XDG_CACHE_HOME:- $HOME / .cache} /release-scope"
6060mkdir -p " $out "
61- uvx --from ' release-scope>=0.9 ,<0.10 ' release-scope collect --project team/backend/shop \
61+ uvx --from ' release-scope>=0.11 ,<0.12 ' release-scope collect --project team/backend/shop \
6262 --output " $out /site" --cache " $out /cache.json"
6363```
6464
@@ -83,7 +83,8 @@ Read `$out/site/report.json` and answer the user's question from it, briefly.
8383- A row is one merged merge request or a direct commit: ` merge_requests ` , ` commits ` , ` tags ` pointing into it,
8484 ` environments ` running exactly its commit now, ` first_deployed_at ` (per environment other than production, when the
8585 first deploy job that shipped this row or a newer one finished), ` jira_keys ` (the keys its merge request or commit
86- text names, plus, with Jira, every issue whose GitLab links point into the row), and ` main_pipeline ` with
86+ text names, plus, with Jira, every issue whose GitLab links point into the row; each key's ` via ` holds ` named ` ,
87+ ` linked ` , or both, to say which), and ` main_pipeline ` with
8788 ` failed_jobs ` . Tag pipelines carry their own ` failed_jobs ` .
8889- A service with no rows is up to date with production.
8990- A service never deployed to production has a ` no_production ` warning; its rows run down to the first commit of the
@@ -93,7 +94,7 @@ Read `$out/site/report.json` and answer the user's question from it, briefly.
9394 highest ` X.Y.Z ` tag with its minor version bumped, or ` null ` ), and ` create_url ` , GitLab's new-tag form for the head.
9495 It is ` null ` when the head is tagged or the service has no rows.
9596- ` candidates ` (newest first): the tags a release could ship, each with ` tag ` and its ` pipeline ` , ` rows ` (how many
96- rows run from that tag down to production), ` jira_keys ` (the in-scope keys of those rows, without duplicates), and
97+ rows run from that tag down to production), ` jira_keys ` (the in-scope keys of those rows, without duplicates, with ` via ` merged across them ), and
9798 ` compare_url ` .
9899 To answer which issues a set of tags releases, merge the ` jira_keys ` of the picked candidates.
99100- ` jira.issues ` by key: ` summary ` , ` status ` , ` status_category ` (anything but ` done ` is not done), ` links ` to GitLab
0 commit comments