Skip to content
noggin

Releases: release-please and the PR Title check (2026-11-01, #303)

Question: what release-please and amannn/action-semantic-pull-request need to give noggin one SemVer version, a CHANGELOG.md written by a release PR, conventional PR titles enforced by a required check, and a tag that still starts Release Assets. Rule: newest release at least two weeks old, pinned by SHA.

Sources, all read 2026-11-01: the action’s README (https://github.com/googleapis/release-please-action/blob/main/README.md), release-please’s manifest docs (https://github.com/googleapis/release-please/blob/main/docs/manifest-releaser.md) and source (RP/ = https://github.com/googleapis/release-please/blob/c589293/src/), the semantic PR action’s README (https://github.com/amannn/action-semantic-pull-request/blob/main/README.md), GitHub’s Dependabot options reference (https://docs.github.com/en/code-security/dependabot/working-with-dependabot/dependabot-options-reference), the GitHub API and uv.

  • googleapis/release-please-action v5.0.0 (2026-04-22, node24, bundles release-please 17.6.0): 45996ed1f6d02564a971a2fa1b5860e934307cf7 (gh api repos/googleapis/release-please-action/commits/v5.0.0).
  • amannn/action-semantic-pull-request v6.1.1 (2025-08-22, the latest): 48f256284bd46cdaab1048c3721360e808335d50.
  • “all resources created by release-please (release tag or release pull request) will not trigger future GitHub actions workflows”; a Personal Access Token is needed “if you want GitHub Actions CI checks to run on Release Please PRs” (action README, “Other Actions on Release Please PRs”). With GITHUB_TOKEN the release PR would get no required checks (no review either) and its tag would not start Release Assets (on: push: tags).
  • The same holds for auto-merge: a merge GitHub performs for auto-merge enabled with GITHUB_TOKEN pushes to main as github-actions, and that push starts no workflow, so release-please would never run to tag the release. Auto-merge is enabled with the same token.
  • release-please-config.json plus .release-please-manifest.json; the manifest “can be empty when release-please is run for the first time but it must exist” (manifest docs, “Manifest”).
  • First version: with no previous release the strategy takes initial-version (RP/strategies/base.ts initialReleaseVersion), so {} plus "initial-version": "0.1.0" gives v0.1.0.
  • bootstrap-sha stops the first changelog’s commit walk (exclusive); ignored once a release PR has merged.
  • A release PR is opened only when the changelog has a visible entry: “No user facing commits found … skipping” (RP/strategies/base.ts buildReleasePullRequest). The default sections show feat, fix, perf, revert and deps; docs, chore, refactor, test, build and ci are hidden, so they ride along with the next visible change.
  • 0.x bumps: bump-minor-pre-major makes a breaking change bump the minor below 1.0.0, and bump-patch-for-minor-pre-major makes a feat bump the patch (manifest docs, config example).
  • The python type updates pyproject.toml (project.version), CHANGELOG.md, and <name>/__init__.py, version.py, setup.py, setup.cfg only where they exist and hold a version (RP/strategies/python.ts; noggin/init.py is empty, so nothing).
  • uv.lock repeats the root project’s version and uv lock --check fails once pyproject.toml moves alone (tried). A toml extra-file with jsonpath $.package[?(@.name.value==="noggin")].version bumps that one line and keeps the rest of the file (RP/updaters/generic-toml.ts; the parser wraps each value as {value}, hence .value); tried with release-please 17.6.0, and uv lock --check passes after it.
  • Default PR title chore${scope}: release${component} ${version} (RP/util/pull-request-title.ts) gives chore(main): ..., a scope no area has; pull-request-title-pattern chore: release noggin v${version} round-trips (tried: it parses back to the version). Tags are v<version> with include-component-in-tag: false; the release’s name is then v<version> (RP/strategies/base.ts buildRelease).
  • Outputs: release_created, tag_name, prs_created, pr (JSON PullRequest, with number) (action README).
  • types and scopes are newline-delimited regexes wrapped in ^ $; a scope is optional unless requireScope; a title has one line, so a breaking change is type!: (semantic PR README).
  • A required check needs synchronize among the triggers; pull_request reads the PR’s own configuration (README, “Event triggers”); edited reruns it when the title changes.
  • Squash merges take the PR title as the commit subject (the repo’s squash_merge_commit_title: PR_TITLE), which is what release-please parses.
  • commit-message.prefix: Dependabot “inserts a colon after the prefix” when it ends in a letter, and PR titles are written from the commit message, so prefix: ci gives ci: bump ...; include: scope would add (deps).
byYellow PineYellow Pine

noggin v0.2.26-6-g09bf9b7 · 09bf9b7