Bump version.org.jboss.logging.jboss-logging-tools from 3.0.2.Final to 3.0.3.Final #1500
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=80&v=4){kind=small}
Bumps `version.org.jboss.logging.jboss-logging-tools` from 3.0.2.Final to 3.0.3.Final. Updates `org.jboss.logging:jboss-logging-processor` from 3.0.2.Final to 3.0.3.Final - [Release notes](https://github.com/jboss-logging/jboss-logging-tools/releases) - [Commits](jboss-logging/jboss-logging-tools@3.0.2.Final...3.0.3.Final) Updates `org.jboss.logging:jboss-logging-annotations` from 3.0.2.Final to 3.0.3.Final - [Release notes](https://github.com/jboss-logging/jboss-logging-tools/releases) - [Commits](jboss-logging/jboss-logging-tools@3.0.2.Final...3.0.3.Final) --- updated-dependencies: - dependency-name: org.jboss.logging:jboss-logging-processor dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: org.jboss.logging:jboss-logging-annotations dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
the
dependencies
|
Thanks for your pull request! This pull request does not follow the contribution rules. Could you have a look? ❌ All commit messages should start with a JIRA issue key matching pattern › This message was automatically generated. |
|
|
@dependabot rebase |
|
Looks like these dependencies are up-to-date now, so this is no longer needed. |
dependabot
bot
deleted the
dependabot/maven/version.org.jboss.logging.jboss-logging-tools-3.0.3.Final
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Bumps
version.org.jboss.logging.jboss-logging-toolsfrom 3.0.2.Final to 3.0.3.Final.Updates
org.jboss.logging:jboss-logging-processorfrom 3.0.2.Final to 3.0.3.FinalRelease notes
Sourced from org.jboss.logging:jboss-logging-processor's releases.
Commits
8da63f2Prepare for 3.0.3.Final releaseee02afeMerge pull request #130 from jamezp/add-release-note-configb0b22f0Add a configuration for release notes.912ebd7Merge pull request #128 from jamezp/issue127c0371c9[127] Remove the scope from the jboss-logging dependency in the jboss-logging...b16d840Merge pull request #124 from jboss-logging/dependabot/maven/org.junit-junit-b...398eb23Merge pull request #126 from jboss-logging/dependabot/maven/org.asciidoctor-a...bfc191cBump org.asciidoctor:asciidoctor-maven-plugin from 3.0.0 to 3.1.143165aaBump org.junit:junit-bom from 5.11.2 to 5.11.307a3997Next is 3.0.3.FinalUpdates
org.jboss.logging:jboss-logging-annotationsfrom 3.0.2.Final to 3.0.3.FinalRelease notes
Sourced from org.jboss.logging:jboss-logging-annotations's releases.
Commits
8da63f2Prepare for 3.0.3.Final releaseee02afeMerge pull request #130 from jamezp/add-release-note-configb0b22f0Add a configuration for release notes.912ebd7Merge pull request #128 from jamezp/issue127c0371c9[127] Remove the scope from the jboss-logging dependency in the jboss-logging...b16d840Merge pull request #124 from jboss-logging/dependabot/maven/org.junit-junit-b...398eb23Merge pull request #126 from jboss-logging/dependabot/maven/org.asciidoctor-a...bfc191cBump org.asciidoctor:asciidoctor-maven-plugin from 3.0.0 to 3.1.143165aaBump org.junit:junit-bom from 5.11.2 to 5.11.307a3997Next is 3.0.3.FinalDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)