Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update go updates #93

Merged
merged 1 commit into from
Feb 14, 2024
Merged

Update go updates #93

merged 1 commit into from
Feb 14, 2024

Conversation

platform-engineering-bot
Copy link
Contributor

@platform-engineering-bot platform-engineering-bot commented Dec 11, 2023 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
github.com/docker/docker require patch v25.0.2+incompatible -> v25.0.3+incompatible
github.com/docker/go-connections indirect minor v0.4.0 -> v0.5.0
github.com/felixge/httpsnoop indirect patch v1.0.3 -> v1.0.4
github.com/go-logr/logr indirect minor v1.2.4 -> v1.4.1
github.com/hashicorp/hcl indirect major v1.0.0 -> v2.19.1
github.com/opencontainers/image-spec indirect patch v1.1.0-rc5.0.20230922152145-93f6e65855a1 -> v1.1.0-rc6
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp indirect minor v0.45.0 -> v0.48.0
go.opentelemetry.io/otel indirect minor v1.19.0 -> v1.23.1
go.opentelemetry.io/otel/metric indirect minor v1.19.0 -> v1.23.1
go.opentelemetry.io/otel/trace indirect minor v1.19.0 -> v1.23.1
golang.org/x/exp indirect digest 1b97071 -> ec58324
golang.org/x/mod indirect minor v0.14.0 -> v0.15.0
golang.org/x/net indirect minor v0.20.0 -> v0.21.0
golang.org/x/sys indirect minor v0.16.0 -> v0.17.0
golang.org/x/tools indirect minor v0.17.0 -> v0.18.0

Release Notes

docker/docker (github.com/docker/docker)

v25.0.3+incompatible

Compare Source

docker/go-connections (github.com/docker/go-connections)

v0.5.0

Compare Source

felixge/httpsnoop (github.com/felixge/httpsnoop)

v1.0.4

Compare Source

go-logr/logr (github.com/go-logr/logr)

v1.4.1

Compare Source

What's Changed

Full Changelog: go-logr/logr@v1.4.0...v1.4.1

v1.4.0

Compare Source

This release dramatically improves interoperability with Go's log/slog package. In particular, logr.NewContext and logr.NewContextWithSlogLogger use the same context key, which allows logr.FromContext and logr.FromContextAsSlogLogger to return logr.Logger or *slog.Logger respectively, including transparently converting each to the other as needed.

Functions logr/slogr.NewLogr and logr/slogr.ToSlogHandler have been superceded by logr.FromSlogHandler and logr.ToSlogHandler respectively, and type logr/slogr.SlogSink has been superceded by logr.SlogSink. All of the old names in logr/slogr remain, for compatibility.

Package logr/funcr now supports logr.SlogSink, meaning that it's output passes all but one of the Slog conformance tests (that exception being that funcr handles the timestamp itself).

Users who have a logr.Logger and need a *slog.Logger can call slog.New(logr.ToSlogHandler(...)) and all output will go through the same stack.

Users who have a *slog.Logger or slog.Handler can call logr.FromSlogHandler(...) and all output will go through the same stack.

What's Changed

New Contributors

Full Changelog: go-logr/logr@v1.3.0...v1.4.0

v1.3.0

Compare Source

This release adds support for slog in a new, self-contained logr/slogr package. Implementers of a logr.LogSink are encouraged, but not required, to extend their implementation to improve the quality of log output coming from a slog API call.

Breaking change: the call depth for LogSink.Enabled when called via Logger.Enabled was fixed to be the same as for other call paths. Implementers of a LogSink who have worked around this bug will need to remove their workarounds.

Security best practices were improved. Only Go versions >= 1.18 are supported by this release.

What's Changed

New Contributors

Full Changelog: go-logr/logr@v1.2.4...v1.3.0

hashicorp/hcl (github.com/hashicorp/hcl)

v2.19.1

Compare Source

What's Changed

Full Changelog: hashicorp/hcl@v2.19.0...v2.19.1

v2.19.0

Compare Source

Enhancements
  • ext/dynblock: dynblock.Expand now supports an optional hook for calling applications to check and potentially veto (by returning error diagnostics) particular for_each values. The behavior is unchanged for callers that don't set the new option. (#​634)
Bugs Fixed
  • hclsyntax: Further fixes for treatment of "marked" values in the conditional expression, and better tracking of refined values into the conditional expression results, building on the fixes from v2.18.1. (#​633)

v2.18.1

Compare Source

Bugs Fixed
  • hclsyntax: Conditional expressions will no longer panic when one or both of their results are "marked", as is the case for situations like how HashiCorp Terraform tracks its concept of "sensitive values". (#​630)

v2.18.0

Compare Source

Enhancements

  • HCL now uses the tables from Unicode 15 when performing string normalization and character segmentation. HCL was previously using the Unicode 13 tables.

    For calling applications where consistent Unicode support is important, consider also upgrading to Go 1.21 at the same time as adopting HCL v2.18.0 so that the standard library unicode tables (used for case folding, etc) will also be from Unicode 15.

v2.17.1

Compare Source

Enhancements
  • hclsyntax: When evaluating string templates that have a long known constant prefix, HCL will truncate the known prefix to avoid creating excessively-large refinements. String prefix refinements are intended primarily for relatively-short fixed prefixes, such as https:// at the start of a URL known to use that scheme. (#​617)
  • ext/tryfunc: The "try" and "can" functions now handle unknown values slightly more precisely, and so can return known values in more situations when given expressions referring to unknown symbols. (#​622)
Bugs Fixed
  • ext/typeexpr: Will no longer try to refine unknown values of unknown type when dealing with a user-specified type constraint containing the any keyword, avoiding an incorrect panic at runtime. (#​625)
  • ext/typeexpr: Now correctly handles attempts to declare the same object type attribute multiple times by returning an error. Previously this could potentially panic by creating an incoherent internal state. (#​624)

v2.17.0

Compare Source

Enhancements

  • HCL now uses a newer version of the upstream cty library which has improved treatment of unknown values: it can now track additional optional information that reduces the range of an unknown value, which allows some operations against unknown values to return known or partially-known results. (#​590)

    Note: This change effectively passes on cty's notion of backward compatibility whereby unknown values can become "more known" in later releases. In particular, if your caller is using cty.Value.RawEquals in its tests against the results of operations with unknown values then you may see those tests begin failing after upgrading, due to the values now being more "refined".

    If so, you should review the refinements with consideration to the cty refinements docs and update your expected results to match only if the reported refinements seem correct for the given situation. The RawEquals method is intended only for making exact value comparisons in test cases, so main application code should not use it; use Equals instead for real logic, which will take refinements into account automatically.

v2.16.2

Compare Source

Bugs Fixed
  • ext/typeexpr: Verify type assumptions when applying default values, and ignore input values that do not match type assumptions. (#​594)

v2.16.1

Compare Source

Bugs Fixed
  • hclsyntax: Report correct Range.End for FunctionCall with incomplete argument (#​588)

v2.16.0

Compare Source

Enhancements

  • ext/typeexpr: Modify the Defaults functionality to implement additional flexibility. HCL will now upcast lists and sets into tuples, and maps into objects, when applying default values if the applied defaults cause the elements within a target collection to have differing types. Previously, this would have resulted in a panic, now HCL will return a modified overall type. (#​574)

    Users should return to the advice provided by v2.14.0, and apply the go-cty convert functionality after setting defaults on a given cty.Value, rather than before.

  • hclfmt: Avoid rewriting unchanged files. (#​576)

  • hclsyntax: Simplify the AST for certain string expressions. (#​584)

Bugs Fixed
  • hclwrite: Fix data race in formatSpaces. (#​511)

v2.15.0

Compare Source

Bugs Fixed
  • ext/typeexpr: Skip null objects when applying defaults. This prevents crashes when null objects are creating inside collections, and stops incomplete objects being created with only optional attributes set. (#​567)
  • ext/typeexpr: Ensure default values do not have optional metadata attached. This prevents crashes when default values are inserted into concrete go-cty values that have also been stripped of their optional metadata. (#​568)
Enhancements
  • ext/typeexpr: With the go-cty upstream depenendency updated to v1.12.0, the Defaults struct and associated functions can apply additional and more flexible 'unsafe' conversions (examples include tuples into collections such as lists and sets, and additional safety around null and dynamic values). (#​564)
  • ext/typeexpr: With the go-cty upstream depenendency updated to v1.12.0, users should now apply the go-cty convert functionality before setting defaults on a given cty.Value, rather than after, if they require a specific cty.Type. (#​564)

v2.14.1

Compare Source

Bugs Fixed
  • ext/typeexpr: Type convert defaults for optional object attributes when applying them. This prevents crashes in certain cases when the objects in question are part of a collection. (#​555)

v2.14.0

Compare Source

Enhancements
  • ext/typeexpr: Added support for optional object attributes to TypeConstraint. Attributes can be wrapped in the special optional(…) modifier, allowing the attribute to be omitted while still meeting the type constraint. For more information, cty's documentation on conversion between object types. (#​549)
  • ext/typeexpr: New function: TypeConstraintWithDefaults. In this mode, the optional(…) modifier accepts a second argument which can be used as the default value for omitted object attributes. The function returns both a cty.Type and associated Defaults, the latter of which has an Apply method to apply defaults to a given value. (#​549)

v2.13.0

Compare Source

Enhancements
  • hcl: hcl.Diagnostic now has an additional field Extra which is intended for carrying arbitrary supporting data ("extra information") related to the diagnostic message, intended to allow diagnostic renderers to optionally tailor the presentation of messages for particular situations. (#​539)
  • hclsyntax: When an error occurs during a function call, the returned diagnostics will include extra information (as described in the previous point) about which function was being called and, if the message is about an error returned by the function itself, that raw error value without any post-processing. (#​539)
Bugs Fixed
  • hclwrite: Fixed a potential data race for any situation where hclwrite.Format runs concurrently with itself. (#​534)

v2.12.0

Compare Source

Enhancements
  • hclsyntax: Evaluation of conditional expressions will now produce more precise error messages about inconsistencies between the types of the true and false result expressions, particularly in cases where both are of the same structural type kind but differ in their nested elements. (#​530)
  • hclsyntax: The lexer will no longer allocate a small object on the heap for each token. Instead, in that situation it will allocate only when needed to return a diagnostic message with source location information. (#​490)
  • hclwrite: New functions TokensForTuple, TokensForObject, and TokensForFunctionCall allow for more easily constructing the three constructs which are supported for static analysis and which HCL-based languages typically use in contexts where an expression is used only for its syntax, and not evaluated to produce a real value. For example, these new functions together are sufficient to construct all valid type constraint expressions from the Type Expressions Extension, which is the basis of variable type constraints in the Terraform language at the time of writing. (#​502)
  • json: New functions IsJSONExpression and IsJSONBody to determine if a given expression or body was created by the JSON syntax parser. In normal situations it's better not to worry about what syntax a particular expression/body originated in, but this can be useful in some trickier cases where an application needs to shim for backwards-compatibility or for static analysis that needs to have special handling of the JSON syntax's embedded expression/template conventions. (#​524)
Bugs Fixed
  • gohcl: Fix docs about supported types for blocks. (#​507)

v2.11.1

Compare Source

Bugs Fixed
  • hclsyntax: The type for an upgraded unknown value with a splat expression cannot be known (#​495)

v2.11.0

Compare Source

Enhancements
  • hclsyntax: Various error messages related to unexpectedly reaching end of file while parsing a delimited subtree will now return specialized messages describing the opening tokens as "unclosed", instead of returning a generic diagnostic that just happens to refer to the empty source range at the end of the file. This gives better feedback when error messages are being presented alongside a source code snippet, as is common in HCL-based applications, because it shows which innermost container the parser was working on when it encountered the error. (#​492)
Bugs Fixed
  • hclsyntax: Upgrading an unknown single value to a list using a splat expression must return unknown (#​493)

v2.10.1

Compare Source

  • dynblock: Decode unknown dynamic blocks in order to obtain any diagnostics even though the decoded value is not used (#​476)
  • hclsyntax: Calling functions is now more robust in the face of an incorrectly-implemented function which returns a function.ArgError whose argument index is out of range for the length of the arguments. Previously this would often lead to a panic, but now it'll return a less-precice error message instead. Functions that return out-of-bounds argument indices still ought to be fixed so that the resulting error diagnostics can be as precise as possible. (#​472)
  • hclsyntax: Ensure marks on unknown values are maintained when processing string templates. (#​478)
  • hcl: Improved error messages for various common error situtions in hcl.Index and hcl.GetAttr. These are part of the implementation of indexing and attribute lookup in the native syntax expression language too, so the new error messages will apply to problems using those operators. (#​474)

v2.10.0

Compare Source

Enhancements
  • dynblock,hcldec: Using dynblock in conjunction with hcldec can now decode blocks with unknown dynamic for_each arguments as entirely unknown values (#​461)
  • hclsyntax: Some syntax errors during parsing of the inside of ${ ... } template interpolation sequences will now produce an extra hint message about the need to escape as $${ when trying to include interpolation syntax for other languages like shell scripting, AWS IAM policies, etc. (#​462)

v2.9.1

Compare Source

Bugs Fixed
  • hclsyntax: Fix panic for marked index value. (#​451)

v2.9.0

Compare Source

Enhancements
  • HCL's native syntax and JSON scanners -- and thus all of the other parsing components that build on top of them -- are now using Unicode 13 rules for text segmentation when counting text characters for the purpose of reporting source location columns. Previously HCL was using Unicode 12. Unicode 13 still uses the same algorithm but includes some additions to the character tables the algorithm is defined in terms of, to properly categorize new characters defined in Unicode 13.

v2.8.2

Compare Source

Bugs Fixed
  • hclsyntax: Fix panic for marked collection splat. (#​436)
  • hclsyntax: Fix panic for marked template loops. (#​437)
  • hclsyntax: Fix for expression marked conditional. (#​438)
  • hclsyntax: Mark objects with keys that are sensitive. (#​440)

v2.8.1

Compare Source

Bugs Fixed
  • hclsyntax: Fix panic when expanding marked function arguments. (#​429)
  • hclsyntax: Error when attempting to use a marked value as an object key. (#​434)
  • hclsyntax: Error when attempting to use a marked value as an object key in expressions. (#​433)

v2.8.0

Compare Source

Enhancements
  • hclsyntax: Expression grouping parentheses will now be reflected by an explicit node in the AST, whereas before they were only considered during parsing. (#​426)
Bugs Fixed
  • hclwrite: The parser will now correctly include the ( and ) tokens when an expression is surrounded by parentheses. Previously it would incorrectly recognize those tokens as being extraneous tokens outside of the expression. (#​426)
  • hclwrite: The formatter will now remove (rather than insert) spaces between the ! (unary boolean "not") operator and its subsequent operand. (#​403)
  • hclsyntax: Unmark conditional values in expressions before checking their truthfulness (#​427)

v2.7.2

Compare Source

Bugs Fixed
  • gohcl: Fix panic when decoding into type containing value slices. (#​335)
  • hclsyntax: The unusual expression null[*] was previously always returning an unknown value, even though the rules for [*] normally call for it to return an empty tuple when applied to a null. As well as being a surprising result, it was particularly problematic because it violated the rule that a calling application may assume that an expression result will always be known unless the application itself introduces unknown values via the evaluation context. null[*] will now produce an empty tuple. (#​416)
  • hclsyntax: Fix panic when traversing a list, tuple, or map with cty "marks" (#​424)

v2.7.1

Compare Source

Bugs Fixed
  • hclwrite: Correctly handle blank quoted string block labels, instead of dropping them (#​422)

v2.7.0

Compare Source

Enhancements
  • json: There is a new function ParseWithStartPos, which allows overriding the starting position for parsing in case the given JSON bytes are a fragment of a larger document, such as might happen when decoding with encoding/json into a json.RawMessage. (#​389)
  • json: There is a new function ParseExpression, which allows parsing a JSON string directly in expression mode, whereas previously it was only possible to parse a JSON string in body mode. (#​381)
  • hclwrite: Block type now supports SetType and SetLabels, allowing surgical changes to the type and labels of an existing block without having to reconstruct the entire block. (#​340)
Bugs Fixed
  • hclsyntax: Fix confusing error message for bitwise OR operator (#​380)
  • hclsyntax: Several bug fixes for using HCL with values containing cty "marks" (#​404, #​406, #​407)

v2.6.0

Compare Source

Enhancements
  • hcldec: Add a new Spec, ValidateSpec, which allows custom validation of values at decode-time. (#​387)
Bugs Fixed
  • hclsyntax: Fix panic with combination of sequences and null arguments (#​386)
  • hclsyntax: Fix handling of unknown values and sequences (#​386)

v2.5.1

Compare Source

Bugs Fixed
  • hclwrite: handle legacy dot access of numeric indexes. (#​369)
  • hclwrite: Fix panic for dotted full splat (foo.*) (#​374)

v2.5.0

Compare Source

Enhancements
  • hclwrite: Generate multi-line objects and maps. (#​372)

v2.4.0

Compare Source

Enhancements
  • The Unicode data tables that HCL uses to produce user-perceived "column" positions in diagnostics and other source ranges are now updated to Unicode 12.0.0, which will cause HCL to produce more accurate column numbers for combining characters introduced to Unicode since Unicode 9.0.0.
Bugs Fixed
  • json: Fix panic when parsing malformed JSON. (#​358)

v2.3.0

Compare Source

Enhancements
  • ext/tryfunc: Optional functions try and can to include in your hcl.EvalContext when evaluating expressions, which allow users to make decisions based on the success of expressions. (#​330)
  • ext/typeexpr: Now has an optional function convert which you can include in your hcl.EvalContext when evaluating expressions, allowing users to convert values to specific type constraints using the type constraint expression syntax. (#​330)
  • ext/typeexpr: A new cty capsule type typeexpr.TypeConstraintType which, when used as either a type constraint for a function parameter or as a type constraint for a hcldec attribute specification will cause the given expression to be interpreted as a type constraint expression rather than a value expression. (#​330)
  • ext/customdecode: An optional extension that allows overriding the static decoding behavior for expressions either in function arguments or hcldec attribute specifications. (#​330)
  • ext/customdecode: New cty capsuletypes customdecode.ExpressionType and customdecode.ExpressionClosureType which, when used as either a type constraint for a function parameter or as a type constraint for a hcldec attribute specification will cause the given expression (and, for the closure type, also the hcl.EvalContext it was evaluated in) to be captured for later analysis, rather than immediately evaluated. (#​330)

v2.2.0

Compare Source

Enhancements
  • hcldec: Attribute evaluation (as part of AttrSpec or BlockAttrsSpec) now captures expression evaluation metadata in any errors it produces during type conversions, allowing for better feedback in calling applications that are able to make use of this metadata when printing diagnostic messages. (#​329)
Bugs Fixed
  • hclsyntax: IndexExpr, SplatExpr, and RelativeTraversalExpr will now report a source range that covers all of their child expression nodes. Previously they would report only the operator part, such as ["foo"], [*], or .foo, which was problematic for callers using source ranges for code analysis. (#​328)
  • hclwrite: Parser will no longer panic when the input includes index, splat, or relative traversal syntax. (#​328)

v2.1.0

Compare Source

Enhancements
  • gohcl: When decoding into a struct value with some fields already populated, those values will be retained if not explicitly overwritten in the given HCL body, with similar overriding/merging behavior as json.Unmarshal in the Go standard library.
  • hclwrite: New interface to set the expression for an attribute to be a raw token sequence, with no special processing. This has some caveats, so if you intend to use it please refer to the godoc comments. (#​320)
Bugs Fixed
  • hclwrite: The Body.Blocks method was returing the blocks in an indefined order, rather than preserving the order of declaration in the source input. (#​313)
  • hclwrite: The TokensForTraversal function (and thus in turn the Body.SetAttributeTraversal method) was not correctly handling index steps in traversals, and thus producing invalid results. (#​319)

v2.0.0

Compare Source

Initial release of HCL 2, which is a new implementating combining the HCL 1
language with the HIL expression language to produce a single language
supporting both nested configuration structures and arbitrary expressions.

HCL 2 has an entirely new Go library API and so is not a drop-in upgrade
relative to HCL 1. It's possible to import both versions of HCL into a single
program using Go's semantic import versioning mechanism:

import (
    hcl1 "github.com/hashicorp/hcl"
    hcl2 "github.com/hashicorp/hcl/v2"
)

Prior to v2.0.0 there was not a curated changelog. Consult the git history
from the latest v1.x.x tag for information on the changes to HCL 1.

opencontainers/image-spec (github.com/opencontainers/image-spec)

v1.1.0-rc6

Compare Source

Vote passed [+6 -0] - https://groups.google.com/a/opencontainers.org/g/dev/c/HOxZlfhr9-o

For changeset and diff please see - https://github.com/opencontainers/image-spec/pull/1157

open-telemetry/opentelemetry-go (go.opentelemetry.io/otel)

v1.23.1: /v0.45.2

Compare Source

Fixed
  • Register all callbacks passed during observable instrument creation instead of just the last one multiple times in go.opentelemetry.io/otel/sdk/metric. (#​4888)

v1.23.0: /v0.45.1

Compare Source

This release contains the first stable, v1, release of the following modules:

  • go.opentelemetry.io/otel/bridge/opencensus
  • go.opentelemetry.io/otel/bridge/opencensus/test
  • go.opentelemetry.io/otel/example/opencensus
  • go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc
  • go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp
  • go.opentelemetry.io/otel/exporters/stdout/stdoutmetric

See our versioning policy for more information about these stability guarantees.

Added
  • Add WithEndpointURL option to the exporters/otlp/otlpmetric/otlpmetricgrpc, exporters/otlp/otlpmetric/otlpmetrichttp, exporters/otlp/otlptrace/otlptracegrpc and exporters/otlp/otlptrace/otlptracehttp packages. (#​4808)
  • Experimental exemplar exporting is added to the metric SDK. See metric documentation for more information about this feature and how to enable it. (#​4871)
  • ErrSchemaURLConflict is added to go.opentelemetry.io/otel/sdk/resource. This error is returned when a merge of two Resources with different (non-empty) schema URL is attempted. (#​4876)
Changed
  • The Merge and New functions in go.opentelemetry.io/otel/sdk/resource now returns a partial result if there is a schema URL merge conflict. Instead of returning nil when two Resources with different (non-empty) schema URLs are merged the merged Resource, along with the new ErrSchemaURLConflict error, is returned. It is up to the user to decide if they want to use the returned Resource or not. It may have desired attributes overwritten or include stale semantic conventions. (#​4876)
Fixed
  • Fix ContainerID resource detection on systemd when cgroup path has a colon. (#​4449)
  • Fix go.opentelemetry.io/otel/sdk/metric to cache instruments to avoid leaking memory when the same instrument is created multiple times. (#​4820)
  • Fix missing Mix and Max values for go.opentelemetry.io/otel/exporters/stdout/stdoutmetric by introducing MarshalText and MarshalJSON for the Extrema type in go.opentelemetry.io/sdk/metric/metricdata. (#​4827)

New Contributors

Full Changelog: open-telemetry/opentelemetry-go@v1.22.0...v1.23.0

v1.22.0: /v0.45.0

Compare Source

Added
  • The go.opentelemetry.io/otel/semconv/v1.22.0 package.
    The package contains semantic conventions from the v1.22.0 version of the OpenTelemetry Semantic Conventions. (#​4735)
  • The go.opentelemetry.io/otel/semconv/v1.23.0 package.
    The package contains semantic conventions from the v1.23.0 version of the OpenTelemetry Semantic Conventions. (#​4746)
  • The go.opentelemetry.io/otel/semconv/v1.23.1 package.
    The package contains semantic conventions from the v1.23.1 version of the OpenTelemetry Semantic Conventions. (#​4749)
  • The go.opentelemetry.io/otel/semconv/v1.24.0 package.
    The package contains semantic conventions from the v1.24.0 version of the OpenTelemetry Semantic Conventions. (#​4770)
  • Add WithResourceAsConstantLabels option to apply resource attributes for every metric emitted by the Prometheus exporter. (#​4733)
  • Experimental cardinality limiting is added to the metric SDK.
    See metric documentation for more information about this feature and how to enable it. (#​4457)
  • Add NewMemberRaw and NewKeyValuePropertyRaw in go.opentelemetry.io/otel/baggage. (#​4804)
Changed
  • Upgrade all use of go.opentelemetry.io/otel/semconv to use v1.24.0. (#​4754)
  • Update transformations in go.opentelemetry.io/otel/exporters/zipkin to follow v1.24.0 version of the OpenTelemetry specification. (#​4754)
  • Record synchronous measurements when the passed context is canceled instead of dropping in go.opentelemetry.io/otel/sdk/metric.
    If you do not want to make a measurement when the context is cancelled, you need to handle it yourself (e.g if ctx.Err() != nil). (#​4671)
  • Improve go.opentelemetry.io/otel/trace.TraceState's performance. (#​4722)
  • Improve go.opentelemetry.io/otel/propagation.TraceContext's performance. (#​4721)
  • Improve go.opentelemetry.io/otel/baggage performance. (#​4743)
  • Improve performance of the (*Set).Filter method in go.opentelemetry.io/otel/attribute when the passed filter does not filter out any attributes from the set. (#​4774)
  • Member.String in go.opentelemetry.io/otel/baggage percent-encodes only when necessary. (#​4775)
  • Property.Value in go.opentelemetry.io/otel/baggage now returns a raw string instead of a percent-encoded value. (#​4804)
Fixed
  • Fix Parse in go.opentelemetry.io/otel/baggage to validate member value before percent-decoding. (#​4755)
  • Fix whitespace encoding of Member.String in go.opentelemetry.io/otel/baggage. (#​4756)
  • Fix baggage item key so that it is not canonicalized in go.opentelemetry.io/otel/bridge/opentracing. (#​4776)
  • Fix go.opentelemetry.io/otel/bridge/opentracing to properly handle baggage values that requires escaping during propagation. (#​4804)
  • Fix a bug where using multiple readers resulted in incorrect asynchronous counter values in go.opentelemetry.io/otel/sdk/metric. (#​4742)

v1.21.0: /v0.44.0

Compare Source

Removed
  • Remove the deprecated go.opentelemetry.io/otel/bridge/opencensus.NewTracer. (#​4706)
  • Remove the deprecated go.opentelemetry.io/otel/exporters/otlp/otlpmetric module. (#​4707)
  • Remove the deprecated go.opentelemetry.io/otel/example/view module. (#​4708)
  • Remove the deprecated go.opentelemetry.io/otel/example/fib module. (#​4723)
Fixed
  • Do not parse non-protobuf responses in go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp. (#​4719)
  • Do not parse non-protobuf responses in go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp. (#​4719)

v1.20.0: /v0.43.0

Compare Source

This release brings a breaking change for custom trace API implementations. Some interfaces (TracerProvider, Tracer, Span) now embed the go.opentelemetry.io/otel/trace/embedded types. Implementors need to update their implementations based on what they want the default behavior to be. See the "API Implementations" section of the [trace API] package documentation for more about how to accomplish this.

Added
  • Add go.opentelemetry.io/otel/bridge/opencensus.InstallTraceBridge, which installs the OpenCensus trace bridge, and replaces opencensus.NewTracer. (#​4567)
  • Add scope version to trace and metric bridges in go.opentelemetry.io/otel/bridge/opencensus. (#​4584)
  • Add the go.opentelemetry.io/otel/trace/embedded package to be embedded in the exported trace API interfaces. (#​4620)
  • Add the go.opentelemetry.io/otel/trace/noop package as a default no-op implementation of the trace API. (#​4620)
  • Add context propagation in go.opentelemetry.io/otel/example/dice. (#​4644)
  • Add view configuration to go.opentelemetry.io/otel/example/prometheus. (#​4649)
  • Add go.opentelemetry.io/otel/metric.WithExplicitBucketBoundaries, which allows defining default explicit bucket boundaries when creating histogram instruments. (#​4603)
  • Add Version function in go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc. (#​4660)
  • Add Version function in go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp. (#​4660)
  • Add Summary, SummaryDataPoint, and QuantileValue to go.opentelemetry.io/sdk/metric/metricdata. (#​4622)
  • go.opentelemetry.io/otel/bridge/opencensus.NewMetricProducer now supports exemplars from OpenCensus. (#​4585)
  • Add support for WithExplicitBucketBoundaries in go.opentelemetry.io/otel/sdk/metric. (#​4605)
  • Add support for Summary metrics in go.opentelemetry.io/otel/bridge/opencensus. (#​4668)
Deprecated
  • Deprecate go.opentelemetry.io/otel/bridge/opencensus.NewTracer in favor of opencensus.InstallTraceBridge. (#​4567)
  • Deprecate go.opentelemetry.io/otel/example/fib package is in favor of go.opentelemetry.io/otel/example/dice. (#​4618)
  • Deprecate go.opentelemetry.io/otel/trace.NewNoopTracerProvider.
    Use the added NewTracerProvider function in go.opentelemetry.io/otel/trace/noop instead. (#​4620)
  • Deprecate `go.opentelemetry.

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@platform-engineering-bot platform-engineering-bot force-pushed the renovate/go-updates branch 4 times, most recently from 876747e to 6c05540 Compare December 18, 2023 01:55
@platform-engineering-bot platform-engineering-bot force-pushed the renovate/go-updates branch 3 times, most recently from 6e996bc to 0ddeccf Compare December 25, 2023 01:54
@platform-engineering-bot platform-engineering-bot force-pushed the renovate/go-updates branch 5 times, most recently from 9c87e6e to 7ae3c5b Compare January 8, 2024 01:56
@platform-engineering-bot platform-engineering-bot force-pushed the renovate/go-updates branch 4 times, most recently from 29da04d to 5ce3e16 Compare January 18, 2024 19:10
@platform-engineering-bot platform-engineering-bot force-pushed the renovate/go-updates branch 3 times, most recently from 1cf7683 to 7698fea Compare January 24, 2024 10:13
@platform-engineering-bot platform-engineering-bot force-pushed the renovate/go-updates branch 4 times, most recently from 8b94761 to 6ebe5a7 Compare February 1, 2024 03:13
@platform-engineering-bot platform-engineering-bot force-pushed the renovate/go-updates branch 7 times, most recently from 7e5af7e to 6464d2a Compare February 7, 2024 01:42
@platform-engineering-bot platform-engineering-bot force-pushed the renovate/go-updates branch 5 times, most recently from 5753485 to aef4c8f Compare February 13, 2024 00:48
@platform-engineering-bot
Update go updates
35d7702 
Signed-off-by: Platform Engineering Bot <[email protected]>
@dustinblack dustinblack merged commit a30fdda into main Feb 14, 2024
6 checks passed
@dustinblack dustinblack deleted the renovate/go-updates branch February 14, 2024 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@platform-engineering-bot @dustinblack