Skip to content

chore: CI on PRs into dev, rc tags as pre-releases, maxRetries wording - #21

Merged
tuzzmaniandevil merged 1 commit into
devfrom
chore/ci-release-retries
Sep 30, 2026
Merged

tuzzmaniandevil merged 1 commit into
devfrom
chore/ci-release-retries

Conversation

@tuzzmaniandevil

Copy link
Copy Markdown
Contributor

Three small fixes. No changelog entry: none changes what the bot does.

What's in it

  • CI runs on PRs into dev, as well as main, so a feature PR is built and tested before it merges instead of first at the release PR. This PR is the first to get it.
  • Release candidates are pre-releases. A tag containing - (for example v1.3.0-rc.1) is published as a GitHub pre-release, and the Docker :latest tag only moves on stable tags. Before, an rc tag would have gone out as the latest release and moved :latest. {{major}} and {{major}}.{{minor}} image tags already skip pre-releases. The expressions are copied from OwlShack's release workflow, which shipped v1.5.0-rc.1 with them.
  • README: maxRetries counts total sends. The default 3 is one send and up to two resends. It was described as a number of retries. Confirmed against the library's retry tracker, and on air.

Verification

  • actionlint passes on both workflows. As a positive control, it catches both a misspelt property and a syntax error planted in the new expression.
  • The release workflow itself can't run from here. Its first real exercise will be the next tag.

- ci.yml: run on pull requests into dev as well as main, so a feature
  PR is built and tested before it merges rather than at the release PR
- release.yml: a tag containing '-' (v1.3.0-rc.1) is published as a
  GitHub pre-release and no longer moves the :latest image tag; the
  same expressions OwlShack's release workflow uses
- README: maxRetries counts total sends, first included, so the default
  3 is one send and up to two resends; it was described as retries
@tuzzmaniandevil
tuzzmaniandevil merged commit 6fdf696 into dev Sep 30, 2026
1 check passed
@tuzzmaniandevil
tuzzmaniandevil deleted the chore/ci-release-retries branch September 30, 2026 04:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant