gradle-curiostack-plugin-0.0.184.3

Bugfixes

• Fixed gradle-golang-plugin's jib task not working #367

gradle-curiostack-plugin-0.0.184.2

Breaking Changes

• Registration of release tags has been changed to be more idiomatic with Gradle, especally with Kotlin. It should be a 1:1 change to update to the new syntax. See an example here

• armeria has introduced several API changes related to creating headers to make them immutable which will likely affect any custom decorators you have. See the release notes for examples on required changes. The changes are to the API and will be easy to find compile failures

• yarn has been upgraded. Upgrading yarn has been known to cause build failures - if you have problems, use the new feature to override tool versions, shown below, to go back to the old version. Stay tuned for a possible migration to rush which should be more stable.

Deprecations

• gradle-curio-static-site-plugin has been renamed to gradle-static-site-plugin. The old name is still present but will be removed at some point

New Features

• Java tests now show assertion failures on CI 🎉

• Tool versions can now be overridden with Gradle properties. Add org.curioswitch.curiostack.tools.<tool name>=<version> to your top-level gradle.properties to override the version of a CurioStack tool.

  • Default versions can be found here

• gradle-curio-generic-ci-plugin now provides public APIs to allow projects to add arbitrary tasks to run as part of the CI build.

  • CurioGenericCiPlugin.addToMasterBuild can be used to register a task for running only during the CI master build. addToReleaseBuild and addToBranchBuild can also be used for their respective builds
  • CurioGenericCiPlugin.getCiState can be used to retrieve information about the current CI build for projects that need to know this

• gradle-static-site-plugin now adds a deployAlpha and deployProd task, former deploying to App Engine and latter deploying to Firebase Web Hosting. Alpha will be deployed automatically during the master build unless opted out. It is recommended all static sites have a corresponding project with IAP enabled as needed for verifying the master build.

  • Set firebaseProject in the build file of the project to the project to deploy release builds to. If appEngineProject isn't set, this will also be the project alpha is deployed to.
  • Set autoDeployAlpha to false to disable automatic deploy
  • If deploying from cloudbuild, you will need to configure your IAM settings to allow the cloudbuild service account to deploy. You should generally use the static site terraform module here. You will also need to enable several APIs in your main project (the one cloudbuild runs in) - appengine, cloudresourcemanager, firebase firebasehosting See #343 #342 #341 #344

• Projects may set the Gradle property org.curioswitch.curiostack.java.disableBom=true, e.g., in gradle.properties for the project, to opt-out of using the CurioStack BOM for version management. This should only be used in rare cases, like when using gradle-curiostack-plugin in a project that publishes public Java artifacts. #313

• The previously forked terraform-provider-kubernetes is no longer downloaded / built. Terraform's upstream provider has support for almost all of its resources and this project has been deprecated

• terraform-provider-gsuite is now downloaded as a prebuilt binary, not built from source. Users may have recently found the source build of the gsuite provider to not work, and this fixes it.

Dependencies

• curiostack-bom 0.0.9 -> 0.0.10

• gcloud 241.0.0 -> 248.0.0

• gradle 5.4 -> 5.4.1

• terraform 0.11.13 -> 0.11.14

• yarn 1.13.0 -> 1.16.0

• Jackson 2.9.8 -> 2.9.9

• java-jwt 3.8.0 -> 3.8.1

• google-api-client 1.28.0 -> 1.29.0

• grpc-google-cloud-trace-v2 0.54.0 -> 0.59.0

• grpc-google-cloud-pubsub-v1 1.53.0 -> 1.58.0

• google-cloud 1.71.0 -> 1.76.0

• google-cloud-kms 1.7.0 -> 1.12.0

• dagger 2.21 -> 2.23.1

• firebase-admin 6.8.0 -> 6.8.1

• protobuf 3.7.0 -> 3.8.0

• armeria 0.84.0 -> 0.86.0

• dropwizard 4.0.3 -> 4.1.0

• grpc 1.20.0 -> 1.21.0

• zipkin-gcp 0.11.1 -> 0.12.0

• bytebuddy 1.9.12 -> 1.9.13

• armeria-google-cloud 0.0.35 -> 0.0.36

• curio-server-framework 0.0.107 -> 0.0.108

• curio-testing-framework 0.0.14 -> 0.0.15

• jooq 3.11.10 -> 3.11.11

• simpleflatmapper 6.6.2 -> 6.7.0

• gradle-docker-plugin 4.8.0 -> 4.9.0

• spotless-plugin-gradle 3.21.1 -> 3.23.0

• jib-gradle-plugin 1.1.2 -> 1.2.0

• mysql-connector-java 8.0.15 -> 8.0.16

• gradle-errorprone-plugin 0.8 -> 0.8.1

• jsoup 1.11.3 -> 1.12.1

Developer Portal - 2019/06/04

Test of the release process

protobuf-jackson-0.4.0

This release brings protobuf-jackson's feature set in sync with protobuf-java-util - unit test coverage has been brought up to sync as well. This will likely be the final release before 1.0.0 unless any bugs are found.

This release also raises the minimum java version from 7 to 8.

New Features

• printingEnumsAsInts configuration option can be used to print out enum values as their int specified in the proto file instead of their name

• sortingMapKeys configuration option can be used to print out map fields with their keys sorted in a stable order. It is recommended not to enable this option unless absolutely necessary as semantically, protobuf map fields are not supposed to have a reliable ordering

• Unknown enum values are now ignored when ignoreUnknownFields is set

Breaking Changes

• The minimum Java version for using protobuf-jackson is now 8, instead of 7 as before. If you need support for Java 7, please continue to use the old version.

protobuf-jackson-0.3.1

Bug Fixes

• Process fields in order of field number regardless of order in proto file

protobuf-jackson-0.3.0

Improvements

• Stops using classloader injection to enable compatibility with Java 11

Eggworld Server Release for 2018/09/02

Curio 160 (#180)

* Have kubectl tasks depend on logging into cluster.

* Update dependencies

@curiostack/base-web-0.0.26

Curio 155 (#168)

* Cleanup packagejson

* Fix food = 0 not working and try migrating to createRef.

* Update web dependencies and fix eggworld ref.

* Update dependencies

* Update dependencies.

* Fix guava compatibility.

* Fix eggworld bugs.

* Update cloud build generation

* Regenerate cloudbuild.

* Remove unused cloudbuild files.

* Fix gcloudLoginToCluster

* Remove deprecated tasks.

* Remove some boilerplate

* Import truth proto for migration to assertj.

* assertj-protobuf compiles.

* Licenses

* Finish assertj-proto

* Wire protoassert into testing framework.

* Spotless

* Prepare for publishing assertj-protobuf.

* Add README

* Add publications

* Add jib building of images.

* Clean

* Set DockerContextTask path

* Use proto assert with listenable future.

* Update web dependencies.

* v0.0.7

* Publish web

* Update dependencies.

* Downgrade ts-jest again

* Bump package.json

* Fix jest

* Spotless

@curiostack/base-web-0.0.25

Curio 155 (#168)

* Cleanup packagejson

* Fix food = 0 not working and try migrating to createRef.

* Update web dependencies and fix eggworld ref.

* Update dependencies

* Update dependencies.

* Fix guava compatibility.

* Fix eggworld bugs.

* Update cloud build generation

* Regenerate cloudbuild.

* Remove unused cloudbuild files.

* Fix gcloudLoginToCluster

* Remove deprecated tasks.

* Remove some boilerplate

* Import truth proto for migration to assertj.

* assertj-protobuf compiles.

* Licenses

* Finish assertj-proto

* Wire protoassert into testing framework.

* Spotless

* Prepare for publishing assertj-protobuf.

* Add README

* Add publications

* Add jib building of images.

* Clean

* Set DockerContextTask path

* Use proto assert with listenable future.

* Update web dependencies.

* v0.0.7

* Publish web

* Update dependencies.

* Downgrade ts-jest again

* Bump package.json

* Fix jest

* Spotless

@curiostack/base-web-0.0.23

Publish new node (#162)

* Fix

* Fix

* base-web 0.0.23

* Update package.json