Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump org.ajoberstar.reckon.settings from 0.18.3 to 0.19.1 #357

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 25, 2024

Bumps org.ajoberstar.reckon.settings from 0.18.3 to 0.19.1.

Release notes

Sourced from org.ajoberstar.reckon.settings's releases.

0.19.1

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 like major: My Message or patch: 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 to minor. The intent was to encourage breaking changes to still be committed as major: 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 a major!: prefix which ignores whether the project is pre-1.0.0 and forces use of the major scope
  • Introduces scopeSupplier = 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 decision
  • scopeSupplier = calcScopeFromCommitMessages(Function) continues to use the same pre-1.0.0 behavior when a major scope is returned for backwards compatibility

Breaking Changes

None

Enhancements

  • #205 Allow commit message scope suppliers to bump version to v1.0.0

Fixes

  • Dependency updates

Deprecations

None

Compatibility

Tested against the following versions.

Java Version Gradle Versions
11 7.0.2, 7.6.4, 8.0.2, 8.11.1
17 7.3.3, 7.6.4, 8.0.2, 8.11.1
21 8.4, 8.11.1

0.19.0

This release makes commit message scope suppliers more flexible.

Use of scopeSupplier = calcScopeFromCommitMessages() allowed specifying the scope with a commit message like major: My Message or patch: 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 to minor. The intent was to encourage breaking changes to still be committed as major: for consistency, but respecting that reaching 1.0.0 is a more significant decision than just the first breaking change introduced into your code.

... (truncated)

Commits
  • 8c53e37 chore: Use build instead of check in CI
  • d73bc92 chore: Fix Javadoc error
  • de2d6b4 Merge pull request #205 from ajoberstar/fixes
  • f681553 patch: Update dependencies
  • 38216f7 chore: Build against Gradle 8.11
  • ef80bb8 chore: Test against Gradle 8.11
  • 4c901a5 chore: Prevent tests from trying to sign
  • d88de13 minor: Allow commit messages to bump to 1.0.0
  • c29b0dc Test against Gradle 8.9
  • c6e9215 Upgrade gradle
  • See full diff 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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @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 [org.ajoberstar.reckon.settings](https://github.com/ajoberstar/reckon) from 0.18.3 to 0.19.1.
- [Release notes](https://github.com/ajoberstar/reckon/releases)
- [Commits](ajoberstar/reckon@0.18.3...0.19.1)

---
updated-dependencies:
- dependency-name: org.ajoberstar.reckon.settings
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Nov 25, 2024
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant