Releases: fortio/fortiotel
Releases · fortio/fortiotel
v1.2.5
Changelog
- 2817f7c Bump fortio.org/fortio from 1.39.0 to 1.39.1
- 1249b64 Merge pull request #18 from fortio/dependabot/go_modules/fortio.org/fortio-1.39.1
v1.2.4
Changelog
- 7a4e717 Bump actions/checkout from 3.2.0 to 3.3.0
- addeda0 Bump docker/setup-buildx-action from 1.7.0 to 2.2.1
- e7bf225 Bump docker/setup-qemu-action from 1.2.0 to 2.1.0
- 9f4bdce Bump github/codeql-action from 2.1.37 to 2.1.38 (#17)
- 6e99534 Merge pull request #13 from fortio/dependabot/github_actions/actions/checkout-3.3.0
- 44a535e Merge pull request #14 from fortio/dependabot/github_actions/docker/setup-qemu-action-2.1.0
- 52cc10f Merge pull request #15 from fortio/dependabot/github_actions/docker/setup-buildx-action-2.2.1
- a24b770 add screenshots
- 5a90e16 switch go version to 'stable' ie 1.19.5 now
v1.2.2
Changelog
- 5301875 move changeDefaults (generalized version) to main fortio
v1.2.1
Changelog
- 090e258 Update README.md
- 496fda2 show current race/crash
- 671020f use fixed version of base fortio (fixed #11) that ensures unique headers
v1.2.0
Changelog
- 6788747 now also setup otelhttp.NewTransport through options and hook to actually get headers setup and matching traces
v1.1.2
Changelog
- 67449bd add OTEL_SERVICE_NAME which is needed/not guessed even in k8s env. remove simple/ binary accidentally checked in
v1.1.1
Changelog
- 4f3ecde syncup dockerfile with original + set OTEL_EXPORTER_OTLP_ENDPOINT for istio case
v1.1.0
Changelog
- 7abc8b7 fixed certs issue with goreleaser, pickup newer fortio with version including ours
v1.0.9
Changelog
- da6bc80 integrate local version, skip certs for now until issue is solved