Skip to content

chore: Update version numbers in README.md #218

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.

Sign up for GitHub

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

Merged
devopsix merged 1 commit into from
Sep 12, 2026
Merged

chore: Update version numbers in README.md #218

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions .github/release-please-config.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,5 +8,8 @@
},
"plugins": [
"sentence-case"
],
"extra-files": [
"README.md"
]
}
6 changes: 5 additions & 1 deletion DEVELOPMENT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,11 @@ Building and deploying the actual Maven Artifacts for a release is the responsib
After a release has been made, Release Please will automatically create another pull request to update the version
numbers in `pom.xml` files to the next snapshot version
(see the [Maven strategy](https://github.com/googleapis/release-please/blob/main/docs/java.md)).
This snapshot “release pull request” has to be merged immediately.
Version numbers in README.md will also get updated with snapshot versions although that is unwanted. Release Please
cannot be configured to skip updating README.md when creating a snapshot release. The unwanted changes need to be
reverted manually.
This snapshot “release pull request” has to be merged immediately after unwanted changes to version numbers in README.md
have been reverted.


[Conventional Commits]: https://www.conventionalcommits.org/
Expand Down
6 changes: 4 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,22 +13,24 @@ The [hamcrest-mail][] sister project provides a set of Hamcrest matchers with si
To use AssertJ Mail in a Maven project add a dependency on `org.devopsix:assertj-mail` (for Java EE 8 / javax.mail) or
`org.devopsix:assertj-mail-jakarta` (for Jakarta EE 9+ / jakarta.mail) to the pom.xml file.

<!-- x-release-please-start-version -->
```xml
<!-- Maven coordinates for Java EE 8 / javax.mail -->
<dependency>
<groupId>org.devopsix</groupId>
<artifactId>assertj-mail</artifactId>
<version>1.0.9</version>
<version>1.0.11</version>
<scope>test</scope>
</dependency>
<!-- Maven coordinates for Jakarta EE 9+ / jakarta.mail -->
<dependency>
<groupId>org.devopsix</groupId>
<artifactId>assertj-mail-jakarta</artifactId>
<version>1.0.9</version>
<version>1.0.11</version>
<scope>test</scope>
</dependency>
```
<!-- x-release-please-end -->

The assertions are available as static methods on the `MailAssertions` class.

Expand Down
Loading