Skip to content

fix(release): fixed mono-repo workflow#100

Merged
fredbi merged 1 commit intomasterfrom
fix/monorepo-release-notes
Feb 9, 2026
Merged

fix(release): fixed mono-repo workflow#100
fredbi merged 1 commit intomasterfrom
fix/monorepo-release-notes

Conversation

@fredbi
Copy link
Member

@fredbi fredbi commented Feb 9, 2026

  • running from a fork or repo outside the go-openapi organization

    • allowed to run workflow with or without PGP sign-off (commits, tags)
    • allowed to run from a fork outside the go-openapi org (must configure bot-go-openapi github app and permissions)
    • fixed secret transmission to cover these use cases
  • gh-actions: fixed svu usage. Updated gh-actions, so that svu doesn't fail on mono-repo prefixed tags

  • fixed release notes

    • ensured git checkout is un-shallowed

    • git-cliff config (also applies to regular releases, not just mono-repo)

      • fixed commit categorization in release notes
      • merge commits grouped as "Other" instead of skipped (consistent count)
      • fix (category "Documentation"): regex overlap causing garbled group headings
      • fix (category "Misc."): added \bCI\b pattern to catch mid-message CI references
      • fix (category "Refactor"): refact rule has precedence over chore
      • polish cliff config categorization and contributor lists (keep all commits, but exclude bots from contributors)
    • release notes construction

      • suppressed tag annotation in module-specific sections
      • fixed wrong module commit scope: module sections use root tag pattern with path filtering
      • --exclude-path which was using absolute paths now uses relative paths with /** globs.
      • skip root module in Part 2 (already covered by full changelog) - was producing redundant sections.
      • derived module include-path from filesystem, not module names (the module name stripping used GITHUB_REPO to strip the prefix from go module paths, but this fails on forks where the repo name differs from the module path.
      • passed --tag to module git-cliff calls to resolve version header. When --include-path filters the commit graph, tag commits that don't touch the module's files are excluded. This prevents git-cliff from resolving the version, resulting in "unreleased" headers.
      • fix: tag message title/body separation for markdown rendering
      • style: polish monorepo release notes markdown presentation (orphaned line separators, modules with no commits, stripped module version header).

Change type

Please select: 🆕 New feature or enhancement|🔧 Bug fix'|📃 Documentation update

Short description

Fixes

Full description

Checklist

  • I have signed all my commits with my name and email (see DCO. This does not require a PGP-signed commit
  • I have rebased and squashed my work, so only one commit remains
  • I have added tests to cover my changes.
  • I have properly enriched go doc comments in code.
  • I have properly documented any breaking change.

* running from a fork or repo outside the go-openapi organization
  * allowed to run workflow with or without PGP sign-off (commits, tags)
  * allowed to run from a fork outside the go-openapi org
    (must configure bot-go-openapi github app and permissions)
  * fixed secret transmission to cover these use cases

* gh-actions: fixed svu usage. Updated gh-actions, so that svu doesn't fail on mono-repo prefixed tags

* fixed release notes
  * ensured git checkout is un-shallowed

  * git-cliff config (also applies to regular releases, not just
    mono-repo)
    * fixed commit categorization in release notes
    * merge commits grouped as "Other" instead of skipped (consistent count)
    * fix (category "Documentation"): regex overlap causing garbled group headings
    * fix (category "Misc."): added \bCI\b pattern to catch mid-message CI references
    * fix (category "Refactor"): refact rule has precedence over chore
    * polish cliff config categorization and contributor lists (keep all
      commits, but exclude bots from contributors)

  * release notes construction
    * suppressed tag annotation in module-specific sections
    * fixed wrong module commit scope: module sections use root tag pattern with path filtering
    *  --exclude-path which was using absolute paths now uses relative paths with /** globs.
    * skip root module in Part 2 (already covered by full changelog) -
      was producing redundant sections.
    * derived module include-path from filesystem, not module names
      (the module name stripping used GITHUB_REPO to strip the prefix from
      go module paths, but this fails on forks where the repo name differs from the module path.
    * passed --tag to module git-cliff calls to resolve version header.
      When --include-path filters the commit graph, tag commits that don't
      touch the module's files are excluded. This prevents git-cliff from
      resolving the version, resulting in "unreleased" headers.
    * fix: tag message title/body separation for markdown rendering
    * style: polish monorepo release notes markdown presentation
      (orphaned line separators, modules with no commits, stripped
      module version header).

Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@fredbi fredbi force-pushed the fix/monorepo-release-notes branch from 493dc86 to fa2cedd Compare February 9, 2026 10:41
@codecov
Copy link

codecov bot commented Feb 9, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (a94fc68) to head (fa2cedd).
⚠️ Report is 2 commits behind head on master.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff            @@
##            master      #100   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            3         3           
  Lines           14        14           
=========================================
  Hits            14        14           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@fredbi fredbi merged commit 565504e into master Feb 9, 2026
35 checks passed
@fredbi fredbi deleted the fix/monorepo-release-notes branch February 9, 2026 10:57
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