update semconv to spec release 1.20.0

[tsloughter]

No description provided.

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (4bef26e) 38.11% compared to head (882af82) 38.11%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #579   +/-   ##
=======================================
  Coverage   38.11%   38.11%           
=======================================
  Files          61       61           
  Lines        3597     3597           
=======================================
  Hits         1371     1371           
  Misses       2226     2226           

Flag	Coverage Δ
api	67.91% <ø> (ø)
elixir	18.29% <ø> (ø)
erlang	38.09% <ø> (ø)
exporter	8.11% <ø> (ø)
sdk	78.13% <ø> (ø)
zipkin	54.16% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[ferd]

Woops, changes seemed straightforward (autogenerated code) but tests appear to fail here and there.

[tsloughter]

Ah, yup, Elixir module ends up with the wrong name with this change.

[andrewhr]

I'm not familiar with the codegen tool, but would be great if we could maintain old attributes as deprecated and maybe aliases, example:

@deprecated "use new_name/0 instead"
def old_name(), do: new_name()

That works even for removed attributes, which deprecated message will say it's removed.

My concern is to make it backward compatible as possible, otherwise this library will end up locking dozens of other libraries, given our approach for Erlang/Elixir to be micro-libraries for each instrumentation.

Would be that possible?

[andrewhr]

In the meantime, we got 1.21.0 released 😬

[bryannaegele]

We could probably keep a list of them, mark them there and in the changelog, and then set a policy for removal. This doesn't get updated often so it doesn't seem like a big burden to add/modify.