Release v0.2.1-alpha

[MikeGoldsmith]

Fixed

• Fix gRPC instrumentation memory access issue on newer kernels. (#150)
• Fix missing spans in gorillamux instrumentation. (#86)

Changed

• Update HTTP span names to include method and route to match semantic conventions. (#143)

[pellared]

I suggest removing the following line from changelog

opentelemetry-go-instrumentation/CHANGELOG.md

Line 18 in a12d31c

- Only pull docker image if not present for the emojivoto example. ([#149](https://github.com/open-telemetry/opentelemetry-go-instrumentation/pull/149))

[pellared]

Do we have any rules saying what should be the new version number? I thought that this would rather be a 0.2.1 as there are no breaking changes.

My assumption was taken from a rule that we have in .NET auto-instrumentation: https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/main/docs/versioning.md#version-numbers-before-100
Do we want to follow a this pattern (or define a similar rule)?

[MikeGoldsmith]

I did consider removing it from the changelog because it is not a functional change but as it didn't have skip changelog it was kept. I'm happy to remove it.

I'm also okay to set version as 0.2.1-alpha. I don't think versions mean all that much at the moment. Regarding no breaking changes, there wasn't any breaking changes when we went from 0.1 to 0.2, I think we did it to help signify the bump in compatibility (arm support) & features (gin support).

[MrAlias]

Can we add a changelog entry for this: #152?

[MrAlias]

This looks ready to merge: #154

Should we merge it before this to include it in the release?

[MikeGoldsmith]

Happy to merge that before the release PR, but it doesn't affect the release 👍🏻

[MrAlias]

Happy to merge that before the release PR, but it doesn't affect the release 👍🏻

Merged. Can you up update this branch?

[pellared]

Regarding no breaking changes, there wasn't any breaking changes when we went from 0.1 to 0.2, I think we did it to help signify the bump in compatibility (arm support) & features (gin support).

This is not true. We did one user-facing breaking change:

opentelemetry-go-instrumentation/CHANGELOG.md

Lines 35 to 36 in b29eef6

	- Change `OTEL_TARGET_EXE` environment variable to `OTEL_GO_AUTO_TARGET_EXE`.
	([#97](https://github.com/open-telemetry/opentelemetry-go-instrumentation/issues/97))