Prepare for release 3.0.4

CHANGELOG.md

@@ -1,5 +1,7 @@
 # Change Log
 
+For a full list of changes, see the [GitHub releases](https://github.com/airbnb/mavericks/releases)
+
 ## 3.0.3
 - Changed flowWhenStarted to emit value on flow coroutine context (#678)
 

RELEASING.md

@@ -2,18 +2,18 @@ Releasing
 ========
 
 1. Bump the VERSION_NAME property in `gradle.properties` based on Major.Minor.Patch naming scheme
-2. Update `CHANGELOG.md`, adding the new release version and release notes
-3. Add your sonatype login information under gradle properties mavenCentralUsername and mavenCentralPassword in your local user gradle.properties file
-4. Run `./gradlew publish` to build the artifacts and publish them to maven
-5. Then run `./commitAndTagRelease.sh Major.Minor.Patch` with your version number
+2. Add your sonatype login information under gradle properties mavenCentralUsername and mavenCentralPassword in your local user gradle.properties file
+3. Run `./gradlew publish` to build the artifacts and publish them to maven
+4. Then run `./commitAndTagRelease.sh Major.Minor.Patch` with your version number
    1. eg "./commitAndTagRelease.sh 3.0.1"
    2. This will make a commit with the given release number and add the version tag
    3. It will then push the tag to github
       1. A github action will automatically run when the tag is pushed to generate a github release for this version
       2. Automated publishing only works if commit is tagged starting with "v". commitAndTagRelease script does this for you when passing a semver version number.
       3. The release will automatically generate release notes from the commits since last release. You may want to manually edit the release notes to add more details.
-   4. The script will also open up the branch for a PR in github
-      1. You can manually follow up with merging the branch changes when ready, but at this point the release is already public. 
+5. The script will also open up the branch for a PR in github
+   1. If there is additional relevant information about the release that isn't captured in the commit history you should add it to the PR description as well as to the release summary
+   2. Manually merge the PR branch to main, but at this point the release is already public.
 
 
 Maven Local Installation

gradle.properties

@@ -1,4 +1,4 @@
-VERSION_NAME=3.0.3
+VERSION_NAME=3.0.4
 GROUP=com.airbnb.android
 POM_DESCRIPTION=Mavericks is an Android application framework that makes product development fast and fun.
 POM_URL=https://github.com/airbnb/mavericks