<?xml version="1.0" encoding="UTF-8"?>
<otherdata xmlns="http://linux.duke.edu/metadata/other" packages="12">
<package pkgid="3652b2a1f75068cf16e8374bbc018940c6f48df5486c35ce81bd1b46663c1f48" name="go1.24" arch="src">
  <version epoch="0" ver="1.24.10" rel="150700.1.2"/>
  <changelog author="jkowalczyk@suse.com" date="1734091200">- go1.24rc1 (released 2024-12-13) is a release candidate version of
  go1.24 cut from the master branch at the revision tagged
  go1.24rc1.
  Refs boo#1236217 go1.24 release tracking
  * go1.24 requires the final point release of go1.22 or later
    for bootstrap.</changelog>
  <changelog author="jkowalczyk@suse.com" date="1737028800">- go1.24rc2 (released 2024-01-16) is a release candidate version of
  go1.24 cut from the master branch at the revision tagged
  go1.24rc2.
  Refs boo#1236217 go1.24 release tracking
  CVE-2024-45341 CVE-2024-45336 CVE-2025-22865 CVE-2024-45340
  * go#71209 go#71156 boo#1236045 security: fix CVE-2024-45341 crypto/x509: properly check for IPv6 hosts in URIs
  * go#71212 go#70530 boo#1236046 security: fix CVE-2024-45336 net/http: persist header stripping across repeated redirects
  * go#71216 boo#1236361 security: fix CVE-2025-22865 crypto/x509: avoid panic when parsing partial PKCS#1 private keys
  * go#71249 boo#1236360 security: fix CVE-2024-45340 cmd/go: restore netrc preferences for GOAUTH and fix domain lookup</changelog>
  <changelog author="jkowalczyk@suse.com" date="1738756800">- go1.24rc3 (released 2024-02-05) is a release candidate version of
  go1.24 cut from the master branch at the revision tagged
  go1.24rc3.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-22866 CVE-2025-22867
  * go#71423 go#71383 boo#1236801 security: fix CVE-2025-22866 crypto/internal/fips140/nistec: p256NegCond is variable time on ppc64le
  * go#71476 boo#1236839 security: fix CVE-2025-22867 cmd/go: arbitrary code execution during build on darwin
  * foo</changelog>
  <changelog author="jkowalczyk@suse.com" date="1739275200">- go1.24 (released 2025-02-11) is a major release of Go.
  go1.24.x minor releases will be provided through February 2026.
  https://github.com/golang/go/wiki/Go-Release-Cycle
  go1.24 arrives six months after Go 1.23. Most of its changes are
  in the implementation of the toolchain, runtime, and
  libraries. As always, the release maintains the Go 1 promise of
  compatibility. We expect almost all Go programs to continue to
  compile and run as before.
  Refs boo#1236217 go1.24 release tracking
  * Language change: Go 1.24 now fully supports generic type
    aliases: a type alias may be parameterized like a defined
    type. See the language spec for details. For now, the feature
    can be disabled by setting GOEXPERIMENT=noaliastypeparams; but
    the aliastypeparams setting will be removed for Go 1.25.
  * go command: Go modules can now track executable dependencies
    using tool directives in go.mod. This removes the need for the
    previous workaround of adding tools as blank imports to a file
    conventionally named "tools.go". The go tool command can now
    run these tools in addition to tools shipped with the Go
    distribution.
  * go command: The new -tool flag for go get causes a tool
    directive to be added to the current module for named packages
    in addition to adding require directives.
  * go command: The new tool meta-pattern refers to all tools in
    the current module. This can be used to upgrade them all with
    go get tool or to install them into your GOBIN directory with
    go install tool.
  * go command: Executables created by go run and the new behavior
    of go tool are now cached in the Go build cache. This makes
    repeated executions faster at the expense of making the cache
    larger. See go#69290.
  * go command: The go build and go install commands now accept a
  - json flag that reports build output and failures as structured
    JSON output on standard output. For details of the reporting
    format, see go help buildjson. Furthermore, go test -json now
    reports build output and failures in JSON, interleaved with
    test result JSON. These are distinguished by new Action types,
    but if they cause problems in a test integration system, you
    can revert to the text build output with GODEBUG setting
    gotestjsonbuildtext=1.
  * go command: The new GOAUTH environment variable provides a
    flexible way to authenticate private module fetches. See go
    help goauth for more information.
  * go command: The go build command now sets the main module's
    version in the compiled binary based on the version control
    system tag and/or commit. A +dirty suffix will be appended if
    there are uncommitted changes. Use the -buildvcs=false flag to
    omit version control information from the binary.
  * go command: The new GODEBUG setting toolchaintrace=1 can be
    used to trace the go command's toolchain selection process.
  * cgo: cgo supports new annotations for C functions to improve
    run time performance. cgo noescape cFunctionName tells the
    compiler that memory passed to the C function cFunctionname
    does not escape. cgo nocallback cFunctionName tells the
    compiler that the C function cFunctionName does not call back
    to any Go functions.
  * cgo: cgo currently refuses to compile calls to a C function
    which has multiple incompatible declarations. For instance,
    if f is declared as both void f(int) and void f(double),
    cgo will report an error instead of possibly generating an
    incorrect call sequence for f(0). New in this release is a
    better detector for this error condition when the incompatible
    declarations appear in different files. See go#67699.
  * objdump: The objdump tool now supports dissassembly on 64-bit
    LoongArch (GOARCH=loong64), RISC-V (GOARCH=riscv64), and S390X
    (GOARCH=s390x).
  * vet: The new tests analyzer reports common mistakes in
    declarations of tests, fuzzers, benchmarks, and examples in
    test packages, such as malformed names, incorrect signatures,
    or examples that document non-existent identifiers. Some of
    these mistakes may cause tests not to run. This analyzer is
    among the subset of analyzers that are run by go test.
  * vet: The existing printf analyzer now reports a diagnostic for
    calls of the form fmt.Printf(s), where s is a non-constant
    format string, with no other arguments. Such calls are nearly
    always a mistake as the value of s may contain the % symbol;
    use fmt.Print instead. See go#60529. This check tends to
    produce findings in existing code, and so is only applied when
    the language version (as specified by the go.mod go directive
    or //go:build comments) is at least Go 1.24, to avoid causing
    continuous integration failures when updating to the 1.24 Go
    toolchain.
  * vet: The existing buildtag analyzer now reports a diagnostic
    when there is an invalid Go major version build constraint
    within a //go:build directive. For example, //go:build go1.23.1
    refers to a point release; use //go:build go1.23 instead.
    See go#64127.
  * vet: The existing copylock analyzer now reports a diagnostic
    when a variable declared in a 3-clause "for" loop such as for i
    := iter(); done(i); i = next(i) { ... } contains a sync.Locker,
    such as a sync.Mutex. Go 1.22 changed the behavior of these
    loops to create a new variable for each iteration, copying the
    value from the previous iteration; this copy operation is not
    safe for locks. See go#66387.
  * GOCACHEPROG: The cmd/go internal binary and test caching
    mechanism can now be implemented by child processes
    implementing a JSON protocol between the cmd/go tool and the
    child process named by the GOCACHEPROG environment
    variable. This was previously behind a GOEXPERIMENT. For
    protocol details, see the documentation.
  * Runtime: Several performance improvements to the runtime have
    decreased CPU overheads by 2-3% on average across a suite of
    representative benchmarks. Results may vary by
    application. These improvements include a new builtin map
    implementation based on Swiss Tables, more efficient memory
    allocation of small objects, and a new runtime-internal mutex
    implementation.
  * Runtime: The new builtin map implementation and new
    runtime-internal mutex may be disabled by setting
    GOEXPERIMENT=noswissmap and GOEXPERIMENT=nospinbitmutex at
    build time respectively.
  * Compiler: The compiler already disallowed defining new methods
    with receiver types that were cgo-generated, but it was
    possible to circumvent that restriction via an alias type. Go
    1.24 now always reports an error if a receiver denotes a
    cgo-generated type, whether directly or indirectly (through an
    alias type).
  * Linker: The linker now generates a GNU build ID (the ELF
    NT_GNU_BUILD_ID note) on ELF platforms and a UUID (the Mach-O
    LC_UUID load command) on macOS by default. The build ID or UUID
    is derived from the Go build ID. It can be disabled by the -B
    none linker flag, or overridden by the -B 0xNNNN linker flag
    with a user-specified hexadecimal value.
  * Bootstrap: As mentioned in the Go 1.22 release notes, Go 1.24
    now requires Go 1.22.6 or later for bootstrap. We expect that
    Go 1.26 will require a point release of Go 1.24 or later for
    bootstrap.
  * Standard library: Directory-limited filesystem access: The new
    os.Root type provides the ability to perform filesystem
    operations within a specific directory. The os.OpenRoot
    function opens a directory and returns an os.Root. Methods on
    os.Root operate within the directory and do not permit paths
    that refer to locations outside the directory, including ones
    that follow symbolic links out of the directory. The methods on
    os.Root mirror most of the file system operations available in
    the os package, including for example os.Root.Open,
    os.Root.Create, os.Root.Mkdir, and os.Root.Stat,
  * Standard library: new benchmark function: Benchmarks may now
    use the faster and less error-prone testing.B.Loop method to
    perform benchmark iterations like for b.Loop() { ... } in place
    of the typical loop structures involving b.N like for range
    b.N. This offers two significant advantages: 1) The benchmark
    function will execute exactly once per -count, so expensive
    setup and cleanup steps execute only once, and 2) Function call
    parameters and results are kept alive, preventing the compiler
    from fully optimizing away the loop body.
  * Standard library: Improved finalizers: The new
    runtime.AddCleanup function is a finalization mechanism that is
    more flexible, more efficient, and less error-prone than
    runtime.SetFinalizer. AddCleanup attaches a cleanup function to
    an object that will run once the object is no longer reachable.
    However, unlike SetFinalizer, multiple cleanups may be attached
    to a single object, cleanups may be attached to interior
    pointers, cleanups do not generally cause leaks when objects
    form a cycle, and cleanups do not delay the freeing of an
    object or objects it points to. New code should prefer
    AddCleanup over SetFinalizer.
  * Standard library: New weak package: The new weak package
    provides weak pointers. Weak pointers are a low-level primitive
    provided to enable the creation of memory-efficient structures,
    such as weak maps for associating values, canonicalization maps
    for anything not covered by package unique, and various kinds
    of caches. For supporting these use-cases, this release also
    provides runtime.AddCleanup and maphash.Comparable.
  * Standard library: New crypto/mlkem package: The new
    crypto/mlkem package implements ML-KEM-768 and
    ML-KEM-1024. ML-KEM is a post-quantum key exchange mechanism
    formerly known as Kyber and specified in FIPS 203.
  * Standard library: New crypto/hkdf, crypto/pbkdf2, and
    crypto/sha3 packages: The new crypto/hkdf package implements
    the HMAC-based Extract-and-Expand key derivation function HKDF,
    as defined in RFC 5869. The new crypto/pbkdf2 package
    implements the password-based key derivation function PBKDF2,
    as defined in RFC 8018. The new crypto/sha3 package implements
    the SHA-3 hash function and SHAKE and cSHAKE extendable-output
    functions, as defined in FIPS 202. All three packages are based
    on pre-existing golang.org/x/crypto/... packages.
  * FIPS: release includes a new set of mechanisms to facilitate
    FIPS 140-3 compliance. See https://go.dev/doc/security/fips140
    The Go Cryptographic Module is a set of internal standard
    library packages that are transparently used to implement FIPS
    140-3 approved algorithms. Applications require no changes to
    use the Go Cryptographic Module for approved algorithms.
  * FIPS: The new GOFIPS140 environment variable can be used to
    select the Go Cryptographic Module version to use in a
    build. The new fips140 GODEBUG setting can be used to enable
    FIPS 140-3 mode at runtime.
  * FIPS: Go 1.24 includes Go Cryptographic Module version v1.0.0,
    which is currently under test with a CMVP-accredited
    laboratory.
  * Standard library: New experimental testing/synctest package:
    The new experimental testing/synctest package provides support
    for testing concurrent code. The synctest.Run function starts a
    group of goroutines in an isolated "bubble". Within the bubble,
    time package functions operate on a fake clock.  The
    synctest.Wait function waits for all goroutines in the current
    bubble to block. The synctest package is experimental and must
    be enabled by setting GOEXPERIMENT=synctest at build time. The
    package API is subject to change in future releases. See issue
    go#67434 for more information and to provide feeback.
  * archive: The (*Writer).AddFS implementations in both
    archive/zip and archive/tar now write a directory header for an
    empty directory.
  * bytes: The bytes package adds several functions that work with
    iterators.
  * bytes: Lines returns an iterator over the newline-terminated
    lines in a byte slice.
  * bytes: SplitSeq returns an iterator over all subslices of a
    byte slice split around a separator.
  * bytes: SplitAfterSeq returns an iterator over subslices of a
    byte slice split after each instance of a separator.
  * bytes: FieldsSeq returns an iterator over subslices of a byte
    slice split around runs of whitespace characters, as defined by
    unicode.IsSpace.
  * bytes: FieldsFuncSeq returns an iterator over subslices of a
    byte slice split around runs of Unicode code points satisfying
    a predicate.
  * crypto/aes: The value returned by NewCipher no longer
    implements the NewCTR, NewGCM, NewCBCEncrypter, and
    NewCBCDecrypter methods. These methods were undocumented and
    not available on all architectures. Instead, the Block value
    should be passed directly to the relevant crypto/cipher
    functions. For now, crypto/cipher still checks for those
    methods on Block values, even if they are not used by the
    standard library anymore.
  * crypto/aes: The Stream implementation returned by NewCTR when
    used with crypto/aes is now several times faster on amd64 and
    arm64.
  * crypto/cipher: The new NewGCMWithRandomNonce function returns
    an AEAD that implements AES-GCM by generating a random nonce
    during Seal and prepending it to the ciphertext.
  * crypto/cipher: NewOFB, NewCFBEncrypter, and NewCFBDecrypter are
    now deprecated. OFB and CFB mode are not authenticated, which
    generally enables active attacks to manipulate and recover the
    plaintext. It is recommended that applications use AEAD modes
    instead. If an unauthenticated Stream mode is required, use
    NewCTR instead.
  * crypto/ecdsa: PrivateKey.Sign now produces a deterministic
    signature according to RFC 6979 if the random source is nil.
  * crypto/md5: The value returned by md5.New now also implements
    the encoding.BinaryAppender interface.
  * crypto/rand: The Read function is now guaranteed not to
    fail. It will always return nil as the error result. If Read
    were to encounter an error while reading from Reader, the
    program will irrecoverably crash. Note that the platform APIs
    used by the default Reader are documented to always succeed, so
    this change should only affect programs that override the
    Reader variable. One exception are Linux kernels before version
    3.17, where the default Reader still opens /dev/urandom and may
    fail.
  * crypto/rand: On Linux 6.11 and later, Reader now uses the
    getrandom system call via vDSO. This is several times faster,
    especially for small reads.
  * crypto/rand: On OpenBSD, Reader now uses arc4random_buf(3).
  * crypto/rand: The new Text function can be used to generate
    cryptographically secure random text strings.
  * crypto/rsa: GenerateKey now returns an error if a key of less
    than 1024 bits is requested. All Sign, Verify, Encrypt, and
    Decrypt methods now return an error if used with a key smaller
    than 1024 bits. Such keys are insecure and should not be
    used. GODEBUG setting rsa1024min=0 restores the old behavior,
    but we recommend doing so only if necessary and only in tests,
    for example by adding a //go:debug rsa1024min=0 line to a test
    file. A new GenerateKey example provides an easy-to-use
    standard 2048-bit test key.
  * crypto/rsa: It is now safe and more efficient to call
    PrivateKey.Precompute before PrivateKey.Validate. Precompute is
    now faster in the presence of partially filled out
    PrecomputedValues, such as when unmarshaling a key from JSON.
  * crypto/rsa: The package now rejects more invalid keys, even
    when Validate is not called, and GenerateKey may return new
    errors for broken random sources. The Primes and Precomputed
    fields of PrivateKey are now used and validated even when some
    values are missing. See also the changes to crypto/x509 parsing
    and marshaling of RSA keys described below.
  * crypto/rsa: SignPKCS1v15 and VerifyPKCS1v15 now support
    SHA-512/224, SHA-512/256, and SHA-3.
  * crypto/rsa: GenerateKey now uses a slightly different method to
    generate the private exponent (Carmichael's totient instead of
    Euler's totient). Rare applications that externally regenerate
    keys from only the prime factors may produce different but
    compatible results.
  * crypto/rsa: Public and private key operations are now up to two
    times faster on wasm.
  * crypto/sha1: The value returned by sha1.New now also implements
    the encoding.BinaryAppender interface.
  * crypto/sha256: The values returned by sha256.New and
    sha256.New224 now also implement the encoding.BinaryAppender
    interface.
  * crypto/sha512: The values returned by sha512.New,
    sha512.New384, sha512.New512_224 and sha512.New512_256 now also
    implement the encoding.BinaryAppender interface.
  * crypto/subtle: The new WithDataIndependentTiming function
    allows the user to run a function with architecture specific
    features enabled which guarantee specific instructions are data
    value timing invariant. This can be used to make sure that code
    designed to run in constant time is not optimized by CPU-level
    features such that it operates in variable time. Currently,
    WithDataIndependentTiming uses the PSTATE.DIT bit on arm64, and
    is a no-op on all other architectures. GODEBUG setting
    dataindependenttiming=1 enables the DIT mode for the entire Go
    program.
  * crypto/subtle: The XORBytes output must overlap exactly or not
    at all with the inputs. Previously, the behavior was otherwise
    undefined, while now XORBytes will panic.
  * crypto/tls: The TLS server now supports Encrypted Client Hello
    (ECH). This feature can be enabled by populating the
    Config.EncryptedClientHelloKeys field.
  * crypto/tls: The new post-quantum X25519MLKEM768 key exchange
    mechanism is now supported and is enabled by default when
    Config.CurvePreferences is nil. GODEBUG setting tlsmlkem=0
    reverts the default.
  * crypto/tls: Support for the experimental X25519Kyber768Draft00
    key exchange has been removed.
  * crypto/tls: Key exchange ordering is now handled entirely by
    the crypto/tls package. The order of Config.CurvePreferences is
    now ignored, and the contents are only used to determine which
    key exchanges to enable when the field is populated.
  * crypto/tls: The new ClientHelloInfo.Extensions field lists the
    IDs of the extensions received in the Client Hello
    message. This can be useful for fingerprinting TLS clients.
  * crypto/x509: The x509sha1 GODEBUG setting has been
    removed. Certificate.Verify no longer supports SHA-1 based
    signatures.
  * crypto/x509: OID now implements the encoding.BinaryAppender and
    encoding.TextAppender interfaces.
  * crypto/x509: The default certificate policies field has changed
    from Certificate.PolicyIdentifiers to
    Certificate.Policies. When parsing certificates, both fields
    will be populated, but when creating certificates policies will
    now be taken from the Certificate.Policies field instead of the
    Certificate.PolicyIdentifiers field. This change can be
    reverted with GODEBUG setting x509usepolicies=0.
  * crypto/x509: CreateCertificate will now generate a serial
    number using a RFC 5280 compliant method when passed a template
    with a nil Certificate.SerialNumber field, instead of failing.
  * crypto/x509: Certificate.Verify now supports policy validation,
    as defined in RFC 5280 and RFC 9618. The new
    VerifyOptions.CertificatePolicies field can be set to an
    acceptable set of policy OIDs. Only certificate chains with
    valid policy graphs will be returned from Certificate.Verify.
  * crypto/x509: MarshalPKCS8PrivateKey now returns an error
    instead of marshaling an invalid RSA
    key. (MarshalPKCS1PrivateKey doesn't have an error return, and
    its behavior when provided invalid keys continues to be
    undefined.)
  * crypto/x509: ParsePKCS1PrivateKey and ParsePKCS8PrivateKey now
    use and validate the encoded CRT values, so might reject
    invalid RSA keys that were previously accepted. Use GODEBUG
    setting x509rsacrt=0 to revert to recomputing the CRT values.
  * debug/elf: The debug/elf package adds support for handling
    symbol versions in dynamic ELF (Executable and Linkable Format)
    files. The new File.DynamicVersions method returns a list of
    dynamic versions defined in the ELF file. The new
    File.DynamicVersionNeeds method returns a list of dynamic
    versions required by this ELF file that are defined in other
    ELF objects. Finally, the new Symbol.HasVersion and
    Symbol.VersionIndex fields indicate the version of a symbol.
  * encoding: Two new interfaces, TextAppender and BinaryAppender,
    have been introduced to append the textual or binary
    representation of an object to a byte slice. These interfaces
    provide the same functionality as TextMarshaler and
    BinaryMarshaler, but instead of allocating a new slice each
    time, they append the data directly to an existing slice. These
    interfaces are now implemented by standard library types that
    already implemented TextMarshaler and/or BinaryMarshaler.
  * encoding/json: When marshaling, a struct field with the new
    omitzero option in the struct field tag will be omitted if its
    value is zero. If the field type has an IsZero() bool method,
    that will be used to determine whether the value is
    zero. Otherwise, the value is zero if it is the zero value for
    its type. The omitzero field tag is clearer and less
    error-prone than omitempty when the intent is to omit zero
    values. In particular, unlike omitempty, omitzero omits
    zero-valued time.Time values, which is a common source of
    friction.
  * encoding/json: If both omitempty and omitzero are specified,
    the field will be omitted if the value is either empty or zero
    (or both).
  * encoding/json: UnmarshalTypeError.Field now includes embedded
    structs to provide more detailed error messages.
  * go/types: All go/types data structures that expose sequences
    using a pair of methods such as Len() int and At(int) T now
    also have methods that return iterators, allowing you to
    simplify code. The methods are: Interface.EmbeddedTypes,
    Interface.ExplicitMethods, Interface.Methods,
    MethodSet.Methods, Named.Methods, Scope.Children,
    Struct.Fields, Tuple.Variables, TypeList.Types,
    TypeParamList.TypeParams, Union.Terms.
  * hash/adler32: The value returned by New now also implements the
    encoding.BinaryAppender interface.
  * hash/crc32: The values returned by New and NewIEEE now also
    implement the encoding.BinaryAppender interface.
  * hash/crc64: The value returned by New now also implements the
    encoding.BinaryAppender interface.
  * hash/fnv: The values returned by New32, New32a, New64, New64a,
    New128 and New128a now also implement the
    encoding.BinaryAppender interface.
  * hash/maphash: The new Comparable and WriteComparable functions
    can compute the hash of any comparable value. These make it
    possible to hash anything that can be used as a Go map key.
  * log/slog: The new DiscardHandler is a handler that is never
    enabled and always discards its output.
  * log/slog: Level and LevelVar now implement the
    encoding.TextAppender interface.
  * math/big: Float, Int and Rat now implement the
    encoding.TextAppender interface.
  * math/rand: Calls to the deprecated top-level Seed function no
    longer have any effect. To restore the old behavior use GODEBUG
    setting randseednop=0. For more background see proposal
    go#67273.
  * math/rand/v2: ChaCha8 and PCG now implement the
    encoding.BinaryAppender interface.
  * net: ListenConfig now uses MPTCP by default on systems where it
    is supported (currently on Linux only).
  * net: IP now implements the encoding.TextAppender interface.
  * net/http: Transport's limit on 1xx informational responses
    received in response to a request has changed. It previously
    aborted a request and returned an error after receiving more
    than 5 1xx responses. It now returns an error if the total size
    of all 1xx responses exceeds the
    Transport.MaxResponseHeaderBytes configuration setting.
  * net/http: In addition, when a request has a
    net/http/httptrace.ClientTrace.Got1xxResponse trace hook, there
    is now no limit on the total number of 1xx responses. The
    Got1xxResponse hook may return an error to abort a request.
  * net/http: Transport and Server now have an HTTP2 field which
    permits configuring HTTP/2 protocol settings.
  * net/http: The new Server.Protocols and Transport.Protocols
    fields provide a simple way to configure what HTTP protocols a
    server or client use.
  * net/http: The server and client may be configured to support
    unencrypted HTTP/2 connections.
  * net/http: When Server.Protocols contains UnencryptedHTTP2, the
    server will accept HTTP/2 connections on unencrypted ports. The
    server can accept both HTTP/1 and unencrypted HTTP/2 on the
    same port.
  * net/http: When Transport.Protocols contains UnencryptedHTTP2
    and does not contain HTTP1, the transport will use unencrypted
    HTTP/2 for http:// URLs. If the transport is configured to use
    both HTTP/1 and unencrypted HTTP/2, it will use HTTP/1.
  * net/http: Unencrypted HTTP/2 support uses "HTTP/2 with Prior
    Knowledge" (RFC 9113, section 3.3). The deprecated "Upgrade:
    h2c" header is not supported.
  * net/netip: Addr, AddrPort and Prefix now implement the
    encoding.BinaryAppender and encoding.TextAppender interfaces.
  * net/url: URL now also implements the encoding.BinaryAppender
    interface.
  * os/user: On Windows, Current can now be used in Windows Nano
    Server. The implementation has been updated to avoid using
    functions from the NetApi32 library, which is not available in
    Nano Server.
  * os/user: On Windows, Current, Lookup and LookupId now support
    the following built-in service user accounts: NT
    AUTHORITY\SYSTEM, NT AUTHORITY\LOCAL SERVICE, NT
    AUTHORITY\NETWORK SERVICE
  * os/user: On Windows, Current has been made considerably faster
    when the current user is joined to a slow domain, which is the
    usual case for many corporate users. The new implementation
    performance is now in the order of milliseconds, compared to
    the previous implementation which could take several seconds,
    or even minutes, to complete.
  * os/user: On Windows, Current now returns the process owner user
    when the current thread is impersonating another
    user. Previously, it returned an error.
  * regexp: Regexp now implements the encoding.TextAppender
    interface.
  * runtime: The GOROOT function is now deprecated. In new code
    prefer to use the system path to locate the "go" binary, and
    use go env GOROOT to find its GOROOT.
  * strings: The strings package adds several functions that work
    with iterators.
  * strings: Lines returns an iterator over the newline-terminated
    lines in a string.
  * strings: SplitSeq returns an iterator over all substrings of a
    string split around a separator.
  * strings: SplitAfterSeq returns an iterator over substrings of a
    string split after each instance of a separator.
  * strings: FieldsSeq returns an iterator over substrings of a
    string split around runs of whitespace characters, as defined
    by unicode.IsSpace.
  * strings: FieldsFuncSeq returns an iterator over substrings of a
    string split around runs of Unicode code points satisfying a
    predicate.
  * sync: The implementation of sync.Map has been changed,
    improving performance, particularly for map modifications. For
    instance, modifications of disjoint sets of keys are much less
    likely to contend on larger maps, and there is no longer any
    ramp-up time required to achieve low-contention loads from the
    map. If you encounter any problems, set
    GOEXPERIMENT=nosynchashtriemap at build time to switch back to
    the old implementation and please file an issue.
  * testing: The new T.Context and B.Context methods return a
    context that's canceled after the test completes and before
    test cleanup functions run.
  * testing: The new T.Chdir and B.Chdir methods can be used to
    change the working directory for the duration of a test or
    benchmark.
  * text/template: Templates now support range-over-func and
    range-over-int.
  * time: Time now implements the encoding.BinaryAppender and
    encoding.TextAppender interfaces.
  * Linux port: As announced in the Go 1.23 release notes, Go 1.24
    requires Linux kernel version 3.2 or later.
  * Darwin port: Go 1.24 is the last release that will run on macOS
    11 Big Sur. Go 1.25 will require macOS 12 Monterey or later.
  * WebAssembly: The go:wasmexport compiler directive is added for
    Go programs to export functions to the WebAssembly host.
  * WebAssembly: On WebAssembly System Interface Preview 1
    (GOOS=wasip1 GOARCH=wasm), Go 1.24 supports building a Go
    program as a reactor/library, by specifying the
  - buildmode=c-shared build flag.
  * WebAssembly: More types are now permitted as argument or result
    types for go:wasmimport functions. Specifically, bool, string,
    uintptr, and pointers to certain types are allowed (see the
    documentation for detail), along with 32-bit and 64-bit integer
    and float types, and unsafe.Pointer, which are already
    allowed. These types are also permitted as argument or result
    types for go:wasmexport functions.
  * WebAssembly: The support files for WebAssembly have been moved
    to lib/wasm from misc/wasm.
  * Windows: The 32-bit windows/arm port (GOOS=windows GOARCH=arm)
    has been marked broken. See issue go#70705 for details.</changelog>
  <changelog author="jkowalczyk@suse.com" date="1741089600">- go1.24.1 (released 2025-03-04) includes security fixes to the
  net/http package, as well as bug fixes to cgo, the compiler, the
  go command, and the reflect, runtime, and syscall packages.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-22870
  * go#71986 go#71984 boo#1238572 security: fix CVE-2025-22870 net/http, x/net/proxy, x/net/http/httpproxy: proxy bypass using IPv6 zone IDs
  * go#71687 cmd/go: panics with GOAUTH='git dir' go get -x
  * go#71705 runtime: add linkname of runtime.lastmoduledatap for cloudwego/sonic
  * go#71728 runtime: usleep computes wrong tv_nsec on s390x
  * go#71745 crypto: add fips140 as an opaque GODEBUG setting and add documentation for it
  * go#71829 cmd/compile: fail to compile package in 1.24
  * go#71836 os: possible regression from Go 1.23 to Go 1.24 when opening DevNull with O_TRUNC
  * go#71840 runtime: recover added in range-over-func loop body doesn't stop panic propagation / segfaults printing error
  * go#71849 os: spurious SIGCHILD on running child process
  * go#71855 cmd/compile: Pow10 freeze the compiler on certain condition on Go 1.24
  * go#71858 debug/buildinfo: false positives with external scanners flag for go117 binary in testdata
  * go#71876 reflect: Value.Seq panicking on functional iterator methods
  * go#71904 cmd/compile: nil dereference when storing field of non-nil struct value
  * go#71916 reflect: Value.Seq iteration value types not matching the type of given int types
  * go#71938 cmd/compile: "fatal error: found pointer to free object" on arm64
  * go#71955 proposal: runtime: allow cleanups to run concurrently
  * go#71963 runtime/cgo: does not build with -Wdeclaration-after-statement
  * go#71977 syscall: js/wasm file operations fail on windows / node.js</changelog>
  <changelog author="jkowalczyk@suse.com" date="1741176000">- Packaging improvements:
  * SLE-12 only: Add declarations to Cgo seccomp_linux.go
    for new syscalls seccomp and getrandom which are not present
    in the kernel headers supplied by glibc version in SLE-12.
    (Marcus Meissner)
    Refs boo#1239182
  * Add patch go-fixseccomp.patch</changelog>
  <changelog author="jkowalczyk@suse.com" date="1743508800">- go1.24.2 (released 2025-04-01) includes security fixes to the
  net/http package, as well as bug fixes to the compiler, the
  runtime, the go command, and the crypto/tls, go/types, net/http,
  and testing packages.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-22871
  * go#72011 go#71988 boo#1240550 security: fix CVE-2025-22871 net/http: reject bare LF in chunked encoding
  * go#72067 cmd/compile: out of memory
  * go#72103 net/http: go1.24 breaks compatibility by modifying in-place the tls.Config{NextProtos}
  * go#72115 runtime: process hangs for mips hardware
  * go#72796 runtime: add an example for AddCleanup
  * go#72822 cmd/compile: OOM with mutually-recursive iter.Seq
  * go#72823 crypto/tls: FIPS 140-3 modes reject ECDSA w/ curve P-521/SHA-512 in TLS
  * go#72826 go/types, types2: CheckExpr / Eval may mutate type checked objects (=&gt; data race)
  * go#72872 runtime: cgo callback on extra M treated as external code after nested cgo callback returns
  * go#72934 testing: b.StopTimer breaks b.Loop
  * go#72938 internal/godebugs: winsymlink and winreadlinkvolume have incorrect defaults for Go 1.22
  * go#72974 testing: b.Loop gives bogus results in some situations</changelog>
  <changelog author="jkowalczyk@suse.com" date="1743595200">- Packaging improvements:
  * SLE-12 only: Fix conditional for go-fixsecomp.patch to work
    correctly when suse_version is undefined.
    Refs boo#1239182
  * Fix RPM warning by removing valid macro syntax in comment
    describing naming format of llvm-tsan_commit.tar.xz</changelog>
  <changelog author="mail+rpm@georg-pfuetzenreuter.net" date="1745236800">- Add gh-issue-73141.patch to repair random segmentation faults (boo#1240764)</changelog>
  <changelog author="jkowalczyk@suse.com" date="1746532800">- go1.24.3 (released 2025-05-06) includes security fixes to the os
  package, as well as bug fixes to the runtime, the compiler, the
  linker, the go command, and the crypto/tls and os packages.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-22873
  * go#73556 go#73555 boo#1242715 security: fix CVE-2025-22873 os: Root permits access to parent directory
  * go#73082 os: Root.Open panics when opening a symlink referencing the root
  * go#73092 cmd/link: linkname directive on userspace variable can override runtime variable
  * go#73118 crypto/tls: ECH decodeInnerClientHello incorrectly rejects ClientHello with GREASE values in supportedVersions
  * go#73144 runtime: segmentation fault from vgetrandomPutState and runtime.growslice w/ runtime.OSLockThread
  * go#73192 runtime: -race data race map traceback report incorrect functions
  * go#73281 cmd/compile: program compiles to wasm but is invalid: go:wasmexport: integer too large
  * go#73379 runtime, x/sys/unix: Connectx is broken on darwin/amd64
  * go#73440 cmd/compile: infinite loop in the inliner
  * go#73500 cmd/go: +dirty in version stamping doesn't combine well with +incompatible
- Packaging improvements:
  * Drop gh-issue-73141.patch to repair random segmentation faults (boo#1240764)
    fixed in upstream release.</changelog>
  <changelog author="jkowalczyk@suse.com" date="1749124800">- go1.24.4 (released 2025-06-05) includes security fixes to the
  crypto/x509, net/http, and os packages, as well as bug fixes to
  the linker, the go command, and the hash/maphash and os packages.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-22874 CVE-2025-0913 CVE-2025-4673
  * go#73700 go#73702 boo#1244158 security: fix CVE-2025-22874 crypto/x509: ExtKeyUsageAny bypasses policy validation
  * go#73720 go#73612 boo#1244157 security: fix CVE-2025-0913 os: inconsistent handling of O_CREATE|O_EXCL on Unix and Windows
  * go#73906 go#73816 boo#1244156 security: fix CVE-2025-4673 net/http: sensitive headers not cleared on cross-origin redirect
  * go#73570 os: Root.Mkdir creates directories with zero permissions on OpenBSD
  * go#73669 hash/maphash: hashing channels with purego impl. of maphash.Comparable panics
  * go#73678 runtime/debug: BuildSetting does not document DefaultGODEBUG
  * go#73809 cmd/go: add fips140 module selection mechanism
  * go#73832 cmd/link: Go 1.24.3 and 1.23.9 regression - duplicated definition of symbol dlopen</changelog>
  <changelog author="jkowalczyk@suse.com" date="1751976000">- go1.24.5 (released 2025-07-08) includes security fixes to the go
  command, as well as bug fixes to the compiler, the linker, the
  runtime, and the go command.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-4674
  * go#74381 go#74380 boo#1246118 security: fix CVE-2025-4674 cmd/go: disable support for multiple vcs in one module
  * go#73908 runtime: bad frame pointer during panic during duffcopy
  * go#74098 cmd/compile: regression on ppc64le bit operations
  * go#74113 cmd/go: crash on unknown GOEXPERIMENT during toolchain selection
  * go#74290 runtime: heap mspan limit is set too late, causing data race between span allocation and conservative scanning
  * go#74294 internal/trace: stress tests triggering suspected deadlock in tracer
  * go#74346 runtime: memlock not unlocked in all control flow paths in sysReserveAlignedSbrk
  * go#74363 runtime/pprof: crash "cannot read stack of running goroutine" in goroutine profile
  * go#74403 cmd/link: duplicated definition of symbol github.com/ebitengine/purego.syscall15XABI0 when running with ASAN</changelog>
  <changelog author="jkowalczyk@suse.com" date="1754481600">- go1.24.6 (released 2025-08-06) includes security fixes to the
  database/sql and os/exec packages, as well as bug fixes to the
  runtime.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-47906 CVE-2025-47907
  * go#74804 go#74466 boo#1247719 security: fix CVE-2025-47906 os/exec: LookPath bug: incorrect expansion of "", "." and ".." in some PATH configurations
  * go#74833 go#74831 boo#1247720 security: fix CVE-2025-47907 database/sql: incorrect results returned from Rows.Scan
  * go#73800 runtime: RSS seems to have increased in Go 1.24 while the runtime accounting has not
  * go#74416 runtime: use-after-free of allpSnapshot in findRunnable
  * go#74694 runtime: segfaults in runtime.(*unwinder).next
  * go#74760 os/user:nolibgcc: TestGroupIdsTestUser failures</changelog>
  <changelog author="jkowalczyk@suse.com" date="1755172800">- Packaging improvements:
  * Remove conditional gccgo bootstrap sections and gcc-go.patch.
    gccgo cannot be used in any version newer than go1.21. Removal
    simplifies go1.x package code.
  * go1.21 can optionally be bootstrapped with gccgo and serve as
    the inital version of go1.x.
  * go1.21 will be the initial version of Go in the bootstrap chain
    until gcc gccgo is updated to support a language level newer
    than go1.18.
  * Drop gcc-go.patch
  * Refs boo#1247816 bootstrap go1.21 with gccgo
  * Refs boo#1248082 drop unused gccgo bootstrap code in go1.22+</changelog>
  <changelog author="jkowalczyk@suse.com" date="1756900800">- go1.24.7 (released 2025-09-03) includes fixes to the go command,
  and the net and os/exec packages.
  Refs boo#1236217 go1.24 release tracking
  * go#75007 os/exec: TestLookPath fails on plan9 after CL 685755
  * go#74821 cmd/go: "get toolchain@latest" should ignore release candidates
  * go#74818 net: WriteMsgUDPAddrPort should accept IPv4-mapped IPv6 destination addresses on IPv4 UDP sockets</changelog>
  <changelog author="asarai@suse.com" date="1758283200">- Package svgpan.js to fix issues with "go tool pprof". boo#1249985</changelog>
  <changelog author="jkowalczyk@suse.com" date="1759838400">- go1.24.8 (released 2025-10-07) includes security fixes to the
  archive/tar, crypto/tls, crypto/x509, encoding/asn1,
  encoding/pem, net/http, net/mail, net/textproto, and net/url
  packages, as well as bug fixes to the compiler, the linker, and
  the debug/pe, net/http, os, and sync/atomic packages.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-58189 CVE-2025-61725 CVE-2025-58188 CVE-2025-58185 CVE-2025-58186 CVE-2025-61723 CVE-2025-58183 CVE-2025-47912 CVE-2025-58187 CVE-2025-61724
  * go#75660 go#75652 boo#1251255 security: fix CVE-2025-58189 crypto/tls: ALPN negotiation error contains attacker controlled information
  * go#75700 go#75680 boo#1251253 security: fix CVE-2025-61725 net/mail: excessive CPU consumption in ParseAddress
  * go#75702 go#75675 boo#1251260 security: fix CVE-2025-58188 crypto/x509: panic when validating certificates with DSA public keys
  * go#75704 go#75671 boo#1251258 security: fix CVE-2025-58185 encoding/asn1: pre-allocating memory when parsing DER payload can cause memory exhaustion
  * go#75706 go#75672 boo#1251259 security: fix CVE-2025-58186 net/http: lack of limit when parsing cookies can cause memory exhaustion
  * go#75708 go#75676 boo#1251256 security: fix CVE-2025-61723 encoding/pem: quadratic complexity when parsing some invalid inputs
  * go#75710 go#75677 boo#1251261 security: fix CVE-2025-58183 archive/tar: unbounded allocation when parsing GNU sparse map
  * go#75712 go#75678 boo#1251257 security: fix CVE-2025-47912 net/url: insufficient validation of bracketed IPv6 hostnames
  * go#75714 go#75681 boo#1251254 security: fix CVE-2025-58187 crypto/x509: quadratic complexity when checking name constraints
  * go#75717 go#75716 boo#1251262 security: fix CVE-2025-61724 net/textproto: excessive CPU consumption in Reader.ReadResponse
  * go#75138 os: Root.OpenRoot sets incorrect name, losing prefix of original root
  * go#75220 debug/pe: pe.Open fails on object files produced by llvm-mingw 21
  * go#75351 cmd/link: panic on riscv64 with CGO enabled due to empty container symbol
  * go#75356 net: new test TestIPv4WriteMsgUDPAddrPortTargetAddrIPVersion fails on plan9
  * go#75359 os: new test TestOpenFileCreateExclDanglingSymlink fails on Plan 9
  * go#75523 crypto/internal/fips140/rsa: requires a panic if self-tests fail
  * go#75538 net/http: internal error: connCount underflow
  * go#75594 cmd/compile: internal compiler error with GOEXPERIMENT=cgocheck2 on github.com/leodido/go-urn
  * go#75609 sync/atomic: comment for Uintptr.Or incorrectly describes return value</changelog>
  <changelog author="jkowalczyk@suse.com" date="1760356800">- go1.24.9 (released 2025-10-13) includes fixes to the crypto/x509
  package.
  Refs boo#1236217 go1.24 release tracking
  * go#75860 crypto/x509: TLS validation fails for FQDNs with trailing dot
- Packaging improvements:
  * Add net-url-allow-IP-literals-with-IPv4-mapped-IPv6-addresses.patch
    needed today and will be available in the next upstream release</changelog>
  <changelog author="jkowalczyk@suse.com" date="1762344000">- go1.24.10 (released 2025-11-05) includes fixes to the
  encoding/pem and net/url packages.
  Refs boo#1236217 go1.24 release tracking
  * go#75831 net/url: ipv4 mapped ipv6 addresses should be valid in square brackets
  * go#75951 encoding/pem: regression when decoding blocks with leading garbage
  * go#76028 pem/encoding: malformed line endings can cause panics
- Packaging improvements:
  * Remove net-url-allow-IP-literals-with-IPv4-mapped-IPv6-addresses.patch
    No longer needed with go#75831 in latest upstream release</changelog>
</package>
<package pkgid="a652c1e31396a228a4c14c098590c8369d42d25e62341a951df849a6ec342042" name="go1.24" arch="x86_64">
  <version epoch="0" ver="1.24.10" rel="150700.1.2"/>
  <changelog author="jkowalczyk@suse.com" date="1734091200">- go1.24rc1 (released 2024-12-13) is a release candidate version of
  go1.24 cut from the master branch at the revision tagged
  go1.24rc1.
  Refs boo#1236217 go1.24 release tracking
  * go1.24 requires the final point release of go1.22 or later
    for bootstrap.</changelog>
  <changelog author="jkowalczyk@suse.com" date="1737028800">- go1.24rc2 (released 2024-01-16) is a release candidate version of
  go1.24 cut from the master branch at the revision tagged
  go1.24rc2.
  Refs boo#1236217 go1.24 release tracking
  CVE-2024-45341 CVE-2024-45336 CVE-2025-22865 CVE-2024-45340
  * go#71209 go#71156 boo#1236045 security: fix CVE-2024-45341 crypto/x509: properly check for IPv6 hosts in URIs
  * go#71212 go#70530 boo#1236046 security: fix CVE-2024-45336 net/http: persist header stripping across repeated redirects
  * go#71216 boo#1236361 security: fix CVE-2025-22865 crypto/x509: avoid panic when parsing partial PKCS#1 private keys
  * go#71249 boo#1236360 security: fix CVE-2024-45340 cmd/go: restore netrc preferences for GOAUTH and fix domain lookup</changelog>
  <changelog author="jkowalczyk@suse.com" date="1738756800">- go1.24rc3 (released 2024-02-05) is a release candidate version of
  go1.24 cut from the master branch at the revision tagged
  go1.24rc3.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-22866 CVE-2025-22867
  * go#71423 go#71383 boo#1236801 security: fix CVE-2025-22866 crypto/internal/fips140/nistec: p256NegCond is variable time on ppc64le
  * go#71476 boo#1236839 security: fix CVE-2025-22867 cmd/go: arbitrary code execution during build on darwin
  * foo</changelog>
  <changelog author="jkowalczyk@suse.com" date="1739275200">- go1.24 (released 2025-02-11) is a major release of Go.
  go1.24.x minor releases will be provided through February 2026.
  https://github.com/golang/go/wiki/Go-Release-Cycle
  go1.24 arrives six months after Go 1.23. Most of its changes are
  in the implementation of the toolchain, runtime, and
  libraries. As always, the release maintains the Go 1 promise of
  compatibility. We expect almost all Go programs to continue to
  compile and run as before.
  Refs boo#1236217 go1.24 release tracking
  * Language change: Go 1.24 now fully supports generic type
    aliases: a type alias may be parameterized like a defined
    type. See the language spec for details. For now, the feature
    can be disabled by setting GOEXPERIMENT=noaliastypeparams; but
    the aliastypeparams setting will be removed for Go 1.25.
  * go command: Go modules can now track executable dependencies
    using tool directives in go.mod. This removes the need for the
    previous workaround of adding tools as blank imports to a file
    conventionally named "tools.go". The go tool command can now
    run these tools in addition to tools shipped with the Go
    distribution.
  * go command: The new -tool flag for go get causes a tool
    directive to be added to the current module for named packages
    in addition to adding require directives.
  * go command: The new tool meta-pattern refers to all tools in
    the current module. This can be used to upgrade them all with
    go get tool or to install them into your GOBIN directory with
    go install tool.
  * go command: Executables created by go run and the new behavior
    of go tool are now cached in the Go build cache. This makes
    repeated executions faster at the expense of making the cache
    larger. See go#69290.
  * go command: The go build and go install commands now accept a
  - json flag that reports build output and failures as structured
    JSON output on standard output. For details of the reporting
    format, see go help buildjson. Furthermore, go test -json now
    reports build output and failures in JSON, interleaved with
    test result JSON. These are distinguished by new Action types,
    but if they cause problems in a test integration system, you
    can revert to the text build output with GODEBUG setting
    gotestjsonbuildtext=1.
  * go command: The new GOAUTH environment variable provides a
    flexible way to authenticate private module fetches. See go
    help goauth for more information.
  * go command: The go build command now sets the main module's
    version in the compiled binary based on the version control
    system tag and/or commit. A +dirty suffix will be appended if
    there are uncommitted changes. Use the -buildvcs=false flag to
    omit version control information from the binary.
  * go command: The new GODEBUG setting toolchaintrace=1 can be
    used to trace the go command's toolchain selection process.
  * cgo: cgo supports new annotations for C functions to improve
    run time performance. cgo noescape cFunctionName tells the
    compiler that memory passed to the C function cFunctionname
    does not escape. cgo nocallback cFunctionName tells the
    compiler that the C function cFunctionName does not call back
    to any Go functions.
  * cgo: cgo currently refuses to compile calls to a C function
    which has multiple incompatible declarations. For instance,
    if f is declared as both void f(int) and void f(double),
    cgo will report an error instead of possibly generating an
    incorrect call sequence for f(0). New in this release is a
    better detector for this error condition when the incompatible
    declarations appear in different files. See go#67699.
  * objdump: The objdump tool now supports dissassembly on 64-bit
    LoongArch (GOARCH=loong64), RISC-V (GOARCH=riscv64), and S390X
    (GOARCH=s390x).
  * vet: The new tests analyzer reports common mistakes in
    declarations of tests, fuzzers, benchmarks, and examples in
    test packages, such as malformed names, incorrect signatures,
    or examples that document non-existent identifiers. Some of
    these mistakes may cause tests not to run. This analyzer is
    among the subset of analyzers that are run by go test.
  * vet: The existing printf analyzer now reports a diagnostic for
    calls of the form fmt.Printf(s), where s is a non-constant
    format string, with no other arguments. Such calls are nearly
    always a mistake as the value of s may contain the % symbol;
    use fmt.Print instead. See go#60529. This check tends to
    produce findings in existing code, and so is only applied when
    the language version (as specified by the go.mod go directive
    or //go:build comments) is at least Go 1.24, to avoid causing
    continuous integration failures when updating to the 1.24 Go
    toolchain.
  * vet: The existing buildtag analyzer now reports a diagnostic
    when there is an invalid Go major version build constraint
    within a //go:build directive. For example, //go:build go1.23.1
    refers to a point release; use //go:build go1.23 instead.
    See go#64127.
  * vet: The existing copylock analyzer now reports a diagnostic
    when a variable declared in a 3-clause "for" loop such as for i
    := iter(); done(i); i = next(i) { ... } contains a sync.Locker,
    such as a sync.Mutex. Go 1.22 changed the behavior of these
    loops to create a new variable for each iteration, copying the
    value from the previous iteration; this copy operation is not
    safe for locks. See go#66387.
  * GOCACHEPROG: The cmd/go internal binary and test caching
    mechanism can now be implemented by child processes
    implementing a JSON protocol between the cmd/go tool and the
    child process named by the GOCACHEPROG environment
    variable. This was previously behind a GOEXPERIMENT. For
    protocol details, see the documentation.
  * Runtime: Several performance improvements to the runtime have
    decreased CPU overheads by 2-3% on average across a suite of
    representative benchmarks. Results may vary by
    application. These improvements include a new builtin map
    implementation based on Swiss Tables, more efficient memory
    allocation of small objects, and a new runtime-internal mutex
    implementation.
  * Runtime: The new builtin map implementation and new
    runtime-internal mutex may be disabled by setting
    GOEXPERIMENT=noswissmap and GOEXPERIMENT=nospinbitmutex at
    build time respectively.
  * Compiler: The compiler already disallowed defining new methods
    with receiver types that were cgo-generated, but it was
    possible to circumvent that restriction via an alias type. Go
    1.24 now always reports an error if a receiver denotes a
    cgo-generated type, whether directly or indirectly (through an
    alias type).
  * Linker: The linker now generates a GNU build ID (the ELF
    NT_GNU_BUILD_ID note) on ELF platforms and a UUID (the Mach-O
    LC_UUID load command) on macOS by default. The build ID or UUID
    is derived from the Go build ID. It can be disabled by the -B
    none linker flag, or overridden by the -B 0xNNNN linker flag
    with a user-specified hexadecimal value.
  * Bootstrap: As mentioned in the Go 1.22 release notes, Go 1.24
    now requires Go 1.22.6 or later for bootstrap. We expect that
    Go 1.26 will require a point release of Go 1.24 or later for
    bootstrap.
  * Standard library: Directory-limited filesystem access: The new
    os.Root type provides the ability to perform filesystem
    operations within a specific directory. The os.OpenRoot
    function opens a directory and returns an os.Root. Methods on
    os.Root operate within the directory and do not permit paths
    that refer to locations outside the directory, including ones
    that follow symbolic links out of the directory. The methods on
    os.Root mirror most of the file system operations available in
    the os package, including for example os.Root.Open,
    os.Root.Create, os.Root.Mkdir, and os.Root.Stat,
  * Standard library: new benchmark function: Benchmarks may now
    use the faster and less error-prone testing.B.Loop method to
    perform benchmark iterations like for b.Loop() { ... } in place
    of the typical loop structures involving b.N like for range
    b.N. This offers two significant advantages: 1) The benchmark
    function will execute exactly once per -count, so expensive
    setup and cleanup steps execute only once, and 2) Function call
    parameters and results are kept alive, preventing the compiler
    from fully optimizing away the loop body.
  * Standard library: Improved finalizers: The new
    runtime.AddCleanup function is a finalization mechanism that is
    more flexible, more efficient, and less error-prone than
    runtime.SetFinalizer. AddCleanup attaches a cleanup function to
    an object that will run once the object is no longer reachable.
    However, unlike SetFinalizer, multiple cleanups may be attached
    to a single object, cleanups may be attached to interior
    pointers, cleanups do not generally cause leaks when objects
    form a cycle, and cleanups do not delay the freeing of an
    object or objects it points to. New code should prefer
    AddCleanup over SetFinalizer.
  * Standard library: New weak package: The new weak package
    provides weak pointers. Weak pointers are a low-level primitive
    provided to enable the creation of memory-efficient structures,
    such as weak maps for associating values, canonicalization maps
    for anything not covered by package unique, and various kinds
    of caches. For supporting these use-cases, this release also
    provides runtime.AddCleanup and maphash.Comparable.
  * Standard library: New crypto/mlkem package: The new
    crypto/mlkem package implements ML-KEM-768 and
    ML-KEM-1024. ML-KEM is a post-quantum key exchange mechanism
    formerly known as Kyber and specified in FIPS 203.
  * Standard library: New crypto/hkdf, crypto/pbkdf2, and
    crypto/sha3 packages: The new crypto/hkdf package implements
    the HMAC-based Extract-and-Expand key derivation function HKDF,
    as defined in RFC 5869. The new crypto/pbkdf2 package
    implements the password-based key derivation function PBKDF2,
    as defined in RFC 8018. The new crypto/sha3 package implements
    the SHA-3 hash function and SHAKE and cSHAKE extendable-output
    functions, as defined in FIPS 202. All three packages are based
    on pre-existing golang.org/x/crypto/... packages.
  * FIPS: release includes a new set of mechanisms to facilitate
    FIPS 140-3 compliance. See https://go.dev/doc/security/fips140
    The Go Cryptographic Module is a set of internal standard
    library packages that are transparently used to implement FIPS
    140-3 approved algorithms. Applications require no changes to
    use the Go Cryptographic Module for approved algorithms.
  * FIPS: The new GOFIPS140 environment variable can be used to
    select the Go Cryptographic Module version to use in a
    build. The new fips140 GODEBUG setting can be used to enable
    FIPS 140-3 mode at runtime.
  * FIPS: Go 1.24 includes Go Cryptographic Module version v1.0.0,
    which is currently under test with a CMVP-accredited
    laboratory.
  * Standard library: New experimental testing/synctest package:
    The new experimental testing/synctest package provides support
    for testing concurrent code. The synctest.Run function starts a
    group of goroutines in an isolated "bubble". Within the bubble,
    time package functions operate on a fake clock.  The
    synctest.Wait function waits for all goroutines in the current
    bubble to block. The synctest package is experimental and must
    be enabled by setting GOEXPERIMENT=synctest at build time. The
    package API is subject to change in future releases. See issue
    go#67434 for more information and to provide feeback.
  * archive: The (*Writer).AddFS implementations in both
    archive/zip and archive/tar now write a directory header for an
    empty directory.
  * bytes: The bytes package adds several functions that work with
    iterators.
  * bytes: Lines returns an iterator over the newline-terminated
    lines in a byte slice.
  * bytes: SplitSeq returns an iterator over all subslices of a
    byte slice split around a separator.
  * bytes: SplitAfterSeq returns an iterator over subslices of a
    byte slice split after each instance of a separator.
  * bytes: FieldsSeq returns an iterator over subslices of a byte
    slice split around runs of whitespace characters, as defined by
    unicode.IsSpace.
  * bytes: FieldsFuncSeq returns an iterator over subslices of a
    byte slice split around runs of Unicode code points satisfying
    a predicate.
  * crypto/aes: The value returned by NewCipher no longer
    implements the NewCTR, NewGCM, NewCBCEncrypter, and
    NewCBCDecrypter methods. These methods were undocumented and
    not available on all architectures. Instead, the Block value
    should be passed directly to the relevant crypto/cipher
    functions. For now, crypto/cipher still checks for those
    methods on Block values, even if they are not used by the
    standard library anymore.
  * crypto/aes: The Stream implementation returned by NewCTR when
    used with crypto/aes is now several times faster on amd64 and
    arm64.
  * crypto/cipher: The new NewGCMWithRandomNonce function returns
    an AEAD that implements AES-GCM by generating a random nonce
    during Seal and prepending it to the ciphertext.
  * crypto/cipher: NewOFB, NewCFBEncrypter, and NewCFBDecrypter are
    now deprecated. OFB and CFB mode are not authenticated, which
    generally enables active attacks to manipulate and recover the
    plaintext. It is recommended that applications use AEAD modes
    instead. If an unauthenticated Stream mode is required, use
    NewCTR instead.
  * crypto/ecdsa: PrivateKey.Sign now produces a deterministic
    signature according to RFC 6979 if the random source is nil.
  * crypto/md5: The value returned by md5.New now also implements
    the encoding.BinaryAppender interface.
  * crypto/rand: The Read function is now guaranteed not to
    fail. It will always return nil as the error result. If Read
    were to encounter an error while reading from Reader, the
    program will irrecoverably crash. Note that the platform APIs
    used by the default Reader are documented to always succeed, so
    this change should only affect programs that override the
    Reader variable. One exception are Linux kernels before version
    3.17, where the default Reader still opens /dev/urandom and may
    fail.
  * crypto/rand: On Linux 6.11 and later, Reader now uses the
    getrandom system call via vDSO. This is several times faster,
    especially for small reads.
  * crypto/rand: On OpenBSD, Reader now uses arc4random_buf(3).
  * crypto/rand: The new Text function can be used to generate
    cryptographically secure random text strings.
  * crypto/rsa: GenerateKey now returns an error if a key of less
    than 1024 bits is requested. All Sign, Verify, Encrypt, and
    Decrypt methods now return an error if used with a key smaller
    than 1024 bits. Such keys are insecure and should not be
    used. GODEBUG setting rsa1024min=0 restores the old behavior,
    but we recommend doing so only if necessary and only in tests,
    for example by adding a //go:debug rsa1024min=0 line to a test
    file. A new GenerateKey example provides an easy-to-use
    standard 2048-bit test key.
  * crypto/rsa: It is now safe and more efficient to call
    PrivateKey.Precompute before PrivateKey.Validate. Precompute is
    now faster in the presence of partially filled out
    PrecomputedValues, such as when unmarshaling a key from JSON.
  * crypto/rsa: The package now rejects more invalid keys, even
    when Validate is not called, and GenerateKey may return new
    errors for broken random sources. The Primes and Precomputed
    fields of PrivateKey are now used and validated even when some
    values are missing. See also the changes to crypto/x509 parsing
    and marshaling of RSA keys described below.
  * crypto/rsa: SignPKCS1v15 and VerifyPKCS1v15 now support
    SHA-512/224, SHA-512/256, and SHA-3.
  * crypto/rsa: GenerateKey now uses a slightly different method to
    generate the private exponent (Carmichael's totient instead of
    Euler's totient). Rare applications that externally regenerate
    keys from only the prime factors may produce different but
    compatible results.
  * crypto/rsa: Public and private key operations are now up to two
    times faster on wasm.
  * crypto/sha1: The value returned by sha1.New now also implements
    the encoding.BinaryAppender interface.
  * crypto/sha256: The values returned by sha256.New and
    sha256.New224 now also implement the encoding.BinaryAppender
    interface.
  * crypto/sha512: The values returned by sha512.New,
    sha512.New384, sha512.New512_224 and sha512.New512_256 now also
    implement the encoding.BinaryAppender interface.
  * crypto/subtle: The new WithDataIndependentTiming function
    allows the user to run a function with architecture specific
    features enabled which guarantee specific instructions are data
    value timing invariant. This can be used to make sure that code
    designed to run in constant time is not optimized by CPU-level
    features such that it operates in variable time. Currently,
    WithDataIndependentTiming uses the PSTATE.DIT bit on arm64, and
    is a no-op on all other architectures. GODEBUG setting
    dataindependenttiming=1 enables the DIT mode for the entire Go
    program.
  * crypto/subtle: The XORBytes output must overlap exactly or not
    at all with the inputs. Previously, the behavior was otherwise
    undefined, while now XORBytes will panic.
  * crypto/tls: The TLS server now supports Encrypted Client Hello
    (ECH). This feature can be enabled by populating the
    Config.EncryptedClientHelloKeys field.
  * crypto/tls: The new post-quantum X25519MLKEM768 key exchange
    mechanism is now supported and is enabled by default when
    Config.CurvePreferences is nil. GODEBUG setting tlsmlkem=0
    reverts the default.
  * crypto/tls: Support for the experimental X25519Kyber768Draft00
    key exchange has been removed.
  * crypto/tls: Key exchange ordering is now handled entirely by
    the crypto/tls package. The order of Config.CurvePreferences is
    now ignored, and the contents are only used to determine which
    key exchanges to enable when the field is populated.
  * crypto/tls: The new ClientHelloInfo.Extensions field lists the
    IDs of the extensions received in the Client Hello
    message. This can be useful for fingerprinting TLS clients.
  * crypto/x509: The x509sha1 GODEBUG setting has been
    removed. Certificate.Verify no longer supports SHA-1 based
    signatures.
  * crypto/x509: OID now implements the encoding.BinaryAppender and
    encoding.TextAppender interfaces.
  * crypto/x509: The default certificate policies field has changed
    from Certificate.PolicyIdentifiers to
    Certificate.Policies. When parsing certificates, both fields
    will be populated, but when creating certificates policies will
    now be taken from the Certificate.Policies field instead of the
    Certificate.PolicyIdentifiers field. This change can be
    reverted with GODEBUG setting x509usepolicies=0.
  * crypto/x509: CreateCertificate will now generate a serial
    number using a RFC 5280 compliant method when passed a template
    with a nil Certificate.SerialNumber field, instead of failing.
  * crypto/x509: Certificate.Verify now supports policy validation,
    as defined in RFC 5280 and RFC 9618. The new
    VerifyOptions.CertificatePolicies field can be set to an
    acceptable set of policy OIDs. Only certificate chains with
    valid policy graphs will be returned from Certificate.Verify.
  * crypto/x509: MarshalPKCS8PrivateKey now returns an error
    instead of marshaling an invalid RSA
    key. (MarshalPKCS1PrivateKey doesn't have an error return, and
    its behavior when provided invalid keys continues to be
    undefined.)
  * crypto/x509: ParsePKCS1PrivateKey and ParsePKCS8PrivateKey now
    use and validate the encoded CRT values, so might reject
    invalid RSA keys that were previously accepted. Use GODEBUG
    setting x509rsacrt=0 to revert to recomputing the CRT values.
  * debug/elf: The debug/elf package adds support for handling
    symbol versions in dynamic ELF (Executable and Linkable Format)
    files. The new File.DynamicVersions method returns a list of
    dynamic versions defined in the ELF file. The new
    File.DynamicVersionNeeds method returns a list of dynamic
    versions required by this ELF file that are defined in other
    ELF objects. Finally, the new Symbol.HasVersion and
    Symbol.VersionIndex fields indicate the version of a symbol.
  * encoding: Two new interfaces, TextAppender and BinaryAppender,
    have been introduced to append the textual or binary
    representation of an object to a byte slice. These interfaces
    provide the same functionality as TextMarshaler and
    BinaryMarshaler, but instead of allocating a new slice each
    time, they append the data directly to an existing slice. These
    interfaces are now implemented by standard library types that
    already implemented TextMarshaler and/or BinaryMarshaler.
  * encoding/json: When marshaling, a struct field with the new
    omitzero option in the struct field tag will be omitted if its
    value is zero. If the field type has an IsZero() bool method,
    that will be used to determine whether the value is
    zero. Otherwise, the value is zero if it is the zero value for
    its type. The omitzero field tag is clearer and less
    error-prone than omitempty when the intent is to omit zero
    values. In particular, unlike omitempty, omitzero omits
    zero-valued time.Time values, which is a common source of
    friction.
  * encoding/json: If both omitempty and omitzero are specified,
    the field will be omitted if the value is either empty or zero
    (or both).
  * encoding/json: UnmarshalTypeError.Field now includes embedded
    structs to provide more detailed error messages.
  * go/types: All go/types data structures that expose sequences
    using a pair of methods such as Len() int and At(int) T now
    also have methods that return iterators, allowing you to
    simplify code. The methods are: Interface.EmbeddedTypes,
    Interface.ExplicitMethods, Interface.Methods,
    MethodSet.Methods, Named.Methods, Scope.Children,
    Struct.Fields, Tuple.Variables, TypeList.Types,
    TypeParamList.TypeParams, Union.Terms.
  * hash/adler32: The value returned by New now also implements the
    encoding.BinaryAppender interface.
  * hash/crc32: The values returned by New and NewIEEE now also
    implement the encoding.BinaryAppender interface.
  * hash/crc64: The value returned by New now also implements the
    encoding.BinaryAppender interface.
  * hash/fnv: The values returned by New32, New32a, New64, New64a,
    New128 and New128a now also implement the
    encoding.BinaryAppender interface.
  * hash/maphash: The new Comparable and WriteComparable functions
    can compute the hash of any comparable value. These make it
    possible to hash anything that can be used as a Go map key.
  * log/slog: The new DiscardHandler is a handler that is never
    enabled and always discards its output.
  * log/slog: Level and LevelVar now implement the
    encoding.TextAppender interface.
  * math/big: Float, Int and Rat now implement the
    encoding.TextAppender interface.
  * math/rand: Calls to the deprecated top-level Seed function no
    longer have any effect. To restore the old behavior use GODEBUG
    setting randseednop=0. For more background see proposal
    go#67273.
  * math/rand/v2: ChaCha8 and PCG now implement the
    encoding.BinaryAppender interface.
  * net: ListenConfig now uses MPTCP by default on systems where it
    is supported (currently on Linux only).
  * net: IP now implements the encoding.TextAppender interface.
  * net/http: Transport's limit on 1xx informational responses
    received in response to a request has changed. It previously
    aborted a request and returned an error after receiving more
    than 5 1xx responses. It now returns an error if the total size
    of all 1xx responses exceeds the
    Transport.MaxResponseHeaderBytes configuration setting.
  * net/http: In addition, when a request has a
    net/http/httptrace.ClientTrace.Got1xxResponse trace hook, there
    is now no limit on the total number of 1xx responses. The
    Got1xxResponse hook may return an error to abort a request.
  * net/http: Transport and Server now have an HTTP2 field which
    permits configuring HTTP/2 protocol settings.
  * net/http: The new Server.Protocols and Transport.Protocols
    fields provide a simple way to configure what HTTP protocols a
    server or client use.
  * net/http: The server and client may be configured to support
    unencrypted HTTP/2 connections.
  * net/http: When Server.Protocols contains UnencryptedHTTP2, the
    server will accept HTTP/2 connections on unencrypted ports. The
    server can accept both HTTP/1 and unencrypted HTTP/2 on the
    same port.
  * net/http: When Transport.Protocols contains UnencryptedHTTP2
    and does not contain HTTP1, the transport will use unencrypted
    HTTP/2 for http:// URLs. If the transport is configured to use
    both HTTP/1 and unencrypted HTTP/2, it will use HTTP/1.
  * net/http: Unencrypted HTTP/2 support uses "HTTP/2 with Prior
    Knowledge" (RFC 9113, section 3.3). The deprecated "Upgrade:
    h2c" header is not supported.
  * net/netip: Addr, AddrPort and Prefix now implement the
    encoding.BinaryAppender and encoding.TextAppender interfaces.
  * net/url: URL now also implements the encoding.BinaryAppender
    interface.
  * os/user: On Windows, Current can now be used in Windows Nano
    Server. The implementation has been updated to avoid using
    functions from the NetApi32 library, which is not available in
    Nano Server.
  * os/user: On Windows, Current, Lookup and LookupId now support
    the following built-in service user accounts: NT
    AUTHORITY\SYSTEM, NT AUTHORITY\LOCAL SERVICE, NT
    AUTHORITY\NETWORK SERVICE
  * os/user: On Windows, Current has been made considerably faster
    when the current user is joined to a slow domain, which is the
    usual case for many corporate users. The new implementation
    performance is now in the order of milliseconds, compared to
    the previous implementation which could take several seconds,
    or even minutes, to complete.
  * os/user: On Windows, Current now returns the process owner user
    when the current thread is impersonating another
    user. Previously, it returned an error.
  * regexp: Regexp now implements the encoding.TextAppender
    interface.
  * runtime: The GOROOT function is now deprecated. In new code
    prefer to use the system path to locate the "go" binary, and
    use go env GOROOT to find its GOROOT.
  * strings: The strings package adds several functions that work
    with iterators.
  * strings: Lines returns an iterator over the newline-terminated
    lines in a string.
  * strings: SplitSeq returns an iterator over all substrings of a
    string split around a separator.
  * strings: SplitAfterSeq returns an iterator over substrings of a
    string split after each instance of a separator.
  * strings: FieldsSeq returns an iterator over substrings of a
    string split around runs of whitespace characters, as defined
    by unicode.IsSpace.
  * strings: FieldsFuncSeq returns an iterator over substrings of a
    string split around runs of Unicode code points satisfying a
    predicate.
  * sync: The implementation of sync.Map has been changed,
    improving performance, particularly for map modifications. For
    instance, modifications of disjoint sets of keys are much less
    likely to contend on larger maps, and there is no longer any
    ramp-up time required to achieve low-contention loads from the
    map. If you encounter any problems, set
    GOEXPERIMENT=nosynchashtriemap at build time to switch back to
    the old implementation and please file an issue.
  * testing: The new T.Context and B.Context methods return a
    context that's canceled after the test completes and before
    test cleanup functions run.
  * testing: The new T.Chdir and B.Chdir methods can be used to
    change the working directory for the duration of a test or
    benchmark.
  * text/template: Templates now support range-over-func and
    range-over-int.
  * time: Time now implements the encoding.BinaryAppender and
    encoding.TextAppender interfaces.
  * Linux port: As announced in the Go 1.23 release notes, Go 1.24
    requires Linux kernel version 3.2 or later.
  * Darwin port: Go 1.24 is the last release that will run on macOS
    11 Big Sur. Go 1.25 will require macOS 12 Monterey or later.
  * WebAssembly: The go:wasmexport compiler directive is added for
    Go programs to export functions to the WebAssembly host.
  * WebAssembly: On WebAssembly System Interface Preview 1
    (GOOS=wasip1 GOARCH=wasm), Go 1.24 supports building a Go
    program as a reactor/library, by specifying the
  - buildmode=c-shared build flag.
  * WebAssembly: More types are now permitted as argument or result
    types for go:wasmimport functions. Specifically, bool, string,
    uintptr, and pointers to certain types are allowed (see the
    documentation for detail), along with 32-bit and 64-bit integer
    and float types, and unsafe.Pointer, which are already
    allowed. These types are also permitted as argument or result
    types for go:wasmexport functions.
  * WebAssembly: The support files for WebAssembly have been moved
    to lib/wasm from misc/wasm.
  * Windows: The 32-bit windows/arm port (GOOS=windows GOARCH=arm)
    has been marked broken. See issue go#70705 for details.</changelog>
  <changelog author="jkowalczyk@suse.com" date="1741089600">- go1.24.1 (released 2025-03-04) includes security fixes to the
  net/http package, as well as bug fixes to cgo, the compiler, the
  go command, and the reflect, runtime, and syscall packages.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-22870
  * go#71986 go#71984 boo#1238572 security: fix CVE-2025-22870 net/http, x/net/proxy, x/net/http/httpproxy: proxy bypass using IPv6 zone IDs
  * go#71687 cmd/go: panics with GOAUTH='git dir' go get -x
  * go#71705 runtime: add linkname of runtime.lastmoduledatap for cloudwego/sonic
  * go#71728 runtime: usleep computes wrong tv_nsec on s390x
  * go#71745 crypto: add fips140 as an opaque GODEBUG setting and add documentation for it
  * go#71829 cmd/compile: fail to compile package in 1.24
  * go#71836 os: possible regression from Go 1.23 to Go 1.24 when opening DevNull with O_TRUNC
  * go#71840 runtime: recover added in range-over-func loop body doesn't stop panic propagation / segfaults printing error
  * go#71849 os: spurious SIGCHILD on running child process
  * go#71855 cmd/compile: Pow10 freeze the compiler on certain condition on Go 1.24
  * go#71858 debug/buildinfo: false positives with external scanners flag for go117 binary in testdata
  * go#71876 reflect: Value.Seq panicking on functional iterator methods
  * go#71904 cmd/compile: nil dereference when storing field of non-nil struct value
  * go#71916 reflect: Value.Seq iteration value types not matching the type of given int types
  * go#71938 cmd/compile: "fatal error: found pointer to free object" on arm64
  * go#71955 proposal: runtime: allow cleanups to run concurrently
  * go#71963 runtime/cgo: does not build with -Wdeclaration-after-statement
  * go#71977 syscall: js/wasm file operations fail on windows / node.js</changelog>
  <changelog author="jkowalczyk@suse.com" date="1741176000">- Packaging improvements:
  * SLE-12 only: Add declarations to Cgo seccomp_linux.go
    for new syscalls seccomp and getrandom which are not present
    in the kernel headers supplied by glibc version in SLE-12.
    (Marcus Meissner)
    Refs boo#1239182
  * Add patch go-fixseccomp.patch</changelog>
  <changelog author="jkowalczyk@suse.com" date="1743508800">- go1.24.2 (released 2025-04-01) includes security fixes to the
  net/http package, as well as bug fixes to the compiler, the
  runtime, the go command, and the crypto/tls, go/types, net/http,
  and testing packages.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-22871
  * go#72011 go#71988 boo#1240550 security: fix CVE-2025-22871 net/http: reject bare LF in chunked encoding
  * go#72067 cmd/compile: out of memory
  * go#72103 net/http: go1.24 breaks compatibility by modifying in-place the tls.Config{NextProtos}
  * go#72115 runtime: process hangs for mips hardware
  * go#72796 runtime: add an example for AddCleanup
  * go#72822 cmd/compile: OOM with mutually-recursive iter.Seq
  * go#72823 crypto/tls: FIPS 140-3 modes reject ECDSA w/ curve P-521/SHA-512 in TLS
  * go#72826 go/types, types2: CheckExpr / Eval may mutate type checked objects (=&gt; data race)
  * go#72872 runtime: cgo callback on extra M treated as external code after nested cgo callback returns
  * go#72934 testing: b.StopTimer breaks b.Loop
  * go#72938 internal/godebugs: winsymlink and winreadlinkvolume have incorrect defaults for Go 1.22
  * go#72974 testing: b.Loop gives bogus results in some situations</changelog>
  <changelog author="jkowalczyk@suse.com" date="1743595200">- Packaging improvements:
  * SLE-12 only: Fix conditional for go-fixsecomp.patch to work
    correctly when suse_version is undefined.
    Refs boo#1239182
  * Fix RPM warning by removing valid macro syntax in comment
    describing naming format of llvm-tsan_commit.tar.xz</changelog>
  <changelog author="mail+rpm@georg-pfuetzenreuter.net" date="1745236800">- Add gh-issue-73141.patch to repair random segmentation faults (boo#1240764)</changelog>
  <changelog author="jkowalczyk@suse.com" date="1746532800">- go1.24.3 (released 2025-05-06) includes security fixes to the os
  package, as well as bug fixes to the runtime, the compiler, the
  linker, the go command, and the crypto/tls and os packages.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-22873
  * go#73556 go#73555 boo#1242715 security: fix CVE-2025-22873 os: Root permits access to parent directory
  * go#73082 os: Root.Open panics when opening a symlink referencing the root
  * go#73092 cmd/link: linkname directive on userspace variable can override runtime variable
  * go#73118 crypto/tls: ECH decodeInnerClientHello incorrectly rejects ClientHello with GREASE values in supportedVersions
  * go#73144 runtime: segmentation fault from vgetrandomPutState and runtime.growslice w/ runtime.OSLockThread
  * go#73192 runtime: -race data race map traceback report incorrect functions
  * go#73281 cmd/compile: program compiles to wasm but is invalid: go:wasmexport: integer too large
  * go#73379 runtime, x/sys/unix: Connectx is broken on darwin/amd64
  * go#73440 cmd/compile: infinite loop in the inliner
  * go#73500 cmd/go: +dirty in version stamping doesn't combine well with +incompatible
- Packaging improvements:
  * Drop gh-issue-73141.patch to repair random segmentation faults (boo#1240764)
    fixed in upstream release.</changelog>
  <changelog author="jkowalczyk@suse.com" date="1749124800">- go1.24.4 (released 2025-06-05) includes security fixes to the
  crypto/x509, net/http, and os packages, as well as bug fixes to
  the linker, the go command, and the hash/maphash and os packages.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-22874 CVE-2025-0913 CVE-2025-4673
  * go#73700 go#73702 boo#1244158 security: fix CVE-2025-22874 crypto/x509: ExtKeyUsageAny bypasses policy validation
  * go#73720 go#73612 boo#1244157 security: fix CVE-2025-0913 os: inconsistent handling of O_CREATE|O_EXCL on Unix and Windows
  * go#73906 go#73816 boo#1244156 security: fix CVE-2025-4673 net/http: sensitive headers not cleared on cross-origin redirect
  * go#73570 os: Root.Mkdir creates directories with zero permissions on OpenBSD
  * go#73669 hash/maphash: hashing channels with purego impl. of maphash.Comparable panics
  * go#73678 runtime/debug: BuildSetting does not document DefaultGODEBUG
  * go#73809 cmd/go: add fips140 module selection mechanism
  * go#73832 cmd/link: Go 1.24.3 and 1.23.9 regression - duplicated definition of symbol dlopen</changelog>
  <changelog author="jkowalczyk@suse.com" date="1751976000">- go1.24.5 (released 2025-07-08) includes security fixes to the go
  command, as well as bug fixes to the compiler, the linker, the
  runtime, and the go command.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-4674
  * go#74381 go#74380 boo#1246118 security: fix CVE-2025-4674 cmd/go: disable support for multiple vcs in one module
  * go#73908 runtime: bad frame pointer during panic during duffcopy
  * go#74098 cmd/compile: regression on ppc64le bit operations
  * go#74113 cmd/go: crash on unknown GOEXPERIMENT during toolchain selection
  * go#74290 runtime: heap mspan limit is set too late, causing data race between span allocation and conservative scanning
  * go#74294 internal/trace: stress tests triggering suspected deadlock in tracer
  * go#74346 runtime: memlock not unlocked in all control flow paths in sysReserveAlignedSbrk
  * go#74363 runtime/pprof: crash "cannot read stack of running goroutine" in goroutine profile
  * go#74403 cmd/link: duplicated definition of symbol github.com/ebitengine/purego.syscall15XABI0 when running with ASAN</changelog>
  <changelog author="jkowalczyk@suse.com" date="1754481600">- go1.24.6 (released 2025-08-06) includes security fixes to the
  database/sql and os/exec packages, as well as bug fixes to the
  runtime.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-47906 CVE-2025-47907
  * go#74804 go#74466 boo#1247719 security: fix CVE-2025-47906 os/exec: LookPath bug: incorrect expansion of "", "." and ".." in some PATH configurations
  * go#74833 go#74831 boo#1247720 security: fix CVE-2025-47907 database/sql: incorrect results returned from Rows.Scan
  * go#73800 runtime: RSS seems to have increased in Go 1.24 while the runtime accounting has not
  * go#74416 runtime: use-after-free of allpSnapshot in findRunnable
  * go#74694 runtime: segfaults in runtime.(*unwinder).next
  * go#74760 os/user:nolibgcc: TestGroupIdsTestUser failures</changelog>
  <changelog author="jkowalczyk@suse.com" date="1755172800">- Packaging improvements:
  * Remove conditional gccgo bootstrap sections and gcc-go.patch.
    gccgo cannot be used in any version newer than go1.21. Removal
    simplifies go1.x package code.
  * go1.21 can optionally be bootstrapped with gccgo and serve as
    the inital version of go1.x.
  * go1.21 will be the initial version of Go in the bootstrap chain
    until gcc gccgo is updated to support a language level newer
    than go1.18.
  * Drop gcc-go.patch
  * Refs boo#1247816 bootstrap go1.21 with gccgo
  * Refs boo#1248082 drop unused gccgo bootstrap code in go1.22+</changelog>
  <changelog author="jkowalczyk@suse.com" date="1756900800">- go1.24.7 (released 2025-09-03) includes fixes to the go command,
  and the net and os/exec packages.
  Refs boo#1236217 go1.24 release tracking
  * go#75007 os/exec: TestLookPath fails on plan9 after CL 685755
  * go#74821 cmd/go: "get toolchain@latest" should ignore release candidates
  * go#74818 net: WriteMsgUDPAddrPort should accept IPv4-mapped IPv6 destination addresses on IPv4 UDP sockets</changelog>
  <changelog author="asarai@suse.com" date="1758283200">- Package svgpan.js to fix issues with "go tool pprof". boo#1249985</changelog>
  <changelog author="jkowalczyk@suse.com" date="1759838400">- go1.24.8 (released 2025-10-07) includes security fixes to the
  archive/tar, crypto/tls, crypto/x509, encoding/asn1,
  encoding/pem, net/http, net/mail, net/textproto, and net/url
  packages, as well as bug fixes to the compiler, the linker, and
  the debug/pe, net/http, os, and sync/atomic packages.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-58189 CVE-2025-61725 CVE-2025-58188 CVE-2025-58185 CVE-2025-58186 CVE-2025-61723 CVE-2025-58183 CVE-2025-47912 CVE-2025-58187 CVE-2025-61724
  * go#75660 go#75652 boo#1251255 security: fix CVE-2025-58189 crypto/tls: ALPN negotiation error contains attacker controlled information
  * go#75700 go#75680 boo#1251253 security: fix CVE-2025-61725 net/mail: excessive CPU consumption in ParseAddress
  * go#75702 go#75675 boo#1251260 security: fix CVE-2025-58188 crypto/x509: panic when validating certificates with DSA public keys
  * go#75704 go#75671 boo#1251258 security: fix CVE-2025-58185 encoding/asn1: pre-allocating memory when parsing DER payload can cause memory exhaustion
  * go#75706 go#75672 boo#1251259 security: fix CVE-2025-58186 net/http: lack of limit when parsing cookies can cause memory exhaustion
  * go#75708 go#75676 boo#1251256 security: fix CVE-2025-61723 encoding/pem: quadratic complexity when parsing some invalid inputs
  * go#75710 go#75677 boo#1251261 security: fix CVE-2025-58183 archive/tar: unbounded allocation when parsing GNU sparse map
  * go#75712 go#75678 boo#1251257 security: fix CVE-2025-47912 net/url: insufficient validation of bracketed IPv6 hostnames
  * go#75714 go#75681 boo#1251254 security: fix CVE-2025-58187 crypto/x509: quadratic complexity when checking name constraints
  * go#75717 go#75716 boo#1251262 security: fix CVE-2025-61724 net/textproto: excessive CPU consumption in Reader.ReadResponse
  * go#75138 os: Root.OpenRoot sets incorrect name, losing prefix of original root
  * go#75220 debug/pe: pe.Open fails on object files produced by llvm-mingw 21
  * go#75351 cmd/link: panic on riscv64 with CGO enabled due to empty container symbol
  * go#75356 net: new test TestIPv4WriteMsgUDPAddrPortTargetAddrIPVersion fails on plan9
  * go#75359 os: new test TestOpenFileCreateExclDanglingSymlink fails on Plan 9
  * go#75523 crypto/internal/fips140/rsa: requires a panic if self-tests fail
  * go#75538 net/http: internal error: connCount underflow
  * go#75594 cmd/compile: internal compiler error with GOEXPERIMENT=cgocheck2 on github.com/leodido/go-urn
  * go#75609 sync/atomic: comment for Uintptr.Or incorrectly describes return value</changelog>
  <changelog author="jkowalczyk@suse.com" date="1760356800">- go1.24.9 (released 2025-10-13) includes fixes to the crypto/x509
  package.
  Refs boo#1236217 go1.24 release tracking
  * go#75860 crypto/x509: TLS validation fails for FQDNs with trailing dot
- Packaging improvements:
  * Add net-url-allow-IP-literals-with-IPv4-mapped-IPv6-addresses.patch
    needed today and will be available in the next upstream release</changelog>
  <changelog author="jkowalczyk@suse.com" date="1762344000">- go1.24.10 (released 2025-11-05) includes fixes to the
  encoding/pem and net/url packages.
  Refs boo#1236217 go1.24 release tracking
  * go#75831 net/url: ipv4 mapped ipv6 addresses should be valid in square brackets
  * go#75951 encoding/pem: regression when decoding blocks with leading garbage
  * go#76028 pem/encoding: malformed line endings can cause panics
- Packaging improvements:
  * Remove net-url-allow-IP-literals-with-IPv4-mapped-IPv6-addresses.patch
    No longer needed with go#75831 in latest upstream release</changelog>
</package>
<package pkgid="35dac0a1b00e546c1d617233f4370a197e8a07f7738ceef5a0e13ca9bf1f64bc" name="go1.24-doc" arch="x86_64">
  <version epoch="0" ver="1.24.10" rel="150700.1.2"/>
  <changelog author="jkowalczyk@suse.com" date="1734091200">- go1.24rc1 (released 2024-12-13) is a release candidate version of
  go1.24 cut from the master branch at the revision tagged
  go1.24rc1.
  Refs boo#1236217 go1.24 release tracking
  * go1.24 requires the final point release of go1.22 or later
    for bootstrap.</changelog>
  <changelog author="jkowalczyk@suse.com" date="1737028800">- go1.24rc2 (released 2024-01-16) is a release candidate version of
  go1.24 cut from the master branch at the revision tagged
  go1.24rc2.
  Refs boo#1236217 go1.24 release tracking
  CVE-2024-45341 CVE-2024-45336 CVE-2025-22865 CVE-2024-45340
  * go#71209 go#71156 boo#1236045 security: fix CVE-2024-45341 crypto/x509: properly check for IPv6 hosts in URIs
  * go#71212 go#70530 boo#1236046 security: fix CVE-2024-45336 net/http: persist header stripping across repeated redirects
  * go#71216 boo#1236361 security: fix CVE-2025-22865 crypto/x509: avoid panic when parsing partial PKCS#1 private keys
  * go#71249 boo#1236360 security: fix CVE-2024-45340 cmd/go: restore netrc preferences for GOAUTH and fix domain lookup</changelog>
  <changelog author="jkowalczyk@suse.com" date="1738756800">- go1.24rc3 (released 2024-02-05) is a release candidate version of
  go1.24 cut from the master branch at the revision tagged
  go1.24rc3.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-22866 CVE-2025-22867
  * go#71423 go#71383 boo#1236801 security: fix CVE-2025-22866 crypto/internal/fips140/nistec: p256NegCond is variable time on ppc64le
  * go#71476 boo#1236839 security: fix CVE-2025-22867 cmd/go: arbitrary code execution during build on darwin
  * foo</changelog>
  <changelog author="jkowalczyk@suse.com" date="1739275200">- go1.24 (released 2025-02-11) is a major release of Go.
  go1.24.x minor releases will be provided through February 2026.
  https://github.com/golang/go/wiki/Go-Release-Cycle
  go1.24 arrives six months after Go 1.23. Most of its changes are
  in the implementation of the toolchain, runtime, and
  libraries. As always, the release maintains the Go 1 promise of
  compatibility. We expect almost all Go programs to continue to
  compile and run as before.
  Refs boo#1236217 go1.24 release tracking
  * Language change: Go 1.24 now fully supports generic type
    aliases: a type alias may be parameterized like a defined
    type. See the language spec for details. For now, the feature
    can be disabled by setting GOEXPERIMENT=noaliastypeparams; but
    the aliastypeparams setting will be removed for Go 1.25.
  * go command: Go modules can now track executable dependencies
    using tool directives in go.mod. This removes the need for the
    previous workaround of adding tools as blank imports to a file
    conventionally named "tools.go". The go tool command can now
    run these tools in addition to tools shipped with the Go
    distribution.
  * go command: The new -tool flag for go get causes a tool
    directive to be added to the current module for named packages
    in addition to adding require directives.
  * go command: The new tool meta-pattern refers to all tools in
    the current module. This can be used to upgrade them all with
    go get tool or to install them into your GOBIN directory with
    go install tool.
  * go command: Executables created by go run and the new behavior
    of go tool are now cached in the Go build cache. This makes
    repeated executions faster at the expense of making the cache
    larger. See go#69290.
  * go command: The go build and go install commands now accept a
  - json flag that reports build output and failures as structured
    JSON output on standard output. For details of the reporting
    format, see go help buildjson. Furthermore, go test -json now
    reports build output and failures in JSON, interleaved with
    test result JSON. These are distinguished by new Action types,
    but if they cause problems in a test integration system, you
    can revert to the text build output with GODEBUG setting
    gotestjsonbuildtext=1.
  * go command: The new GOAUTH environment variable provides a
    flexible way to authenticate private module fetches. See go
    help goauth for more information.
  * go command: The go build command now sets the main module's
    version in the compiled binary based on the version control
    system tag and/or commit. A +dirty suffix will be appended if
    there are uncommitted changes. Use the -buildvcs=false flag to
    omit version control information from the binary.
  * go command: The new GODEBUG setting toolchaintrace=1 can be
    used to trace the go command's toolchain selection process.
  * cgo: cgo supports new annotations for C functions to improve
    run time performance. cgo noescape cFunctionName tells the
    compiler that memory passed to the C function cFunctionname
    does not escape. cgo nocallback cFunctionName tells the
    compiler that the C function cFunctionName does not call back
    to any Go functions.
  * cgo: cgo currently refuses to compile calls to a C function
    which has multiple incompatible declarations. For instance,
    if f is declared as both void f(int) and void f(double),
    cgo will report an error instead of possibly generating an
    incorrect call sequence for f(0). New in this release is a
    better detector for this error condition when the incompatible
    declarations appear in different files. See go#67699.
  * objdump: The objdump tool now supports dissassembly on 64-bit
    LoongArch (GOARCH=loong64), RISC-V (GOARCH=riscv64), and S390X
    (GOARCH=s390x).
  * vet: The new tests analyzer reports common mistakes in
    declarations of tests, fuzzers, benchmarks, and examples in
    test packages, such as malformed names, incorrect signatures,
    or examples that document non-existent identifiers. Some of
    these mistakes may cause tests not to run. This analyzer is
    among the subset of analyzers that are run by go test.
  * vet: The existing printf analyzer now reports a diagnostic for
    calls of the form fmt.Printf(s), where s is a non-constant
    format string, with no other arguments. Such calls are nearly
    always a mistake as the value of s may contain the % symbol;
    use fmt.Print instead. See go#60529. This check tends to
    produce findings in existing code, and so is only applied when
    the language version (as specified by the go.mod go directive
    or //go:build comments) is at least Go 1.24, to avoid causing
    continuous integration failures when updating to the 1.24 Go
    toolchain.
  * vet: The existing buildtag analyzer now reports a diagnostic
    when there is an invalid Go major version build constraint
    within a //go:build directive. For example, //go:build go1.23.1
    refers to a point release; use //go:build go1.23 instead.
    See go#64127.
  * vet: The existing copylock analyzer now reports a diagnostic
    when a variable declared in a 3-clause "for" loop such as for i
    := iter(); done(i); i = next(i) { ... } contains a sync.Locker,
    such as a sync.Mutex. Go 1.22 changed the behavior of these
    loops to create a new variable for each iteration, copying the
    value from the previous iteration; this copy operation is not
    safe for locks. See go#66387.
  * GOCACHEPROG: The cmd/go internal binary and test caching
    mechanism can now be implemented by child processes
    implementing a JSON protocol between the cmd/go tool and the
    child process named by the GOCACHEPROG environment
    variable. This was previously behind a GOEXPERIMENT. For
    protocol details, see the documentation.
  * Runtime: Several performance improvements to the runtime have
    decreased CPU overheads by 2-3% on average across a suite of
    representative benchmarks. Results may vary by
    application. These improvements include a new builtin map
    implementation based on Swiss Tables, more efficient memory
    allocation of small objects, and a new runtime-internal mutex
    implementation.
  * Runtime: The new builtin map implementation and new
    runtime-internal mutex may be disabled by setting
    GOEXPERIMENT=noswissmap and GOEXPERIMENT=nospinbitmutex at
    build time respectively.
  * Compiler: The compiler already disallowed defining new methods
    with receiver types that were cgo-generated, but it was
    possible to circumvent that restriction via an alias type. Go
    1.24 now always reports an error if a receiver denotes a
    cgo-generated type, whether directly or indirectly (through an
    alias type).
  * Linker: The linker now generates a GNU build ID (the ELF
    NT_GNU_BUILD_ID note) on ELF platforms and a UUID (the Mach-O
    LC_UUID load command) on macOS by default. The build ID or UUID
    is derived from the Go build ID. It can be disabled by the -B
    none linker flag, or overridden by the -B 0xNNNN linker flag
    with a user-specified hexadecimal value.
  * Bootstrap: As mentioned in the Go 1.22 release notes, Go 1.24
    now requires Go 1.22.6 or later for bootstrap. We expect that
    Go 1.26 will require a point release of Go 1.24 or later for
    bootstrap.
  * Standard library: Directory-limited filesystem access: The new
    os.Root type provides the ability to perform filesystem
    operations within a specific directory. The os.OpenRoot
    function opens a directory and returns an os.Root. Methods on
    os.Root operate within the directory and do not permit paths
    that refer to locations outside the directory, including ones
    that follow symbolic links out of the directory. The methods on
    os.Root mirror most of the file system operations available in
    the os package, including for example os.Root.Open,
    os.Root.Create, os.Root.Mkdir, and os.Root.Stat,
  * Standard library: new benchmark function: Benchmarks may now
    use the faster and less error-prone testing.B.Loop method to
    perform benchmark iterations like for b.Loop() { ... } in place
    of the typical loop structures involving b.N like for range
    b.N. This offers two significant advantages: 1) The benchmark
    function will execute exactly once per -count, so expensive
    setup and cleanup steps execute only once, and 2) Function call
    parameters and results are kept alive, preventing the compiler
    from fully optimizing away the loop body.
  * Standard library: Improved finalizers: The new
    runtime.AddCleanup function is a finalization mechanism that is
    more flexible, more efficient, and less error-prone than
    runtime.SetFinalizer. AddCleanup attaches a cleanup function to
    an object that will run once the object is no longer reachable.
    However, unlike SetFinalizer, multiple cleanups may be attached
    to a single object, cleanups may be attached to interior
    pointers, cleanups do not generally cause leaks when objects
    form a cycle, and cleanups do not delay the freeing of an
    object or objects it points to. New code should prefer
    AddCleanup over SetFinalizer.
  * Standard library: New weak package: The new weak package
    provides weak pointers. Weak pointers are a low-level primitive
    provided to enable the creation of memory-efficient structures,
    such as weak maps for associating values, canonicalization maps
    for anything not covered by package unique, and various kinds
    of caches. For supporting these use-cases, this release also
    provides runtime.AddCleanup and maphash.Comparable.
  * Standard library: New crypto/mlkem package: The new
    crypto/mlkem package implements ML-KEM-768 and
    ML-KEM-1024. ML-KEM is a post-quantum key exchange mechanism
    formerly known as Kyber and specified in FIPS 203.
  * Standard library: New crypto/hkdf, crypto/pbkdf2, and
    crypto/sha3 packages: The new crypto/hkdf package implements
    the HMAC-based Extract-and-Expand key derivation function HKDF,
    as defined in RFC 5869. The new crypto/pbkdf2 package
    implements the password-based key derivation function PBKDF2,
    as defined in RFC 8018. The new crypto/sha3 package implements
    the SHA-3 hash function and SHAKE and cSHAKE extendable-output
    functions, as defined in FIPS 202. All three packages are based
    on pre-existing golang.org/x/crypto/... packages.
  * FIPS: release includes a new set of mechanisms to facilitate
    FIPS 140-3 compliance. See https://go.dev/doc/security/fips140
    The Go Cryptographic Module is a set of internal standard
    library packages that are transparently used to implement FIPS
    140-3 approved algorithms. Applications require no changes to
    use the Go Cryptographic Module for approved algorithms.
  * FIPS: The new GOFIPS140 environment variable can be used to
    select the Go Cryptographic Module version to use in a
    build. The new fips140 GODEBUG setting can be used to enable
    FIPS 140-3 mode at runtime.
  * FIPS: Go 1.24 includes Go Cryptographic Module version v1.0.0,
    which is currently under test with a CMVP-accredited
    laboratory.
  * Standard library: New experimental testing/synctest package:
    The new experimental testing/synctest package provides support
    for testing concurrent code. The synctest.Run function starts a
    group of goroutines in an isolated "bubble". Within the bubble,
    time package functions operate on a fake clock.  The
    synctest.Wait function waits for all goroutines in the current
    bubble to block. The synctest package is experimental and must
    be enabled by setting GOEXPERIMENT=synctest at build time. The
    package API is subject to change in future releases. See issue
    go#67434 for more information and to provide feeback.
  * archive: The (*Writer).AddFS implementations in both
    archive/zip and archive/tar now write a directory header for an
    empty directory.
  * bytes: The bytes package adds several functions that work with
    iterators.
  * bytes: Lines returns an iterator over the newline-terminated
    lines in a byte slice.
  * bytes: SplitSeq returns an iterator over all subslices of a
    byte slice split around a separator.
  * bytes: SplitAfterSeq returns an iterator over subslices of a
    byte slice split after each instance of a separator.
  * bytes: FieldsSeq returns an iterator over subslices of a byte
    slice split around runs of whitespace characters, as defined by
    unicode.IsSpace.
  * bytes: FieldsFuncSeq returns an iterator over subslices of a
    byte slice split around runs of Unicode code points satisfying
    a predicate.
  * crypto/aes: The value returned by NewCipher no longer
    implements the NewCTR, NewGCM, NewCBCEncrypter, and
    NewCBCDecrypter methods. These methods were undocumented and
    not available on all architectures. Instead, the Block value
    should be passed directly to the relevant crypto/cipher
    functions. For now, crypto/cipher still checks for those
    methods on Block values, even if they are not used by the
    standard library anymore.
  * crypto/aes: The Stream implementation returned by NewCTR when
    used with crypto/aes is now several times faster on amd64 and
    arm64.
  * crypto/cipher: The new NewGCMWithRandomNonce function returns
    an AEAD that implements AES-GCM by generating a random nonce
    during Seal and prepending it to the ciphertext.
  * crypto/cipher: NewOFB, NewCFBEncrypter, and NewCFBDecrypter are
    now deprecated. OFB and CFB mode are not authenticated, which
    generally enables active attacks to manipulate and recover the
    plaintext. It is recommended that applications use AEAD modes
    instead. If an unauthenticated Stream mode is required, use
    NewCTR instead.
  * crypto/ecdsa: PrivateKey.Sign now produces a deterministic
    signature according to RFC 6979 if the random source is nil.
  * crypto/md5: The value returned by md5.New now also implements
    the encoding.BinaryAppender interface.
  * crypto/rand: The Read function is now guaranteed not to
    fail. It will always return nil as the error result. If Read
    were to encounter an error while reading from Reader, the
    program will irrecoverably crash. Note that the platform APIs
    used by the default Reader are documented to always succeed, so
    this change should only affect programs that override the
    Reader variable. One exception are Linux kernels before version
    3.17, where the default Reader still opens /dev/urandom and may
    fail.
  * crypto/rand: On Linux 6.11 and later, Reader now uses the
    getrandom system call via vDSO. This is several times faster,
    especially for small reads.
  * crypto/rand: On OpenBSD, Reader now uses arc4random_buf(3).
  * crypto/rand: The new Text function can be used to generate
    cryptographically secure random text strings.
  * crypto/rsa: GenerateKey now returns an error if a key of less
    than 1024 bits is requested. All Sign, Verify, Encrypt, and
    Decrypt methods now return an error if used with a key smaller
    than 1024 bits. Such keys are insecure and should not be
    used. GODEBUG setting rsa1024min=0 restores the old behavior,
    but we recommend doing so only if necessary and only in tests,
    for example by adding a //go:debug rsa1024min=0 line to a test
    file. A new GenerateKey example provides an easy-to-use
    standard 2048-bit test key.
  * crypto/rsa: It is now safe and more efficient to call
    PrivateKey.Precompute before PrivateKey.Validate. Precompute is
    now faster in the presence of partially filled out
    PrecomputedValues, such as when unmarshaling a key from JSON.
  * crypto/rsa: The package now rejects more invalid keys, even
    when Validate is not called, and GenerateKey may return new
    errors for broken random sources. The Primes and Precomputed
    fields of PrivateKey are now used and validated even when some
    values are missing. See also the changes to crypto/x509 parsing
    and marshaling of RSA keys described below.
  * crypto/rsa: SignPKCS1v15 and VerifyPKCS1v15 now support
    SHA-512/224, SHA-512/256, and SHA-3.
  * crypto/rsa: GenerateKey now uses a slightly different method to
    generate the private exponent (Carmichael's totient instead of
    Euler's totient). Rare applications that externally regenerate
    keys from only the prime factors may produce different but
    compatible results.
  * crypto/rsa: Public and private key operations are now up to two
    times faster on wasm.
  * crypto/sha1: The value returned by sha1.New now also implements
    the encoding.BinaryAppender interface.
  * crypto/sha256: The values returned by sha256.New and
    sha256.New224 now also implement the encoding.BinaryAppender
    interface.
  * crypto/sha512: The values returned by sha512.New,
    sha512.New384, sha512.New512_224 and sha512.New512_256 now also
    implement the encoding.BinaryAppender interface.
  * crypto/subtle: The new WithDataIndependentTiming function
    allows the user to run a function with architecture specific
    features enabled which guarantee specific instructions are data
    value timing invariant. This can be used to make sure that code
    designed to run in constant time is not optimized by CPU-level
    features such that it operates in variable time. Currently,
    WithDataIndependentTiming uses the PSTATE.DIT bit on arm64, and
    is a no-op on all other architectures. GODEBUG setting
    dataindependenttiming=1 enables the DIT mode for the entire Go
    program.
  * crypto/subtle: The XORBytes output must overlap exactly or not
    at all with the inputs. Previously, the behavior was otherwise
    undefined, while now XORBytes will panic.
  * crypto/tls: The TLS server now supports Encrypted Client Hello
    (ECH). This feature can be enabled by populating the
    Config.EncryptedClientHelloKeys field.
  * crypto/tls: The new post-quantum X25519MLKEM768 key exchange
    mechanism is now supported and is enabled by default when
    Config.CurvePreferences is nil. GODEBUG setting tlsmlkem=0
    reverts the default.
  * crypto/tls: Support for the experimental X25519Kyber768Draft00
    key exchange has been removed.
  * crypto/tls: Key exchange ordering is now handled entirely by
    the crypto/tls package. The order of Config.CurvePreferences is
    now ignored, and the contents are only used to determine which
    key exchanges to enable when the field is populated.
  * crypto/tls: The new ClientHelloInfo.Extensions field lists the
    IDs of the extensions received in the Client Hello
    message. This can be useful for fingerprinting TLS clients.
  * crypto/x509: The x509sha1 GODEBUG setting has been
    removed. Certificate.Verify no longer supports SHA-1 based
    signatures.
  * crypto/x509: OID now implements the encoding.BinaryAppender and
    encoding.TextAppender interfaces.
  * crypto/x509: The default certificate policies field has changed
    from Certificate.PolicyIdentifiers to
    Certificate.Policies. When parsing certificates, both fields
    will be populated, but when creating certificates policies will
    now be taken from the Certificate.Policies field instead of the
    Certificate.PolicyIdentifiers field. This change can be
    reverted with GODEBUG setting x509usepolicies=0.
  * crypto/x509: CreateCertificate will now generate a serial
    number using a RFC 5280 compliant method when passed a template
    with a nil Certificate.SerialNumber field, instead of failing.
  * crypto/x509: Certificate.Verify now supports policy validation,
    as defined in RFC 5280 and RFC 9618. The new
    VerifyOptions.CertificatePolicies field can be set to an
    acceptable set of policy OIDs. Only certificate chains with
    valid policy graphs will be returned from Certificate.Verify.
  * crypto/x509: MarshalPKCS8PrivateKey now returns an error
    instead of marshaling an invalid RSA
    key. (MarshalPKCS1PrivateKey doesn't have an error return, and
    its behavior when provided invalid keys continues to be
    undefined.)
  * crypto/x509: ParsePKCS1PrivateKey and ParsePKCS8PrivateKey now
    use and validate the encoded CRT values, so might reject
    invalid RSA keys that were previously accepted. Use GODEBUG
    setting x509rsacrt=0 to revert to recomputing the CRT values.
  * debug/elf: The debug/elf package adds support for handling
    symbol versions in dynamic ELF (Executable and Linkable Format)
    files. The new File.DynamicVersions method returns a list of
    dynamic versions defined in the ELF file. The new
    File.DynamicVersionNeeds method returns a list of dynamic
    versions required by this ELF file that are defined in other
    ELF objects. Finally, the new Symbol.HasVersion and
    Symbol.VersionIndex fields indicate the version of a symbol.
  * encoding: Two new interfaces, TextAppender and BinaryAppender,
    have been introduced to append the textual or binary
    representation of an object to a byte slice. These interfaces
    provide the same functionality as TextMarshaler and
    BinaryMarshaler, but instead of allocating a new slice each
    time, they append the data directly to an existing slice. These
    interfaces are now implemented by standard library types that
    already implemented TextMarshaler and/or BinaryMarshaler.
  * encoding/json: When marshaling, a struct field with the new
    omitzero option in the struct field tag will be omitted if its
    value is zero. If the field type has an IsZero() bool method,
    that will be used to determine whether the value is
    zero. Otherwise, the value is zero if it is the zero value for
    its type. The omitzero field tag is clearer and less
    error-prone than omitempty when the intent is to omit zero
    values. In particular, unlike omitempty, omitzero omits
    zero-valued time.Time values, which is a common source of
    friction.
  * encoding/json: If both omitempty and omitzero are specified,
    the field will be omitted if the value is either empty or zero
    (or both).
  * encoding/json: UnmarshalTypeError.Field now includes embedded
    structs to provide more detailed error messages.
  * go/types: All go/types data structures that expose sequences
    using a pair of methods such as Len() int and At(int) T now
    also have methods that return iterators, allowing you to
    simplify code. The methods are: Interface.EmbeddedTypes,
    Interface.ExplicitMethods, Interface.Methods,
    MethodSet.Methods, Named.Methods, Scope.Children,
    Struct.Fields, Tuple.Variables, TypeList.Types,
    TypeParamList.TypeParams, Union.Terms.
  * hash/adler32: The value returned by New now also implements the
    encoding.BinaryAppender interface.
  * hash/crc32: The values returned by New and NewIEEE now also
    implement the encoding.BinaryAppender interface.
  * hash/crc64: The value returned by New now also implements the
    encoding.BinaryAppender interface.
  * hash/fnv: The values returned by New32, New32a, New64, New64a,
    New128 and New128a now also implement the
    encoding.BinaryAppender interface.
  * hash/maphash: The new Comparable and WriteComparable functions
    can compute the hash of any comparable value. These make it
    possible to hash anything that can be used as a Go map key.
  * log/slog: The new DiscardHandler is a handler that is never
    enabled and always discards its output.
  * log/slog: Level and LevelVar now implement the
    encoding.TextAppender interface.
  * math/big: Float, Int and Rat now implement the
    encoding.TextAppender interface.
  * math/rand: Calls to the deprecated top-level Seed function no
    longer have any effect. To restore the old behavior use GODEBUG
    setting randseednop=0. For more background see proposal
    go#67273.
  * math/rand/v2: ChaCha8 and PCG now implement the
    encoding.BinaryAppender interface.
  * net: ListenConfig now uses MPTCP by default on systems where it
    is supported (currently on Linux only).
  * net: IP now implements the encoding.TextAppender interface.
  * net/http: Transport's limit on 1xx informational responses
    received in response to a request has changed. It previously
    aborted a request and returned an error after receiving more
    than 5 1xx responses. It now returns an error if the total size
    of all 1xx responses exceeds the
    Transport.MaxResponseHeaderBytes configuration setting.
  * net/http: In addition, when a request has a
    net/http/httptrace.ClientTrace.Got1xxResponse trace hook, there
    is now no limit on the total number of 1xx responses. The
    Got1xxResponse hook may return an error to abort a request.
  * net/http: Transport and Server now have an HTTP2 field which
    permits configuring HTTP/2 protocol settings.
  * net/http: The new Server.Protocols and Transport.Protocols
    fields provide a simple way to configure what HTTP protocols a
    server or client use.
  * net/http: The server and client may be configured to support
    unencrypted HTTP/2 connections.
  * net/http: When Server.Protocols contains UnencryptedHTTP2, the
    server will accept HTTP/2 connections on unencrypted ports. The
    server can accept both HTTP/1 and unencrypted HTTP/2 on the
    same port.
  * net/http: When Transport.Protocols contains UnencryptedHTTP2
    and does not contain HTTP1, the transport will use unencrypted
    HTTP/2 for http:// URLs. If the transport is configured to use
    both HTTP/1 and unencrypted HTTP/2, it will use HTTP/1.
  * net/http: Unencrypted HTTP/2 support uses "HTTP/2 with Prior
    Knowledge" (RFC 9113, section 3.3). The deprecated "Upgrade:
    h2c" header is not supported.
  * net/netip: Addr, AddrPort and Prefix now implement the
    encoding.BinaryAppender and encoding.TextAppender interfaces.
  * net/url: URL now also implements the encoding.BinaryAppender
    interface.
  * os/user: On Windows, Current can now be used in Windows Nano
    Server. The implementation has been updated to avoid using
    functions from the NetApi32 library, which is not available in
    Nano Server.
  * os/user: On Windows, Current, Lookup and LookupId now support
    the following built-in service user accounts: NT
    AUTHORITY\SYSTEM, NT AUTHORITY\LOCAL SERVICE, NT
    AUTHORITY\NETWORK SERVICE
  * os/user: On Windows, Current has been made considerably faster
    when the current user is joined to a slow domain, which is the
    usual case for many corporate users. The new implementation
    performance is now in the order of milliseconds, compared to
    the previous implementation which could take several seconds,
    or even minutes, to complete.
  * os/user: On Windows, Current now returns the process owner user
    when the current thread is impersonating another
    user. Previously, it returned an error.
  * regexp: Regexp now implements the encoding.TextAppender
    interface.
  * runtime: The GOROOT function is now deprecated. In new code
    prefer to use the system path to locate the "go" binary, and
    use go env GOROOT to find its GOROOT.
  * strings: The strings package adds several functions that work
    with iterators.
  * strings: Lines returns an iterator over the newline-terminated
    lines in a string.
  * strings: SplitSeq returns an iterator over all substrings of a
    string split around a separator.
  * strings: SplitAfterSeq returns an iterator over substrings of a
    string split after each instance of a separator.
  * strings: FieldsSeq returns an iterator over substrings of a
    string split around runs of whitespace characters, as defined
    by unicode.IsSpace.
  * strings: FieldsFuncSeq returns an iterator over substrings of a
    string split around runs of Unicode code points satisfying a
    predicate.
  * sync: The implementation of sync.Map has been changed,
    improving performance, particularly for map modifications. For
    instance, modifications of disjoint sets of keys are much less
    likely to contend on larger maps, and there is no longer any
    ramp-up time required to achieve low-contention loads from the
    map. If you encounter any problems, set
    GOEXPERIMENT=nosynchashtriemap at build time to switch back to
    the old implementation and please file an issue.
  * testing: The new T.Context and B.Context methods return a
    context that's canceled after the test completes and before
    test cleanup functions run.
  * testing: The new T.Chdir and B.Chdir methods can be used to
    change the working directory for the duration of a test or
    benchmark.
  * text/template: Templates now support range-over-func and
    range-over-int.
  * time: Time now implements the encoding.BinaryAppender and
    encoding.TextAppender interfaces.
  * Linux port: As announced in the Go 1.23 release notes, Go 1.24
    requires Linux kernel version 3.2 or later.
  * Darwin port: Go 1.24 is the last release that will run on macOS
    11 Big Sur. Go 1.25 will require macOS 12 Monterey or later.
  * WebAssembly: The go:wasmexport compiler directive is added for
    Go programs to export functions to the WebAssembly host.
  * WebAssembly: On WebAssembly System Interface Preview 1
    (GOOS=wasip1 GOARCH=wasm), Go 1.24 supports building a Go
    program as a reactor/library, by specifying the
  - buildmode=c-shared build flag.
  * WebAssembly: More types are now permitted as argument or result
    types for go:wasmimport functions. Specifically, bool, string,
    uintptr, and pointers to certain types are allowed (see the
    documentation for detail), along with 32-bit and 64-bit integer
    and float types, and unsafe.Pointer, which are already
    allowed. These types are also permitted as argument or result
    types for go:wasmexport functions.
  * WebAssembly: The support files for WebAssembly have been moved
    to lib/wasm from misc/wasm.
  * Windows: The 32-bit windows/arm port (GOOS=windows GOARCH=arm)
    has been marked broken. See issue go#70705 for details.</changelog>
  <changelog author="jkowalczyk@suse.com" date="1741089600">- go1.24.1 (released 2025-03-04) includes security fixes to the
  net/http package, as well as bug fixes to cgo, the compiler, the
  go command, and the reflect, runtime, and syscall packages.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-22870
  * go#71986 go#71984 boo#1238572 security: fix CVE-2025-22870 net/http, x/net/proxy, x/net/http/httpproxy: proxy bypass using IPv6 zone IDs
  * go#71687 cmd/go: panics with GOAUTH='git dir' go get -x
  * go#71705 runtime: add linkname of runtime.lastmoduledatap for cloudwego/sonic
  * go#71728 runtime: usleep computes wrong tv_nsec on s390x
  * go#71745 crypto: add fips140 as an opaque GODEBUG setting and add documentation for it
  * go#71829 cmd/compile: fail to compile package in 1.24
  * go#71836 os: possible regression from Go 1.23 to Go 1.24 when opening DevNull with O_TRUNC
  * go#71840 runtime: recover added in range-over-func loop body doesn't stop panic propagation / segfaults printing error
  * go#71849 os: spurious SIGCHILD on running child process
  * go#71855 cmd/compile: Pow10 freeze the compiler on certain condition on Go 1.24
  * go#71858 debug/buildinfo: false positives with external scanners flag for go117 binary in testdata
  * go#71876 reflect: Value.Seq panicking on functional iterator methods
  * go#71904 cmd/compile: nil dereference when storing field of non-nil struct value
  * go#71916 reflect: Value.Seq iteration value types not matching the type of given int types
  * go#71938 cmd/compile: "fatal error: found pointer to free object" on arm64
  * go#71955 proposal: runtime: allow cleanups to run concurrently
  * go#71963 runtime/cgo: does not build with -Wdeclaration-after-statement
  * go#71977 syscall: js/wasm file operations fail on windows / node.js</changelog>
  <changelog author="jkowalczyk@suse.com" date="1741176000">- Packaging improvements:
  * SLE-12 only: Add declarations to Cgo seccomp_linux.go
    for new syscalls seccomp and getrandom which are not present
    in the kernel headers supplied by glibc version in SLE-12.
    (Marcus Meissner)
    Refs boo#1239182
  * Add patch go-fixseccomp.patch</changelog>
  <changelog author="jkowalczyk@suse.com" date="1743508800">- go1.24.2 (released 2025-04-01) includes security fixes to the
  net/http package, as well as bug fixes to the compiler, the
  runtime, the go command, and the crypto/tls, go/types, net/http,
  and testing packages.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-22871
  * go#72011 go#71988 boo#1240550 security: fix CVE-2025-22871 net/http: reject bare LF in chunked encoding
  * go#72067 cmd/compile: out of memory
  * go#72103 net/http: go1.24 breaks compatibility by modifying in-place the tls.Config{NextProtos}
  * go#72115 runtime: process hangs for mips hardware
  * go#72796 runtime: add an example for AddCleanup
  * go#72822 cmd/compile: OOM with mutually-recursive iter.Seq
  * go#72823 crypto/tls: FIPS 140-3 modes reject ECDSA w/ curve P-521/SHA-512 in TLS
  * go#72826 go/types, types2: CheckExpr / Eval may mutate type checked objects (=&gt; data race)
  * go#72872 runtime: cgo callback on extra M treated as external code after nested cgo callback returns
  * go#72934 testing: b.StopTimer breaks b.Loop
  * go#72938 internal/godebugs: winsymlink and winreadlinkvolume have incorrect defaults for Go 1.22
  * go#72974 testing: b.Loop gives bogus results in some situations</changelog>
  <changelog author="jkowalczyk@suse.com" date="1743595200">- Packaging improvements:
  * SLE-12 only: Fix conditional for go-fixsecomp.patch to work
    correctly when suse_version is undefined.
    Refs boo#1239182
  * Fix RPM warning by removing valid macro syntax in comment
    describing naming format of llvm-tsan_commit.tar.xz</changelog>
  <changelog author="mail+rpm@georg-pfuetzenreuter.net" date="1745236800">- Add gh-issue-73141.patch to repair random segmentation faults (boo#1240764)</changelog>
  <changelog author="jkowalczyk@suse.com" date="1746532800">- go1.24.3 (released 2025-05-06) includes security fixes to the os
  package, as well as bug fixes to the runtime, the compiler, the
  linker, the go command, and the crypto/tls and os packages.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-22873
  * go#73556 go#73555 boo#1242715 security: fix CVE-2025-22873 os: Root permits access to parent directory
  * go#73082 os: Root.Open panics when opening a symlink referencing the root
  * go#73092 cmd/link: linkname directive on userspace variable can override runtime variable
  * go#73118 crypto/tls: ECH decodeInnerClientHello incorrectly rejects ClientHello with GREASE values in supportedVersions
  * go#73144 runtime: segmentation fault from vgetrandomPutState and runtime.growslice w/ runtime.OSLockThread
  * go#73192 runtime: -race data race map traceback report incorrect functions
  * go#73281 cmd/compile: program compiles to wasm but is invalid: go:wasmexport: integer too large
  * go#73379 runtime, x/sys/unix: Connectx is broken on darwin/amd64
  * go#73440 cmd/compile: infinite loop in the inliner
  * go#73500 cmd/go: +dirty in version stamping doesn't combine well with +incompatible
- Packaging improvements:
  * Drop gh-issue-73141.patch to repair random segmentation faults (boo#1240764)
    fixed in upstream release.</changelog>
  <changelog author="jkowalczyk@suse.com" date="1749124800">- go1.24.4 (released 2025-06-05) includes security fixes to the
  crypto/x509, net/http, and os packages, as well as bug fixes to
  the linker, the go command, and the hash/maphash and os packages.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-22874 CVE-2025-0913 CVE-2025-4673
  * go#73700 go#73702 boo#1244158 security: fix CVE-2025-22874 crypto/x509: ExtKeyUsageAny bypasses policy validation
  * go#73720 go#73612 boo#1244157 security: fix CVE-2025-0913 os: inconsistent handling of O_CREATE|O_EXCL on Unix and Windows
  * go#73906 go#73816 boo#1244156 security: fix CVE-2025-4673 net/http: sensitive headers not cleared on cross-origin redirect
  * go#73570 os: Root.Mkdir creates directories with zero permissions on OpenBSD
  * go#73669 hash/maphash: hashing channels with purego impl. of maphash.Comparable panics
  * go#73678 runtime/debug: BuildSetting does not document DefaultGODEBUG
  * go#73809 cmd/go: add fips140 module selection mechanism
  * go#73832 cmd/link: Go 1.24.3 and 1.23.9 regression - duplicated definition of symbol dlopen</changelog>
  <changelog author="jkowalczyk@suse.com" date="1751976000">- go1.24.5 (released 2025-07-08) includes security fixes to the go
  command, as well as bug fixes to the compiler, the linker, the
  runtime, and the go command.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-4674
  * go#74381 go#74380 boo#1246118 security: fix CVE-2025-4674 cmd/go: disable support for multiple vcs in one module
  * go#73908 runtime: bad frame pointer during panic during duffcopy
  * go#74098 cmd/compile: regression on ppc64le bit operations
  * go#74113 cmd/go: crash on unknown GOEXPERIMENT during toolchain selection
  * go#74290 runtime: heap mspan limit is set too late, causing data race between span allocation and conservative scanning
  * go#74294 internal/trace: stress tests triggering suspected deadlock in tracer
  * go#74346 runtime: memlock not unlocked in all control flow paths in sysReserveAlignedSbrk
  * go#74363 runtime/pprof: crash "cannot read stack of running goroutine" in goroutine profile
  * go#74403 cmd/link: duplicated definition of symbol github.com/ebitengine/purego.syscall15XABI0 when running with ASAN</changelog>
  <changelog author="jkowalczyk@suse.com" date="1754481600">- go1.24.6 (released 2025-08-06) includes security fixes to the
  database/sql and os/exec packages, as well as bug fixes to the
  runtime.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-47906 CVE-2025-47907
  * go#74804 go#74466 boo#1247719 security: fix CVE-2025-47906 os/exec: LookPath bug: incorrect expansion of "", "." and ".." in some PATH configurations
  * go#74833 go#74831 boo#1247720 security: fix CVE-2025-47907 database/sql: incorrect results returned from Rows.Scan
  * go#73800 runtime: RSS seems to have increased in Go 1.24 while the runtime accounting has not
  * go#74416 runtime: use-after-free of allpSnapshot in findRunnable
  * go#74694 runtime: segfaults in runtime.(*unwinder).next
  * go#74760 os/user:nolibgcc: TestGroupIdsTestUser failures</changelog>
  <changelog author="jkowalczyk@suse.com" date="1755172800">- Packaging improvements:
  * Remove conditional gccgo bootstrap sections and gcc-go.patch.
    gccgo cannot be used in any version newer than go1.21. Removal
    simplifies go1.x package code.
  * go1.21 can optionally be bootstrapped with gccgo and serve as
    the inital version of go1.x.
  * go1.21 will be the initial version of Go in the bootstrap chain
    until gcc gccgo is updated to support a language level newer
    than go1.18.
  * Drop gcc-go.patch
  * Refs boo#1247816 bootstrap go1.21 with gccgo
  * Refs boo#1248082 drop unused gccgo bootstrap code in go1.22+</changelog>
  <changelog author="jkowalczyk@suse.com" date="1756900800">- go1.24.7 (released 2025-09-03) includes fixes to the go command,
  and the net and os/exec packages.
  Refs boo#1236217 go1.24 release tracking
  * go#75007 os/exec: TestLookPath fails on plan9 after CL 685755
  * go#74821 cmd/go: "get toolchain@latest" should ignore release candidates
  * go#74818 net: WriteMsgUDPAddrPort should accept IPv4-mapped IPv6 destination addresses on IPv4 UDP sockets</changelog>
  <changelog author="asarai@suse.com" date="1758283200">- Package svgpan.js to fix issues with "go tool pprof". boo#1249985</changelog>
  <changelog author="jkowalczyk@suse.com" date="1759838400">- go1.24.8 (released 2025-10-07) includes security fixes to the
  archive/tar, crypto/tls, crypto/x509, encoding/asn1,
  encoding/pem, net/http, net/mail, net/textproto, and net/url
  packages, as well as bug fixes to the compiler, the linker, and
  the debug/pe, net/http, os, and sync/atomic packages.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-58189 CVE-2025-61725 CVE-2025-58188 CVE-2025-58185 CVE-2025-58186 CVE-2025-61723 CVE-2025-58183 CVE-2025-47912 CVE-2025-58187 CVE-2025-61724
  * go#75660 go#75652 boo#1251255 security: fix CVE-2025-58189 crypto/tls: ALPN negotiation error contains attacker controlled information
  * go#75700 go#75680 boo#1251253 security: fix CVE-2025-61725 net/mail: excessive CPU consumption in ParseAddress
  * go#75702 go#75675 boo#1251260 security: fix CVE-2025-58188 crypto/x509: panic when validating certificates with DSA public keys
  * go#75704 go#75671 boo#1251258 security: fix CVE-2025-58185 encoding/asn1: pre-allocating memory when parsing DER payload can cause memory exhaustion
  * go#75706 go#75672 boo#1251259 security: fix CVE-2025-58186 net/http: lack of limit when parsing cookies can cause memory exhaustion
  * go#75708 go#75676 boo#1251256 security: fix CVE-2025-61723 encoding/pem: quadratic complexity when parsing some invalid inputs
  * go#75710 go#75677 boo#1251261 security: fix CVE-2025-58183 archive/tar: unbounded allocation when parsing GNU sparse map
  * go#75712 go#75678 boo#1251257 security: fix CVE-2025-47912 net/url: insufficient validation of bracketed IPv6 hostnames
  * go#75714 go#75681 boo#1251254 security: fix CVE-2025-58187 crypto/x509: quadratic complexity when checking name constraints
  * go#75717 go#75716 boo#1251262 security: fix CVE-2025-61724 net/textproto: excessive CPU consumption in Reader.ReadResponse
  * go#75138 os: Root.OpenRoot sets incorrect name, losing prefix of original root
  * go#75220 debug/pe: pe.Open fails on object files produced by llvm-mingw 21
  * go#75351 cmd/link: panic on riscv64 with CGO enabled due to empty container symbol
  * go#75356 net: new test TestIPv4WriteMsgUDPAddrPortTargetAddrIPVersion fails on plan9
  * go#75359 os: new test TestOpenFileCreateExclDanglingSymlink fails on Plan 9
  * go#75523 crypto/internal/fips140/rsa: requires a panic if self-tests fail
  * go#75538 net/http: internal error: connCount underflow
  * go#75594 cmd/compile: internal compiler error with GOEXPERIMENT=cgocheck2 on github.com/leodido/go-urn
  * go#75609 sync/atomic: comment for Uintptr.Or incorrectly describes return value</changelog>
  <changelog author="jkowalczyk@suse.com" date="1760356800">- go1.24.9 (released 2025-10-13) includes fixes to the crypto/x509
  package.
  Refs boo#1236217 go1.24 release tracking
  * go#75860 crypto/x509: TLS validation fails for FQDNs with trailing dot
- Packaging improvements:
  * Add net-url-allow-IP-literals-with-IPv4-mapped-IPv6-addresses.patch
    needed today and will be available in the next upstream release</changelog>
  <changelog author="jkowalczyk@suse.com" date="1762344000">- go1.24.10 (released 2025-11-05) includes fixes to the
  encoding/pem and net/url packages.
  Refs boo#1236217 go1.24 release tracking
  * go#75831 net/url: ipv4 mapped ipv6 addresses should be valid in square brackets
  * go#75951 encoding/pem: regression when decoding blocks with leading garbage
  * go#76028 pem/encoding: malformed line endings can cause panics
- Packaging improvements:
  * Remove net-url-allow-IP-literals-with-IPv4-mapped-IPv6-addresses.patch
    No longer needed with go#75831 in latest upstream release</changelog>
</package>
<package pkgid="32a88116435b8f89610226c9bb101036e801e702b595b46527fd2a4b4315332b" name="go1.24-race" arch="x86_64">
  <version epoch="0" ver="1.24.10" rel="150700.1.2"/>
  <changelog author="jkowalczyk@suse.com" date="1734091200">- go1.24rc1 (released 2024-12-13) is a release candidate version of
  go1.24 cut from the master branch at the revision tagged
  go1.24rc1.
  Refs boo#1236217 go1.24 release tracking
  * go1.24 requires the final point release of go1.22 or later
    for bootstrap.</changelog>
  <changelog author="jkowalczyk@suse.com" date="1737028800">- go1.24rc2 (released 2024-01-16) is a release candidate version of
  go1.24 cut from the master branch at the revision tagged
  go1.24rc2.
  Refs boo#1236217 go1.24 release tracking
  CVE-2024-45341 CVE-2024-45336 CVE-2025-22865 CVE-2024-45340
  * go#71209 go#71156 boo#1236045 security: fix CVE-2024-45341 crypto/x509: properly check for IPv6 hosts in URIs
  * go#71212 go#70530 boo#1236046 security: fix CVE-2024-45336 net/http: persist header stripping across repeated redirects
  * go#71216 boo#1236361 security: fix CVE-2025-22865 crypto/x509: avoid panic when parsing partial PKCS#1 private keys
  * go#71249 boo#1236360 security: fix CVE-2024-45340 cmd/go: restore netrc preferences for GOAUTH and fix domain lookup</changelog>
  <changelog author="jkowalczyk@suse.com" date="1738756800">- go1.24rc3 (released 2024-02-05) is a release candidate version of
  go1.24 cut from the master branch at the revision tagged
  go1.24rc3.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-22866 CVE-2025-22867
  * go#71423 go#71383 boo#1236801 security: fix CVE-2025-22866 crypto/internal/fips140/nistec: p256NegCond is variable time on ppc64le
  * go#71476 boo#1236839 security: fix CVE-2025-22867 cmd/go: arbitrary code execution during build on darwin
  * foo</changelog>
  <changelog author="jkowalczyk@suse.com" date="1739275200">- go1.24 (released 2025-02-11) is a major release of Go.
  go1.24.x minor releases will be provided through February 2026.
  https://github.com/golang/go/wiki/Go-Release-Cycle
  go1.24 arrives six months after Go 1.23. Most of its changes are
  in the implementation of the toolchain, runtime, and
  libraries. As always, the release maintains the Go 1 promise of
  compatibility. We expect almost all Go programs to continue to
  compile and run as before.
  Refs boo#1236217 go1.24 release tracking
  * Language change: Go 1.24 now fully supports generic type
    aliases: a type alias may be parameterized like a defined
    type. See the language spec for details. For now, the feature
    can be disabled by setting GOEXPERIMENT=noaliastypeparams; but
    the aliastypeparams setting will be removed for Go 1.25.
  * go command: Go modules can now track executable dependencies
    using tool directives in go.mod. This removes the need for the
    previous workaround of adding tools as blank imports to a file
    conventionally named "tools.go". The go tool command can now
    run these tools in addition to tools shipped with the Go
    distribution.
  * go command: The new -tool flag for go get causes a tool
    directive to be added to the current module for named packages
    in addition to adding require directives.
  * go command: The new tool meta-pattern refers to all tools in
    the current module. This can be used to upgrade them all with
    go get tool or to install them into your GOBIN directory with
    go install tool.
  * go command: Executables created by go run and the new behavior
    of go tool are now cached in the Go build cache. This makes
    repeated executions faster at the expense of making the cache
    larger. See go#69290.
  * go command: The go build and go install commands now accept a
  - json flag that reports build output and failures as structured
    JSON output on standard output. For details of the reporting
    format, see go help buildjson. Furthermore, go test -json now
    reports build output and failures in JSON, interleaved with
    test result JSON. These are distinguished by new Action types,
    but if they cause problems in a test integration system, you
    can revert to the text build output with GODEBUG setting
    gotestjsonbuildtext=1.
  * go command: The new GOAUTH environment variable provides a
    flexible way to authenticate private module fetches. See go
    help goauth for more information.
  * go command: The go build command now sets the main module's
    version in the compiled binary based on the version control
    system tag and/or commit. A +dirty suffix will be appended if
    there are uncommitted changes. Use the -buildvcs=false flag to
    omit version control information from the binary.
  * go command: The new GODEBUG setting toolchaintrace=1 can be
    used to trace the go command's toolchain selection process.
  * cgo: cgo supports new annotations for C functions to improve
    run time performance. cgo noescape cFunctionName tells the
    compiler that memory passed to the C function cFunctionname
    does not escape. cgo nocallback cFunctionName tells the
    compiler that the C function cFunctionName does not call back
    to any Go functions.
  * cgo: cgo currently refuses to compile calls to a C function
    which has multiple incompatible declarations. For instance,
    if f is declared as both void f(int) and void f(double),
    cgo will report an error instead of possibly generating an
    incorrect call sequence for f(0). New in this release is a
    better detector for this error condition when the incompatible
    declarations appear in different files. See go#67699.
  * objdump: The objdump tool now supports dissassembly on 64-bit
    LoongArch (GOARCH=loong64), RISC-V (GOARCH=riscv64), and S390X
    (GOARCH=s390x).
  * vet: The new tests analyzer reports common mistakes in
    declarations of tests, fuzzers, benchmarks, and examples in
    test packages, such as malformed names, incorrect signatures,
    or examples that document non-existent identifiers. Some of
    these mistakes may cause tests not to run. This analyzer is
    among the subset of analyzers that are run by go test.
  * vet: The existing printf analyzer now reports a diagnostic for
    calls of the form fmt.Printf(s), where s is a non-constant
    format string, with no other arguments. Such calls are nearly
    always a mistake as the value of s may contain the % symbol;
    use fmt.Print instead. See go#60529. This check tends to
    produce findings in existing code, and so is only applied when
    the language version (as specified by the go.mod go directive
    or //go:build comments) is at least Go 1.24, to avoid causing
    continuous integration failures when updating to the 1.24 Go
    toolchain.
  * vet: The existing buildtag analyzer now reports a diagnostic
    when there is an invalid Go major version build constraint
    within a //go:build directive. For example, //go:build go1.23.1
    refers to a point release; use //go:build go1.23 instead.
    See go#64127.
  * vet: The existing copylock analyzer now reports a diagnostic
    when a variable declared in a 3-clause "for" loop such as for i
    := iter(); done(i); i = next(i) { ... } contains a sync.Locker,
    such as a sync.Mutex. Go 1.22 changed the behavior of these
    loops to create a new variable for each iteration, copying the
    value from the previous iteration; this copy operation is not
    safe for locks. See go#66387.
  * GOCACHEPROG: The cmd/go internal binary and test caching
    mechanism can now be implemented by child processes
    implementing a JSON protocol between the cmd/go tool and the
    child process named by the GOCACHEPROG environment
    variable. This was previously behind a GOEXPERIMENT. For
    protocol details, see the documentation.
  * Runtime: Several performance improvements to the runtime have
    decreased CPU overheads by 2-3% on average across a suite of
    representative benchmarks. Results may vary by
    application. These improvements include a new builtin map
    implementation based on Swiss Tables, more efficient memory
    allocation of small objects, and a new runtime-internal mutex
    implementation.
  * Runtime: The new builtin map implementation and new
    runtime-internal mutex may be disabled by setting
    GOEXPERIMENT=noswissmap and GOEXPERIMENT=nospinbitmutex at
    build time respectively.
  * Compiler: The compiler already disallowed defining new methods
    with receiver types that were cgo-generated, but it was
    possible to circumvent that restriction via an alias type. Go
    1.24 now always reports an error if a receiver denotes a
    cgo-generated type, whether directly or indirectly (through an
    alias type).
  * Linker: The linker now generates a GNU build ID (the ELF
    NT_GNU_BUILD_ID note) on ELF platforms and a UUID (the Mach-O
    LC_UUID load command) on macOS by default. The build ID or UUID
    is derived from the Go build ID. It can be disabled by the -B
    none linker flag, or overridden by the -B 0xNNNN linker flag
    with a user-specified hexadecimal value.
  * Bootstrap: As mentioned in the Go 1.22 release notes, Go 1.24
    now requires Go 1.22.6 or later for bootstrap. We expect that
    Go 1.26 will require a point release of Go 1.24 or later for
    bootstrap.
  * Standard library: Directory-limited filesystem access: The new
    os.Root type provides the ability to perform filesystem
    operations within a specific directory. The os.OpenRoot
    function opens a directory and returns an os.Root. Methods on
    os.Root operate within the directory and do not permit paths
    that refer to locations outside the directory, including ones
    that follow symbolic links out of the directory. The methods on
    os.Root mirror most of the file system operations available in
    the os package, including for example os.Root.Open,
    os.Root.Create, os.Root.Mkdir, and os.Root.Stat,
  * Standard library: new benchmark function: Benchmarks may now
    use the faster and less error-prone testing.B.Loop method to
    perform benchmark iterations like for b.Loop() { ... } in place
    of the typical loop structures involving b.N like for range
    b.N. This offers two significant advantages: 1) The benchmark
    function will execute exactly once per -count, so expensive
    setup and cleanup steps execute only once, and 2) Function call
    parameters and results are kept alive, preventing the compiler
    from fully optimizing away the loop body.
  * Standard library: Improved finalizers: The new
    runtime.AddCleanup function is a finalization mechanism that is
    more flexible, more efficient, and less error-prone than
    runtime.SetFinalizer. AddCleanup attaches a cleanup function to
    an object that will run once the object is no longer reachable.
    However, unlike SetFinalizer, multiple cleanups may be attached
    to a single object, cleanups may be attached to interior
    pointers, cleanups do not generally cause leaks when objects
    form a cycle, and cleanups do not delay the freeing of an
    object or objects it points to. New code should prefer
    AddCleanup over SetFinalizer.
  * Standard library: New weak package: The new weak package
    provides weak pointers. Weak pointers are a low-level primitive
    provided to enable the creation of memory-efficient structures,
    such as weak maps for associating values, canonicalization maps
    for anything not covered by package unique, and various kinds
    of caches. For supporting these use-cases, this release also
    provides runtime.AddCleanup and maphash.Comparable.
  * Standard library: New crypto/mlkem package: The new
    crypto/mlkem package implements ML-KEM-768 and
    ML-KEM-1024. ML-KEM is a post-quantum key exchange mechanism
    formerly known as Kyber and specified in FIPS 203.
  * Standard library: New crypto/hkdf, crypto/pbkdf2, and
    crypto/sha3 packages: The new crypto/hkdf package implements
    the HMAC-based Extract-and-Expand key derivation function HKDF,
    as defined in RFC 5869. The new crypto/pbkdf2 package
    implements the password-based key derivation function PBKDF2,
    as defined in RFC 8018. The new crypto/sha3 package implements
    the SHA-3 hash function and SHAKE and cSHAKE extendable-output
    functions, as defined in FIPS 202. All three packages are based
    on pre-existing golang.org/x/crypto/... packages.
  * FIPS: release includes a new set of mechanisms to facilitate
    FIPS 140-3 compliance. See https://go.dev/doc/security/fips140
    The Go Cryptographic Module is a set of internal standard
    library packages that are transparently used to implement FIPS
    140-3 approved algorithms. Applications require no changes to
    use the Go Cryptographic Module for approved algorithms.
  * FIPS: The new GOFIPS140 environment variable can be used to
    select the Go Cryptographic Module version to use in a
    build. The new fips140 GODEBUG setting can be used to enable
    FIPS 140-3 mode at runtime.
  * FIPS: Go 1.24 includes Go Cryptographic Module version v1.0.0,
    which is currently under test with a CMVP-accredited
    laboratory.
  * Standard library: New experimental testing/synctest package:
    The new experimental testing/synctest package provides support
    for testing concurrent code. The synctest.Run function starts a
    group of goroutines in an isolated "bubble". Within the bubble,
    time package functions operate on a fake clock.  The
    synctest.Wait function waits for all goroutines in the current
    bubble to block. The synctest package is experimental and must
    be enabled by setting GOEXPERIMENT=synctest at build time. The
    package API is subject to change in future releases. See issue
    go#67434 for more information and to provide feeback.
  * archive: The (*Writer).AddFS implementations in both
    archive/zip and archive/tar now write a directory header for an
    empty directory.
  * bytes: The bytes package adds several functions that work with
    iterators.
  * bytes: Lines returns an iterator over the newline-terminated
    lines in a byte slice.
  * bytes: SplitSeq returns an iterator over all subslices of a
    byte slice split around a separator.
  * bytes: SplitAfterSeq returns an iterator over subslices of a
    byte slice split after each instance of a separator.
  * bytes: FieldsSeq returns an iterator over subslices of a byte
    slice split around runs of whitespace characters, as defined by
    unicode.IsSpace.
  * bytes: FieldsFuncSeq returns an iterator over subslices of a
    byte slice split around runs of Unicode code points satisfying
    a predicate.
  * crypto/aes: The value returned by NewCipher no longer
    implements the NewCTR, NewGCM, NewCBCEncrypter, and
    NewCBCDecrypter methods. These methods were undocumented and
    not available on all architectures. Instead, the Block value
    should be passed directly to the relevant crypto/cipher
    functions. For now, crypto/cipher still checks for those
    methods on Block values, even if they are not used by the
    standard library anymore.
  * crypto/aes: The Stream implementation returned by NewCTR when
    used with crypto/aes is now several times faster on amd64 and
    arm64.
  * crypto/cipher: The new NewGCMWithRandomNonce function returns
    an AEAD that implements AES-GCM by generating a random nonce
    during Seal and prepending it to the ciphertext.
  * crypto/cipher: NewOFB, NewCFBEncrypter, and NewCFBDecrypter are
    now deprecated. OFB and CFB mode are not authenticated, which
    generally enables active attacks to manipulate and recover the
    plaintext. It is recommended that applications use AEAD modes
    instead. If an unauthenticated Stream mode is required, use
    NewCTR instead.
  * crypto/ecdsa: PrivateKey.Sign now produces a deterministic
    signature according to RFC 6979 if the random source is nil.
  * crypto/md5: The value returned by md5.New now also implements
    the encoding.BinaryAppender interface.
  * crypto/rand: The Read function is now guaranteed not to
    fail. It will always return nil as the error result. If Read
    were to encounter an error while reading from Reader, the
    program will irrecoverably crash. Note that the platform APIs
    used by the default Reader are documented to always succeed, so
    this change should only affect programs that override the
    Reader variable. One exception are Linux kernels before version
    3.17, where the default Reader still opens /dev/urandom and may
    fail.
  * crypto/rand: On Linux 6.11 and later, Reader now uses the
    getrandom system call via vDSO. This is several times faster,
    especially for small reads.
  * crypto/rand: On OpenBSD, Reader now uses arc4random_buf(3).
  * crypto/rand: The new Text function can be used to generate
    cryptographically secure random text strings.
  * crypto/rsa: GenerateKey now returns an error if a key of less
    than 1024 bits is requested. All Sign, Verify, Encrypt, and
    Decrypt methods now return an error if used with a key smaller
    than 1024 bits. Such keys are insecure and should not be
    used. GODEBUG setting rsa1024min=0 restores the old behavior,
    but we recommend doing so only if necessary and only in tests,
    for example by adding a //go:debug rsa1024min=0 line to a test
    file. A new GenerateKey example provides an easy-to-use
    standard 2048-bit test key.
  * crypto/rsa: It is now safe and more efficient to call
    PrivateKey.Precompute before PrivateKey.Validate. Precompute is
    now faster in the presence of partially filled out
    PrecomputedValues, such as when unmarshaling a key from JSON.
  * crypto/rsa: The package now rejects more invalid keys, even
    when Validate is not called, and GenerateKey may return new
    errors for broken random sources. The Primes and Precomputed
    fields of PrivateKey are now used and validated even when some
    values are missing. See also the changes to crypto/x509 parsing
    and marshaling of RSA keys described below.
  * crypto/rsa: SignPKCS1v15 and VerifyPKCS1v15 now support
    SHA-512/224, SHA-512/256, and SHA-3.
  * crypto/rsa: GenerateKey now uses a slightly different method to
    generate the private exponent (Carmichael's totient instead of
    Euler's totient). Rare applications that externally regenerate
    keys from only the prime factors may produce different but
    compatible results.
  * crypto/rsa: Public and private key operations are now up to two
    times faster on wasm.
  * crypto/sha1: The value returned by sha1.New now also implements
    the encoding.BinaryAppender interface.
  * crypto/sha256: The values returned by sha256.New and
    sha256.New224 now also implement the encoding.BinaryAppender
    interface.
  * crypto/sha512: The values returned by sha512.New,
    sha512.New384, sha512.New512_224 and sha512.New512_256 now also
    implement the encoding.BinaryAppender interface.
  * crypto/subtle: The new WithDataIndependentTiming function
    allows the user to run a function with architecture specific
    features enabled which guarantee specific instructions are data
    value timing invariant. This can be used to make sure that code
    designed to run in constant time is not optimized by CPU-level
    features such that it operates in variable time. Currently,
    WithDataIndependentTiming uses the PSTATE.DIT bit on arm64, and
    is a no-op on all other architectures. GODEBUG setting
    dataindependenttiming=1 enables the DIT mode for the entire Go
    program.
  * crypto/subtle: The XORBytes output must overlap exactly or not
    at all with the inputs. Previously, the behavior was otherwise
    undefined, while now XORBytes will panic.
  * crypto/tls: The TLS server now supports Encrypted Client Hello
    (ECH). This feature can be enabled by populating the
    Config.EncryptedClientHelloKeys field.
  * crypto/tls: The new post-quantum X25519MLKEM768 key exchange
    mechanism is now supported and is enabled by default when
    Config.CurvePreferences is nil. GODEBUG setting tlsmlkem=0
    reverts the default.
  * crypto/tls: Support for the experimental X25519Kyber768Draft00
    key exchange has been removed.
  * crypto/tls: Key exchange ordering is now handled entirely by
    the crypto/tls package. The order of Config.CurvePreferences is
    now ignored, and the contents are only used to determine which
    key exchanges to enable when the field is populated.
  * crypto/tls: The new ClientHelloInfo.Extensions field lists the
    IDs of the extensions received in the Client Hello
    message. This can be useful for fingerprinting TLS clients.
  * crypto/x509: The x509sha1 GODEBUG setting has been
    removed. Certificate.Verify no longer supports SHA-1 based
    signatures.
  * crypto/x509: OID now implements the encoding.BinaryAppender and
    encoding.TextAppender interfaces.
  * crypto/x509: The default certificate policies field has changed
    from Certificate.PolicyIdentifiers to
    Certificate.Policies. When parsing certificates, both fields
    will be populated, but when creating certificates policies will
    now be taken from the Certificate.Policies field instead of the
    Certificate.PolicyIdentifiers field. This change can be
    reverted with GODEBUG setting x509usepolicies=0.
  * crypto/x509: CreateCertificate will now generate a serial
    number using a RFC 5280 compliant method when passed a template
    with a nil Certificate.SerialNumber field, instead of failing.
  * crypto/x509: Certificate.Verify now supports policy validation,
    as defined in RFC 5280 and RFC 9618. The new
    VerifyOptions.CertificatePolicies field can be set to an
    acceptable set of policy OIDs. Only certificate chains with
    valid policy graphs will be returned from Certificate.Verify.
  * crypto/x509: MarshalPKCS8PrivateKey now returns an error
    instead of marshaling an invalid RSA
    key. (MarshalPKCS1PrivateKey doesn't have an error return, and
    its behavior when provided invalid keys continues to be
    undefined.)
  * crypto/x509: ParsePKCS1PrivateKey and ParsePKCS8PrivateKey now
    use and validate the encoded CRT values, so might reject
    invalid RSA keys that were previously accepted. Use GODEBUG
    setting x509rsacrt=0 to revert to recomputing the CRT values.
  * debug/elf: The debug/elf package adds support for handling
    symbol versions in dynamic ELF (Executable and Linkable Format)
    files. The new File.DynamicVersions method returns a list of
    dynamic versions defined in the ELF file. The new
    File.DynamicVersionNeeds method returns a list of dynamic
    versions required by this ELF file that are defined in other
    ELF objects. Finally, the new Symbol.HasVersion and
    Symbol.VersionIndex fields indicate the version of a symbol.
  * encoding: Two new interfaces, TextAppender and BinaryAppender,
    have been introduced to append the textual or binary
    representation of an object to a byte slice. These interfaces
    provide the same functionality as TextMarshaler and
    BinaryMarshaler, but instead of allocating a new slice each
    time, they append the data directly to an existing slice. These
    interfaces are now implemented by standard library types that
    already implemented TextMarshaler and/or BinaryMarshaler.
  * encoding/json: When marshaling, a struct field with the new
    omitzero option in the struct field tag will be omitted if its
    value is zero. If the field type has an IsZero() bool method,
    that will be used to determine whether the value is
    zero. Otherwise, the value is zero if it is the zero value for
    its type. The omitzero field tag is clearer and less
    error-prone than omitempty when the intent is to omit zero
    values. In particular, unlike omitempty, omitzero omits
    zero-valued time.Time values, which is a common source of
    friction.
  * encoding/json: If both omitempty and omitzero are specified,
    the field will be omitted if the value is either empty or zero
    (or both).
  * encoding/json: UnmarshalTypeError.Field now includes embedded
    structs to provide more detailed error messages.
  * go/types: All go/types data structures that expose sequences
    using a pair of methods such as Len() int and At(int) T now
    also have methods that return iterators, allowing you to
    simplify code. The methods are: Interface.EmbeddedTypes,
    Interface.ExplicitMethods, Interface.Methods,
    MethodSet.Methods, Named.Methods, Scope.Children,
    Struct.Fields, Tuple.Variables, TypeList.Types,
    TypeParamList.TypeParams, Union.Terms.
  * hash/adler32: The value returned by New now also implements the
    encoding.BinaryAppender interface.
  * hash/crc32: The values returned by New and NewIEEE now also
    implement the encoding.BinaryAppender interface.
  * hash/crc64: The value returned by New now also implements the
    encoding.BinaryAppender interface.
  * hash/fnv: The values returned by New32, New32a, New64, New64a,
    New128 and New128a now also implement the
    encoding.BinaryAppender interface.
  * hash/maphash: The new Comparable and WriteComparable functions
    can compute the hash of any comparable value. These make it
    possible to hash anything that can be used as a Go map key.
  * log/slog: The new DiscardHandler is a handler that is never
    enabled and always discards its output.
  * log/slog: Level and LevelVar now implement the
    encoding.TextAppender interface.
  * math/big: Float, Int and Rat now implement the
    encoding.TextAppender interface.
  * math/rand: Calls to the deprecated top-level Seed function no
    longer have any effect. To restore the old behavior use GODEBUG
    setting randseednop=0. For more background see proposal
    go#67273.
  * math/rand/v2: ChaCha8 and PCG now implement the
    encoding.BinaryAppender interface.
  * net: ListenConfig now uses MPTCP by default on systems where it
    is supported (currently on Linux only).
  * net: IP now implements the encoding.TextAppender interface.
  * net/http: Transport's limit on 1xx informational responses
    received in response to a request has changed. It previously
    aborted a request and returned an error after receiving more
    than 5 1xx responses. It now returns an error if the total size
    of all 1xx responses exceeds the
    Transport.MaxResponseHeaderBytes configuration setting.
  * net/http: In addition, when a request has a
    net/http/httptrace.ClientTrace.Got1xxResponse trace hook, there
    is now no limit on the total number of 1xx responses. The
    Got1xxResponse hook may return an error to abort a request.
  * net/http: Transport and Server now have an HTTP2 field which
    permits configuring HTTP/2 protocol settings.
  * net/http: The new Server.Protocols and Transport.Protocols
    fields provide a simple way to configure what HTTP protocols a
    server or client use.
  * net/http: The server and client may be configured to support
    unencrypted HTTP/2 connections.
  * net/http: When Server.Protocols contains UnencryptedHTTP2, the
    server will accept HTTP/2 connections on unencrypted ports. The
    server can accept both HTTP/1 and unencrypted HTTP/2 on the
    same port.
  * net/http: When Transport.Protocols contains UnencryptedHTTP2
    and does not contain HTTP1, the transport will use unencrypted
    HTTP/2 for http:// URLs. If the transport is configured to use
    both HTTP/1 and unencrypted HTTP/2, it will use HTTP/1.
  * net/http: Unencrypted HTTP/2 support uses "HTTP/2 with Prior
    Knowledge" (RFC 9113, section 3.3). The deprecated "Upgrade:
    h2c" header is not supported.
  * net/netip: Addr, AddrPort and Prefix now implement the
    encoding.BinaryAppender and encoding.TextAppender interfaces.
  * net/url: URL now also implements the encoding.BinaryAppender
    interface.
  * os/user: On Windows, Current can now be used in Windows Nano
    Server. The implementation has been updated to avoid using
    functions from the NetApi32 library, which is not available in
    Nano Server.
  * os/user: On Windows, Current, Lookup and LookupId now support
    the following built-in service user accounts: NT
    AUTHORITY\SYSTEM, NT AUTHORITY\LOCAL SERVICE, NT
    AUTHORITY\NETWORK SERVICE
  * os/user: On Windows, Current has been made considerably faster
    when the current user is joined to a slow domain, which is the
    usual case for many corporate users. The new implementation
    performance is now in the order of milliseconds, compared to
    the previous implementation which could take several seconds,
    or even minutes, to complete.
  * os/user: On Windows, Current now returns the process owner user
    when the current thread is impersonating another
    user. Previously, it returned an error.
  * regexp: Regexp now implements the encoding.TextAppender
    interface.
  * runtime: The GOROOT function is now deprecated. In new code
    prefer to use the system path to locate the "go" binary, and
    use go env GOROOT to find its GOROOT.
  * strings: The strings package adds several functions that work
    with iterators.
  * strings: Lines returns an iterator over the newline-terminated
    lines in a string.
  * strings: SplitSeq returns an iterator over all substrings of a
    string split around a separator.
  * strings: SplitAfterSeq returns an iterator over substrings of a
    string split after each instance of a separator.
  * strings: FieldsSeq returns an iterator over substrings of a
    string split around runs of whitespace characters, as defined
    by unicode.IsSpace.
  * strings: FieldsFuncSeq returns an iterator over substrings of a
    string split around runs of Unicode code points satisfying a
    predicate.
  * sync: The implementation of sync.Map has been changed,
    improving performance, particularly for map modifications. For
    instance, modifications of disjoint sets of keys are much less
    likely to contend on larger maps, and there is no longer any
    ramp-up time required to achieve low-contention loads from the
    map. If you encounter any problems, set
    GOEXPERIMENT=nosynchashtriemap at build time to switch back to
    the old implementation and please file an issue.
  * testing: The new T.Context and B.Context methods return a
    context that's canceled after the test completes and before
    test cleanup functions run.
  * testing: The new T.Chdir and B.Chdir methods can be used to
    change the working directory for the duration of a test or
    benchmark.
  * text/template: Templates now support range-over-func and
    range-over-int.
  * time: Time now implements the encoding.BinaryAppender and
    encoding.TextAppender interfaces.
  * Linux port: As announced in the Go 1.23 release notes, Go 1.24
    requires Linux kernel version 3.2 or later.
  * Darwin port: Go 1.24 is the last release that will run on macOS
    11 Big Sur. Go 1.25 will require macOS 12 Monterey or later.
  * WebAssembly: The go:wasmexport compiler directive is added for
    Go programs to export functions to the WebAssembly host.
  * WebAssembly: On WebAssembly System Interface Preview 1
    (GOOS=wasip1 GOARCH=wasm), Go 1.24 supports building a Go
    program as a reactor/library, by specifying the
  - buildmode=c-shared build flag.
  * WebAssembly: More types are now permitted as argument or result
    types for go:wasmimport functions. Specifically, bool, string,
    uintptr, and pointers to certain types are allowed (see the
    documentation for detail), along with 32-bit and 64-bit integer
    and float types, and unsafe.Pointer, which are already
    allowed. These types are also permitted as argument or result
    types for go:wasmexport functions.
  * WebAssembly: The support files for WebAssembly have been moved
    to lib/wasm from misc/wasm.
  * Windows: The 32-bit windows/arm port (GOOS=windows GOARCH=arm)
    has been marked broken. See issue go#70705 for details.</changelog>
  <changelog author="jkowalczyk@suse.com" date="1741089600">- go1.24.1 (released 2025-03-04) includes security fixes to the
  net/http package, as well as bug fixes to cgo, the compiler, the
  go command, and the reflect, runtime, and syscall packages.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-22870
  * go#71986 go#71984 boo#1238572 security: fix CVE-2025-22870 net/http, x/net/proxy, x/net/http/httpproxy: proxy bypass using IPv6 zone IDs
  * go#71687 cmd/go: panics with GOAUTH='git dir' go get -x
  * go#71705 runtime: add linkname of runtime.lastmoduledatap for cloudwego/sonic
  * go#71728 runtime: usleep computes wrong tv_nsec on s390x
  * go#71745 crypto: add fips140 as an opaque GODEBUG setting and add documentation for it
  * go#71829 cmd/compile: fail to compile package in 1.24
  * go#71836 os: possible regression from Go 1.23 to Go 1.24 when opening DevNull with O_TRUNC
  * go#71840 runtime: recover added in range-over-func loop body doesn't stop panic propagation / segfaults printing error
  * go#71849 os: spurious SIGCHILD on running child process
  * go#71855 cmd/compile: Pow10 freeze the compiler on certain condition on Go 1.24
  * go#71858 debug/buildinfo: false positives with external scanners flag for go117 binary in testdata
  * go#71876 reflect: Value.Seq panicking on functional iterator methods
  * go#71904 cmd/compile: nil dereference when storing field of non-nil struct value
  * go#71916 reflect: Value.Seq iteration value types not matching the type of given int types
  * go#71938 cmd/compile: "fatal error: found pointer to free object" on arm64
  * go#71955 proposal: runtime: allow cleanups to run concurrently
  * go#71963 runtime/cgo: does not build with -Wdeclaration-after-statement
  * go#71977 syscall: js/wasm file operations fail on windows / node.js</changelog>
  <changelog author="jkowalczyk@suse.com" date="1741176000">- Packaging improvements:
  * SLE-12 only: Add declarations to Cgo seccomp_linux.go
    for new syscalls seccomp and getrandom which are not present
    in the kernel headers supplied by glibc version in SLE-12.
    (Marcus Meissner)
    Refs boo#1239182
  * Add patch go-fixseccomp.patch</changelog>
  <changelog author="jkowalczyk@suse.com" date="1743508800">- go1.24.2 (released 2025-04-01) includes security fixes to the
  net/http package, as well as bug fixes to the compiler, the
  runtime, the go command, and the crypto/tls, go/types, net/http,
  and testing packages.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-22871
  * go#72011 go#71988 boo#1240550 security: fix CVE-2025-22871 net/http: reject bare LF in chunked encoding
  * go#72067 cmd/compile: out of memory
  * go#72103 net/http: go1.24 breaks compatibility by modifying in-place the tls.Config{NextProtos}
  * go#72115 runtime: process hangs for mips hardware
  * go#72796 runtime: add an example for AddCleanup
  * go#72822 cmd/compile: OOM with mutually-recursive iter.Seq
  * go#72823 crypto/tls: FIPS 140-3 modes reject ECDSA w/ curve P-521/SHA-512 in TLS
  * go#72826 go/types, types2: CheckExpr / Eval may mutate type checked objects (=&gt; data race)
  * go#72872 runtime: cgo callback on extra M treated as external code after nested cgo callback returns
  * go#72934 testing: b.StopTimer breaks b.Loop
  * go#72938 internal/godebugs: winsymlink and winreadlinkvolume have incorrect defaults for Go 1.22
  * go#72974 testing: b.Loop gives bogus results in some situations</changelog>
  <changelog author="jkowalczyk@suse.com" date="1743595200">- Packaging improvements:
  * SLE-12 only: Fix conditional for go-fixsecomp.patch to work
    correctly when suse_version is undefined.
    Refs boo#1239182
  * Fix RPM warning by removing valid macro syntax in comment
    describing naming format of llvm-tsan_commit.tar.xz</changelog>
  <changelog author="mail+rpm@georg-pfuetzenreuter.net" date="1745236800">- Add gh-issue-73141.patch to repair random segmentation faults (boo#1240764)</changelog>
  <changelog author="jkowalczyk@suse.com" date="1746532800">- go1.24.3 (released 2025-05-06) includes security fixes to the os
  package, as well as bug fixes to the runtime, the compiler, the
  linker, the go command, and the crypto/tls and os packages.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-22873
  * go#73556 go#73555 boo#1242715 security: fix CVE-2025-22873 os: Root permits access to parent directory
  * go#73082 os: Root.Open panics when opening a symlink referencing the root
  * go#73092 cmd/link: linkname directive on userspace variable can override runtime variable
  * go#73118 crypto/tls: ECH decodeInnerClientHello incorrectly rejects ClientHello with GREASE values in supportedVersions
  * go#73144 runtime: segmentation fault from vgetrandomPutState and runtime.growslice w/ runtime.OSLockThread
  * go#73192 runtime: -race data race map traceback report incorrect functions
  * go#73281 cmd/compile: program compiles to wasm but is invalid: go:wasmexport: integer too large
  * go#73379 runtime, x/sys/unix: Connectx is broken on darwin/amd64
  * go#73440 cmd/compile: infinite loop in the inliner
  * go#73500 cmd/go: +dirty in version stamping doesn't combine well with +incompatible
- Packaging improvements:
  * Drop gh-issue-73141.patch to repair random segmentation faults (boo#1240764)
    fixed in upstream release.</changelog>
  <changelog author="jkowalczyk@suse.com" date="1749124800">- go1.24.4 (released 2025-06-05) includes security fixes to the
  crypto/x509, net/http, and os packages, as well as bug fixes to
  the linker, the go command, and the hash/maphash and os packages.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-22874 CVE-2025-0913 CVE-2025-4673
  * go#73700 go#73702 boo#1244158 security: fix CVE-2025-22874 crypto/x509: ExtKeyUsageAny bypasses policy validation
  * go#73720 go#73612 boo#1244157 security: fix CVE-2025-0913 os: inconsistent handling of O_CREATE|O_EXCL on Unix and Windows
  * go#73906 go#73816 boo#1244156 security: fix CVE-2025-4673 net/http: sensitive headers not cleared on cross-origin redirect
  * go#73570 os: Root.Mkdir creates directories with zero permissions on OpenBSD
  * go#73669 hash/maphash: hashing channels with purego impl. of maphash.Comparable panics
  * go#73678 runtime/debug: BuildSetting does not document DefaultGODEBUG
  * go#73809 cmd/go: add fips140 module selection mechanism
  * go#73832 cmd/link: Go 1.24.3 and 1.23.9 regression - duplicated definition of symbol dlopen</changelog>
  <changelog author="jkowalczyk@suse.com" date="1751976000">- go1.24.5 (released 2025-07-08) includes security fixes to the go
  command, as well as bug fixes to the compiler, the linker, the
  runtime, and the go command.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-4674
  * go#74381 go#74380 boo#1246118 security: fix CVE-2025-4674 cmd/go: disable support for multiple vcs in one module
  * go#73908 runtime: bad frame pointer during panic during duffcopy
  * go#74098 cmd/compile: regression on ppc64le bit operations
  * go#74113 cmd/go: crash on unknown GOEXPERIMENT during toolchain selection
  * go#74290 runtime: heap mspan limit is set too late, causing data race between span allocation and conservative scanning
  * go#74294 internal/trace: stress tests triggering suspected deadlock in tracer
  * go#74346 runtime: memlock not unlocked in all control flow paths in sysReserveAlignedSbrk
  * go#74363 runtime/pprof: crash "cannot read stack of running goroutine" in goroutine profile
  * go#74403 cmd/link: duplicated definition of symbol github.com/ebitengine/purego.syscall15XABI0 when running with ASAN</changelog>
  <changelog author="jkowalczyk@suse.com" date="1754481600">- go1.24.6 (released 2025-08-06) includes security fixes to the
  database/sql and os/exec packages, as well as bug fixes to the
  runtime.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-47906 CVE-2025-47907
  * go#74804 go#74466 boo#1247719 security: fix CVE-2025-47906 os/exec: LookPath bug: incorrect expansion of "", "." and ".." in some PATH configurations
  * go#74833 go#74831 boo#1247720 security: fix CVE-2025-47907 database/sql: incorrect results returned from Rows.Scan
  * go#73800 runtime: RSS seems to have increased in Go 1.24 while the runtime accounting has not
  * go#74416 runtime: use-after-free of allpSnapshot in findRunnable
  * go#74694 runtime: segfaults in runtime.(*unwinder).next
  * go#74760 os/user:nolibgcc: TestGroupIdsTestUser failures</changelog>
  <changelog author="jkowalczyk@suse.com" date="1755172800">- Packaging improvements:
  * Remove conditional gccgo bootstrap sections and gcc-go.patch.
    gccgo cannot be used in any version newer than go1.21. Removal
    simplifies go1.x package code.
  * go1.21 can optionally be bootstrapped with gccgo and serve as
    the inital version of go1.x.
  * go1.21 will be the initial version of Go in the bootstrap chain
    until gcc gccgo is updated to support a language level newer
    than go1.18.
  * Drop gcc-go.patch
  * Refs boo#1247816 bootstrap go1.21 with gccgo
  * Refs boo#1248082 drop unused gccgo bootstrap code in go1.22+</changelog>
  <changelog author="jkowalczyk@suse.com" date="1756900800">- go1.24.7 (released 2025-09-03) includes fixes to the go command,
  and the net and os/exec packages.
  Refs boo#1236217 go1.24 release tracking
  * go#75007 os/exec: TestLookPath fails on plan9 after CL 685755
  * go#74821 cmd/go: "get toolchain@latest" should ignore release candidates
  * go#74818 net: WriteMsgUDPAddrPort should accept IPv4-mapped IPv6 destination addresses on IPv4 UDP sockets</changelog>
  <changelog author="asarai@suse.com" date="1758283200">- Package svgpan.js to fix issues with "go tool pprof". boo#1249985</changelog>
  <changelog author="jkowalczyk@suse.com" date="1759838400">- go1.24.8 (released 2025-10-07) includes security fixes to the
  archive/tar, crypto/tls, crypto/x509, encoding/asn1,
  encoding/pem, net/http, net/mail, net/textproto, and net/url
  packages, as well as bug fixes to the compiler, the linker, and
  the debug/pe, net/http, os, and sync/atomic packages.
  Refs boo#1236217 go1.24 release tracking
  CVE-2025-58189 CVE-2025-61725 CVE-2025-58188 CVE-2025-58185 CVE-2025-58186 CVE-2025-61723 CVE-2025-58183 CVE-2025-47912 CVE-2025-58187 CVE-2025-61724
  * go#75660 go#75652 boo#1251255 security: fix CVE-2025-58189 crypto/tls: ALPN negotiation error contains attacker controlled information
  * go#75700 go#75680 boo#1251253 security: fix CVE-2025-61725 net/mail: excessive CPU consumption in ParseAddress
  * go#75702 go#75675 boo#1251260 security: fix CVE-2025-58188 crypto/x509: panic when validating certificates with DSA public keys
  * go#75704 go#75671 boo#1251258 security: fix CVE-2025-58185 encoding/asn1: pre-allocating memory when parsing DER payload can cause memory exhaustion
  * go#75706 go#75672 boo#1251259 security: fix CVE-2025-58186 net/http: lack of limit when parsing cookies can cause memory exhaustion
  * go#75708 go#75676 boo#1251256 security: fix CVE-2025-61723 encoding/pem: quadratic complexity when parsing some invalid inputs
  * go#75710 go#75677 boo#1251261 security: fix CVE-2025-58183 archive/tar: unbounded allocation when parsing GNU sparse map
  * go#75712 go#75678 boo#1251257 security: fix CVE-2025-47912 net/url: insufficient validation of bracketed IPv6 hostnames
  * go#75714 go#75681 boo#1251254 security: fix CVE-2025-58187 crypto/x509: quadratic complexity when checking name constraints
  * go#75717 go#75716 boo#1251262 security: fix CVE-2025-61724 net/textproto: excessive CPU consumption in Reader.ReadResponse
  * go#75138 os: Root.OpenRoot sets incorrect name, losing prefix of original root
  * go#75220 debug/pe: pe.Open fails on object files produced by llvm-mingw 21
  * go#75351 cmd/link: panic on riscv64 with CGO enabled due to empty container symbol
  * go#75356 net: new test TestIPv4WriteMsgUDPAddrPortTargetAddrIPVersion fails on plan9
  * go#75359 os: new test TestOpenFileCreateExclDanglingSymlink fails on Plan 9
  * go#75523 crypto/internal/fips140/rsa: requires a panic if self-tests fail
  * go#75538 net/http: internal error: connCount underflow
  * go#75594 cmd/compile: internal compiler error with GOEXPERIMENT=cgocheck2 on github.com/leodido/go-urn
  * go#75609 sync/atomic: comment for Uintptr.Or incorrectly describes return value</changelog>
  <changelog author="jkowalczyk@suse.com" date="1760356800">- go1.24.9 (released 2025-10-13) includes fixes to the crypto/x509
  package.
  Refs boo#1236217 go1.24 release tracking
  * go#75860 crypto/x509: TLS validation fails for FQDNs with trailing dot
- Packaging improvements:
  * Add net-url-allow-IP-literals-with-IPv4-mapped-IPv6-addresses.patch
    needed today and will be available in the next upstream release</changelog>
  <changelog author="jkowalczyk@suse.com" date="1762344000">- go1.24.10 (released 2025-11-05) includes fixes to the
  encoding/pem and net/url packages.
  Refs boo#1236217 go1.24 release tracking
  * go#75831 net/url: ipv4 mapped ipv6 addresses should be valid in square brackets
  * go#75951 encoding/pem: regression when decoding blocks with leading garbage
  * go#76028 pem/encoding: malformed line endings can cause panics
- Packaging improvements:
  * Remove net-url-allow-IP-literals-with-IPv4-mapped-IPv6-addresses.patch
    No longer needed with go#75831 in latest upstream release</changelog>
</package>
<package pkgid="03d8fb8bebe12cffd7810fc30bdda2d03baaf6022bad652fe3fe535fc5211e86" name="opentofu" arch="src">
  <version epoch="0" ver="1.10.7" rel="150700.1.2"/>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1722254400">- Update to version 1.8.0:
  * What's New?
  - Early variable/locals evaluation
  - Provider mocking in tofu test
  - Resource overrides in tofu test
  - Override files for OpenTofu: keeping compatibility
  - Deprecation: use_legacy_workflow has been removed from the S3
    backend-backend
  See the launch post on our blog:
  https://opentofu.org/blog/opentofu-1-8-0/
  For all the features, see the detailed changelog:
  https://github.com/opentofu/opentofu/blob/v1.8.0/CHANGELOG.md
  You can find the full diff here:
  https://github.com/opentofu/opentofu/compare/v1.7..v1.8.0</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1723032000">- Update to version 1.8.1:
  * Bump to 1.8.1 (#1893)
  * Fix missing module source panic (#1888) (#1889)
  * Backport/v1.8/1876 (#1886)
  * 1666/tacos website docs backport to 1.8 (#1883)
  * Fix 1.8 release workers (#1870)
  * Switch to alternate runner group (#1868)
  * Run releases on larger workers. (#1587) (#1867)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1725969600">- Update to version 1.8.2:
  * Update version and changelog to 1.8.2 (#1968)
  * Backport bump go version to v1.8 (#1966)
  * Better handling of key_provider references (#1921) (#1965)
  * fix inconsistent sidebar title of functions on v1.8 branch
    (#1907)
  * Fix Docusaurus "broken link" warnings on 1.8 branch of docs
    (#1884) (#1898)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1728043200">- Update to version 1.8.3:
  * Backport 1.8 handle static variable secrets (#2046)
  * Make sure test vars are only processed during test commands
    (#2040)
  * Fix Terraform Version in 1.8.x Migration Guide (#1987) (#2000)
  * Update docs version message (#1990) (#1997)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1729771200">- Update to version 1.8.4:
  * Bumped versionfile for 1.8 (#2097)
  * Backport recent changes to v1.8 (#2093)
  * CHANGELOG entry for #2055 and #2060
  * command/init: Support static eval for backend config migration
    check</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1731412800">- Update to version 1.8.5:
  * Prepare for the v1.8.6 release (#2137)
  * v1.8 Backport: Fix regression of backend reinit detection when
    backend schema has required arguments (#2135)
  * Partially unknown provider functions arguments fixed (#2127)
    (#2133)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1732276800">- Update to version 1.8.6:
  * update 1.8 versions (#2211)
  * fix changelog for 1.8.6 (#2207)
  * [BACKPORT] add missing changelog entry for http backend logging
    (#2206) (#2209)
  * Bump golang version to 1.22.8 (address CVE-2024-34156) (#2050)
    (#2182)
  * [BACKPORT] fix mock type conversion in tofu test (#2144)
    (#2197)
  * [BACKPORT] fix mock provider validation (#2140) (#2196)
  * [BACKPORT] Add DEBUG-level logging to the "http" state storage
    backend (#2120) (#2192)
  * [BACKPORT] pin node version for docusaurus build (#2177)
    (#2194)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1733486400">- Update to version 1.8.7:
  * BUG FIXES:
  - Error messages related to validation of sensitive input
    variables will no longer disclose the sensitive value in the
    UI. (#2219)
  - Changes to encryption configuration now auto-apply the
    migration (#2232)
  - Updated github.com/golang-jwt/jwt/v4 from 4.4.2 to 4.5.1 to
    make security scanners happy (no vulnerability, see #2179)
  - tofu test is now setting nulls for dynamic type when
    generating mock values. (#2245)
  - Variables declared in test files are now taking into account
    type default values. (#2244)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1735300800">- Update to version 1.8.8:
  * prepare branch for v1.8.8 release (#2314)
  * [BACKPORT v1.8] bump golang.org/x/net from 0.25 to 0.33 (#2311)
    (#2313)
  * Backport[v1.8]: Bump golang.org/x/crypto from 0.21.0 to 0.31.0
    (#2288)
  * [BACKPORT] add simulated state serialization between tofu test
    runs (#2274) (#2276)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1736510400">- Update to version 1.9.0:
  We're proud to announce that OpenTofu 1.9.0 is now officially
  out! This release includes a lot of major and minor new features,
  as well as a ton of community contributions!
  The highlights are:
  * for_each in provider configuration blocks: An alternate (aka
    "aliased") provider configuration can now have multiple
    dynamically-chosen instances using the for_each argument:
    provider "aws" {
    alias    = "by_region"
    for_each = var.aws_regions
    region = each.key
    }
    Each instance of a resource can also potentially select a
    different instance of the associated provider configuration,
    making it easier to declare infrastructure that ought to be
    duplicated for each region.
  * -exclude planning option: similar to -target, this allows
    operators to tell OpenTofu to work on only a subset of the
    objects declared in the configuration or tracked in the state.
    tofu plan -exclude=kubernetes_manifest.crds
    While -target specifies the objects to include and skips
    everything not needed for the selected objects, -exclude
    instead specifies objects to skip. OpenTofu will exclude the
    selected objects and everything that depends on them.
  Please take the above for a spin and let us know your feedback!
  For all the features, see the detailed changelog.
  https://github.com/opentofu/opentofu/blob/v1.9.0/CHANGELOG.md</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1745582400">- Update to version 1.9.1:
  * BUG FIXES:
  - Provider used in import is correctly identified. (#2336)
  - plantimestamp() now returns unknown value during validation
    (#2397)
  - Syntax error in the required_providers block does not panic
    anymore, but yields "syntax error" (2344)
  - Fix the error message when default value of a complex
    variable is containing a wrong type (2394)
  - Changing Go version to 1.22.11 in order to fix CVE-2024-45336
    and CVE-2024-45341 (#2438)
  - Fix the way OpenTofu downloads a module that is sourced from
    a GitHub branch containing slashes in the name. (2396)
  - Changing Go version to 1.22.12 in order to fix CVE-2025-22866
    and CVE-2024-45341 (#2438)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1750852800">- Update to version 1.10.0:
  We're thrilled to announce the release of OpenTofu 1.10.0, our
  most comprehensive update yet! This release represents months of
  dedicated work from our community, introducing some fantastic
  features that will improve how OpenTofu users manage and
  distribute infrastructure as code.
  Full changelog:
  https://github.com/opentofu/opentofu/blob/v1.10/CHANGELOG.md
  * Highlights
    This release cycle introduces major new capabilities and
    integrations:
  - OCI Registry Support
    Full integration with OCI registries for both provider and
    module distribution, valuable for organizations with private
    infrastructure-as-code components, air-gapped environments,
    or enhanced security requirements.
    For more information, refer to Module Packages in OCI
    Registries and Provider Mirrors in OCI Registries.
    https://opentofu.org/docs/cli/oci_registries/module-package/
    https://opentofu.org/docs/cli/oci_registries/provider-mirror/
  - Native S3 Locking
    Simplify your infrastructure by using S3's conditional writes
    capability for state locking, eliminating the need for a
    separate DynamoDB table.
  - OpenTelemetry Tracing
    Gain insights into OpenTofu operations with experimental
    OpenTelemetry tracing, completely local and under your
    control.
  - Resource Management with Target Files
    Manage complex deployments more easily with the new
  - target-file and -exclude-file options, allowing
    version-controlled resource targeting patterns.
    Code examples can be found here:
    https://github.com/opentofu/opentofu/releases/tag/v1.10.0
  * Compatibility Notes
  - Linux: Requires kernel version 3.2 or later
  - macOS: Requires macOS 11 Big Sur or later
  - The ghcr.io/opentofu/opentofu image is no longer supported as
    a base image
  - Windows: Symbolic links and junctions are now handled
    differently
  - The PostgreSQL backend in OpenTofu 1.10 should not be used
    alongside older versions</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1751284800">- Update to version 1.10.1:
  * BUG FIXES:
  - Fix TF_APPEND_USER_AGENT handling in the S3 remote state
    backend. (#2955)
  * OTHER CHANGES:
  - OpenTofu is now built with Go 1.24.4, which should clear some
    false-positive indirect security advisories.</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1751457600">- Update to version 1.10.2:
  * S3 backend now correctly sends the x-amz-server-side-encryption
    header for the lockfile. (#2870)
  * A provider source address explicitly using the hostname
    registry.terraform.io will no longer cause errors related to a
    corresponding provider on registry.opentofu.org when executing
    workflow commands like plan and apply. (#2979)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1752321600">- BuildRequire go1.24 &gt;= 1.24.4 to not use go1.25rc2</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1752667200">- Update to version 1.10.3:
  * BUG FIXES:
  - OpenTofu will no longer crash in a rare case where a
    dynamically-invalid expression has its error suppressed by
    try or can and then that expression becomes relevant for
    deciding whether to report a "change outside of OpenTofu" in
    the human-oriented plan diff. (#2988)
  - Ensure provider downloads into temp are cleaned up correctly
    on windows. (#2843)
  - Correctly handle structural typed attributes during test
    provider mocking. (#2994)
  - Fix erroneous detection of changes with sensitive resource
    attributes. (#3024)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1754049600">- Update to version 1.10.4:
  * BUG FIXES:
  - Fixed crash where sensitive set values used in for_each could
    cause a panic. (#3070)
  - Fixed incorrect approach to mocking provider "ReadResource"
    calls in test. (#3068)
  - Reduced calls to ListKeys in azure backend (for rate
    limiting). (#3083)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1754222400">- Update to version 1.10.5:
  * BUG FIXES:
  - Fixed issue where usage of TF_PLUGIN_CACHE_DIR could result
    in unexpected lock contention errors (#3090)
    NOTE: It is still highly recommended to have valid
    .terraform.lock.hcl files in projects using
    TF_PLUGIN_CACHE_DIR</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1758196800">- Update to version 1.10.6:
  * UPGRADE NOTES:
  - Upgrade go from 1.24.4 to 1.24.6 to fix GO-2025-3849 (3127)
  - Upgrade github.com/openbao/openbao/api/v2 from 2.1.0 to 2.3.0
    to fix GO-2025-3783 (3134)
  - The upgrade is necessary to silence the security scanner
    and does not affect the actual state encryption provided by
    OpenBao.
  * BUG FIXES:
  - Variables with validation no longer interfere with the
    destroy process (#3131)
  - Fixed crash when processing multiple deprecated marks on a
    complex object (#3105)
  - When OpenTelemetry encounters errors, log it at the warning
    level instead of panic (#3235)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1762430400">- Update to version 1.10.7:
  * SECURITY ADVISORIES:
    This release contains fixes for some security advisories
    related to previous releases in this series.
  - tofu init in OpenTofu v1.10.6 and earlier could potentially
    use unbounded memory if there is a direct or indirect
    dependency on a maliciously-crafted module package
    distributed as a "tar" archive.
    This would require the attacker to coerce a root module
    author to depend (directly or indirectly) on a module package
    they control, using the HTTP, Amazon S3, or Google Cloud
    Storage source types to refer to a tar archive.
    This release incorporates the upstream fixes for
    CVE-2025-58183.
  - When making requests to HTTPS servers, OpenTofu v1.10.6 and
    earlier could potentially use unbounded memory or crash with
    a "panic" error if TLS verification involves an
    excessively-long certificate chain or a chain including DSA
    public keys.
    This affected all outgoing HTTPS requests made by OpenTofu
    itself, including requests to HTTPS-based state storage
    backends, module registries, and provider registries. For
    example, an attacker could coerce a root module author to
    depend (directly or indirectly) on a module they control
    which then refers to a module or provider from an
    attacker-controlled registry. That mode of attack would cause
    failures in tofu init, at module or provider installation
    time.
    Provider plugins contain their own HTTPS client code, which
    may have similar problems. OpenTofu v1.10.7 cannot address
    similar problems within provider plugins, and so we recommend
    checking for similar advisories and fixes in the provider
    plugins you use.
    This release incorporates upstream fixes for CVE-2025-58185,
    CVE-2025-58187, and CVE-2025-58188.
  * BUG FIXES:
  - Fix crash in tofu test when using deprecated outputs (#3249)
  - Fix missing provider functions when parentheses are used
    (#3402)
  - for_each inside dynamic blocks can now call provider-defined
    functions. (#3429)</changelog>
</package>
<package pkgid="8396e8a4ae597bde01731fb35d172da2711a26dd7ff893b4d21e3dc09aca3a73" name="opentofu" arch="x86_64">
  <version epoch="0" ver="1.10.7" rel="150700.1.2"/>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1722254400">- Update to version 1.8.0:
  * What's New?
  - Early variable/locals evaluation
  - Provider mocking in tofu test
  - Resource overrides in tofu test
  - Override files for OpenTofu: keeping compatibility
  - Deprecation: use_legacy_workflow has been removed from the S3
    backend-backend
  See the launch post on our blog:
  https://opentofu.org/blog/opentofu-1-8-0/
  For all the features, see the detailed changelog:
  https://github.com/opentofu/opentofu/blob/v1.8.0/CHANGELOG.md
  You can find the full diff here:
  https://github.com/opentofu/opentofu/compare/v1.7..v1.8.0</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1723032000">- Update to version 1.8.1:
  * Bump to 1.8.1 (#1893)
  * Fix missing module source panic (#1888) (#1889)
  * Backport/v1.8/1876 (#1886)
  * 1666/tacos website docs backport to 1.8 (#1883)
  * Fix 1.8 release workers (#1870)
  * Switch to alternate runner group (#1868)
  * Run releases on larger workers. (#1587) (#1867)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1725969600">- Update to version 1.8.2:
  * Update version and changelog to 1.8.2 (#1968)
  * Backport bump go version to v1.8 (#1966)
  * Better handling of key_provider references (#1921) (#1965)
  * fix inconsistent sidebar title of functions on v1.8 branch
    (#1907)
  * Fix Docusaurus "broken link" warnings on 1.8 branch of docs
    (#1884) (#1898)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1728043200">- Update to version 1.8.3:
  * Backport 1.8 handle static variable secrets (#2046)
  * Make sure test vars are only processed during test commands
    (#2040)
  * Fix Terraform Version in 1.8.x Migration Guide (#1987) (#2000)
  * Update docs version message (#1990) (#1997)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1729771200">- Update to version 1.8.4:
  * Bumped versionfile for 1.8 (#2097)
  * Backport recent changes to v1.8 (#2093)
  * CHANGELOG entry for #2055 and #2060
  * command/init: Support static eval for backend config migration
    check</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1731412800">- Update to version 1.8.5:
  * Prepare for the v1.8.6 release (#2137)
  * v1.8 Backport: Fix regression of backend reinit detection when
    backend schema has required arguments (#2135)
  * Partially unknown provider functions arguments fixed (#2127)
    (#2133)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1732276800">- Update to version 1.8.6:
  * update 1.8 versions (#2211)
  * fix changelog for 1.8.6 (#2207)
  * [BACKPORT] add missing changelog entry for http backend logging
    (#2206) (#2209)
  * Bump golang version to 1.22.8 (address CVE-2024-34156) (#2050)
    (#2182)
  * [BACKPORT] fix mock type conversion in tofu test (#2144)
    (#2197)
  * [BACKPORT] fix mock provider validation (#2140) (#2196)
  * [BACKPORT] Add DEBUG-level logging to the "http" state storage
    backend (#2120) (#2192)
  * [BACKPORT] pin node version for docusaurus build (#2177)
    (#2194)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1733486400">- Update to version 1.8.7:
  * BUG FIXES:
  - Error messages related to validation of sensitive input
    variables will no longer disclose the sensitive value in the
    UI. (#2219)
  - Changes to encryption configuration now auto-apply the
    migration (#2232)
  - Updated github.com/golang-jwt/jwt/v4 from 4.4.2 to 4.5.1 to
    make security scanners happy (no vulnerability, see #2179)
  - tofu test is now setting nulls for dynamic type when
    generating mock values. (#2245)
  - Variables declared in test files are now taking into account
    type default values. (#2244)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1735300800">- Update to version 1.8.8:
  * prepare branch for v1.8.8 release (#2314)
  * [BACKPORT v1.8] bump golang.org/x/net from 0.25 to 0.33 (#2311)
    (#2313)
  * Backport[v1.8]: Bump golang.org/x/crypto from 0.21.0 to 0.31.0
    (#2288)
  * [BACKPORT] add simulated state serialization between tofu test
    runs (#2274) (#2276)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1736510400">- Update to version 1.9.0:
  We're proud to announce that OpenTofu 1.9.0 is now officially
  out! This release includes a lot of major and minor new features,
  as well as a ton of community contributions!
  The highlights are:
  * for_each in provider configuration blocks: An alternate (aka
    "aliased") provider configuration can now have multiple
    dynamically-chosen instances using the for_each argument:
    provider "aws" {
    alias    = "by_region"
    for_each = var.aws_regions
    region = each.key
    }
    Each instance of a resource can also potentially select a
    different instance of the associated provider configuration,
    making it easier to declare infrastructure that ought to be
    duplicated for each region.
  * -exclude planning option: similar to -target, this allows
    operators to tell OpenTofu to work on only a subset of the
    objects declared in the configuration or tracked in the state.
    tofu plan -exclude=kubernetes_manifest.crds
    While -target specifies the objects to include and skips
    everything not needed for the selected objects, -exclude
    instead specifies objects to skip. OpenTofu will exclude the
    selected objects and everything that depends on them.
  Please take the above for a spin and let us know your feedback!
  For all the features, see the detailed changelog.
  https://github.com/opentofu/opentofu/blob/v1.9.0/CHANGELOG.md</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1745582400">- Update to version 1.9.1:
  * BUG FIXES:
  - Provider used in import is correctly identified. (#2336)
  - plantimestamp() now returns unknown value during validation
    (#2397)
  - Syntax error in the required_providers block does not panic
    anymore, but yields "syntax error" (2344)
  - Fix the error message when default value of a complex
    variable is containing a wrong type (2394)
  - Changing Go version to 1.22.11 in order to fix CVE-2024-45336
    and CVE-2024-45341 (#2438)
  - Fix the way OpenTofu downloads a module that is sourced from
    a GitHub branch containing slashes in the name. (2396)
  - Changing Go version to 1.22.12 in order to fix CVE-2025-22866
    and CVE-2024-45341 (#2438)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1750852800">- Update to version 1.10.0:
  We're thrilled to announce the release of OpenTofu 1.10.0, our
  most comprehensive update yet! This release represents months of
  dedicated work from our community, introducing some fantastic
  features that will improve how OpenTofu users manage and
  distribute infrastructure as code.
  Full changelog:
  https://github.com/opentofu/opentofu/blob/v1.10/CHANGELOG.md
  * Highlights
    This release cycle introduces major new capabilities and
    integrations:
  - OCI Registry Support
    Full integration with OCI registries for both provider and
    module distribution, valuable for organizations with private
    infrastructure-as-code components, air-gapped environments,
    or enhanced security requirements.
    For more information, refer to Module Packages in OCI
    Registries and Provider Mirrors in OCI Registries.
    https://opentofu.org/docs/cli/oci_registries/module-package/
    https://opentofu.org/docs/cli/oci_registries/provider-mirror/
  - Native S3 Locking
    Simplify your infrastructure by using S3's conditional writes
    capability for state locking, eliminating the need for a
    separate DynamoDB table.
  - OpenTelemetry Tracing
    Gain insights into OpenTofu operations with experimental
    OpenTelemetry tracing, completely local and under your
    control.
  - Resource Management with Target Files
    Manage complex deployments more easily with the new
  - target-file and -exclude-file options, allowing
    version-controlled resource targeting patterns.
    Code examples can be found here:
    https://github.com/opentofu/opentofu/releases/tag/v1.10.0
  * Compatibility Notes
  - Linux: Requires kernel version 3.2 or later
  - macOS: Requires macOS 11 Big Sur or later
  - The ghcr.io/opentofu/opentofu image is no longer supported as
    a base image
  - Windows: Symbolic links and junctions are now handled
    differently
  - The PostgreSQL backend in OpenTofu 1.10 should not be used
    alongside older versions</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1751284800">- Update to version 1.10.1:
  * BUG FIXES:
  - Fix TF_APPEND_USER_AGENT handling in the S3 remote state
    backend. (#2955)
  * OTHER CHANGES:
  - OpenTofu is now built with Go 1.24.4, which should clear some
    false-positive indirect security advisories.</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1751457600">- Update to version 1.10.2:
  * S3 backend now correctly sends the x-amz-server-side-encryption
    header for the lockfile. (#2870)
  * A provider source address explicitly using the hostname
    registry.terraform.io will no longer cause errors related to a
    corresponding provider on registry.opentofu.org when executing
    workflow commands like plan and apply. (#2979)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1752321600">- BuildRequire go1.24 &gt;= 1.24.4 to not use go1.25rc2</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1752667200">- Update to version 1.10.3:
  * BUG FIXES:
  - OpenTofu will no longer crash in a rare case where a
    dynamically-invalid expression has its error suppressed by
    try or can and then that expression becomes relevant for
    deciding whether to report a "change outside of OpenTofu" in
    the human-oriented plan diff. (#2988)
  - Ensure provider downloads into temp are cleaned up correctly
    on windows. (#2843)
  - Correctly handle structural typed attributes during test
    provider mocking. (#2994)
  - Fix erroneous detection of changes with sensitive resource
    attributes. (#3024)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1754049600">- Update to version 1.10.4:
  * BUG FIXES:
  - Fixed crash where sensitive set values used in for_each could
    cause a panic. (#3070)
  - Fixed incorrect approach to mocking provider "ReadResource"
    calls in test. (#3068)
  - Reduced calls to ListKeys in azure backend (for rate
    limiting). (#3083)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1754222400">- Update to version 1.10.5:
  * BUG FIXES:
  - Fixed issue where usage of TF_PLUGIN_CACHE_DIR could result
    in unexpected lock contention errors (#3090)
    NOTE: It is still highly recommended to have valid
    .terraform.lock.hcl files in projects using
    TF_PLUGIN_CACHE_DIR</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1758196800">- Update to version 1.10.6:
  * UPGRADE NOTES:
  - Upgrade go from 1.24.4 to 1.24.6 to fix GO-2025-3849 (3127)
  - Upgrade github.com/openbao/openbao/api/v2 from 2.1.0 to 2.3.0
    to fix GO-2025-3783 (3134)
  - The upgrade is necessary to silence the security scanner
    and does not affect the actual state encryption provided by
    OpenBao.
  * BUG FIXES:
  - Variables with validation no longer interfere with the
    destroy process (#3131)
  - Fixed crash when processing multiple deprecated marks on a
    complex object (#3105)
  - When OpenTelemetry encounters errors, log it at the warning
    level instead of panic (#3235)</changelog>
  <changelog author="opensuse_buildservice@ojkastl.de" date="1762430400">- Update to version 1.10.7:
  * SECURITY ADVISORIES:
    This release contains fixes for some security advisories
    related to previous releases in this series.
  - tofu init in OpenTofu v1.10.6 and earlier could potentially
    use unbounded memory if there is a direct or indirect
    dependency on a maliciously-crafted module package
    distributed as a "tar" archive.
    This would require the attacker to coerce a root module
    author to depend (directly or indirectly) on a module package
    they control, using the HTTP, Amazon S3, or Google Cloud
    Storage source types to refer to a tar archive.
    This release incorporates the upstream fixes for
    CVE-2025-58183.
  - When making requests to HTTPS servers, OpenTofu v1.10.6 and
    earlier could potentially use unbounded memory or crash with
    a "panic" error if TLS verification involves an
    excessively-long certificate chain or a chain including DSA
    public keys.
    This affected all outgoing HTTPS requests made by OpenTofu
    itself, including requests to HTTPS-based state storage
    backends, module registries, and provider registries. For
    example, an attacker could coerce a root module author to
    depend (directly or indirectly) on a module they control
    which then refers to a module or provider from an
    attacker-controlled registry. That mode of attack would cause
    failures in tofu init, at module or provider installation
    time.
    Provider plugins contain their own HTTPS client code, which
    may have similar problems. OpenTofu v1.10.7 cannot address
    similar problems within provider plugins, and so we recommend
    checking for similar advisories and fixes in the provider
    plugins you use.
    This release incorporates upstream fixes for CVE-2025-58185,
    CVE-2025-58187, and CVE-2025-58188.
  * BUG FIXES:
  - Fix crash in tofu test when using deprecated outputs (#3249)
  - Fix missing provider functions when parentheses are used
    (#3402)
  - for_each inside dynamic blocks can now call provider-defined
    functions. (#3429)</changelog>
</package>
<package pkgid="16166d67fcea6a973ac9e1d293fc337e6604868d54cca2ee00662b7cfa09b6cc" name="terraform" arch="src">
  <version epoch="0" ver="1.0.10" rel="150700.94.14"/>
  <changelog author="thipp@suse.de" date="1505736000">- Update to v0.10.5:
  - NEW FEATURES:
  * config: indent interpolation function appends spaces to all but the first
    line of a multi-line string (#15311)
  - IMPROVEMENTS:
  * cli: terraform fmt has a new option -check which makes it return a
    non-zero exit status if any formatting changes are required (#15387)
  * cli: When running Terraform in automation, a new environment variable
    TF_IN_AUTOMATION can be used to disable or adjust certain prompts that
    would normally include specific CLI commands to run. This assumes that
    the wrapping automation tool is providing its own UI for guiding the user
    through the workflow, and thus the standard advice would be redundant
    and/or confusing. (#16059)
  - BUG FIXES:
  * cli: restore the "(forces new resource)" annotations on attributes that
    were inadvertently disabled in 0.10.4. (#16067)
  * cli: fix regression with installing modules from git when the
    GIT_SSH_COMMAND environment variable is set (#16099)</changelog>
  <changelog author="thipp@suse.de" date="1505822400">- Update to v0.10.6:
  - UPGRADE NOTES:
  * The internal storage of modules has changed in this release, so after
    upgrading terraform init must be run to re-install modules in the new
    on-disk format. The existing installed versions of modules will be
    ignored, so the latest version of each module will be installed.
  - IMPROVEMENTS:
  * cli: terraform import now accepts an option -allow-missing-config that
    overrides the default requirement that a configuration block must already
    be present for the resource being imported. (#15876)</changelog>
  <changelog author="thipp@suse.de" date="1507118400">- Update to v0.10.7:
  - NEW FEATURES:
  * Provider plugins can now optionally be cached in a shared directory to
    avoid re-downloading them for each configuration working directory. For
    more information, see the documentation. (#16000)
  - IMPROVEMENTS:
  * config: New abs interpolation function, returning the absolute value of a
    number (#16168)
  * config: New transpose interpolation function, which swaps the keys and
    values in a map of lists of strings. (#16192)
  * cli: The Terraform CLI now supports tab-completion for commands and
    certain arguments for bash and zsh users. See the tab-completion docs for
    information on how to enable it. (#16176)
  * cli: terraform state rm now includes in its output the count of resources
    that were removed from the state. (#16137)
  - BUG FIXES:
  * modules: Update go-getter to fix crash when fetching invalid source
    subdir (#16161)
  * modules: Fix regression in the handling of modules sourcing other modules
    with relative paths (#16160)
  * core: Skip local value interpolation during destroy (#16213)</changelog>
  <changelog author="tbechtold@suse.com" date="1507291200">- Add terraform-rpmlintrc as Source99</changelog>
  <changelog author="fcastelli@suse.com" date="1518868800">- Update to v0.11.3:
  * IMPROVEMENTS:
  * backend/s3: add support for the eu-west-3 region ([#17193](https://github.com/hashicorp/terraform/issues/17193))
  * BUG FIXES:
  * core: fix crash when an error is encountered during refresh ([#17076](https://github.com/hashicorp/terraform/issues/17076))
  * config: fixed crash when module source is invalid ([#17134](https://github.com/hashicorp/terraform/issues/17134))
  * config: allow the count pseudo-attribute of a resource to be interpolated into `provisioner` and `connection` blocks without errors ([#17133](https://github.com/hashicorp/terraform/issues/17133))
  * backend/s3: allow the workspace name to be a prefix of workspace_key_prefix ([#17086](https://github.com/hashicorp/terraform/issues/17086))
  * provisioner/chef: fix crash when validating `use_policyfile` ([#17147](https://github.com/hashicorp/terraform/issues/17147))
- Changes of version 0.11.2:
  * BACKWARDS INCOMPATIBILITIES / NOTES:
  * backend/gcs: The gcs remote state backend was erroneously creating the state bucket if it didn't exist. This is not the intended behavior of backends, as Terraform cannot track or manage that resource. The target bucket must now be created separately, before using it with Terraform. ([#16865](https://github.com/hashicorp/terraform/issues/16865))
  * NEW FEATURES:
  * **[Habitat](https://www.habitat.sh/) Provisioner** allowing automatic installation of the Habitat agent ([#16280](https://github.com/hashicorp/terraform/issues/16280))
  * IMPROVEMENTS:
  * core: removed duplicate prompts and clarified working when migration backend configurations ([#16939](https://github.com/hashicorp/terraform/issues/16939))
  * config: new `rsadecrypt` interpolation function allows decrypting a base64-encoded ciphertext using a given private key. This is particularly useful for decrypting the password for a Windows instance on AWS EC2, but is generic and may find other uses too. ([#16647](https://github.com/hashicorp/terraform/issues/16647))
  * config: new `timeadd` interpolation function allows calculating a new timestamp relative to an existing known timestamp. ([#16644](https://github.com/hashicorp/terraform/issues/16644))
  * cli: Passing an empty string to `-plugin-dir` during init will remove previously saved paths ([#16969](https://github.com/hashicorp/terraform/issues/16969))
  * cli: Module and provider installation (and some other Terraform features) now implement [RFC6555](https://tools.ietf.org/html/rfc6555) when making outgoing HTTP requests, which should improve installation reliability for dual-stack (both IPv4 and IPv6) hosts running on networks that have non-performant or broken IPv6 Internet connectivity by trying both IPv4 and IPv6 connections. ([#16805](https://github.com/hashicorp/terraform/issues/16805))
  * backend/s3: it is now possible to disable the region check, for improved compatibility with third-party services that attempt to mimic the S3 API. ([#16757](https://github.com/hashicorp/terraform/issues/16757))
  * backend/s3: it is now possible to for the path-based S3 API form, for improved compatibility with third-party services that attempt to mimic the S3 API. ([#17001](https://github.com/hashicorp/terraform/issues/17001))
  * backend/s3: it is now possible to use named credentials from the `~/.aws/credentials` file, similarly to the AWS plugin ([#16661](https://github.com/hashicorp/terraform/issues/16661))
  * backend/manta: support for Triton RBAC ([#17003](https://github.com/hashicorp/terraform/issues/17003))
  * backend/gcs: support for customer-supplied encryption keys for remote state buckets ([#16936](https://github.com/hashicorp/terraform/issues/16936))
  * provider/terraform: in `terraform_remote_state`, the argument `environment` is now deprecated in favor of `workspace`. The `environment` argument will be removed in a later Terraform release. ([#16558](https://github.com/hashicorp/terraform/issues/16558))
  * BUG FIXES:
  * config: fixed crash in `substr` interpolation function with invalid offset ([#17043](https://github.com/hashicorp/terraform/issues/17043))
  * config: Referencing a count attribute in an output no longer generates a warning ([#16866](https://github.com/hashicorp/terraform/issues/16866))
  * cli: Terraform will no longer crash when `terraform plan`, `terraform apply`, and some other commands encounter an invalid provider version constraint in configuration, generating a proper error message instead. ([#16867](https://github.com/hashicorp/terraform/issues/16867))
  * backend/gcs: The usage of the GOOGLE_CREDENTIALS environment variable now matches that of the google provider ([#16865](https://github.com/hashicorp/terraform/issues/16865))
  * backend/gcs: fixed the locking methodology to avoid "double-locking" issues when used with the `terraform_remote_state` data source ([#16852](https://github.com/hashicorp/terraform/issues/16852))
  * backend/s3: the `workspace_key_prefix` can now be an empty string or contain slashes ([#16932](https://github.com/hashicorp/terraform/issues/16932))
  * provisioner/salt-masterless: now waits for all of the remote operations to complete before returning ([#16704](https://github.com/hashicorp/terraform/issues/16704))
- Changes of version 0.11.1
  * IMPROVEMENTS:
  * modules: Modules can now receive a specific provider configuration in the `providers` map, even if it's only implicitly used ([#16619](https://github.com/hashicorp/terraform/issues/16619))
  * config: Terraform will now detect and warn about outputs containing potentially-problematic references to resources with `count` set where the references does not use the "splat" syntax. This identifies situations where an output may [reference a resource with `count = 0`](https://www.terraform.io/upgrade-guides/0-11.html#referencing-attributes-from-resources-with-count-0) even if the `count` expression does not _currently_ evaluate to `0`, allowing the bug to be detected and fixed _before_ the value is later changed to `0` and would thus become an error. **This usage will become a fatal error in Terraform 0.12**. ([#16735](https://github.com/hashicorp/terraform/issues/16735))
  * core: A new environment variable `TF_WARN_OUTPUT_ERRORS=1` is supported to opt out of the behavior introduced in 0.11.0 where errors in output expressions halt execution. This restores the previous behavior where such errors are ignored, allowing users to apply problematic configurations without fixing all of the errors. This opt-out will be removed in Terraform 0.12, so it is strongly recommended to use the new warning described in the previous item to detect and fix these problematic expressions. ([#16782](https://github.com/hashicorp/terraform/issues/16782))
  * BUG FIXES:
  * cli: fix crash when subcommands with sub-subcommands are accidentally provided as a single argument, such as `terraform "workspace list"` ([#16789](https://github.com/hashicorp/terraform/issues/16789))
- Changes of version 0.11.0
  * BACKWARDS INCOMPATIBILITIES / NOTES:
    The following items give an overview of the incompatibilities and other noteworthy changes in this release. For more details on some of these changes, along with information on how to upgrade existing configurations where needed, see [the v0.11 upgrade guide](https://www.terraform.io/upgrade-guides/0-11.html).
  * Output interpolation errors are now fatal. Module configs with unused outputs which contained errors will no longer be valid.
  * Module configuration blocks have 2 new reserved attribute names, "providers" and "version". Modules using these as input variables will need to be updated.
  * The module provider inheritance rules have changed. Inherited provider configurations will no longer be merged with local configurations, and additional (aliased) provider configurations must be explicitly passed between modules when shared. See [the upgrade guide](https://www.terraform.io/upgrade-guides/0-11.html) for more details.
  * The command `terraform apply` with no explicit plan argument is now interactive by default. Specifically, it will show the generated plan and wait for confirmation before applying it, similar to the existing behavior of `terraform destroy`. The behavior is unchanged when a plan file argument is provided, and the previous behavior can be obtained _without_ a plan file by using the `-auto-approve` option.
  * The `terraform` provider (that is, the provider that contains the `terraform_remote_state` data source) has been re-incorporated as a built-in provider in the Terraform Core executable. In 0.10 it was split into a separate plugin along with all of the other providers, but this provider uses several internal Terraform Core APIs and so in practice it's been confusing to version that separately from Terraform Core. As a consequence, this provider no longer supports version constraints, and so `version` attributes for this provider in configuration must be removed.
  * When remote state is enabled, Terraform will no longer generate a local `terraform.tfstate.backup` file before updating remote state. Previously this file could potentially be used to recover a previous state to help recover after a mistake, but it also caused a potentially-sensitive state file to be generated in an unexpected location that may be inadvertently copied or checked in to version control. With this local backup now removed, we recommend instead relying on versioning or backup mechanisms provided by the backend, such as Amazon S3 versioning or Terraform Enterprise's built-in state history mechanism. (Terraform will still create the local file `errored.tfstate` in the unlikely event that there is an error when writing to the remote backend.)
  * NEW FEATURES:
  * modules: Module configuration blocks now have a "version" attribute, to set a version constraint for modules sourced from a registry. ([#16466](https://github.com/hashicorp/terraform/issues/16466))
  * modules: Module configuration blocks now have a "providers" attribute, to map a provider configuration from the current module into a submodule ([#16379](https://github.com/hashicorp/terraform/issues/16379))
  * backend/gcs: The gcs remote state backend now supports workspaces and locking.
  * backend/manta: The Manta backend now supports workspaces and locking ([#16296](https://github.com/hashicorp/terraform/issues/16296))
  * IMPROVEMENTS:
  * cli: The `terraform apply` command now waits for interactive approval of the generated plan before applying it, unless an explicit plan file is provided. ([#16502](https://github.com/hashicorp/terraform/issues/16502))
  * cli: The `terraform version` command now prints out the version numbers of initialized plugins as well as the version of Terraform core, so that they can be more easily shared when opening GitHub Issues, etc. ([#16439](https://github.com/hashicorp/terraform/issues/16439))
  * cli: A new `TF_DATA_DIR` environment variable can be used to override the location where Terraform stores the files normally placed in the `.terraform` directory. ([#16207](https://github.com/hashicorp/terraform/issues/16207))
  * provider/terraform: now built in to Terraform Core so that it will always have the same backend functionality as the Terraform release it corresponds to. ([#16543](https://github.com/hashicorp/terraform/issues/16543))
  * BUG FIXES:
  * config: Provider config in submodules will no longer be overridden by parent providers with the same name. ([#16379](https://github.com/hashicorp/terraform/issues/16379))
  * cli: When remote state is enabled, Terraform will no longer generate a local `terraform.tfstate.backup` file before updating remote state. ([#16464](https://github.com/hashicorp/terraform/issues/16464))
  * core: state now includes a reference to the provider configuration most recently used to create or update a resource, so that the same configuration can be used to destroy that resource if its configuration (including the explicit pointer to a provider configuration) is removed ([#16586](https://github.com/hashicorp/terraform/issues/16586))
  * core: Module outputs can now produce errors, preventing them from silently propagating through the config. ([#16204](https://github.com/hashicorp/terraform/issues/16204))
  * backend/gcs: will now automatically add a slash to the given prefix if not present, since without it the workspace enumeration does not function correctly ([#16585](https://github.com/hashicorp/terraform/issues/16585))
  * PROVIDER FRAMEWORK CHANGES (not user-facing):
  * helper/schema: Loosen validation for 'id' field ([#16456](https://github.com/hashicorp/terraform/issues/16456))
- Changes of version 0.10.8
  * NEW FEATURES:
  * **New `etcdv3` backend**, for use with the newer etcd api ([#15680](https://github.com/hashicorp/terraform/issues/15680))
  * **New interpolation function `chunklist`**, for spliting a list into a list of lists with specified sublist chunk sizes. ([#15112](https://github.com/hashicorp/terraform/issues/15112))
  * IMPROVEMENTS:
  * backend/s3: Add options to skip AWS validation which allows non-AWS S3 backends ([#15553](https://github.com/hashicorp/terraform/issues/15553))
  * BUG FIXES:
  * command/validate: Respect `-plugin-dir` overridden plugin paths in the `terraform validate` command. ([#15985](https://github.com/hashicorp/terraform/issues/15985))
  * provisioner/chef: Clean clients from `chef-vault` when `recreate_client` enabled ([#16357](https://github.com/hashicorp/terraform/issues/16357))
  * communicator/winrm: Support the `cacert` option for custom certificate authorities when provisioning over WinRM ([#14783](https://github.com/hashicorp/terraform/issues/14783))</changelog>
  <changelog author="tbechtold@suse.com" date="1523620800">- update to 0.11.7:
  BUG FIXES:
  * core: Fix handling of interpolated counts when applying a destroy plan ([#17824](https://github.com/hashicorp/terraform/issues/17824))
  PROVIDER SDK CHANGES (not user-facing):
  * helper/schema: Invoking `ForceNew` on a key being removed from config during
    diff customization now correctly exposes that key as being removed in the
    updated diff. This prevents diff mismatches under certain circumstances.
    ([#17811](https://github.com/hashicorp/terraform/issues/17811))
  * helper/schema: Invoking `ForceNew` during diff customization on its own no
    longer writes any new data to the diff. This prevents writing of new nil to
    zero value diffs for sub-fields of complex lists and sets where a diff did not
    exist before. ([#17811](https://github.com/hashicorp/terraform/issues/17811))
  BUG FIXES:
  * cli: Don't allow -target without arguments ([#16360](https://github.com/hashicorp/terraform/issues/16360))
  * cli: Fix strange formatting of list and map values in the `terraform console` command ([#17714](https://github.com/hashicorp/terraform/issues/17714))
  * core: Don't evaluate unused outputs during a full destroy operation ([#17768](https://github.com/hashicorp/terraform/issues/17768))
  * core: Fix local and output evaluation when they reference a resource being scaled down to 0 ([#17765](https://github.com/hashicorp/terraform/issues/17765))
  * connection/ssh: Retry on authentication failures when the remote service is available before it is completely configured ([#17744](https://github.com/hashicorp/terraform/issues/17744))
  * connection/winrm: Get execution errors from winrm commands ([#17788](https://github.com/hashicorp/terraform/issues/17788))
  * connection/winrm: Support NTLM authentication ([#17748](https://github.com/hashicorp/terraform/issues/17748))
  * provisioner/chef: Fix regression causing connection to be prematurely closed ([#17609](https://github.com/hashicorp/terraform/pull/17609))
  * provisioner/habitat: Set channel and builder URL during install, and enable service before start ([#17403](https://github.com/hashicorp/terraform/issues/17403)) ([#17781](https://github.com/hashicorp/terraform/issues/17781))
  PROVIDER SDK CHANGES (not user-facing):
  * helper/schema: Attribute value is no longer included in error message when `ConflictsWith` keys are used together. ([#17738](https://github.com/hashicorp/terraform/issues/17738))
  IMPROVEMENTS:
  * provisioner/chef: Allow specifying a channel ([#17355](https://github.com/hashicorp/terraform/issues/17355))
  BUG FIXES:
  * core: Fix the timeout handling for provisioners ([#17646](https://github.com/hashicorp/terraform/issues/17646))
  * core: Ensure that state is unlocked after running console, import, graph or push commands ([#17645](https://github.com/hashicorp/terraform/issues/17645))
  * core: Don't open multiple file descriptors for local state files, which would cause reading the state to fail on Windows ([#17636](https://github.com/hashicorp/terraform/issues/17636))
  IMPROVEMENTS:
  * cli: `terraform state list` now accepts a new argument `-id=...` for filtering resources for display by their remote ids ([#17221](https://github.com/hashicorp/terraform/issues/17221))
  * cli: `terraform destroy` now uses the option `-auto-approve` instead of `-force`, for consistency with `terraform apply`. The old flag is preserved for backward-compatibility, but is now deprecated; it will be retained for at least one major release. ([#17218](https://github.com/hashicorp/terraform/issues/17218))
  * connection/ssh: Add support for host key verification ([#17354](https://github.com/hashicorp/terraform/issues/17354))
  * backend/s3: add support for the cn-northwest-1 region ([#17216](https://github.com/hashicorp/terraform/issues/17216))
  * provisioner/local-exec: Allow setting custom environment variables when running commands ([#13880](https://github.com/hashicorp/terraform/issues/13880))
  * provisioner/habitat: Detect if hab user exists and only create if necessary ([#17195](https://github.com/hashicorp/terraform/issues/17195))
  * provisioner/habitat: Allow custom service name ([#17196](https://github.com/hashicorp/terraform/issues/17196))
  * general: https URLs are now supported in the HTTP_PROXY environment variable for URLs interpreted by Terraform Core. (This will not immediately be true for all Terraform provider plugins, since each must upgrade its own HTTP client.) [go1.10:net/http](https://golang.org/doc/go1.10#net/http)
  BUG FIXES:
  * core: Make sure state is locked during initial refresh ([#17422](https://github.com/hashicorp/terraform/issues/17422))
  * core: Halt on fatal provisioner errors, rather than retrying until a timeout ([#17359](https://github.com/hashicorp/terraform/issues/17359))
  * core: When handling a forced exit due to multiple interrupts, prevent the process from exiting while the state is being written ([#17323](https://github.com/hashicorp/terraform/issues/17323))
  * core: Fix handling of locals and outputs at destroy time ([#17241](https://github.com/hashicorp/terraform/issues/17241))
  * core: Fix regression in handling of `count` arguments that refer to `count` attributes from other resources ([#17548](https://github.com/hashicorp/terraform/issues/17548))
  * provider/terraform: restore support for the deprecated `environment` argument to the `terraform_remote_state` data source ([#17545](https://github.com/hashicorp/terraform/issues/17545))
  * backend/gcs: Report the correct lock ID for GCS state locks ([#17397](https://github.com/hashicorp/terraform/issues/17397))
  PROVIDER SDK CHANGES (not user-facing):
  * helper/schema: Prevent crash on removal of computed field in CustomizeDiff ([#17261](https://github.com/hashicorp/terraform/issues/17261))
  * helper/schema: Allow ResourceDiff.ForceNew on nested fields (avoid crash) ([#17463](https://github.com/hashicorp/terraform/issues/17463))
  * helper/schema: Allow `TypeMap` to have a `*schema.Schema` as its `Elem`, for consistency with `TypeSet` and `TypeList` ([#17097](https://github.com/hashicorp/terraform/issues/17097))
  * helper/validation: Add ValidateRFC3339TimeString function ([#17484](https://github.com/hashicorp/terraform/issues/17484))</changelog>
  <changelog author="petr@cervinka.net" date="1549886400">- Update to 0.11.11
  IMPROVEMENTS:
  * backend/remote: Return detailed version (in)compatibility information ([#19659](https://github.com/hashicorp/terraform/issues/19659))
  * core: Enhance service discovery error handling and messaging ([#19589](https://github.com/hashicorp/terraform/issues/19589))
  * core: Add support to retrieve version constraints to service discovery ([#19647](https://github.com/hashicorp/terraform/issues/19647))
  BUG FIXES:
  * backend/remote: Fix symlink issues and Windows support when uploading configurations ([#19573](https://github.com/hashicorp/terraform/issues/19573))
- Changes of version 0.11.10
  BUG FIXES:
  * backend/local: Do not use backend operation variables ([#19175](https://github.com/hashicorp/terraform/issues/19175))
- Changes of version 0.11.9
  IMPROVEMENTS:
  * backend/remote: Also show policy check output when running a plan ([#19088](https://github.com/hashicorp/terraform/issues/19088))
- Changes of version 0.11.9-beta1
  IMPROVEMENTS:
  * provisioner/chef: Use user:group chown syntax ([#18533](https://github.com/hashicorp/terraform/issues/18533))
  * helper/resource: Add `ParallelTest()` to allow opt-in acceptance testing concurrency with `t.Parallel()` ([#18688](https://github.com/hashicorp/terraform/issues/18688))
  * backend/manta: Deprecate the `objectName` attribute in favor of the new `object_name` attribute ([#18759](https://github.com/hashicorp/terraform/issues/18759))
  * backend/migrations: Migrate existing non-empty default states when the backend only supports named states ([#18760](https://github.com/hashicorp/terraform/issues/18760))
  * provider/terraform: `terraform_remote_state` now accepts complex backend configurations ([#18759](https://github.com/hashicorp/terraform/issues/18759))
  * backend/remote: Implement the state.Locker interface to support state locking ([#18826](https://github.com/hashicorp/terraform/issues/18826))
  * backend/remote: Add initial support for the apply command ([#18950](https://github.com/hashicorp/terraform/issues/18950))
  * backend/remote: Ask to cancel pending remote operations when Ctrl-C is pressed ([#18979](https://github.com/hashicorp/terraform/issues/18979))
  * backend/remote: Add support for the `-no-color` command line flag ([#19002](https://github.com/hashicorp/terraform/issues/19002))
  * backend/remote: Prevent running plan or apply without permissions ([#19012](https://github.com/hashicorp/terraform/issues/19012))
  * backend/remote: Add checks for all flags we currently don’t support ([#19013](https://github.com/hashicorp/terraform/issues/19013))
  * backend/remote: Allow enhanced backends to pass custom exit codes ([#19014](https://github.com/hashicorp/terraform/issues/19014))
  * backend/remote: Properly handle workspaces that auto apply changes ([#19022](https://github.com/hashicorp/terraform/issues/19022))
  * backend/remote: Don’t ask questions when `-auto-approve` is set ([#19035](https://github.com/hashicorp/terraform/issues/19035))
  * backend/remote: Print status updates while waiting for the run to start ([#19047](https://github.com/hashicorp/terraform/issues/19047))
  BUG FIXES:
  * backend/azurerm: Update endpoint for Azure Government (SDK Update) ([#18877](https://github.com/hashicorp/terraform/issues/18877))
  * backend/migrations: Check all workspaces for existing non-empty states ([#18757](https://github.com/hashicorp/terraform/issues/18757))
  * provider/terraform: Always call the backend validation method to prevent a possible panic ([#18759](https://github.com/hashicorp/terraform/issues/18759))
  * backend/remote: Take working directories (optional on workspaces) into account ([#18773](https://github.com/hashicorp/terraform/issues/18773))
  * backend/remote: Use pagination when retrieving states (workspaces) ([#18817](https://github.com/hashicorp/terraform/issues/18817))
  * backend/remote: Add the run ID to associate state when being used in TFE ([#18818](https://github.com/hashicorp/terraform/issues/18818))
  * core: Make sure the state is locked before it is used when `(un)tainting` ([#18894](https://github.com/hashicorp/terraform/issues/18894))
- Changes of version  0.11.8
  NEW FEATURES:
  * New `remote` backend: Inital release of the `remote` backend for use with Terraform Enterprise and Private Terraform Enterprise ([#18596](https://github.com/hashicorp/terraform/issues/18596))
  IMPROVEMENTS:
  * cli: display workspace name in apply and destroy commands if not default ([#18253](https://github.com/hashicorp/terraform/issues/18253))
  * cli: Remove error on empty outputs when `-json` is set ([#11721](https://github.com/hashicorp/terraform/issues/11721))
  * helper/schema: Resources have a new `DeprecationMessage` property that can be set to a string, allowing full resources to be deprecated ([#18286](https://github.com/hashicorp/terraform/issues/18286))
  * backend/s3: Allow fallback to session-derived credentials (e.g. session via `AWS_PROFILE` environment variable and shared configuration) ([#17901](https://github.com/hashicorp/terraform/issues/17901))
  * backend/s3: Allow usage of `AWS_EC2_METADATA_DISABLED` environment variable ([#17901](https://github.com/hashicorp/terraform/issues/17901))
  BUG FIXES:
  * config: The `rsadecrypt` interpolation function will no longer include the private key in an error message if it cannot be processed. ([#18333](https://github.com/hashicorp/terraform/issues/18333))
  * provisioner/habitat: add missing space for service url ([#18400](https://github.com/hashicorp/terraform/issues/18400))
  * backend/s3: Skip extraneous EC2 metadata redirect ([#18570](https://github.com/hashicorp/terraform/issues/18570))</changelog>
  <changelog author="petr@cervinka.net" date="1557403200">- Update to 0.11.13
  BUG FIXES:
  * backend/remote: Fix a backend initialization bug ([#20638](https://github.com/hashicorp/terraform/issues/20638))
- Update to 0.11.12
  IMPROVEMENTS:
  * The `filemd5`, `filesha1`, etc functions from Terraform v0.12 are backported primarily to allow writing
    modules that can work in both Terraform 0.11 and 0.12, since the `sha1(file("..."))` pattern in 0.12
    works only for files containing valid UTF-8 text; `sha1file("...")` must be used instead.  Both
    forms are equivalent in Terraform 0.11.
  * backend/remote: Retry calls when the remote backend responds with a server error ([#20589](https://github.com/hashicorp/terraform/issues/20589))
  * backend/remote: Check for external updates while waiting for user input ([#20622](https://github.com/hashicorp/terraform/issues/20622))
  BUG FIXES:
  * backend/remote: Fix "token too long" errors when streaming remote operation logs ([#20241](https://github.com/hashicorp/terraform/issues/20241))
  * backend/remote: Use the `can-queue-apply` permission to detect if apply is allowed ([#20462](https://github.com/hashicorp/terraform/issues/20462))
  * backend/remote: Exit with 1 when a remote run is canceled ([#20482](https://github.com/hashicorp/terraform/issues/20482))
  * core: Use slashes in the module manifest to prevent Windows/Linux compatibility issues ([#20246](https://github.com/hashicorp/terraform/issues/20246))
- Update to 0.11.12-beta1
  IMPROVEMENTS:
  * command/state: Use locking when updating states ([#19939](https://github.com/hashicorp/terraform/issues/19939))
  * backend/remote: Add support for remote state only organizations ([#20007](https://github.com/hashicorp/terraform/issues/20007))
  * backend/remote: Make sure the correct error is shown when having version incompatibilities ([#20086](https://github.com/hashicorp/terraform/issues/20086))
  BUG FIXES:
  * backend/remote: Fix an error that prevents checking version constraints ([#19668](https://github.com/hashicorp/terraform/issues/19668))
  * backend/remote: Compare versions without the prerelease ([#19705](https://github.com/hashicorp/terraform/issues/19705))
- Run spec-cleaner
- Add GOFLAGS=-mod=vendor to fix build on Tumbleweed and Leap 15.1</changelog>
  <changelog author="petr@cervinka.net" date="1558440000">- Update to 0.11.14
  NEW FEATURES:
  * `terraform 0.12checklist` command detects and reports on some preparation steps that will make a subsequent
    Terraform 0.12 upgrade smoother. ([#21241](https://github.com/hashicorp/terraform/issues/21241))
  IMPROVEMENTS:
  * provider/terraform: The `terraform_remote_state` data source is now able to read outputs from a state snapshot
    created by Terraform 0.12, to provide more flexibility when upgrading individual configurations
    to Terraform 0.12 in a decomposed environment. ([#21226](https://github.com/hashicorp/terraform/issues/21226))
  * backend/s3: Support DynamoDB, IAM, and STS endpoint configurations ([#20659](https://github.com/hashicorp/terraform/issues/20659))
  * backend/s3: Support for AWS regions `eu-north-1` and `us-gov-east-1` ([#20659](https://github.com/hashicorp/terraform/issues/20659))
  * backend/s3: Enhance retry logic and provide `max_retries` configuration for retry attempts ([#20659](https://github.com/hashicorp/terraform/issues/20659))
  * backend/s3: Enhance S3 `NoSuchBucket` error to include additional information ([#20659](https://github.com/hashicorp/terraform/issues/20659))
  * backend/s3: Remove unused EC2 platform and AWS Account ID lookup, and deprecate equivalent `skip_get_ec2_platforms`
    and `skip_requesting_account_id` arguments ([#20659](https://github.com/hashicorp/terraform/issues/20659))
  * backend/remote: Do not unlock a workspace after a failed state upload ([#21148](https://github.com/hashicorp/terraform/issues/21148))
  BUG FIXES:
  * backend/remote: Ensure variables are loaded correctly when using `terraform console` ([#20858](https://github.com/hashicorp/terraform/issues/20858))
  * backend/remote: Make sure workspaces are correctly uploaded ([#20953](https://github.com/hashicorp/terraform/issues/20953))
  * backend/remote: Fix panic when loading cached configuration with 0.12 backend schema ([#21199](https://github.com/hashicorp/terraform/issues/21199))
  * core: Fix a potential crash when loading module manifests with Windows paths ([#20812](https://github.com/hashicorp/terraform/issues/20812))
  * core: Make sure UIInput keeps working after being canceled ([#21140](https://github.com/hashicorp/terraform/issues/21140))
  * core: Always try to select a workspace after initialization ([#21230](https://github.com/hashicorp/terraform/issues/21230))</changelog>
  <changelog author="petr@cervinka.net" date="1558440001">- Update to 0.12.0
  Incompatibilities and Notes
  * Version is not compatible with previous releases, it is needed to follow upgrade manual
  * See full upstream changelog for details
  New Features
  * First-class expressions
  * for expressions
  * Dynamic configuration blocks
  * Generalised "splat" operator
  * Nullable argument values
  * Rich types in module inputs variables and output values
  * Resource and module object values
  * Extended template syntax
  * jsondecode and csvdecode interpolation functions
  * Revamped error messages
  * Structual plan output
  Other Improvements
  * `terraform validate` now accepts an argument `-json` which produces machine-readable output
  * The JSON-based variant of the Terraform language now has a more tightly-specified and reliable mapping to the native syntax variant
  * The new built-in function [`templatefile`]
  * The new built-in function [`formatdate`]
  * The new built-in functions [`reverse`]
  * A new `pg` state storage backend allows storing state in a PostgreSQL database.
  * The `azurerm` state storage backend supports new authentication mechanisms, custom resource manager endpoints, and HTTP proxies.
  * The `s3` state storage backend now supports `credential_source` in AWS configuration file
  * The `swift` state storage backend now supports locking and workspaces.
- Increase go version dependency
- Remove conditions for module vendoring</changelog>
  <changelog author="petr@cervinka.net" date="1561982400">- Fix versionformat in service file</changelog>
  <changelog author="petr@cervinka.net" date="1561982401">- Update to 0.12.3
  ENHANCEMENTS:
  * config: add GCS source support for modules ([#21254](https://github.com/hashicorp/terraform/issues/21254))
  * command/format: Reduce extra whitespaces &amp; new lines ([#21334](https://github.com/hashicorp/terraform/issues/21334))
  * backend/s3: Support for chaining assume IAM role from AWS shared configuration files ([#21815](https://github.com/hashicorp/terraform/issues/21815))
  BUG FIXES:
  * configs: Can now use references like `tags["foo"]` in `ignore_changes` to ignore in-place updates to specific keys in a map ([#21788](https://github.com/hashicorp/terraform/issues/21788))
  * configs: Fix panic on missing value for `version` attribute in `provider` blocks. ([#21825](https://github.com/hashicorp/terraform/issues/21825))
  * lang/funcs: Fix `merge` panic on null values. Now will give an error if null used ([#21695](https://github.com/hashicorp/terraform/issues/21695))
  * backend/remote: Fix "Conflict" error if the first state snapshot written after a Terraform CLI upgrade has the same content as the prior state. ([#21811](https://github.com/hashicorp/terraform/issues/21811))
  * backend/s3: Fix AWS shared configuration file credential source not assuming a role with environment and ECS credentials ([#21815](https://github.com/hashicorp/terraform/issues/21815))
- Changes of version 0.12.2
  NEW FEATURES:
  * provisioners: new provisioner: `puppet` ([#18851](https://github.com/hashicorp/terraform/issues/18851))
  * `range` function for generating a sequence of numbers as a list ([#21461](https://github.com/hashicorp/terraform/issues/21461))
  * `yamldecode` and *experimental* `yamlencode` functions for working with YAML-serialized data ([#21459](https://github.com/hashicorp/terraform/issues/21459))
  * `uuidv5` function for generating name-based (as opposed to pseudorandom) UUIDs ([#21244](https://github.com/hashicorp/terraform/issues/21244))
  * backend/oss: Add support for Alibaba OSS remote state ([#16927](https://github.com/hashicorp/terraform/issues/16927))
  ENHANCEMENTS:
  * config: consider build metadata when interpreting module versions ([#21640](https://github.com/hashicorp/terraform/issues/21640))
  * backend/http: implement retries for the http backend ([#19702](https://github.com/hashicorp/terraform/issues/19702))
  * backend/swift: authentication mechanisms now more consistent with other OpenStack-compatible tools ([#18671](https://github.com/hashicorp/terraform/issues/18671))
  * backend/swift: add application credential support ([#20914](https://github.com/hashicorp/terraform/pull/20914))
  BUG FIXES:
  * command/show: use the state snapshot included in the planfile when rendering a plan to json ([#21597](https://github.com/hashicorp/terraform/issues/21597))
  * config: Fix issue with empty dynamic blocks failing when usign ConfigModeAttr ([#21549](https://github.com/hashicorp/terraform/issues/21549))
  * core: Re-validate resource config during final plan ([#21555](https://github.com/hashicorp/terraform/issues/21555))
  * core: Fix missing resource timeouts during destroy ([#21611](https://github.com/hashicorp/terraform/issues/21611))
  * core: Don't panic when encountering an invalid `depends_on` ([#21590](https://github.com/hashicorp/terraform/issues/21590))
  * backend: Fix panic when upgrading from a state with a hash value greater than MaxInt ([#21484](https://github.com/hashicorp/terraform/issues/21484))
- Changes of version 0.12.1
  BUG FIXES:
  * core: Always try to select a workspace after initialization ([#21234](https://github.com/hashicorp/terraform/issues/21234))
  * command/show: fix inconsistent json output causing a panic ([#21541](https://github.com/hashicorp/terraform/issues/21541))
  * config: `distinct` function no longer panics when given an empty list ([#21538](https://github.com/hashicorp/terraform/issues/21538))
  * config: Don't panic when a `version` constraint is added to a module that was previously initialized without one ([#21542](https://github.com/hashicorp/terraform/issues/21542))
  * config: `matchkeys` function argument type checking will no longer fail incorrectly during validation ([#21576](https://github.com/hashicorp/terraform/issues/21576))
  * backend/local: Don't panic if an instance in the state only has deposed instances, and no current instance ([#21575](https://github.com/hashicorp/terraform/issues/21575))</changelog>
  <changelog author="dmueller@suse.com" date="1566216000">- update to 0.12.6:
  * backend/s3: After this update, the AWS Go SDK will prefer credentials found via the `AWS_PROFILE` environment variable when both the `AWS_PROFILE` environment variable and the `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` environment variables are statically defined. Previously the SDK would ignore the `AWS_PROFILE` environment variable, if static environment credentials were also specified. This is listed as a bug fix in the AWS Go SDK release notes. ([#22253](https://github.com/hashicorp/terraform/issues/22253))
  NEW FEATURES:
  * backend/oss: added support for assume role config ([#22186](https://github.com/hashicorp/terraform/issues/22186))
  * config: Resources can now use a for_each meta-argument ([#17179](https://github.com/hashicorp/terraform/issues/17179))
  * backend/s3: Add support for assuming role via web identity token via the `AWS_WEB_IDENTITY_TOKEN_FILE` and `AWS_ROLE_ARN` environment variables ([#22253](https://github.com/hashicorp/terraform/issues/22253))
  * backend/s3: Support automatic region validation for `me-south-1`. For AWS operations to work in the new region, the region must be explicitly enabled as outlined in the [AWS Documentation](https://docs.aws.amazon.com/general/latest/gr/rande-manage.html#rande-manage-enable) ([#22253](https://github.com/hashicorp/terraform/issues/22253))
  * connection/ssh: Improve connection debug messages ([#22097](https://github.com/hashicorp/terraform/issues/22097))
  * command/format: No longer show no-ops in `terraform show`, since nothing will change ([#21907](https://github.com/hashicorp/terraform/issues/21907))
  * backend/s3: Support for assuming role using credential process from the shared AWS configuration file (support profile containing both `credential_process` and `role_arn` configurations) ([#21908](https://github.com/hashicorp/terraform/issues/21908))
  * connection/ssh: Abort ssh connections when the server is no longer responding ([#22037](https://github.com/hashicorp/terraform/issues/22037))
  * connection/ssh: Support ssh diffie-hellman-group-exchange-sha256 key exchange ([#22037](https://github.com/hashicorp/terraform/issues/22037))
  * lang/funcs: new `abspath` function returns the absolute path to a given file ([#21409](https://github.com/hashicorp/terraform/issues/21409))
  * backend/swift: support for user configured state object names in swift containers ([#17465](https://github.com/hashicorp/terraform/issues/17465))
  * Bugfixes, see included Changelog for details</changelog>
  <changelog author="petr@cervinka.net" date="1568116800">- Update to 0.12.8
  NEW FEATURES:
  * lang/funcs: New `fileset` function, for finding static local files that match a glob pattern. ([#22523](https://github.com/hashicorp/terraform/issues/22523))
  ENHANCEMENTS:
  * remote-state/pg: add option to skip schema creation ([#21607](https://github.com/hashicorp/terraform/issues/21607))
  BUG FIXES:
  * command/console: use user-supplied `-plugin-dir` ([#22616](https://github.com/hashicorp/terraform/issues/22616))
  * config: ensure sets are appropriately known for `for_each` ([#22597](https://github.com/hashicorp/terraform/issues/22597))
- Changes of version 0.12.7
  NEW FEATURES:
  * New functions `regex` and `regexall` allow applying a regular expression pattern to a string and retrieving any matching substring(s) ([#22353](https://github.com/hashicorp/terraform/issues/22353))
  ENHANCEMENTS:
  * lang/funcs: `lookup()` can work with maps of lists, maps and objects ([#22269](https://github.com/hashicorp/terraform/issues/22269))
  * SDK: helper/acctest: Add function to return random IP address ([#22312](https://github.com/hashicorp/terraform/issues/22312))
  * SDK: httpclient: Introduce composable `UserAgent(version)` ([#22272](https://github.com/hashicorp/terraform/issues/22272))
  * connection/ssh: Support certificate authentication ([#22156](https://github.com/hashicorp/terraform/issues/22156))
  BUG FIXES:
  * config: reduce MinItems and MaxItems  validation during decoding, to allow for use of dynamic blocks ([#22530](https://github.com/hashicorp/terraform/issues/22530))
  * config: don't validate MinItems and MaxItems in CoerceValue, allowing providers to set incomplete values ([#22478](https://github.com/hashicorp/terraform/issues/22478))
  * config: fix panic on tuples with `for_each` ([#22279](https://github.com/hashicorp/terraform/issues/22279))
  * config: fix references to `each` of `for_each` in s ([#22289](https://github.com/hashicorp/terraform/issues/22289))
  * config: fix panic when using nested dynamic blocks ([#22314](https://github.com/hashicorp/terraform/issues/22314))
  * config: ensure consistent evaluation when moving between single resources and `for_each` in addressing ([#22454](https://github.com/hashicorp/terraform/issues/22454))
  * core: only start a single instance of each required provisioner ([#22553](https://github.com/hashicorp/terraform/issues/22553))
  * command: fix issue where commands occasionally exited before the error message printed ([#22373](https://github.com/hashicorp/terraform/issues/22373))
  * command/0.12upgrade: use user-supplied plugin-dir ([#22306](https://github.com/hashicorp/terraform/issues/22306))
  * command/hook_ui: Truncate the ID considering multibyte characters ([#18823](https://github.com/hashicorp/terraform/issues/18823))
  * command/fmt: Terraform fmt no longer inserts spaces after % ([#22356](https://github.com/hashicorp/terraform/issues/22356))
  * command/state: Allow moving resources to modules not yet in state ([#22299](https://github.com/hashicorp/terraform/issues/22299))
  * backend/google: Now using the OAuth2 token endpoint on `googleapis.com` instead of `google.com`. These endpoints are equivalent in functionality but `googleapis.com` hosts are resolvable from private Google Cloud Platform VPCs where other connectivity is restricted. ([#22451](https://github.com/hashicorp/terraform/issues/22451))</changelog>
  <changelog author="adrian.glaubitz@suse.com" date="1568635200">- Add %ix86 to ExcludeArch as the build currently fails on i586
  * See: https://github.com/hashicorp/terraform/issues/22807</changelog>
  <changelog author="petr@cervinka.net" date="1568808000">- Update to 0.12.9
  NOTES:
  * core: `ignore_changes` is now processed (in addition to existing behaviors) before the provider plan is run. This means that users may see fewer planned changes when using `ignore_changes`, as before this change, changes to ignored attributes were still being sent to CustomizeDiff in providers (which could mean cascading changes for some resources). This should be indicative that providers are no longer getting changes that were marked as ignored, but if unexpected plans are seen while using `ignore_changes`, investigate the settings in the `ignore_changes` block to ensure the appropriate attributes are set. ([#22520](https://github.com/hashicorp/terraform/issues/22520))
  ENHANCEMENTS:
  * provisioners/habitat: `accept_license` argument available to automate accepting the EULA, now required by this client ([#22745](https://github.com/hashicorp/terraform/issues/22745))
  * config: add source addressing to unknown value errors in `for_each` ([#22760](https://github.com/hashicorp/terraform/issues/22760))
  BUG FIXES:
  * command/console: support -var and -var-file flags ([#22145](https://github.com/hashicorp/terraform/issues/22145))
  * command/show: Fixed bug with wrong errors being returned or swallowed. ([#22772](https://github.com/hashicorp/terraform/issues/22772))
  * config: The `cidrhost`, `cidrsubnet`, and `cidrnetmask` functions now behave correctly with IPv6 prefixes that are short enough for the host portion to be greater than 64-bit or 32-bit (depending on the target architecture). ([#22505](https://github.com/hashicorp/terraform/issues/22505))
  * config: Fixed bug on empty sets with `for_each` ([#22281](https://github.com/hashicorp/terraform/issues/22281))</changelog>
  <changelog author="petr@cervinka.net" date="1570536000">- Update to 0.12.10
  ENHANCEMENTS:
  * `terraform plan` and `terraform apply` will now warn when the `-target` option is used, to draw attention to the fact that the result of applying the plan is likely to be incomplete, and to remind to re-run `terraform plan` with no targets afterwards to ensure that the configuration has converged. ([#22783](https://github.com/hashicorp/terraform/issues/22783))
  * config: New function `parseint` for parsing strings containing digits as integers in various bases. ([#22747](https://github.com/hashicorp/terraform/issues/22747))
  * config: New function `cidrsubnets`, which is a companion to the existing function `cidrsubnet` which can allocate multiple consecutive subnet prefixes (possibly of different prefix lengths) in a single call. ([#22858](https://github.com/hashicorp/terraform/issues/22858))
  * backend/google: The GCS backend now supports OAuth2 token authentication. ([#21772](https://github.com/hashicorp/terraform/issues/21772))
  * provisioner/habitat: Multiple updates and fixes, see PR for details ([#22705](https://github.com/hashicorp/terraform/issues/22705))
  BUG FIXES:
  * backend/manta: fix panic when `insecure_skip_tls_verify` was not set ([#22918](https://github.com/hashicorp/terraform/issues/22918))</changelog>
  <changelog author="pcervinka@suse.com" date="1571659200">- Update to 0.12.12
  BUG FIXES:
  * backend/remote: Don't do local validation of whether variables are set prior to submitting, because only the remote system knows the full set of configured stored variables and environment variables that might contribute. This avoids erroneous error messages about unset required variables for remote runs when those variables will be set by stored variables in the remote workspace. ([#23122](https://github.com/hashicorp/terraform/issues/23122))
- Changes of version  0.12.11
  ENHANCEMENTS:
  * backend/s3: Support `role_arn` in AWS configuration files ([#22994](https://github.com/hashicorp/terraform/issues/22994))
  * backend/remote: Remote backend will now ignore all .terraform/ (exclusive of .terraform/modules) and .git/ directories for uploads during remote plans/applies. You can exclude files from upload to TFC by adding a .terraformignore file to your configuration directory, more details at https://www.terraform.io/docs/backends/types/remote.html ([#23105](https://github.com/hashicorp/terraform/issues/23105))
  BUG FIXES:
  * config: Clean up orphan modules in the presence of -target ([#21313](https://github.com/hashicorp/terraform/issues/21313))
  * config: Always evaluate whole resources rather than instances in expressions, so that invalid instance indexes can return a useful error rather than unknown ([#22846](https://github.com/hashicorp/terraform/issues/22846))
  * command/jsonplan: fix bug with missing nested modules `planned_values` output ([#23092](https://github.com/hashicorp/terraform/issues/23092))
  * command/show: Fix panic when the only resource instance is deposed ([#23027](https://github.com/hashicorp/terraform/issues/23027))
  * commands: When required root module variables are not provided and interactive input is disabled (`-input=false`), produce a proper "variable not defined" error rather than falling through to an internal assertion failure. ([#23040](https://github.com/hashicorp/terraform/issues/23040))
  * provisioner/puppet: fix bug when connection type was not set in config ([#23057](https://github.com/hashicorp/terraform/issues/23057))</changelog>
  <changelog author="moio@suse.com" date="1573646400">- Update to 0.12.13
  UPGRADE NOTES:
  * Remote backend local-only operations:** Previously the remote backend was not correctly handling variables marked as "HCL" in the remote workspace when running local-only operations like `terraform import`, instead interpreting them as literal strings as described in [#23228](https://github.com/hashicorp/terraform/issues/23228).
    That behavior is now corrected in this release, but in the unlikely event that an existing remote workspace contains a variable marked as "HCL" whose value is not valid HCL syntax these local-only commands will now fail with a syntax error where previously the value would not have been parsed at all and so an operation not relying on that value may have succeeded in spite of the problem. If you see an error like "Invalid expression for var.example" on local-only commands after upgrading, ensure that the remotely-stored value for the given variable uses correct HCL value syntax.
    This _does not_ affect true remote operations like `terraform plan` and `terraform apply`, because the processing of variables for those always happens in the remote system.
  BUG FIXES:
  * config: Fix regression where self wasn't properly evaluated when using for_each ([#23215](https://github.com/hashicorp/terraform/issues/23215))
  * config: dotfiles are no longer excluded when copying existing modules; previously, any dotfile/dir was excluded in this copy, but this change makes the local copy behavior match go-getter behavior ([#22946](https://github.com/hashicorp/terraform/issues/22946))
  * core: Ensure create_before_destroy ordering is enforced with dependencies between modules ([#22937](https://github.com/hashicorp/terraform/issues/22937))
  * core: Fix some destroy-time cycles due to unnecessary edges in the graph, and remove unused resource nodes ([#22976](https://github.com/hashicorp/terraform/issues/22976))
  * backend/remote: Correctly handle remotely-stored variables that are marked as "HCL" when running local-only operations like `terraform import`. Previously they would produce a type mismatch error, due to misinterpreting them as literal strings. ([#23229](https://github.com/hashicorp/terraform/issues/23229))</changelog>
  <changelog author="rmateus@suse.com" date="1636545600">- Update to 1.0.10
  * https://raw.githubusercontent.com/hashicorp/terraform/v0.12/CHANGELOG.md
  * https://raw.githubusercontent.com/hashicorp/terraform/v0.13/CHANGELOG.md
  * https://raw.githubusercontent.com/hashicorp/terraform/v0.14/CHANGELOG.md
  * https://raw.githubusercontent.com/hashicorp/terraform/v0.15/CHANGELOG.md
  * https://raw.githubusercontent.com/hashicorp/terraform/v1.0/CHANGELOG.md</changelog>
</package>
<package pkgid="bf49931e6c70b5bd3952e0fafb85fc2646895f9e49eecf7aaa0cf540e7ba3b55" name="terraform" arch="x86_64">
  <version epoch="0" ver="1.0.10" rel="150700.94.14"/>
  <changelog author="thipp@suse.de" date="1505736000">- Update to v0.10.5:
  - NEW FEATURES:
  * config: indent interpolation function appends spaces to all but the first
    line of a multi-line string (#15311)
  - IMPROVEMENTS:
  * cli: terraform fmt has a new option -check which makes it return a
    non-zero exit status if any formatting changes are required (#15387)
  * cli: When running Terraform in automation, a new environment variable
    TF_IN_AUTOMATION can be used to disable or adjust certain prompts that
    would normally include specific CLI commands to run. This assumes that
    the wrapping automation tool is providing its own UI for guiding the user
    through the workflow, and thus the standard advice would be redundant
    and/or confusing. (#16059)
  - BUG FIXES:
  * cli: restore the "(forces new resource)" annotations on attributes that
    were inadvertently disabled in 0.10.4. (#16067)
  * cli: fix regression with installing modules from git when the
    GIT_SSH_COMMAND environment variable is set (#16099)</changelog>
  <changelog author="thipp@suse.de" date="1505822400">- Update to v0.10.6:
  - UPGRADE NOTES:
  * The internal storage of modules has changed in this release, so after
    upgrading terraform init must be run to re-install modules in the new
    on-disk format. The existing installed versions of modules will be
    ignored, so the latest version of each module will be installed.
  - IMPROVEMENTS:
  * cli: terraform import now accepts an option -allow-missing-config that
    overrides the default requirement that a configuration block must already
    be present for the resource being imported. (#15876)</changelog>
  <changelog author="thipp@suse.de" date="1507118400">- Update to v0.10.7:
  - NEW FEATURES:
  * Provider plugins can now optionally be cached in a shared directory to
    avoid re-downloading them for each configuration working directory. For
    more information, see the documentation. (#16000)
  - IMPROVEMENTS:
  * config: New abs interpolation function, returning the absolute value of a
    number (#16168)
  * config: New transpose interpolation function, which swaps the keys and
    values in a map of lists of strings. (#16192)
  * cli: The Terraform CLI now supports tab-completion for commands and
    certain arguments for bash and zsh users. See the tab-completion docs for
    information on how to enable it. (#16176)
  * cli: terraform state rm now includes in its output the count of resources
    that were removed from the state. (#16137)
  - BUG FIXES:
  * modules: Update go-getter to fix crash when fetching invalid source
    subdir (#16161)
  * modules: Fix regression in the handling of modules sourcing other modules
    with relative paths (#16160)
  * core: Skip local value interpolation during destroy (#16213)</changelog>
  <changelog author="tbechtold@suse.com" date="1507291200">- Add terraform-rpmlintrc as Source99</changelog>
  <changelog author="fcastelli@suse.com" date="1518868800">- Update to v0.11.3:
  * IMPROVEMENTS:
  * backend/s3: add support for the eu-west-3 region ([#17193](https://github.com/hashicorp/terraform/issues/17193))
  * BUG FIXES:
  * core: fix crash when an error is encountered during refresh ([#17076](https://github.com/hashicorp/terraform/issues/17076))
  * config: fixed crash when module source is invalid ([#17134](https://github.com/hashicorp/terraform/issues/17134))
  * config: allow the count pseudo-attribute of a resource to be interpolated into `provisioner` and `connection` blocks without errors ([#17133](https://github.com/hashicorp/terraform/issues/17133))
  * backend/s3: allow the workspace name to be a prefix of workspace_key_prefix ([#17086](https://github.com/hashicorp/terraform/issues/17086))
  * provisioner/chef: fix crash when validating `use_policyfile` ([#17147](https://github.com/hashicorp/terraform/issues/17147))
- Changes of version 0.11.2:
  * BACKWARDS INCOMPATIBILITIES / NOTES:
  * backend/gcs: The gcs remote state backend was erroneously creating the state bucket if it didn't exist. This is not the intended behavior of backends, as Terraform cannot track or manage that resource. The target bucket must now be created separately, before using it with Terraform. ([#16865](https://github.com/hashicorp/terraform/issues/16865))
  * NEW FEATURES:
  * **[Habitat](https://www.habitat.sh/) Provisioner** allowing automatic installation of the Habitat agent ([#16280](https://github.com/hashicorp/terraform/issues/16280))
  * IMPROVEMENTS:
  * core: removed duplicate prompts and clarified working when migration backend configurations ([#16939](https://github.com/hashicorp/terraform/issues/16939))
  * config: new `rsadecrypt` interpolation function allows decrypting a base64-encoded ciphertext using a given private key. This is particularly useful for decrypting the password for a Windows instance on AWS EC2, but is generic and may find other uses too. ([#16647](https://github.com/hashicorp/terraform/issues/16647))
  * config: new `timeadd` interpolation function allows calculating a new timestamp relative to an existing known timestamp. ([#16644](https://github.com/hashicorp/terraform/issues/16644))
  * cli: Passing an empty string to `-plugin-dir` during init will remove previously saved paths ([#16969](https://github.com/hashicorp/terraform/issues/16969))
  * cli: Module and provider installation (and some other Terraform features) now implement [RFC6555](https://tools.ietf.org/html/rfc6555) when making outgoing HTTP requests, which should improve installation reliability for dual-stack (both IPv4 and IPv6) hosts running on networks that have non-performant or broken IPv6 Internet connectivity by trying both IPv4 and IPv6 connections. ([#16805](https://github.com/hashicorp/terraform/issues/16805))
  * backend/s3: it is now possible to disable the region check, for improved compatibility with third-party services that attempt to mimic the S3 API. ([#16757](https://github.com/hashicorp/terraform/issues/16757))
  * backend/s3: it is now possible to for the path-based S3 API form, for improved compatibility with third-party services that attempt to mimic the S3 API. ([#17001](https://github.com/hashicorp/terraform/issues/17001))
  * backend/s3: it is now possible to use named credentials from the `~/.aws/credentials` file, similarly to the AWS plugin ([#16661](https://github.com/hashicorp/terraform/issues/16661))
  * backend/manta: support for Triton RBAC ([#17003](https://github.com/hashicorp/terraform/issues/17003))
  * backend/gcs: support for customer-supplied encryption keys for remote state buckets ([#16936](https://github.com/hashicorp/terraform/issues/16936))
  * provider/terraform: in `terraform_remote_state`, the argument `environment` is now deprecated in favor of `workspace`. The `environment` argument will be removed in a later Terraform release. ([#16558](https://github.com/hashicorp/terraform/issues/16558))
  * BUG FIXES:
  * config: fixed crash in `substr` interpolation function with invalid offset ([#17043](https://github.com/hashicorp/terraform/issues/17043))
  * config: Referencing a count attribute in an output no longer generates a warning ([#16866](https://github.com/hashicorp/terraform/issues/16866))
  * cli: Terraform will no longer crash when `terraform plan`, `terraform apply`, and some other commands encounter an invalid provider version constraint in configuration, generating a proper error message instead. ([#16867](https://github.com/hashicorp/terraform/issues/16867))
  * backend/gcs: The usage of the GOOGLE_CREDENTIALS environment variable now matches that of the google provider ([#16865](https://github.com/hashicorp/terraform/issues/16865))
  * backend/gcs: fixed the locking methodology to avoid "double-locking" issues when used with the `terraform_remote_state` data source ([#16852](https://github.com/hashicorp/terraform/issues/16852))
  * backend/s3: the `workspace_key_prefix` can now be an empty string or contain slashes ([#16932](https://github.com/hashicorp/terraform/issues/16932))
  * provisioner/salt-masterless: now waits for all of the remote operations to complete before returning ([#16704](https://github.com/hashicorp/terraform/issues/16704))
- Changes of version 0.11.1
  * IMPROVEMENTS:
  * modules: Modules can now receive a specific provider configuration in the `providers` map, even if it's only implicitly used ([#16619](https://github.com/hashicorp/terraform/issues/16619))
  * config: Terraform will now detect and warn about outputs containing potentially-problematic references to resources with `count` set where the references does not use the "splat" syntax. This identifies situations where an output may [reference a resource with `count = 0`](https://www.terraform.io/upgrade-guides/0-11.html#referencing-attributes-from-resources-with-count-0) even if the `count` expression does not _currently_ evaluate to `0`, allowing the bug to be detected and fixed _before_ the value is later changed to `0` and would thus become an error. **This usage will become a fatal error in Terraform 0.12**. ([#16735](https://github.com/hashicorp/terraform/issues/16735))
  * core: A new environment variable `TF_WARN_OUTPUT_ERRORS=1` is supported to opt out of the behavior introduced in 0.11.0 where errors in output expressions halt execution. This restores the previous behavior where such errors are ignored, allowing users to apply problematic configurations without fixing all of the errors. This opt-out will be removed in Terraform 0.12, so it is strongly recommended to use the new warning described in the previous item to detect and fix these problematic expressions. ([#16782](https://github.com/hashicorp/terraform/issues/16782))
  * BUG FIXES:
  * cli: fix crash when subcommands with sub-subcommands are accidentally provided as a single argument, such as `terraform "workspace list"` ([#16789](https://github.com/hashicorp/terraform/issues/16789))
- Changes of version 0.11.0
  * BACKWARDS INCOMPATIBILITIES / NOTES:
    The following items give an overview of the incompatibilities and other noteworthy changes in this release. For more details on some of these changes, along with information on how to upgrade existing configurations where needed, see [the v0.11 upgrade guide](https://www.terraform.io/upgrade-guides/0-11.html).
  * Output interpolation errors are now fatal. Module configs with unused outputs which contained errors will no longer be valid.
  * Module configuration blocks have 2 new reserved attribute names, "providers" and "version". Modules using these as input variables will need to be updated.
  * The module provider inheritance rules have changed. Inherited provider configurations will no longer be merged with local configurations, and additional (aliased) provider configurations must be explicitly passed between modules when shared. See [the upgrade guide](https://www.terraform.io/upgrade-guides/0-11.html) for more details.
  * The command `terraform apply` with no explicit plan argument is now interactive by default. Specifically, it will show the generated plan and wait for confirmation before applying it, similar to the existing behavior of `terraform destroy`. The behavior is unchanged when a plan file argument is provided, and the previous behavior can be obtained _without_ a plan file by using the `-auto-approve` option.
  * The `terraform` provider (that is, the provider that contains the `terraform_remote_state` data source) has been re-incorporated as a built-in provider in the Terraform Core executable. In 0.10 it was split into a separate plugin along with all of the other providers, but this provider uses several internal Terraform Core APIs and so in practice it's been confusing to version that separately from Terraform Core. As a consequence, this provider no longer supports version constraints, and so `version` attributes for this provider in configuration must be removed.
  * When remote state is enabled, Terraform will no longer generate a local `terraform.tfstate.backup` file before updating remote state. Previously this file could potentially be used to recover a previous state to help recover after a mistake, but it also caused a potentially-sensitive state file to be generated in an unexpected location that may be inadvertently copied or checked in to version control. With this local backup now removed, we recommend instead relying on versioning or backup mechanisms provided by the backend, such as Amazon S3 versioning or Terraform Enterprise's built-in state history mechanism. (Terraform will still create the local file `errored.tfstate` in the unlikely event that there is an error when writing to the remote backend.)
  * NEW FEATURES:
  * modules: Module configuration blocks now have a "version" attribute, to set a version constraint for modules sourced from a registry. ([#16466](https://github.com/hashicorp/terraform/issues/16466))
  * modules: Module configuration blocks now have a "providers" attribute, to map a provider configuration from the current module into a submodule ([#16379](https://github.com/hashicorp/terraform/issues/16379))
  * backend/gcs: The gcs remote state backend now supports workspaces and locking.
  * backend/manta: The Manta backend now supports workspaces and locking ([#16296](https://github.com/hashicorp/terraform/issues/16296))
  * IMPROVEMENTS:
  * cli: The `terraform apply` command now waits for interactive approval of the generated plan before applying it, unless an explicit plan file is provided. ([#16502](https://github.com/hashicorp/terraform/issues/16502))
  * cli: The `terraform version` command now prints out the version numbers of initialized plugins as well as the version of Terraform core, so that they can be more easily shared when opening GitHub Issues, etc. ([#16439](https://github.com/hashicorp/terraform/issues/16439))
  * cli: A new `TF_DATA_DIR` environment variable can be used to override the location where Terraform stores the files normally placed in the `.terraform` directory. ([#16207](https://github.com/hashicorp/terraform/issues/16207))
  * provider/terraform: now built in to Terraform Core so that it will always have the same backend functionality as the Terraform release it corresponds to. ([#16543](https://github.com/hashicorp/terraform/issues/16543))
  * BUG FIXES:
  * config: Provider config in submodules will no longer be overridden by parent providers with the same name. ([#16379](https://github.com/hashicorp/terraform/issues/16379))
  * cli: When remote state is enabled, Terraform will no longer generate a local `terraform.tfstate.backup` file before updating remote state. ([#16464](https://github.com/hashicorp/terraform/issues/16464))
  * core: state now includes a reference to the provider configuration most recently used to create or update a resource, so that the same configuration can be used to destroy that resource if its configuration (including the explicit pointer to a provider configuration) is removed ([#16586](https://github.com/hashicorp/terraform/issues/16586))
  * core: Module outputs can now produce errors, preventing them from silently propagating through the config. ([#16204](https://github.com/hashicorp/terraform/issues/16204))
  * backend/gcs: will now automatically add a slash to the given prefix if not present, since without it the workspace enumeration does not function correctly ([#16585](https://github.com/hashicorp/terraform/issues/16585))
  * PROVIDER FRAMEWORK CHANGES (not user-facing):
  * helper/schema: Loosen validation for 'id' field ([#16456](https://github.com/hashicorp/terraform/issues/16456))
- Changes of version 0.10.8
  * NEW FEATURES:
  * **New `etcdv3` backend**, for use with the newer etcd api ([#15680](https://github.com/hashicorp/terraform/issues/15680))
  * **New interpolation function `chunklist`**, for spliting a list into a list of lists with specified sublist chunk sizes. ([#15112](https://github.com/hashicorp/terraform/issues/15112))
  * IMPROVEMENTS:
  * backend/s3: Add options to skip AWS validation which allows non-AWS S3 backends ([#15553](https://github.com/hashicorp/terraform/issues/15553))
  * BUG FIXES:
  * command/validate: Respect `-plugin-dir` overridden plugin paths in the `terraform validate` command. ([#15985](https://github.com/hashicorp/terraform/issues/15985))
  * provisioner/chef: Clean clients from `chef-vault` when `recreate_client` enabled ([#16357](https://github.com/hashicorp/terraform/issues/16357))
  * communicator/winrm: Support the `cacert` option for custom certificate authorities when provisioning over WinRM ([#14783](https://github.com/hashicorp/terraform/issues/14783))</changelog>
  <changelog author="tbechtold@suse.com" date="1523620800">- update to 0.11.7:
  BUG FIXES:
  * core: Fix handling of interpolated counts when applying a destroy plan ([#17824](https://github.com/hashicorp/terraform/issues/17824))
  PROVIDER SDK CHANGES (not user-facing):
  * helper/schema: Invoking `ForceNew` on a key being removed from config during
    diff customization now correctly exposes that key as being removed in the
    updated diff. This prevents diff mismatches under certain circumstances.
    ([#17811](https://github.com/hashicorp/terraform/issues/17811))
  * helper/schema: Invoking `ForceNew` during diff customization on its own no
    longer writes any new data to the diff. This prevents writing of new nil to
    zero value diffs for sub-fields of complex lists and sets where a diff did not
    exist before. ([#17811](https://github.com/hashicorp/terraform/issues/17811))
  BUG FIXES:
  * cli: Don't allow -target without arguments ([#16360](https://github.com/hashicorp/terraform/issues/16360))
  * cli: Fix strange formatting of list and map values in the `terraform console` command ([#17714](https://github.com/hashicorp/terraform/issues/17714))
  * core: Don't evaluate unused outputs during a full destroy operation ([#17768](https://github.com/hashicorp/terraform/issues/17768))
  * core: Fix local and output evaluation when they reference a resource being scaled down to 0 ([#17765](https://github.com/hashicorp/terraform/issues/17765))
  * connection/ssh: Retry on authentication failures when the remote service is available before it is completely configured ([#17744](https://github.com/hashicorp/terraform/issues/17744))
  * connection/winrm: Get execution errors from winrm commands ([#17788](https://github.com/hashicorp/terraform/issues/17788))
  * connection/winrm: Support NTLM authentication ([#17748](https://github.com/hashicorp/terraform/issues/17748))
  * provisioner/chef: Fix regression causing connection to be prematurely closed ([#17609](https://github.com/hashicorp/terraform/pull/17609))
  * provisioner/habitat: Set channel and builder URL during install, and enable service before start ([#17403](https://github.com/hashicorp/terraform/issues/17403)) ([#17781](https://github.com/hashicorp/terraform/issues/17781))
  PROVIDER SDK CHANGES (not user-facing):
  * helper/schema: Attribute value is no longer included in error message when `ConflictsWith` keys are used together. ([#17738](https://github.com/hashicorp/terraform/issues/17738))
  IMPROVEMENTS:
  * provisioner/chef: Allow specifying a channel ([#17355](https://github.com/hashicorp/terraform/issues/17355))
  BUG FIXES:
  * core: Fix the timeout handling for provisioners ([#17646](https://github.com/hashicorp/terraform/issues/17646))
  * core: Ensure that state is unlocked after running console, import, graph or push commands ([#17645](https://github.com/hashicorp/terraform/issues/17645))
  * core: Don't open multiple file descriptors for local state files, which would cause reading the state to fail on Windows ([#17636](https://github.com/hashicorp/terraform/issues/17636))
  IMPROVEMENTS:
  * cli: `terraform state list` now accepts a new argument `-id=...` for filtering resources for display by their remote ids ([#17221](https://github.com/hashicorp/terraform/issues/17221))
  * cli: `terraform destroy` now uses the option `-auto-approve` instead of `-force`, for consistency with `terraform apply`. The old flag is preserved for backward-compatibility, but is now deprecated; it will be retained for at least one major release. ([#17218](https://github.com/hashicorp/terraform/issues/17218))
  * connection/ssh: Add support for host key verification ([#17354](https://github.com/hashicorp/terraform/issues/17354))
  * backend/s3: add support for the cn-northwest-1 region ([#17216](https://github.com/hashicorp/terraform/issues/17216))
  * provisioner/local-exec: Allow setting custom environment variables when running commands ([#13880](https://github.com/hashicorp/terraform/issues/13880))
  * provisioner/habitat: Detect if hab user exists and only create if necessary ([#17195](https://github.com/hashicorp/terraform/issues/17195))
  * provisioner/habitat: Allow custom service name ([#17196](https://github.com/hashicorp/terraform/issues/17196))
  * general: https URLs are now supported in the HTTP_PROXY environment variable for URLs interpreted by Terraform Core. (This will not immediately be true for all Terraform provider plugins, since each must upgrade its own HTTP client.) [go1.10:net/http](https://golang.org/doc/go1.10#net/http)
  BUG FIXES:
  * core: Make sure state is locked during initial refresh ([#17422](https://github.com/hashicorp/terraform/issues/17422))
  * core: Halt on fatal provisioner errors, rather than retrying until a timeout ([#17359](https://github.com/hashicorp/terraform/issues/17359))
  * core: When handling a forced exit due to multiple interrupts, prevent the process from exiting while the state is being written ([#17323](https://github.com/hashicorp/terraform/issues/17323))
  * core: Fix handling of locals and outputs at destroy time ([#17241](https://github.com/hashicorp/terraform/issues/17241))
  * core: Fix regression in handling of `count` arguments that refer to `count` attributes from other resources ([#17548](https://github.com/hashicorp/terraform/issues/17548))
  * provider/terraform: restore support for the deprecated `environment` argument to the `terraform_remote_state` data source ([#17545](https://github.com/hashicorp/terraform/issues/17545))
  * backend/gcs: Report the correct lock ID for GCS state locks ([#17397](https://github.com/hashicorp/terraform/issues/17397))
  PROVIDER SDK CHANGES (not user-facing):
  * helper/schema: Prevent crash on removal of computed field in CustomizeDiff ([#17261](https://github.com/hashicorp/terraform/issues/17261))
  * helper/schema: Allow ResourceDiff.ForceNew on nested fields (avoid crash) ([#17463](https://github.com/hashicorp/terraform/issues/17463))
  * helper/schema: Allow `TypeMap` to have a `*schema.Schema` as its `Elem`, for consistency with `TypeSet` and `TypeList` ([#17097](https://github.com/hashicorp/terraform/issues/17097))
  * helper/validation: Add ValidateRFC3339TimeString function ([#17484](https://github.com/hashicorp/terraform/issues/17484))</changelog>
  <changelog author="petr@cervinka.net" date="1549886400">- Update to 0.11.11
  IMPROVEMENTS:
  * backend/remote: Return detailed version (in)compatibility information ([#19659](https://github.com/hashicorp/terraform/issues/19659))
  * core: Enhance service discovery error handling and messaging ([#19589](https://github.com/hashicorp/terraform/issues/19589))
  * core: Add support to retrieve version constraints to service discovery ([#19647](https://github.com/hashicorp/terraform/issues/19647))
  BUG FIXES:
  * backend/remote: Fix symlink issues and Windows support when uploading configurations ([#19573](https://github.com/hashicorp/terraform/issues/19573))
- Changes of version 0.11.10
  BUG FIXES:
  * backend/local: Do not use backend operation variables ([#19175](https://github.com/hashicorp/terraform/issues/19175))
- Changes of version 0.11.9
  IMPROVEMENTS:
  * backend/remote: Also show policy check output when running a plan ([#19088](https://github.com/hashicorp/terraform/issues/19088))
- Changes of version 0.11.9-beta1
  IMPROVEMENTS:
  * provisioner/chef: Use user:group chown syntax ([#18533](https://github.com/hashicorp/terraform/issues/18533))
  * helper/resource: Add `ParallelTest()` to allow opt-in acceptance testing concurrency with `t.Parallel()` ([#18688](https://github.com/hashicorp/terraform/issues/18688))
  * backend/manta: Deprecate the `objectName` attribute in favor of the new `object_name` attribute ([#18759](https://github.com/hashicorp/terraform/issues/18759))
  * backend/migrations: Migrate existing non-empty default states when the backend only supports named states ([#18760](https://github.com/hashicorp/terraform/issues/18760))
  * provider/terraform: `terraform_remote_state` now accepts complex backend configurations ([#18759](https://github.com/hashicorp/terraform/issues/18759))
  * backend/remote: Implement the state.Locker interface to support state locking ([#18826](https://github.com/hashicorp/terraform/issues/18826))
  * backend/remote: Add initial support for the apply command ([#18950](https://github.com/hashicorp/terraform/issues/18950))
  * backend/remote: Ask to cancel pending remote operations when Ctrl-C is pressed ([#18979](https://github.com/hashicorp/terraform/issues/18979))
  * backend/remote: Add support for the `-no-color` command line flag ([#19002](https://github.com/hashicorp/terraform/issues/19002))
  * backend/remote: Prevent running plan or apply without permissions ([#19012](https://github.com/hashicorp/terraform/issues/19012))
  * backend/remote: Add checks for all flags we currently don’t support ([#19013](https://github.com/hashicorp/terraform/issues/19013))
  * backend/remote: Allow enhanced backends to pass custom exit codes ([#19014](https://github.com/hashicorp/terraform/issues/19014))
  * backend/remote: Properly handle workspaces that auto apply changes ([#19022](https://github.com/hashicorp/terraform/issues/19022))
  * backend/remote: Don’t ask questions when `-auto-approve` is set ([#19035](https://github.com/hashicorp/terraform/issues/19035))
  * backend/remote: Print status updates while waiting for the run to start ([#19047](https://github.com/hashicorp/terraform/issues/19047))
  BUG FIXES:
  * backend/azurerm: Update endpoint for Azure Government (SDK Update) ([#18877](https://github.com/hashicorp/terraform/issues/18877))
  * backend/migrations: Check all workspaces for existing non-empty states ([#18757](https://github.com/hashicorp/terraform/issues/18757))
  * provider/terraform: Always call the backend validation method to prevent a possible panic ([#18759](https://github.com/hashicorp/terraform/issues/18759))
  * backend/remote: Take working directories (optional on workspaces) into account ([#18773](https://github.com/hashicorp/terraform/issues/18773))
  * backend/remote: Use pagination when retrieving states (workspaces) ([#18817](https://github.com/hashicorp/terraform/issues/18817))
  * backend/remote: Add the run ID to associate state when being used in TFE ([#18818](https://github.com/hashicorp/terraform/issues/18818))
  * core: Make sure the state is locked before it is used when `(un)tainting` ([#18894](https://github.com/hashicorp/terraform/issues/18894))
- Changes of version  0.11.8
  NEW FEATURES:
  * New `remote` backend: Inital release of the `remote` backend for use with Terraform Enterprise and Private Terraform Enterprise ([#18596](https://github.com/hashicorp/terraform/issues/18596))
  IMPROVEMENTS:
  * cli: display workspace name in apply and destroy commands if not default ([#18253](https://github.com/hashicorp/terraform/issues/18253))
  * cli: Remove error on empty outputs when `-json` is set ([#11721](https://github.com/hashicorp/terraform/issues/11721))
  * helper/schema: Resources have a new `DeprecationMessage` property that can be set to a string, allowing full resources to be deprecated ([#18286](https://github.com/hashicorp/terraform/issues/18286))
  * backend/s3: Allow fallback to session-derived credentials (e.g. session via `AWS_PROFILE` environment variable and shared configuration) ([#17901](https://github.com/hashicorp/terraform/issues/17901))
  * backend/s3: Allow usage of `AWS_EC2_METADATA_DISABLED` environment variable ([#17901](https://github.com/hashicorp/terraform/issues/17901))
  BUG FIXES:
  * config: The `rsadecrypt` interpolation function will no longer include the private key in an error message if it cannot be processed. ([#18333](https://github.com/hashicorp/terraform/issues/18333))
  * provisioner/habitat: add missing space for service url ([#18400](https://github.com/hashicorp/terraform/issues/18400))
  * backend/s3: Skip extraneous EC2 metadata redirect ([#18570](https://github.com/hashicorp/terraform/issues/18570))</changelog>
  <changelog author="petr@cervinka.net" date="1557403200">- Update to 0.11.13
  BUG FIXES:
  * backend/remote: Fix a backend initialization bug ([#20638](https://github.com/hashicorp/terraform/issues/20638))
- Update to 0.11.12
  IMPROVEMENTS:
  * The `filemd5`, `filesha1`, etc functions from Terraform v0.12 are backported primarily to allow writing
    modules that can work in both Terraform 0.11 and 0.12, since the `sha1(file("..."))` pattern in 0.12
    works only for files containing valid UTF-8 text; `sha1file("...")` must be used instead.  Both
    forms are equivalent in Terraform 0.11.
  * backend/remote: Retry calls when the remote backend responds with a server error ([#20589](https://github.com/hashicorp/terraform/issues/20589))
  * backend/remote: Check for external updates while waiting for user input ([#20622](https://github.com/hashicorp/terraform/issues/20622))
  BUG FIXES:
  * backend/remote: Fix "token too long" errors when streaming remote operation logs ([#20241](https://github.com/hashicorp/terraform/issues/20241))
  * backend/remote: Use the `can-queue-apply` permission to detect if apply is allowed ([#20462](https://github.com/hashicorp/terraform/issues/20462))
  * backend/remote: Exit with 1 when a remote run is canceled ([#20482](https://github.com/hashicorp/terraform/issues/20482))
  * core: Use slashes in the module manifest to prevent Windows/Linux compatibility issues ([#20246](https://github.com/hashicorp/terraform/issues/20246))
- Update to 0.11.12-beta1
  IMPROVEMENTS:
  * command/state: Use locking when updating states ([#19939](https://github.com/hashicorp/terraform/issues/19939))
  * backend/remote: Add support for remote state only organizations ([#20007](https://github.com/hashicorp/terraform/issues/20007))
  * backend/remote: Make sure the correct error is shown when having version incompatibilities ([#20086](https://github.com/hashicorp/terraform/issues/20086))
  BUG FIXES:
  * backend/remote: Fix an error that prevents checking version constraints ([#19668](https://github.com/hashicorp/terraform/issues/19668))
  * backend/remote: Compare versions without the prerelease ([#19705](https://github.com/hashicorp/terraform/issues/19705))
- Run spec-cleaner
- Add GOFLAGS=-mod=vendor to fix build on Tumbleweed and Leap 15.1</changelog>
  <changelog author="petr@cervinka.net" date="1558440000">- Update to 0.11.14
  NEW FEATURES:
  * `terraform 0.12checklist` command detects and reports on some preparation steps that will make a subsequent
    Terraform 0.12 upgrade smoother. ([#21241](https://github.com/hashicorp/terraform/issues/21241))
  IMPROVEMENTS:
  * provider/terraform: The `terraform_remote_state` data source is now able to read outputs from a state snapshot
    created by Terraform 0.12, to provide more flexibility when upgrading individual configurations
    to Terraform 0.12 in a decomposed environment. ([#21226](https://github.com/hashicorp/terraform/issues/21226))
  * backend/s3: Support DynamoDB, IAM, and STS endpoint configurations ([#20659](https://github.com/hashicorp/terraform/issues/20659))
  * backend/s3: Support for AWS regions `eu-north-1` and `us-gov-east-1` ([#20659](https://github.com/hashicorp/terraform/issues/20659))
  * backend/s3: Enhance retry logic and provide `max_retries` configuration for retry attempts ([#20659](https://github.com/hashicorp/terraform/issues/20659))
  * backend/s3: Enhance S3 `NoSuchBucket` error to include additional information ([#20659](https://github.com/hashicorp/terraform/issues/20659))
  * backend/s3: Remove unused EC2 platform and AWS Account ID lookup, and deprecate equivalent `skip_get_ec2_platforms`
    and `skip_requesting_account_id` arguments ([#20659](https://github.com/hashicorp/terraform/issues/20659))
  * backend/remote: Do not unlock a workspace after a failed state upload ([#21148](https://github.com/hashicorp/terraform/issues/21148))
  BUG FIXES:
  * backend/remote: Ensure variables are loaded correctly when using `terraform console` ([#20858](https://github.com/hashicorp/terraform/issues/20858))
  * backend/remote: Make sure workspaces are correctly uploaded ([#20953](https://github.com/hashicorp/terraform/issues/20953))
  * backend/remote: Fix panic when loading cached configuration with 0.12 backend schema ([#21199](https://github.com/hashicorp/terraform/issues/21199))
  * core: Fix a potential crash when loading module manifests with Windows paths ([#20812](https://github.com/hashicorp/terraform/issues/20812))
  * core: Make sure UIInput keeps working after being canceled ([#21140](https://github.com/hashicorp/terraform/issues/21140))
  * core: Always try to select a workspace after initialization ([#21230](https://github.com/hashicorp/terraform/issues/21230))</changelog>
  <changelog author="petr@cervinka.net" date="1558440001">- Update to 0.12.0
  Incompatibilities and Notes
  * Version is not compatible with previous releases, it is needed to follow upgrade manual
  * See full upstream changelog for details
  New Features
  * First-class expressions
  * for expressions
  * Dynamic configuration blocks
  * Generalised "splat" operator
  * Nullable argument values
  * Rich types in module inputs variables and output values
  * Resource and module object values
  * Extended template syntax
  * jsondecode and csvdecode interpolation functions
  * Revamped error messages
  * Structual plan output
  Other Improvements
  * `terraform validate` now accepts an argument `-json` which produces machine-readable output
  * The JSON-based variant of the Terraform language now has a more tightly-specified and reliable mapping to the native syntax variant
  * The new built-in function [`templatefile`]
  * The new built-in function [`formatdate`]
  * The new built-in functions [`reverse`]
  * A new `pg` state storage backend allows storing state in a PostgreSQL database.
  * The `azurerm` state storage backend supports new authentication mechanisms, custom resource manager endpoints, and HTTP proxies.
  * The `s3` state storage backend now supports `credential_source` in AWS configuration file
  * The `swift` state storage backend now supports locking and workspaces.
- Increase go version dependency
- Remove conditions for module vendoring</changelog>
  <changelog author="petr@cervinka.net" date="1561982400">- Fix versionformat in service file</changelog>
  <changelog author="petr@cervinka.net" date="1561982401">- Update to 0.12.3
  ENHANCEMENTS:
  * config: add GCS source support for modules ([#21254](https://github.com/hashicorp/terraform/issues/21254))
  * command/format: Reduce extra whitespaces &amp; new lines ([#21334](https://github.com/hashicorp/terraform/issues/21334))
  * backend/s3: Support for chaining assume IAM role from AWS shared configuration files ([#21815](https://github.com/hashicorp/terraform/issues/21815))
  BUG FIXES:
  * configs: Can now use references like `tags["foo"]` in `ignore_changes` to ignore in-place updates to specific keys in a map ([#21788](https://github.com/hashicorp/terraform/issues/21788))
  * configs: Fix panic on missing value for `version` attribute in `provider` blocks. ([#21825](https://github.com/hashicorp/terraform/issues/21825))
  * lang/funcs: Fix `merge` panic on null values. Now will give an error if null used ([#21695](https://github.com/hashicorp/terraform/issues/21695))
  * backend/remote: Fix "Conflict" error if the first state snapshot written after a Terraform CLI upgrade has the same content as the prior state. ([#21811](https://github.com/hashicorp/terraform/issues/21811))
  * backend/s3: Fix AWS shared configuration file credential source not assuming a role with environment and ECS credentials ([#21815](https://github.com/hashicorp/terraform/issues/21815))
- Changes of version 0.12.2
  NEW FEATURES:
  * provisioners: new provisioner: `puppet` ([#18851](https://github.com/hashicorp/terraform/issues/18851))
  * `range` function for generating a sequence of numbers as a list ([#21461](https://github.com/hashicorp/terraform/issues/21461))
  * `yamldecode` and *experimental* `yamlencode` functions for working with YAML-serialized data ([#21459](https://github.com/hashicorp/terraform/issues/21459))
  * `uuidv5` function for generating name-based (as opposed to pseudorandom) UUIDs ([#21244](https://github.com/hashicorp/terraform/issues/21244))
  * backend/oss: Add support for Alibaba OSS remote state ([#16927](https://github.com/hashicorp/terraform/issues/16927))
  ENHANCEMENTS:
  * config: consider build metadata when interpreting module versions ([#21640](https://github.com/hashicorp/terraform/issues/21640))
  * backend/http: implement retries for the http backend ([#19702](https://github.com/hashicorp/terraform/issues/19702))
  * backend/swift: authentication mechanisms now more consistent with other OpenStack-compatible tools ([#18671](https://github.com/hashicorp/terraform/issues/18671))
  * backend/swift: add application credential support ([#20914](https://github.com/hashicorp/terraform/pull/20914))
  BUG FIXES:
  * command/show: use the state snapshot included in the planfile when rendering a plan to json ([#21597](https://github.com/hashicorp/terraform/issues/21597))
  * config: Fix issue with empty dynamic blocks failing when usign ConfigModeAttr ([#21549](https://github.com/hashicorp/terraform/issues/21549))
  * core: Re-validate resource config during final plan ([#21555](https://github.com/hashicorp/terraform/issues/21555))
  * core: Fix missing resource timeouts during destroy ([#21611](https://github.com/hashicorp/terraform/issues/21611))
  * core: Don't panic when encountering an invalid `depends_on` ([#21590](https://github.com/hashicorp/terraform/issues/21590))
  * backend: Fix panic when upgrading from a state with a hash value greater than MaxInt ([#21484](https://github.com/hashicorp/terraform/issues/21484))
- Changes of version 0.12.1
  BUG FIXES:
  * core: Always try to select a workspace after initialization ([#21234](https://github.com/hashicorp/terraform/issues/21234))
  * command/show: fix inconsistent json output causing a panic ([#21541](https://github.com/hashicorp/terraform/issues/21541))
  * config: `distinct` function no longer panics when given an empty list ([#21538](https://github.com/hashicorp/terraform/issues/21538))
  * config: Don't panic when a `version` constraint is added to a module that was previously initialized without one ([#21542](https://github.com/hashicorp/terraform/issues/21542))
  * config: `matchkeys` function argument type checking will no longer fail incorrectly during validation ([#21576](https://github.com/hashicorp/terraform/issues/21576))
  * backend/local: Don't panic if an instance in the state only has deposed instances, and no current instance ([#21575](https://github.com/hashicorp/terraform/issues/21575))</changelog>
  <changelog author="dmueller@suse.com" date="1566216000">- update to 0.12.6:
  * backend/s3: After this update, the AWS Go SDK will prefer credentials found via the `AWS_PROFILE` environment variable when both the `AWS_PROFILE` environment variable and the `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` environment variables are statically defined. Previously the SDK would ignore the `AWS_PROFILE` environment variable, if static environment credentials were also specified. This is listed as a bug fix in the AWS Go SDK release notes. ([#22253](https://github.com/hashicorp/terraform/issues/22253))
  NEW FEATURES:
  * backend/oss: added support for assume role config ([#22186](https://github.com/hashicorp/terraform/issues/22186))
  * config: Resources can now use a for_each meta-argument ([#17179](https://github.com/hashicorp/terraform/issues/17179))
  * backend/s3: Add support for assuming role via web identity token via the `AWS_WEB_IDENTITY_TOKEN_FILE` and `AWS_ROLE_ARN` environment variables ([#22253](https://github.com/hashicorp/terraform/issues/22253))
  * backend/s3: Support automatic region validation for `me-south-1`. For AWS operations to work in the new region, the region must be explicitly enabled as outlined in the [AWS Documentation](https://docs.aws.amazon.com/general/latest/gr/rande-manage.html#rande-manage-enable) ([#22253](https://github.com/hashicorp/terraform/issues/22253))
  * connection/ssh: Improve connection debug messages ([#22097](https://github.com/hashicorp/terraform/issues/22097))
  * command/format: No longer show no-ops in `terraform show`, since nothing will change ([#21907](https://github.com/hashicorp/terraform/issues/21907))
  * backend/s3: Support for assuming role using credential process from the shared AWS configuration file (support profile containing both `credential_process` and `role_arn` configurations) ([#21908](https://github.com/hashicorp/terraform/issues/21908))
  * connection/ssh: Abort ssh connections when the server is no longer responding ([#22037](https://github.com/hashicorp/terraform/issues/22037))
  * connection/ssh: Support ssh diffie-hellman-group-exchange-sha256 key exchange ([#22037](https://github.com/hashicorp/terraform/issues/22037))
  * lang/funcs: new `abspath` function returns the absolute path to a given file ([#21409](https://github.com/hashicorp/terraform/issues/21409))
  * backend/swift: support for user configured state object names in swift containers ([#17465](https://github.com/hashicorp/terraform/issues/17465))
  * Bugfixes, see included Changelog for details</changelog>
  <changelog author="petr@cervinka.net" date="1568116800">- Update to 0.12.8
  NEW FEATURES:
  * lang/funcs: New `fileset` function, for finding static local files that match a glob pattern. ([#22523](https://github.com/hashicorp/terraform/issues/22523))
  ENHANCEMENTS:
  * remote-state/pg: add option to skip schema creation ([#21607](https://github.com/hashicorp/terraform/issues/21607))
  BUG FIXES:
  * command/console: use user-supplied `-plugin-dir` ([#22616](https://github.com/hashicorp/terraform/issues/22616))
  * config: ensure sets are appropriately known for `for_each` ([#22597](https://github.com/hashicorp/terraform/issues/22597))
- Changes of version 0.12.7
  NEW FEATURES:
  * New functions `regex` and `regexall` allow applying a regular expression pattern to a string and retrieving any matching substring(s) ([#22353](https://github.com/hashicorp/terraform/issues/22353))
  ENHANCEMENTS:
  * lang/funcs: `lookup()` can work with maps of lists, maps and objects ([#22269](https://github.com/hashicorp/terraform/issues/22269))
  * SDK: helper/acctest: Add function to return random IP address ([#22312](https://github.com/hashicorp/terraform/issues/22312))
  * SDK: httpclient: Introduce composable `UserAgent(version)` ([#22272](https://github.com/hashicorp/terraform/issues/22272))
  * connection/ssh: Support certificate authentication ([#22156](https://github.com/hashicorp/terraform/issues/22156))
  BUG FIXES:
  * config: reduce MinItems and MaxItems  validation during decoding, to allow for use of dynamic blocks ([#22530](https://github.com/hashicorp/terraform/issues/22530))
  * config: don't validate MinItems and MaxItems in CoerceValue, allowing providers to set incomplete values ([#22478](https://github.com/hashicorp/terraform/issues/22478))
  * config: fix panic on tuples with `for_each` ([#22279](https://github.com/hashicorp/terraform/issues/22279))
  * config: fix references to `each` of `for_each` in s ([#22289](https://github.com/hashicorp/terraform/issues/22289))
  * config: fix panic when using nested dynamic blocks ([#22314](https://github.com/hashicorp/terraform/issues/22314))
  * config: ensure consistent evaluation when moving between single resources and `for_each` in addressing ([#22454](https://github.com/hashicorp/terraform/issues/22454))
  * core: only start a single instance of each required provisioner ([#22553](https://github.com/hashicorp/terraform/issues/22553))
  * command: fix issue where commands occasionally exited before the error message printed ([#22373](https://github.com/hashicorp/terraform/issues/22373))
  * command/0.12upgrade: use user-supplied plugin-dir ([#22306](https://github.com/hashicorp/terraform/issues/22306))
  * command/hook_ui: Truncate the ID considering multibyte characters ([#18823](https://github.com/hashicorp/terraform/issues/18823))
  * command/fmt: Terraform fmt no longer inserts spaces after % ([#22356](https://github.com/hashicorp/terraform/issues/22356))
  * command/state: Allow moving resources to modules not yet in state ([#22299](https://github.com/hashicorp/terraform/issues/22299))
  * backend/google: Now using the OAuth2 token endpoint on `googleapis.com` instead of `google.com`. These endpoints are equivalent in functionality but `googleapis.com` hosts are resolvable from private Google Cloud Platform VPCs where other connectivity is restricted. ([#22451](https://github.com/hashicorp/terraform/issues/22451))</changelog>
  <changelog author="adrian.glaubitz@suse.com" date="1568635200">- Add %ix86 to ExcludeArch as the build currently fails on i586
  * See: https://github.com/hashicorp/terraform/issues/22807</changelog>
  <changelog author="petr@cervinka.net" date="1568808000">- Update to 0.12.9
  NOTES:
  * core: `ignore_changes` is now processed (in addition to existing behaviors) before the provider plan is run. This means that users may see fewer planned changes when using `ignore_changes`, as before this change, changes to ignored attributes were still being sent to CustomizeDiff in providers (which could mean cascading changes for some resources). This should be indicative that providers are no longer getting changes that were marked as ignored, but if unexpected plans are seen while using `ignore_changes`, investigate the settings in the `ignore_changes` block to ensure the appropriate attributes are set. ([#22520](https://github.com/hashicorp/terraform/issues/22520))
  ENHANCEMENTS:
  * provisioners/habitat: `accept_license` argument available to automate accepting the EULA, now required by this client ([#22745](https://github.com/hashicorp/terraform/issues/22745))
  * config: add source addressing to unknown value errors in `for_each` ([#22760](https://github.com/hashicorp/terraform/issues/22760))
  BUG FIXES:
  * command/console: support -var and -var-file flags ([#22145](https://github.com/hashicorp/terraform/issues/22145))
  * command/show: Fixed bug with wrong errors being returned or swallowed. ([#22772](https://github.com/hashicorp/terraform/issues/22772))
  * config: The `cidrhost`, `cidrsubnet`, and `cidrnetmask` functions now behave correctly with IPv6 prefixes that are short enough for the host portion to be greater than 64-bit or 32-bit (depending on the target architecture). ([#22505](https://github.com/hashicorp/terraform/issues/22505))
  * config: Fixed bug on empty sets with `for_each` ([#22281](https://github.com/hashicorp/terraform/issues/22281))</changelog>
  <changelog author="petr@cervinka.net" date="1570536000">- Update to 0.12.10
  ENHANCEMENTS:
  * `terraform plan` and `terraform apply` will now warn when the `-target` option is used, to draw attention to the fact that the result of applying the plan is likely to be incomplete, and to remind to re-run `terraform plan` with no targets afterwards to ensure that the configuration has converged. ([#22783](https://github.com/hashicorp/terraform/issues/22783))
  * config: New function `parseint` for parsing strings containing digits as integers in various bases. ([#22747](https://github.com/hashicorp/terraform/issues/22747))
  * config: New function `cidrsubnets`, which is a companion to the existing function `cidrsubnet` which can allocate multiple consecutive subnet prefixes (possibly of different prefix lengths) in a single call. ([#22858](https://github.com/hashicorp/terraform/issues/22858))
  * backend/google: The GCS backend now supports OAuth2 token authentication. ([#21772](https://github.com/hashicorp/terraform/issues/21772))
  * provisioner/habitat: Multiple updates and fixes, see PR for details ([#22705](https://github.com/hashicorp/terraform/issues/22705))
  BUG FIXES:
  * backend/manta: fix panic when `insecure_skip_tls_verify` was not set ([#22918](https://github.com/hashicorp/terraform/issues/22918))</changelog>
  <changelog author="pcervinka@suse.com" date="1571659200">- Update to 0.12.12
  BUG FIXES:
  * backend/remote: Don't do local validation of whether variables are set prior to submitting, because only the remote system knows the full set of configured stored variables and environment variables that might contribute. This avoids erroneous error messages about unset required variables for remote runs when those variables will be set by stored variables in the remote workspace. ([#23122](https://github.com/hashicorp/terraform/issues/23122))
- Changes of version  0.12.11
  ENHANCEMENTS:
  * backend/s3: Support `role_arn` in AWS configuration files ([#22994](https://github.com/hashicorp/terraform/issues/22994))
  * backend/remote: Remote backend will now ignore all .terraform/ (exclusive of .terraform/modules) and .git/ directories for uploads during remote plans/applies. You can exclude files from upload to TFC by adding a .terraformignore file to your configuration directory, more details at https://www.terraform.io/docs/backends/types/remote.html ([#23105](https://github.com/hashicorp/terraform/issues/23105))
  BUG FIXES:
  * config: Clean up orphan modules in the presence of -target ([#21313](https://github.com/hashicorp/terraform/issues/21313))
  * config: Always evaluate whole resources rather than instances in expressions, so that invalid instance indexes can return a useful error rather than unknown ([#22846](https://github.com/hashicorp/terraform/issues/22846))
  * command/jsonplan: fix bug with missing nested modules `planned_values` output ([#23092](https://github.com/hashicorp/terraform/issues/23092))
  * command/show: Fix panic when the only resource instance is deposed ([#23027](https://github.com/hashicorp/terraform/issues/23027))
  * commands: When required root module variables are not provided and interactive input is disabled (`-input=false`), produce a proper "variable not defined" error rather than falling through to an internal assertion failure. ([#23040](https://github.com/hashicorp/terraform/issues/23040))
  * provisioner/puppet: fix bug when connection type was not set in config ([#23057](https://github.com/hashicorp/terraform/issues/23057))</changelog>
  <changelog author="moio@suse.com" date="1573646400">- Update to 0.12.13
  UPGRADE NOTES:
  * Remote backend local-only operations:** Previously the remote backend was not correctly handling variables marked as "HCL" in the remote workspace when running local-only operations like `terraform import`, instead interpreting them as literal strings as described in [#23228](https://github.com/hashicorp/terraform/issues/23228).
    That behavior is now corrected in this release, but in the unlikely event that an existing remote workspace contains a variable marked as "HCL" whose value is not valid HCL syntax these local-only commands will now fail with a syntax error where previously the value would not have been parsed at all and so an operation not relying on that value may have succeeded in spite of the problem. If you see an error like "Invalid expression for var.example" on local-only commands after upgrading, ensure that the remotely-stored value for the given variable uses correct HCL value syntax.
    This _does not_ affect true remote operations like `terraform plan` and `terraform apply`, because the processing of variables for those always happens in the remote system.
  BUG FIXES:
  * config: Fix regression where self wasn't properly evaluated when using for_each ([#23215](https://github.com/hashicorp/terraform/issues/23215))
  * config: dotfiles are no longer excluded when copying existing modules; previously, any dotfile/dir was excluded in this copy, but this change makes the local copy behavior match go-getter behavior ([#22946](https://github.com/hashicorp/terraform/issues/22946))
  * core: Ensure create_before_destroy ordering is enforced with dependencies between modules ([#22937](https://github.com/hashicorp/terraform/issues/22937))
  * core: Fix some destroy-time cycles due to unnecessary edges in the graph, and remove unused resource nodes ([#22976](https://github.com/hashicorp/terraform/issues/22976))
  * backend/remote: Correctly handle remotely-stored variables that are marked as "HCL" when running local-only operations like `terraform import`. Previously they would produce a type mismatch error, due to misinterpreting them as literal strings. ([#23229](https://github.com/hashicorp/terraform/issues/23229))</changelog>
  <changelog author="rmateus@suse.com" date="1636545600">- Update to 1.0.10
  * https://raw.githubusercontent.com/hashicorp/terraform/v0.12/CHANGELOG.md
  * https://raw.githubusercontent.com/hashicorp/terraform/v0.13/CHANGELOG.md
  * https://raw.githubusercontent.com/hashicorp/terraform/v0.14/CHANGELOG.md
  * https://raw.githubusercontent.com/hashicorp/terraform/v0.15/CHANGELOG.md
  * https://raw.githubusercontent.com/hashicorp/terraform/v1.0/CHANGELOG.md</changelog>
</package>
<package pkgid="a10d7c2c0dfc608db7c68e9641c274fea6bb97976f112042177741c9dca8f776" name="terraform-provider-feilong-v6" arch="src">
  <version epoch="0" ver="0.0.9" rel="150700.2.1"/>
  <changelog author="ebischoff@suse.com" date="1700481600">- Initial release</changelog>
  <changelog author="ebischoff@suse.com" date="1700740800">- Wait for IP address of guest</changelog>
  <changelog author="eric.bischoff.fr@gmail.com" date="1701777600">- Support for custom switches</changelog>
  <changelog author="eric.bischoff.fr@gmail.com" date="1702641600">- Support for authentication</changelog>
  <changelog author="eric.bischoff.fr@gmail.com" date="1703419200">- Removed network parameters</changelog>
  <changelog author="eric.bischoff.fr@gmail.com" date="1708257600">- Added missing CRUD functions for guest</changelog>
  <changelog author="eric.bischoff.fr@gmail.com" date="1764331200">- Added missing CRUD functions for switch
- New adapter_address parameter for guest
- Instructions for OpenTofu</changelog>
  <changelog author="eric.bischoff.fr@gmail.com" date="1764417600">- Bumped base go library</changelog>
  <changelog author="eric.bischoff.fr@gmail.com" date="1765022400">- Configure first network interface at OS level
- Booleans did not always get marshalled into json
- Allow to configure static IPs</changelog>
</package>
<package pkgid="b2e1b3aac0f796393b97ca2d55379164bea6dfb70f81517d5eaf4856b9b21ae6" name="terraform-provider-feilong-v6" arch="x86_64">
  <version epoch="0" ver="0.0.9" rel="150700.2.1"/>
  <changelog author="ebischoff@suse.com" date="1700481600">- Initial release</changelog>
  <changelog author="ebischoff@suse.com" date="1700740800">- Wait for IP address of guest</changelog>
  <changelog author="eric.bischoff.fr@gmail.com" date="1701777600">- Support for custom switches</changelog>
  <changelog author="eric.bischoff.fr@gmail.com" date="1702641600">- Support for authentication</changelog>
  <changelog author="eric.bischoff.fr@gmail.com" date="1703419200">- Removed network parameters</changelog>
  <changelog author="eric.bischoff.fr@gmail.com" date="1708257600">- Added missing CRUD functions for guest</changelog>
  <changelog author="eric.bischoff.fr@gmail.com" date="1764331200">- Added missing CRUD functions for switch
- New adapter_address parameter for guest
- Instructions for OpenTofu</changelog>
  <changelog author="eric.bischoff.fr@gmail.com" date="1764417600">- Bumped base go library</changelog>
  <changelog author="eric.bischoff.fr@gmail.com" date="1765022400">- Configure first network interface at OS level
- Booleans did not always get marshalled into json
- Allow to configure static IPs</changelog>
</package>
<package pkgid="af5af9c0dc7b711043a51f2eda2d494e5b4895b76fdd1e7ce50eaf5b8f37c8c8" name="terraform-provider-libvirt" arch="src">
  <version epoch="0" ver="0.8.3+git.1741083459.5d70006" rel="150700.2.8"/>
  <changelog author="thipp@suse.de" date="1502193600">- Update to version 0.0.0+git20170808.d9c8d155:
  * ensure volumes are free'd if there are no errors
  * network: ensure networks are recreated
  * vendor: depend on terraform v0.10.0
  * fix import
  * cloudinit: handle changes correctly
  * cloudinit: show user_data in .tfstate file</changelog>
  <changelog author="thipp@suse.de" date="1502280000">- Update to version 0.0.0+git20170809.92ff0867:
  * fix XML name of DHCP host element
- Depend on terraform &gt;= 0.10.0</changelog>
  <changelog author="thipp@suse.de" date="1505822400">- Update to version 0.0.0+git20170919.3fd193d2:
  * Adding tests for machine and arch domain attributes from #166
  * domain: Add support for BootDevice.
  * domain: Improve documentation and add examples for BootDevice.
  * FIX graphics autoport setting in examples
  * fixes misspelling of boot_device in docs and example
  * vendor: update deps
  * FIX waitForLeases invalid key issue
  * Fixing travis for forks</changelog>
  <changelog author="thipp@suse.de" date="1506081600">- Update to version 0.0.0+git20170922.dbe46f97:
  * update Terraform and Go version
  * Full support for arch,machine &amp; emulator settings
  * Trying longer timeout
  * Remove redundant hostname check</changelog>
  <changelog author="thipp@suse.de" date="1507809600">- Update to version 0.0.0+git20171012.c034dc8e:
  * Update readme with some details about the go version to use</changelog>
  <changelog author="opensuse-packaging@opensuse.org" date="1508241600">- Update to version 0.0.0+git20171017.4907902b:
  * Fix crash occuring when domain is in state file but doesn't exist in libvirt.
  * vendor: add libvirt-go-xml
  * use github.com/libvirt-go-xml
  * Fix broken tests
  * fix failing console port conversion
  * Improve documentation
  * Added support for specifying NVRAM templates when using UEFI images.
  * ensure volumes are free'd if there are no errors
  * network: ensure networks are recreated
  * vendor: depend on terraform v0.10.0
  * fix import
  * cloudinit: handle changes correctly
  * cloudinit: show user_data in .tfstate file
  * fix XML name of DHCP host element
  * Fix string format of network addresses
  * use libvirt-go-xml for volumes
  * Ensure libvirt stream are cleaned up properly
  * Adding support for arch and machine type
  * Adding tests for machine and arch domain attributes from #166
  * domain: Add support for BootDevice.
  * domain: Improve documentation and add examples for BootDevice.
  * FIX graphics autoport setting in examples
  * fixes misspelling of boot_device in docs and example
  * vendor: update deps
  * FIX waitForLeases invalid key issue
  * Fixing travis for forks
  * Full support for arch,machine &amp; emulator settings
  * Trying longer timeout
  * Remove redundant hostname check
  * update Terraform and Go version
  * Update readme with some details about the go version to use
  * Bugfix: let libvirt populate channel source</changelog>
  <changelog author="opensuse-packaging@opensuse.org" date="1519128000">- Update to version 0.0.0+git20180220.09834dbc:
  * Handle keyword-less kernel params
  * Add make target to run acceptance tests
  * Update to use latest release of terraform (0.11.3)
  * Fix broken tests on Travis
  * Make the tests less noisy
  * Fix apt directive for travis
  * Travis: ensure libvirt development headers are installed
  * Travis: fix error
  * Ensure libvirt connection is released
  * travis: do not run acceptance tests
  * sort imports
  * remove dead/unreachable code
  * refactor cloudinit
  * refactor resourceLibvirtDomainCreate
  * refactor schemas
  * fix difference detection when using an existing bridge network
  * Update README's requirement section
  * Modify cloudinit to use 'mkisofs' instead of 'genisoimage'.
  * fix network linke
  * add an example for ubuntu
  * spelling....
  * fix markdown spelling
  * add the website docs to the README for visibility
  * domain: honor arch, machine, and emulator settings
  * Add new method to get information on domain interfaces
  * Make add/updateHost a bit more resilient
  * support local cdroms
  * check uniqueness of storage volume name
  * remove running from documentation
  * remove running property in net and domain
  * tests: format hcl strings
  * Simplify the wait_for_leases mechanism
  * Retry the query about interfaces to the qemu-agent
  * adding documentation about network autostart
  * add test for autostart option
  * Init first backport
  * Typo
  * Add missing hcl markdown fence
  * Remove intermediate variables in map iteration
  * Simplify for loop
  * Typo in cmdline docs
  * Type not needed in literal anymore
  * No need to make a 0 len slice
  * Do not choke on empty kernel cmdline
  * Split kernel cmdline test
  * Read back cmdline, initrd and kernel attributes from the resource
  * Fix tests by adding fixture for kernel and initrd
  * Add support for kernel/initrd/cmdline
  * don't allocate memory with 0 make variables
  * remove duplicata declaration and simplify code.
  * use poolMutexKV for locking resources.
  * init govet on travis
  * golint: Url -&gt; URL
  * Document disks from url
  * Reuse newDefDisk()
  * Add support for remote http disks (qemu http curl backend)
  * add volume cloud_init test check
  * add geniso to travis_guest
  * Add AcceptTest for CloudInit
  * golint on resource_libvirt_domain_test.go Use correct names in comments
  * common string constant for errmsg lvirtconn is nil
  * golint on various files
  * Type name will be used as libvirt.LibVirtNetwork
  * type name will be used as libvirt.LibVirtDomain by
  * golinting on various files
  * don't export oui variable
  * fix golint on coreos_ingition_def.go
  * fix golint on stream and volume_def.go
  * Fix IP golint issues (style)
  * fix golint on utils_net.go
  * fix golint issues on utils.go
  * Fix golint on test cloudinit
  * error strings should not be capitalized or end
  * fix golint on cloudinit_def.go
  * comment on exported function should Start with
  * don't use underscores in Go names
  * fix golint on libvirt/utils_volume.go
  * fix golinting libvirt/resource_libvirt_domain_test
  * golint enablement
  * Make test don't depend on install
  * Dont print debug info it tests are ok
  * Add more doc about the Makefile workflow(suggested)
  * Add golint to makefile
  * ligthen process with makefile
  * fix travis
  * make golint happy
  * Improve layout Readme
  * make the firmware file consistent with the docs
  * Fix libvirt ovmf firmware integration test on non-Ubuntu
  * Uri should be named URI
  * Use the right markdown for doc troublesh.
  * Add note about latest golang version required
  * add gofmt check for pkg(libvirt and main)
  * Google terraform link has changed: update link
  * Add a small note about libvirt-devel
  * DOC: improve readme, separating troubleshooting.</changelog>
  <changelog author="opensuse-packaging@opensuse.org" date="1519128001">- Update to version 0.0.0+git20180220.f2cef405:
  * Handle keyword-less kernel params</changelog>
  <changelog author="fcastelli@suse.com" date="1528286400">- Remove the `genisoimage` requirement, this is no longer used
- Add the `mkisofs` requirement</changelog>
  <changelog author="dmacvicar@suse.de" date="1539691200">- add -ldflags "-X main.version=%{version}"</changelog>
  <changelog author="Duncan Mac-Vicar &lt;dmacvicar@suse.de" date="1550836800">- GO111MODULE=off GOPROXY=off to keep building with GOPATH
  and vendor, in order to support multiple distributions and
  go versions.</changelog>
  <changelog author="petr@cervinka.net" date="1562068800">- Temporary support for terraform 0.12 to follow master branch in
  service file</changelog>
  <changelog author="dmacvicar@suse.de" date="1592481600">- Update to version 0.6.2+git.1590253051.d1cf93cd:
  * remove broken network if the creation failed
  * Fix error msg
  * Update to the latest testify
  * Handle correctly destruction of inactive networks
  * blacklist graphics for aarch64 as well.
  * remove logging eyecatcher
  * #703 - permit multiple libvirt networks
  * Update .travis.yml to satisfy build config validation</changelog>
  <changelog author="dmacvicar@suse.de" date="1605009600">- Update to version 0.6.3+git.1604843676.67f4f2aa:
  * Revert adding of forward device parameter for networks
  * Add .terraform to .gitignore
  * Tubleweed -&gt; Tumbleweed
  * Example: Use the OpenStack image as it supports cloud-init
  * Tubleweed -&gt; Tumbleweed
  * Fix channel type for qemu-guest-agent
  * Improve terraform v0.13 migration doc
  * CONTRIBUTING.md: process for schema changes
  * CONTRIBUTING.md: mention testcases reproducing an issue
  * Remove unused script
  * Delete setup-host script not longer needed
  * Remove unnecessary mknod /dev/kvm already present in Focal
  * Assume this is not longer an issue
  * Upgrade go to 1.13.x
  * Comment which network attributes require ForceNew
  * Do not run tests twice
  * Upgrade Travis environment
  * Restrict the network mutex to network definition
  * go fmt
  * Force creation of network when we can't update
  * Do not allow defining networks in parallel
  * Test case to reproduce issue #703
  * Revert "Merge pull request #740 from vmorris/master"
  * Fix pty console integration tests
  * Add missing link to libvirt_pool documentation
  * add more info to migration doc
  * adapt toc
  * Add documentation for v13
  * Init example for TF13
  * network: Trim the bridge name to 15 characters
  * Fix gofmt errors
  * Implement network detection for static IPs
  * Remove unused function and variables
  * Even an isolated network has dhcp
  * Make static IP addresses permanent across reboots
  * Update README.md
  * Listen only to localhost
  * Adjust generated dhcp to match libvirt limitation of max 65535 addresses
  * Add tubleweed example</changelog>
  <changelog author="dmacvicar@suse.de" date="1605009601">- Install also in /usr/share/terraform to comply with v0.13
  provider installation path.
  https://www.terraform.io/docs/commands/cli-config.html#provider-installation</changelog>
  <changelog author="dmueller@suse.com" date="1609934400">- spec-cleaner run</changelog>
  <changelog author="hello@anthonyrabbito.com" date="1613217600">- Added if condition in spec if on a SUSE version use mkisofs, instead of genisoimage</changelog>
  <changelog author="paolo.invernizzi@suse.com" date="1736251200">- Update to version 0.8.1+git.1729332308.1cd90b7</changelog>
  <changelog author="paolo.invernizzi@suse.com" date="1736856000">- Apply a patch with the following changes:
  * https://github.com/dmacvicar/terraform-provider-libvirt/pull/1144 (restore error handling for network operations)
  * An additional check to consider a network interface as not ready to be used if it has only link-local IPv6 addresses</changelog>
  <changelog author="paolo.invernizzi@suse.com" date="1741089600">- Update to version 0.8.3+git.1741083459.5d70006</changelog>
</package>
<package pkgid="c6afcc4103f0ea7df4f219b9ec07c96b9509f4af1dd5b4737c4452e0751e3a32" name="terraform-provider-libvirt" arch="x86_64">
  <version epoch="0" ver="0.8.3+git.1741083459.5d70006" rel="150700.2.8"/>
  <changelog author="thipp@suse.de" date="1502193600">- Update to version 0.0.0+git20170808.d9c8d155:
  * ensure volumes are free'd if there are no errors
  * network: ensure networks are recreated
  * vendor: depend on terraform v0.10.0
  * fix import
  * cloudinit: handle changes correctly
  * cloudinit: show user_data in .tfstate file</changelog>
  <changelog author="thipp@suse.de" date="1502280000">- Update to version 0.0.0+git20170809.92ff0867:
  * fix XML name of DHCP host element
- Depend on terraform &gt;= 0.10.0</changelog>
  <changelog author="thipp@suse.de" date="1505822400">- Update to version 0.0.0+git20170919.3fd193d2:
  * Adding tests for machine and arch domain attributes from #166
  * domain: Add support for BootDevice.
  * domain: Improve documentation and add examples for BootDevice.
  * FIX graphics autoport setting in examples
  * fixes misspelling of boot_device in docs and example
  * vendor: update deps
  * FIX waitForLeases invalid key issue
  * Fixing travis for forks</changelog>
  <changelog author="thipp@suse.de" date="1506081600">- Update to version 0.0.0+git20170922.dbe46f97:
  * update Terraform and Go version
  * Full support for arch,machine &amp; emulator settings
  * Trying longer timeout
  * Remove redundant hostname check</changelog>
  <changelog author="thipp@suse.de" date="1507809600">- Update to version 0.0.0+git20171012.c034dc8e:
  * Update readme with some details about the go version to use</changelog>
  <changelog author="opensuse-packaging@opensuse.org" date="1508241600">- Update to version 0.0.0+git20171017.4907902b:
  * Fix crash occuring when domain is in state file but doesn't exist in libvirt.
  * vendor: add libvirt-go-xml
  * use github.com/libvirt-go-xml
  * Fix broken tests
  * fix failing console port conversion
  * Improve documentation
  * Added support for specifying NVRAM templates when using UEFI images.
  * ensure volumes are free'd if there are no errors
  * network: ensure networks are recreated
  * vendor: depend on terraform v0.10.0
  * fix import
  * cloudinit: handle changes correctly
  * cloudinit: show user_data in .tfstate file
  * fix XML name of DHCP host element
  * Fix string format of network addresses
  * use libvirt-go-xml for volumes
  * Ensure libvirt stream are cleaned up properly
  * Adding support for arch and machine type
  * Adding tests for machine and arch domain attributes from #166
  * domain: Add support for BootDevice.
  * domain: Improve documentation and add examples for BootDevice.
  * FIX graphics autoport setting in examples
  * fixes misspelling of boot_device in docs and example
  * vendor: update deps
  * FIX waitForLeases invalid key issue
  * Fixing travis for forks
  * Full support for arch,machine &amp; emulator settings
  * Trying longer timeout
  * Remove redundant hostname check
  * update Terraform and Go version
  * Update readme with some details about the go version to use
  * Bugfix: let libvirt populate channel source</changelog>
  <changelog author="opensuse-packaging@opensuse.org" date="1519128000">- Update to version 0.0.0+git20180220.09834dbc:
  * Handle keyword-less kernel params
  * Add make target to run acceptance tests
  * Update to use latest release of terraform (0.11.3)
  * Fix broken tests on Travis
  * Make the tests less noisy
  * Fix apt directive for travis
  * Travis: ensure libvirt development headers are installed
  * Travis: fix error
  * Ensure libvirt connection is released
  * travis: do not run acceptance tests
  * sort imports
  * remove dead/unreachable code
  * refactor cloudinit
  * refactor resourceLibvirtDomainCreate
  * refactor schemas
  * fix difference detection when using an existing bridge network
  * Update README's requirement section
  * Modify cloudinit to use 'mkisofs' instead of 'genisoimage'.
  * fix network linke
  * add an example for ubuntu
  * spelling....
  * fix markdown spelling
  * add the website docs to the README for visibility
  * domain: honor arch, machine, and emulator settings
  * Add new method to get information on domain interfaces
  * Make add/updateHost a bit more resilient
  * support local cdroms
  * check uniqueness of storage volume name
  * remove running from documentation
  * remove running property in net and domain
  * tests: format hcl strings
  * Simplify the wait_for_leases mechanism
  * Retry the query about interfaces to the qemu-agent
  * adding documentation about network autostart
  * add test for autostart option
  * Init first backport
  * Typo
  * Add missing hcl markdown fence
  * Remove intermediate variables in map iteration
  * Simplify for loop
  * Typo in cmdline docs
  * Type not needed in literal anymore
  * No need to make a 0 len slice
  * Do not choke on empty kernel cmdline
  * Split kernel cmdline test
  * Read back cmdline, initrd and kernel attributes from the resource
  * Fix tests by adding fixture for kernel and initrd
  * Add support for kernel/initrd/cmdline
  * don't allocate memory with 0 make variables
  * remove duplicata declaration and simplify code.
  * use poolMutexKV for locking resources.
  * init govet on travis
  * golint: Url -&gt; URL
  * Document disks from url
  * Reuse newDefDisk()
  * Add support for remote http disks (qemu http curl backend)
  * add volume cloud_init test check
  * add geniso to travis_guest
  * Add AcceptTest for CloudInit
  * golint on resource_libvirt_domain_test.go Use correct names in comments
  * common string constant for errmsg lvirtconn is nil
  * golint on various files
  * Type name will be used as libvirt.LibVirtNetwork
  * type name will be used as libvirt.LibVirtDomain by
  * golinting on various files
  * don't export oui variable
  * fix golint on coreos_ingition_def.go
  * fix golint on stream and volume_def.go
  * Fix IP golint issues (style)
  * fix golint on utils_net.go
  * fix golint issues on utils.go
  * Fix golint on test cloudinit
  * error strings should not be capitalized or end
  * fix golint on cloudinit_def.go
  * comment on exported function should Start with
  * don't use underscores in Go names
  * fix golint on libvirt/utils_volume.go
  * fix golinting libvirt/resource_libvirt_domain_test
  * golint enablement
  * Make test don't depend on install
  * Dont print debug info it tests are ok
  * Add more doc about the Makefile workflow(suggested)
  * Add golint to makefile
  * ligthen process with makefile
  * fix travis
  * make golint happy
  * Improve layout Readme
  * make the firmware file consistent with the docs
  * Fix libvirt ovmf firmware integration test on non-Ubuntu
  * Uri should be named URI
  * Use the right markdown for doc troublesh.
  * Add note about latest golang version required
  * add gofmt check for pkg(libvirt and main)
  * Google terraform link has changed: update link
  * Add a small note about libvirt-devel
  * DOC: improve readme, separating troubleshooting.</changelog>
  <changelog author="opensuse-packaging@opensuse.org" date="1519128001">- Update to version 0.0.0+git20180220.f2cef405:
  * Handle keyword-less kernel params</changelog>
  <changelog author="fcastelli@suse.com" date="1528286400">- Remove the `genisoimage` requirement, this is no longer used
- Add the `mkisofs` requirement</changelog>
  <changelog author="dmacvicar@suse.de" date="1539691200">- add -ldflags "-X main.version=%{version}"</changelog>
  <changelog author="Duncan Mac-Vicar &lt;dmacvicar@suse.de" date="1550836800">- GO111MODULE=off GOPROXY=off to keep building with GOPATH
  and vendor, in order to support multiple distributions and
  go versions.</changelog>
  <changelog author="petr@cervinka.net" date="1562068800">- Temporary support for terraform 0.12 to follow master branch in
  service file</changelog>
  <changelog author="dmacvicar@suse.de" date="1592481600">- Update to version 0.6.2+git.1590253051.d1cf93cd:
  * remove broken network if the creation failed
  * Fix error msg
  * Update to the latest testify
  * Handle correctly destruction of inactive networks
  * blacklist graphics for aarch64 as well.
  * remove logging eyecatcher
  * #703 - permit multiple libvirt networks
  * Update .travis.yml to satisfy build config validation</changelog>
  <changelog author="dmacvicar@suse.de" date="1605009600">- Update to version 0.6.3+git.1604843676.67f4f2aa:
  * Revert adding of forward device parameter for networks
  * Add .terraform to .gitignore
  * Tubleweed -&gt; Tumbleweed
  * Example: Use the OpenStack image as it supports cloud-init
  * Tubleweed -&gt; Tumbleweed
  * Fix channel type for qemu-guest-agent
  * Improve terraform v0.13 migration doc
  * CONTRIBUTING.md: process for schema changes
  * CONTRIBUTING.md: mention testcases reproducing an issue
  * Remove unused script
  * Delete setup-host script not longer needed
  * Remove unnecessary mknod /dev/kvm already present in Focal
  * Assume this is not longer an issue
  * Upgrade go to 1.13.x
  * Comment which network attributes require ForceNew
  * Do not run tests twice
  * Upgrade Travis environment
  * Restrict the network mutex to network definition
  * go fmt
  * Force creation of network when we can't update
  * Do not allow defining networks in parallel
  * Test case to reproduce issue #703
  * Revert "Merge pull request #740 from vmorris/master"
  * Fix pty console integration tests
  * Add missing link to libvirt_pool documentation
  * add more info to migration doc
  * adapt toc
  * Add documentation for v13
  * Init example for TF13
  * network: Trim the bridge name to 15 characters
  * Fix gofmt errors
  * Implement network detection for static IPs
  * Remove unused function and variables
  * Even an isolated network has dhcp
  * Make static IP addresses permanent across reboots
  * Update README.md
  * Listen only to localhost
  * Adjust generated dhcp to match libvirt limitation of max 65535 addresses
  * Add tubleweed example</changelog>
  <changelog author="dmacvicar@suse.de" date="1605009601">- Install also in /usr/share/terraform to comply with v0.13
  provider installation path.
  https://www.terraform.io/docs/commands/cli-config.html#provider-installation</changelog>
  <changelog author="dmueller@suse.com" date="1609934400">- spec-cleaner run</changelog>
  <changelog author="hello@anthonyrabbito.com" date="1613217600">- Added if condition in spec if on a SUSE version use mkisofs, instead of genisoimage</changelog>
  <changelog author="paolo.invernizzi@suse.com" date="1736251200">- Update to version 0.8.1+git.1729332308.1cd90b7</changelog>
  <changelog author="paolo.invernizzi@suse.com" date="1736856000">- Apply a patch with the following changes:
  * https://github.com/dmacvicar/terraform-provider-libvirt/pull/1144 (restore error handling for network operations)
  * An additional check to consider a network interface as not ready to be used if it has only link-local IPv6 addresses</changelog>
  <changelog author="paolo.invernizzi@suse.com" date="1741089600">- Update to version 0.8.3+git.1741083459.5d70006</changelog>
</package>
</otherdata>