Skip to content

Release - #122

Merged
jtrobles-cdd merged 7 commits into
masterfrom
develop
Sep 14, 2026
Merged

jtrobles-cdd merged 7 commits into
masterfrom
develop

Conversation

@jtrobles-cdd

Copy link
Copy Markdown
Member

Changes

jtrobles-cdd and others added 7 commits September 14, 2026 11:20
- GitHub renders the summary of each step as a Markdown document of its own and joins them with a
  blank line, so the reviewers, written by a later step than the rest, ended up as a list of their
  own rather than as the last item of the one above them.
- The summary is therefore written last, by a step that does nothing else, out of the outputs of
  the steps that produced the values. The step that requests the reviews now records the users in
  outputs instead of writing them to the summary itself.
- The step runs unless the run was cancelled, rather than only on success, so that a failure after
  the pull request was opened still leaves its URL in the summary.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
- GitHub renders every newline of a comment as a line break, so a hard-wrapped checklist item
  reaches the pull request broken across lines. The items this workflow contributes were already
  joined by a line continuation, but nothing said so to the callers that supply their own, and
  theirs arrive wrapped. The description of both inputs now states it.
- The continuation of the common pre-deployment item was aligned under the text it continues, and
  that alignment survived the join as a run of seven spaces in the comment body. It now continues
  without indentation, as the tip above it already does.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…on-format-128b67

task-release: Fix the formatting of the Markdown it writes
- The other values of the same list are sentences or identifiers that begin with a capital letter,
  and the placeholder standing in for an empty list of reviewers did not.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…-nobody

task-release: Capitalize the reviewer placeholder of the job summary
The readme opened its recommendation with a bare U+26A0 WARNING SIGN, which browsers and
terminals drew as a monochrome outline instead of the yellow triangle it was meant to be.

- U+26A0 has the Unicode property `Emoji_Presentation = No`, which makes it a text-default
  character: a renderer draws its plain text glyph unless it is asked for the emoji one. The
  glyph therefore came from the first font in the stack that covers the character, such as
  Segoe UI Symbol, DejaVu Sans or Noto Sans Symbols, and the color emoji font was never
  reached.
- Appending U+FE0F VARIATION SELECTOR-16 requests emoji presentation for the character
  preceding it. That is what characters colored by default, such as U+1F6A7 CONSTRUCTION
  SIGN, already carry implicitly.
- GitHub's `:warning:` shortcode produces a yellow triangle too, but only in GitHub Flavored
  Markdown. It stays literal text in every other renderer, and this file is read outside the
  web interface as well.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…f1e03

docs: Render the warning sign in color
@jtrobles-cdd jtrobles-cdd self-assigned this Sep 14, 2026
@jtrobles-cdd jtrobles-cdd added task Task or chore kind: release Release labels Sep 14, 2026
@sonarqubecloud

Copy link
Copy Markdown

@jtrobles-cdd
jtrobles-cdd merged commit 7df4a36 into master Sep 14, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind: release Release task Task or chore

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant