Skip to content

Commit

Permalink
Update after 1.3.0 release (#720)
Browse files Browse the repository at this point in the history
* update after 1.3.0 release

* prepare for 1.3.1 patch

* update badge

* add note about badge
  • Loading branch information
breedx-splk authored Dec 14, 2023
1 parent 5daaa14 commit a7148e4
Show file tree
Hide file tree
Showing 5 changed files with 25 additions and 5 deletions.
19 changes: 19 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,25 @@ adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

* tbd

## Version 1.3.1 - 2023-12-14

The previous release was mistakenly built against an OpenTelemetry `SNAPSHOT` build.
This remedies that and compiles against the 1.32.0 non-SNAPSHOT bom.

* Compile against OpenTelemetry Java Instrumentation 1.32.0 (no SNAPSHOT).

## Version 1.3.0 - 2023-12-13

This is a standard release following the regular upstream `opentelemetry-android` release.
This version is succeeded by a patch release: Users should use 1.3.1 instead of 1.3.0.

* Update to use upstream `opentelemetry-android` 0.3.0 (#714)
* Reduce unnecessary attempts at directory deletion for disk buffered telemetry (#683)
* Change session sampling strategy to be consistent with other splunk RUM implementations (#698)
* Global attributes and screen attributes are now handled by upstream (#710)
* Network monitoring and network attributes appender now handle by upstream (#713)
* Fix broken url targets in sample app (#715)

## Version 1.2.0 - 2023-10-25

This is the first version of `splunk-otel-android` that is based on the upstream version of
Expand Down
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,8 @@

<p align="center">
<img alt="Stable" src="https://img.shields.io/badge/status-stable-informational?style=for-the-badge">
<a href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/tag/v1.21.0">
<img alt="OpenTelemetry Instrumentation for Java Version" src="https://img.shields.io/badge/otel-1.21.0-blueviolet?style=for-the-badge">
<a href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/tag/v1.32.0">
<img alt="OpenTelemetry Instrumentation for Java Version" src="https://img.shields.io/badge/otel-1.32.0-blueviolet?style=for-the-badge">
</a>
<a href="https://github.com/signalfx/gdi-specification/releases/tag/v1.4.0">
<img alt="Splunk GDI specification" src="https://img.shields.io/badge/GDI-1.4.0-blueviolet?style=for-the-badge">
Expand Down
3 changes: 2 additions & 1 deletion RELEASING.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,8 @@ This is the process to use to do a release:

6) Create a PR to update the version in the `gradle.properties` to the next development
version. This PR can and probably should also include updating any documentation (CHANGELOG.md,
README.md, etc) that mentions the previous version.
README.md, etc) that mentions the previous version. Make sure the badget in the top README.md
reflects the accurate upstream otel version.

7) Once this PR is merged, create a release in Github that points at the newly created version,
and make sure to provide release notes that at least mirror the contents of the CHANGELOG.md
2 changes: 1 addition & 1 deletion gradle.properties
Original file line number Diff line number Diff line change
Expand Up @@ -17,5 +17,5 @@ org.gradle.jvmargs=-Xmx2048m -Dfile.encoding=UTF-8
android.useAndroidX=true

# generate the BuildConfig class that contains the app version
version=1.3.0
version=1.3.1
group=com.splunk
2 changes: 1 addition & 1 deletion splunk-otel-android/build.gradle.kts
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ android {
}
}

val otelVersion = "1.32.0-SNAPSHOT"
val otelVersion = "1.32.0"
val otelAlphaVersion = otelVersion.replaceFirst("(-SNAPSHOT)?$".toRegex(), "-alpha$1")
val otelSemconvVersion = "1.21.0-alpha"

Expand Down

0 comments on commit a7148e4

Please sign in to comment.