Skip to content

Latest commit

 

History

History
79 lines (58 loc) · 3.33 KB

2.x.md

File metadata and controls

79 lines (58 loc) · 3.33 KB
Raw

2.1.2

Apply suppression to lang-tag false positive as shares same version as go library [email protected] (dhowden/tag#77)

Version upgrades

  • com.google.guava:guava [30.0-jre -> 31.0-jre]
  • org.owasp.dependencycheck [6.0.3 -> 6.0.4]
  • org.jetbrains.kotlin:kotlin-gradle-plugin [1.4.21 -> 1.4.21-2]

2.1.1

Fix bug where Junit 4 tests were not being run.

This has been a problem since 1.1.2 when Spring Boot was upgraded to 2.4.0.

2.1.0

Upgrade to Kotlin 1.4.21 for full release notes) (also see 1.4.20.

Upgrade Spring Boot to version 2.4.1

Revert App Insights Agent to 2.6.2 to avoid some teething problems with V3.

Version upgrades

  • com.google.guava:guava [29.0-jre -> 30.0-jre]
  • net.javacrumbs.json-unit:json-unit-assertj [2.21.0 -> 2.22.0]
  • net.logstash.logback:logstash-logback-encoder [6.4 -> 6.5]
  • org.eclipse.jgit:org.eclipse.jgit [5.9.0.202009080501-r -> 5.10.0.202012080955-r]
  • org.mockito:mockito-junit-jupiter [3.6.0 -> 3.6.28]

2.0.2

Bug fix to set make test tasks use Junit5 after all such tasks have been evaluated.

2.0.1

Bug fix to set the JVM target for KotlinCompile tasks once all such tasks have been evaluated. #2.0.0

This includes an upgrade to Application Insights Agent v3. No new version of the SDK has been released and this remains at 2.6.2. Using SDK 2.6.2 with agent 3.0.0 is a supported configuration.

Note that the environment variables the Application Insights agent accepts have changed. APPLICATION_INSIGHTS_IKEY is no longer supported. It can be replaced by APPINSIGHTS_INSTRUMENTATIONKEY, or you can switch to using APPLICATIONINSIGHTS_CONNECTION_STRING and a connection string which is the recommended method. See here for details about connection strings.

The configuration file has moved from AI-Agent.xml to applicationinsights.json.

Attaching the application version number to all traces via the context no longer works - this can be worked around by making BUILD_NUMBER available as an environment variable which is then picked up by the custom dimension configuration below.

Minimum suggested configuration file:

{
  "role": {
    "name": "application-name"
  },
  "customDimensions": {
    "application_Version": "${BUILD_NUMBER}"
  },
  "selfDiagnostics": {
    "destination": "console"
  }
}

This also includes an upgrade to Spring Boot 2.4.0 and removing old suppressed vulnerabilities.

Spring Boot Upgrade guide

Spring Boot 2.4.0 has changed the way in that property files are processed. If you are not ready to update an application to the new way, legacy mode can be enabled by adding the following to the application.yml file, as mentioned in the Spring Boot Config Data Migration Guide:

spring:
    config:
       use-legacy-processing: true