Revert to use the old guava port cache (via jar) (#200 )

* Revert to using guava port cache by depending on jar

* Apply suggestions from code review

* revert code to old cache

* clean up build.gradle

* manually remove cache4 entries that are regenerated locally because of some dirty cache?

* bump gradle

* rerun tasks

* try to deflake rx tests

* cache builder tests

* api dump

* bump ktlint to work with 1.4 features

* formatting

Co-authored-by: Mike Nakhimovich <digitalbuddha@users.noreply.github.com>

2020-09-14 14:49:34 -07:00

1.4 KiB

Raw Blame History

Releasing

Change the version in top level build.gradle to a non-SNAPSHOT verson.
Update the CHANGELOG.md for the impending release.
Update the README.md with the new version.
git commit -am "Prepare for release X.Y.Z." (where X.Y.Z is the new version)
git tag -a X.Y.X -m "Version X.Y.Z" (where X.Y.Z is the new version)
- Run git tag to verify it.
git push && git push --tags
- This should be pushed to your fork.
Create a PR with this commit and merge it.
Update the top level build.gradle to the next SNAPSHOT version.
git commit -am "Prepare next development version."
Create a PR with this commit and merge it.
Login to Sonatype to promote the artifacts https://central.sonatype.org/pages/releasing-the-deployment.html
Update dependencies.gradle to point to the newly released version of cache. (It may take ~2 hours for artifact to be available after release)

Note: We are currently not pinning the sample app to the last version because the API is still fluid while Store is in alpha. We will resume pinning the sample app to a released version when we move to beta (see #159).

When we're ready to pin, restore the final step:

Update the sample module's build.gradle to point to the newly released version. (It may take ~2 hours for artifact to be available after release)

1.4 KiB Raw Blame History

Releasing

1.4 KiB

Raw Blame History