Skip to content

[cli] github-release: let a docs-only PR (docs/release) republish the docs at the latest Release - #314

Merged
jesusmpc merged 4 commits into
mainfrom
improvement/GH-313-cli-github-release-let
Nov 12, 2026
Merged

jesusmpc merged 4 commits into
mainfrom
improvement/GH-313-cli-github-release-let

Conversation

@jesusmpc

Copy link
Copy Markdown
Contributor

Closes #313

Signed-off-by: Jesus Manuel Piñeiro Cid <jesusmpc@inditex.com>
@jesusmpc jesusmpc self-assigned this Nov 11, 2026
@jesusmpc jesusmpc added release-type/minor Minor version release release-type/patch Patch version release and removed release-type/minor Minor version release labels Nov 11, 2026
@jesusmpc
jesusmpc marked this pull request as ready for review November 11, 2026 16:44
@github-actions

Copy link
Copy Markdown
Contributor

❗ ❗ ❗ This Pull Request will not trigger a Release

A Pull Request with no changes to the code/ folder will not trigger a release

… docs at the latest Release

Under `docouture.versionSource: "github-release"`, a merged `docs/release`
pull request now republishes the docs at the highest published stable
GitHub Release instead of failing after the merge.

- `docouture release resolve --releases <a,b>`: picks the highest SemVer
  among the supplied Release tags, filtered by `versionSourcePrefix`,
  ignoring SemVer prereleases and non-SemVer tags. `--release-tag` still wins.
- docouture-release.yml lists published Releases for pull_request events;
  docouture-release-preview.yml states the version that would be republished.
- Docs: scenario-by-source table, reference-cli, v1.4.1 release note, and the
  docouture-docs-versioning skill.

Closes #313
@jesusmpc
jesusmpc requested a review from a team as a code owner November 12, 2026 07:17
@github-actions

Copy link
Copy Markdown
Contributor

ℹ️ The docs release follows the code release

This Pull Request has a release-type/* label. If the code release publishes a GitHub Release, the docs site is released automatically when that Release is published, so you do not need the docs/release label.

The docs will not be released if:

  • your code release does not publish a GitHub Release, or
  • it does publish one but the Release fails, stays a draft, or is marked pre-release.

In those cases, start docouture-release manually from the Actions tab, or release the docs in a separate Pull Request with the docs/release label and no release-type/* label.

@github-actions

Copy link
Copy Markdown
Contributor

🚀 Release Preview Success

You are going to release the version 1.4.1 (patch) with the following changes:

1.4.1 - 2026-11-12

Added

  • #313 \[cli] github-release: let a docs-only PR (docs/release) republish the docs at the latest Release

Changelog

When this PR is released, code/CHANGELOG.md gets:

Added

  • #313 [cli] github-release: let a docs-only PR (docs/release) republish the docs at the latest Release

The text is the issue title, read at release time: edit the issue title or labels to change it.

As of 06b1e71.

With the skip-release label, merging publishes no release: the entries of the issues this PR closes go into the next release. Without a linked issue, the PR gets no entry.

The 1.4.0 release left blank lines between the link reference definitions,
and prettier --check (Code / Verify) fails on them, on main as well.
Whitespace only; no entry changed.

Refs #313
@github-actions

Copy link
Copy Markdown
Contributor

ℹ️ The docs release follows the code release

This Pull Request has a release-type/* label. If the code release publishes a GitHub Release, the docs site is released automatically when that Release is published, so you do not need the docs/release label.

The docs will not be released if:

  • your code release does not publish a GitHub Release, or
  • it does publish one but the Release fails, stays a draft, or is marked pre-release.

In those cases, start docouture-release manually from the Actions tab, or release the docs in a separate Pull Request with the docs/release label and no release-type/* label.

@github-actions

Copy link
Copy Markdown
Contributor

🚀 Release Preview Success

You are going to release the version 1.4.1 (patch) with the following changes:

1.4.1 - 2026-11-12

Added

  • #313 \[cli] github-release: let a docs-only PR (docs/release) republish the docs at the latest Release

Changelog

When this PR is released, code/CHANGELOG.md gets:

Added

  • #313 [cli] github-release: let a docs-only PR (docs/release) republish the docs at the latest Release

The text is the issue title, read at release time: edit the issue title or labels to change it.

As of 992f077.

With the skip-release label, merging publishes no release: the entries of the issues this PR closes go into the next release. Without a linked issue, the PR gets no entry.

@github-actions

Copy link
Copy Markdown
Contributor

ℹ️ The docs release follows the code release

This Pull Request has a release-type/* label. If the code release publishes a GitHub Release, the docs site is released automatically when that Release is published, so you do not need the docs/release label.

The docs will not be released if:

  • your code release does not publish a GitHub Release, or
  • it does publish one but the Release fails, stays a draft, or is marked pre-release.

In those cases, start docouture-release manually from the Actions tab, or release the docs in a separate Pull Request with the docs/release label and no release-type/* label.

@github-actions

Copy link
Copy Markdown
Contributor

🚀 Release Preview Success

You are going to release the version 1.4.1 (patch) with the following changes:

1.4.1 - 2026-11-12

Added

  • #313 \[cli] github-release: let a docs-only PR (docs/release) republish the docs at the latest Release

Changelog

When this PR is released, code/CHANGELOG.md gets:

Added

  • #313 [cli] github-release: let a docs-only PR (docs/release) republish the docs at the latest Release

The text is the issue title, read at release time: edit the issue title or labels to change it.

As of 68e3ad1.

With the skip-release label, merging publishes no release: the entries of the issues this PR closes go into the next release. Without a linked issue, the PR gets no entry.

@jesusmpc
jesusmpc merged commit d801c22 into main Nov 12, 2026
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-type/patch Patch version release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[cli] github-release: let a docs-only PR (docs/release) republish the docs at the latest Release

1 participant