Skip to content

Bump TriPSs/conventional-changelog-action from 5.4.0 to 6.4.0#481

Open
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/github_actions/TriPSs/conventional-changelog-action-6.4.0
Open

Bump TriPSs/conventional-changelog-action from 5.4.0 to 6.4.0#481
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/github_actions/TriPSs/conventional-changelog-action-6.4.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 13, 2026

Copy link
Copy Markdown
Contributor

Bumps TriPSs/conventional-changelog-action from 5.4.0 to 6.4.0.

Release notes

Sourced from TriPSs/conventional-changelog-action's releases.

v6.4.0

Bug Fixes

  • refactor template and header/footer handling for improved version bumping logic (b9d2369)
  • update template and header/footer handling for improved version bumping logic (f3f10ee)
  • update templates and bump version logic for prerelease handling (c8f0be0)

Features

  • add pre-release-smart-bump option for intelligent pre-release version bumping (3af15c8)
  • improve version bumping logic (193d21b)

v6.3.1

Bug Fixes

  • pass skipUnstable to file changelog generation (98b99c1)

v6.3.0

Features

  • Update Node version from 20 to 24 in action.yml (c6d4281)

v6.2.0

Features

  • add no-verify option to pass to git commit (ad190ee)
  • remove extra space from commit command (4d9c8c2)

v6.1.0

Features

  • add version file support for java .properties file format (5e05ac7)

v6.0.0

Features

  • set corresponding prerelease type derived from releaseType (792a7f7)

BREAKING CHANGES

  • prerelease option generates pre[major|minor|patch] release
Changelog

Sourced from TriPSs/conventional-changelog-action's changelog.

6.4.0 (2026-07-08)

Bug Fixes

  • refactor template and header/footer handling for improved version bumping logic (b9d2369)
  • update template and header/footer handling for improved version bumping logic (f3f10ee)
  • update templates and bump version logic for prerelease handling (c8f0be0)

Features

  • add pre-release-smart-bump option for intelligent pre-release version bumping (3af15c8)
  • improve version bumping logic (193d21b)

6.3.1 (2026-04-23)

Bug Fixes

  • pass skipUnstable to file changelog generation (98b99c1)

6.3.0 (2026-03-19)

Features

  • Update Node version from 20 to 24 in action.yml (c6d4281)

6.2.0 (2025-10-22)

Features

  • add no-verify option to pass to git commit (ad190ee)
  • remove extra space from commit command (4d9c8c2)

6.1.0 (2025-09-04)

Features

... (truncated)

Commits
  • ee43def chore(release): v6.4.0 [skip ci]
  • 6311770 feat: Add smart pre-release bump (#288)
  • 7eca0b7 Merge branch 'releases/v6' of ssh://github.com/TriPSs/conventional-changelog-...
  • 2e89f51 ci: make multiple git path test fork-safe
  • 952b14b chore(release): v6.3.1 [skip ci]
  • 0dd7c73 fix: pass skipUnstable to file changelog generation (#295)
  • 98b99c1 fix: pass skipUnstable to file changelog generation
  • 66284f9 build(deps): bump yaml from 2.6.0 to 2.8.3 (#291)
  • 39d718b build(deps): bump handlebars from 4.7.8 to 4.7.9 (#292)
  • a5389ab build(deps): bump handlebars from 4.7.8 to 4.7.9
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [TriPSs/conventional-changelog-action](https://github.com/tripss/conventional-changelog-action) from 5.4.0 to 6.4.0.
- [Release notes](https://github.com/tripss/conventional-changelog-action/releases)
- [Changelog](https://github.com/TriPSs/conventional-changelog-action/blob/releases/v6/CHANGELOG.md)
- [Commits](TriPSs/conventional-changelog-action@v5.4.0...v6.4.0)

---
updated-dependencies:
- dependency-name: TriPSs/conventional-changelog-action
  dependency-version: 6.4.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Jul 13, 2026
@iav

iav commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Version-numbering impact of this bump (v5.4.0 → v6.4.0)

This is a major bump with a behavioral change that affects our nightly versioning. All six workflows here call the action with pre-release: true for nightly builds (false for stable). The only relevant code change is in src/helpers/bumpVersion.js: v5 computed the new version as semver.inc(version, 'prerelease', identifier), whereas v6.0.0 changed it to semver.inc(version, 'pre' + releaseType, identifier). In other words, when pre-release is set, v5 always incremented just the -trunk.N counter and kept the base version fixed, while v6 now derives the bump from conventional-commits (prepatch/preminor/premajor) and resets the counter to .0.

Concretely, our nightly stream changes from 26.08.0-trunk.0 → .1 → .2 … (base pinned, counter climbing) to 26.08.1-trunk.0 → 26.08.2-trunk.0 → 26.09.0-trunk.0 … — the base version now advances on every nightly (patch or minor depending on the commits) and the -trunk counter is always .0. semver ordering stays monotonic, so downstream version comparisons and the apt repo won't break, but the numbering scheme itself is different, and since nightly has skip_tag=false the created tag names change accordingly. The stable path (pre-release: false) is unaffected — both versions bump straight by releaseType.

Nothing here fails CI, and the Node 20 → 24 runtime change (v6.3.0) is fine since the bump step runs on ubuntu-latest. The only decision is whether the faster-moving base version for nightlies is acceptable.

The good news: v6.4.0 (exactly the version this PR bumps to) adds a pre-release-smart-bump option that restores the old behavior for our case. With pre-release-smart-bump: 'true', when the current version is already a pre-release with the same identifier, the action only increments the -trunk.N counter as long as the base stays on the same target release type. Since our base is calendar-driven (YY.MM.0, i.e. minor > 0, patch = 0, "targeting a minor"), both fix: and feat: commits keep bumping just the counter (26.08.0-trunk.N → .N+1), identical to v5. The only remaining difference is that a major/breaking conventional commit would still jump the base to 27.0.0-trunk.0 — but breaking commits are rare and, since the base is calendar-controlled rather than derived from commits, such a jump was never intended anyway. So rather than merging as-is, I'd suggest adding pre-release-smart-bump: 'true' to the with: block in all six workflows alongside this bump, which keeps the existing -trunk.N progression for real nightly commits.

conventional-changelog-action v6.0.0 changed the pre-release bump from a
plain prerelease-counter increment to pre<releaseType>, which advances the
nightly base version on every build and resets the -trunk counter. Enable
pre-release-smart-bump (added in v6.4.0) so the existing -trunk.N
progression is kept for our calendar-driven YY.MM.0 base; only a rare
major/breaking commit would move the base, matching prior intent.

Assisted-by: Claude:claude-opus-4.8
@igorpecovnik

Copy link
Copy Markdown
Member

this changelog is due for deprecation ... i am working on a new solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants