Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.18.3
->0.19.1
Release Notes
ajoberstar/reckon (org.ajoberstar.reckon)
v0.19.1
Compare Source
NOTE: 0.19.1 is the same as 0.19.0. There was a publishing issue preventing 0.19.0 from getting out to Central.
This release makes commit message scope suppliers more flexible.
Use of
scopeSupplier = calcScopeFromCommitMessages()
allowed specifying the scope with a commit message likemajor: My Message
orpatch: My message
. However, there was a special case when the project hadn't reached 1.0.0 yet.Before a project reaches 1.0.0,
major:
prefixes were downgraded tominor
. The intent was to encourage breaking changes to still be committed asmajor:
for consistency, but respecting that reaching 1.0.0 is a more significant decision than just the first breaking change introduced into your code.The downside was that the only alternative to get to 1.0.0 was to use
-Preckon.scope=major
to supersede what the commit message supplier decided. This can be incompatible with many workflows that don't allow user interaction when reckon runs.With this release:
scopeSupplier = calcScopeFromCommitMessages()
now additionally supports amajor!:
prefix which ignores whether the project is pre-1.0.0 and forces use of the major scopescopeSupplier = calcScopeFromCommitMessageParser(BiFunction)
which allows custom logic to consider both the commit message and whether the project is pre-1.0.0 when it makes it's scope decisionscopeSupplier = calcScopeFromCommitMessages(Function)
continues to use the same pre-1.0.0 behavior when a major scope is returned for backwards compatibilityBreaking Changes
None
Enhancements
Fixes
Deprecations
None
Compatibility
Tested against the following versions.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.