Skip to content

Pluggable docs version resolvers: descriptor, github-release, tag-bump - #305

Merged
jesusmpc merged 5 commits into
mainfrom
improvement/GH-299-pluggable-docs-version
Nov 11, 2026
Merged

jesusmpc merged 5 commits into
mainfrom
improvement/GH-299-pluggable-docs-version

Conversation

@jesusmpc

Copy link
Copy Markdown
Contributor

Closes #299

Signed-off-by: Jesus Manuel Piñeiro Cid <jesusmpc@inditex.com>
@jesusmpc jesusmpc self-assigned this Nov 11, 2026
@jesusmpc jesusmpc added the release-type/minor Minor version release label Nov 11, 2026
@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

@jesusmpc
jesusmpc marked this pull request as ready for review November 11, 2026 13:07
@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

…ag-bump

Each versioned site now chooses where its docs release version comes from
with docouture.versionSource in docs/package.json: descriptor (default,
docs/.release-version), github-release (the published Release's tag, with
an optional prefix) or tag-bump (latest docs/v* tag plus a bump chosen by
the docs/release, docs/release-minor or docs/release-major label).

- docouture release resolve: one tested implementation of the version
  rules, with semver-aware tag ordering and bumps; the release workflow
  calls it and gates the descriptor bump and the git-flow sync on it
- release preview follows the source and installs dependencies only for
  tag-bump
- docouture version-source: show or switch the source
- docouture new --version-source, upgrade backfill and CLI skew warning,
  doctor checks
- docs, docouture-docs-versioning skill, v1.4.0 release notes, specs

Closes #299
@jesusmpc
jesusmpc requested a review from a team as a code owner November 11, 2026 15:08
@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.0 (minor) with the following changes:

1.4.0 - 2026-11-11

Added

  • #300 Generate CHANGELOG.md entries from closing issues instead of manual PR edits
  • #299 Pluggable docs version resolvers: descriptor, github-release, tag-bump

Fixed

  • #298 docouture-release: bump release descriptor rejected (GH013) when the App token is narrowed

Documentation

  • #296 Update to docouture 1.3.2

Changelog

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

Added

  • #299 Pluggable docs version resolvers: descriptor, github-release, tag-bump

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

As of 8ec96b0.

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.0 (minor) with the following changes:

1.4.0 - 2026-11-11

Added

  • #300 Generate CHANGELOG.md entries from closing issues instead of manual PR edits
  • #299 Pluggable docs version resolvers: descriptor, github-release, tag-bump

Fixed

  • #298 docouture-release: bump release descriptor rejected (GH013) when the App token is narrowed

Documentation

  • #296 Update to docouture 1.3.2

Changelog

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

Added

  • #299 Pluggable docs version resolvers: descriptor, github-release, tag-bump

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

As of 2244ec9.

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.

1 similar comment
@github-actions

Copy link
Copy Markdown
Contributor

🚀 Release Preview Success

You are going to release the version 1.4.0 (minor) with the following changes:

1.4.0 - 2026-11-11

Added

  • #300 Generate CHANGELOG.md entries from closing issues instead of manual PR edits
  • #299 Pluggable docs version resolvers: descriptor, github-release, tag-bump

Fixed

  • #298 docouture-release: bump release descriptor rejected (GH013) when the App token is narrowed

Documentation

  • #296 Update to docouture 1.3.2

Changelog

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

Added

  • #299 Pluggable docs version resolvers: descriptor, github-release, tag-bump

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

As of 2244ec9.

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

🚀 Release Preview Success

You are going to release the version 1.4.0 (minor) with the following changes:

1.4.0 - 2026-11-11

Added

  • #299 Pluggable docs version resolvers: descriptor, github-release, tag-bump

Fixed

  • #298 docouture-release: bump release descriptor rejected (GH013) when the App token is narrowed

Changelog

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

Added

  • #299 Pluggable docs version resolvers: descriptor, github-release, tag-bump

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

As of 2244ec9.

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.

- Keep the NOSONAR for S4036 on the execFile call line in docs-tags.ts
- Split release resolve, version-source and new into small helpers
- Replace the long SemVer regex with an isSemver parser, and simplify
  compareSemver
- Read the installed CLI candidates in parallel in project-cli.ts
- version-source with no argument now fails on an unknown declared source

Signed-off-by: Jesus Manuel Piñeiro Cid <jesusmpc@inditex.com>
@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.0 (minor) with the following changes:

1.4.0 - 2026-11-11

Added

  • #299 Pluggable docs version resolvers: descriptor, github-release, tag-bump

Fixed

  • #298 docouture-release: bump release descriptor rejected (GH013) when the App token is narrowed

Changelog

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

Added

  • #299 Pluggable docs version resolvers: descriptor, github-release, tag-bump

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

As of 92b996a.

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.0 (minor) with the following changes:

1.4.0 - 2026-11-11

Added

  • #299 Pluggable docs version resolvers: descriptor, github-release, tag-bump

Fixed

  • #298 docouture-release: bump release descriptor rejected (GH013) when the App token is narrowed

Changelog

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

Added

  • #299 Pluggable docs version resolvers: descriptor, github-release, tag-bump

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

As of 9ec871a.

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 1d4bc53 into main Nov 11, 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/minor Minor version release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[tooling] Pluggable docs version resolvers: descriptor, github-release, tag-bump

1 participant