<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Updates on denis256</title><link>https://denis256.dev/updates/</link><description>Recent content in Updates on denis256</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 15 Nov 2026 07:07:20 +0000</lastBuildDate><atom:link href="https://denis256.dev/updates/index.xml" rel="self" type="application/rss+xml"/><item><title>opentelemetry-java This Week: Stable Declarative Config API and a Jaeger Sampler Fix</title><link>https://denis256.dev/updates/opentelemetry-java-declarative-config-stable-jaeger-sampler-fix/</link><pubDate>Sun, 15 Nov 2026 07:07:20 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-java-declarative-config-stable-jaeger-sampler-fix/</guid><description>&lt;p&gt;Opentelemetry-java, the Java SDK and API for OpenTelemetry, had a busy week. Seven commits landed, touching 472 files, and the headline work is clear: three declarative config classes moved to stable API, config parsing became pluggable, and the Jaeger remote sampler got a real bug fix. Everything below comes from the &lt;a href="https://github.com/open-telemetry/java-opentelemetry"&gt;main branch&lt;/a&gt; activity of the last seven days on &lt;a href="https://github.com/open-telemetry/opentelemetry-java"&gt;open-telemetry/opentelemetry-java&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>otel-arrow Go v0.60.2: Dependency Bump Release</title><link>https://denis256.dev/updates/otel-arrow-go-v0-60-2-dependency-updates/</link><pubDate>Sun, 15 Nov 2026 07:02:10 +0000</pubDate><guid>https://denis256.dev/updates/otel-arrow-go-v0-60-2-dependency-updates/</guid><description>&lt;p&gt;The otel-arrow Go module got a small maintenance release on November 2, 2026. Tag &lt;code&gt;go/v0.60.2&lt;/code&gt; follows &lt;code&gt;go/v0.60.1&lt;/code&gt; and contains no new features or bug fixes. The whole point of this release is keeping the Go dependencies current.&lt;/p&gt;
&lt;p&gt;If you consume the otel-arrow Go packages, this is a routine version bump. Nothing in the release notes changes behavior.&lt;/p&gt;</description></item><item><title>opentelemetry-collector-releases: Windows Arm64 Builds for otelcol-k8s and a Dependency Week</title><link>https://denis256.dev/updates/opentelemetry-collector-releases-otelcol-k8s-windows-binaries/</link><pubDate>Sat, 14 Nov 2026 07:12:25 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-collector-releases-otelcol-k8s-windows-binaries/</guid><description>&lt;p&gt;I looked at the last week of commits in &lt;a href="https://github.com/open-telemetry/opentelemetry-collector-releases"&gt;opentelemetry-collector-releases&lt;/a&gt;, the repo that packages the OpenTelemetry Collector distributions. The interesting change for operators is &lt;a href="https://github.com/open-telemetry/opentelemetry-collector-releases/pull/1750"&gt;Windows binaries for otelcol-k8s on 386 and arm64&lt;/a&gt;. The rest is routine but healthy dependency maintenance across all the Docker image builds.&lt;/p&gt;</description></item><item><title>OpenTelemetry .NET Instrumentation v1.19.0: Kafka Span Fix and Runtime Async Support</title><link>https://denis256.dev/updates/opentelemetry-dotnet-instrumentation-v1-19-0-release/</link><pubDate>Sat, 14 Nov 2026 07:02:19 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-dotnet-instrumentation-v1-19-0-release/</guid><description>&lt;p&gt;OpenTelemetry .NET Instrumentation v1.19.0 shipped on November 4, 2026. The two changes most likely to matter in production are a fix for unfinished Kafka &lt;code&gt;ProduceAsync&lt;/code&gt; spans and new instrumentation support for methods compiled with the experimental .NET runtime async feature.&lt;/p&gt;
&lt;p&gt;The full release notes and downloads are on the &lt;a href="https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/releases/tag/v1.19.0"&gt;GitHub release page&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>opentofu-schema This Week: KMS Encryption Attributes and Submodule Docs Click</title><link>https://denis256.dev/updates/opentofu-schema-encryption-attributes-and-submodule-docs-click/</link><pubDate>Fri, 13 Nov 2026 07:08:06 +0000</pubDate><guid>https://denis256.dev/updates/opentofu-schema-encryption-attributes-and-submodule-docs-click/</guid><description>&lt;p&gt;Last week was quiet but useful for &lt;a href="https://github.com/opentofu/opentofu-schema"&gt;opentofu-schema&lt;/a&gt;, the schema library behind OpenTofu editor tooling. Two merged pull requests landed: one teaches the schema about new KMS encryption attributes coming in OpenTofu 1.12.4, the other fixes docs links for modules with submodules. Both matter if you edit OpenTofu in an IDE.&lt;/p&gt;</description></item><item><title>OpenTofu v1.13.8 - Version Flag and State Encryption Fixes</title><link>https://denis256.dev/updates/opentofu-v1-13-8-bug-fix-release/</link><pubDate>Fri, 13 Nov 2026 07:02:17 +0000</pubDate><guid>https://denis256.dev/updates/opentofu-v1-13-8-bug-fix-release/</guid><description>&lt;p&gt;OpenTofu v1.13.8 shipped on November 4, 2026 as a small bug fix release. Two fixes stand out: the &lt;code&gt;-v&lt;/code&gt; short option works again as an alias for &lt;code&gt;version&lt;/code&gt; and &lt;code&gt;--version&lt;/code&gt;, and OpenTofu no longer panics when the state encryption configuration is invalid. This is a full release, not a prerelease.&lt;/p&gt;</description></item><item><title>Fetch drops a logging dependency and removes release asset tests</title><link>https://denis256.dev/updates/fetch-logging-dependency-and-release-test-cleanup/</link><pubDate>Thu, 12 Nov 2026 07:21:51 +0000</pubDate><guid>https://denis256.dev/updates/fetch-logging-dependency-and-release-test-cleanup/</guid><description>&lt;p&gt;&lt;a href="https://github.com/gruntwork-io/fetch"&gt;Fetch&lt;/a&gt;, a CLI for downloading files, folders, and release assets from GitHub and GitLab, dropped its shared logging helper this week. Two maintenance commits on &lt;code&gt;master&lt;/code&gt; also removed tests that depended on an external release fixture. For users and contributors, the useful details are how Fetch now configures logging and which download checks disappeared.&lt;/p&gt;</description></item><item><title>OpenTelemetry Semantic Conventions v1.45.0 - Stable RPC Spans</title><link>https://denis256.dev/updates/semantic-conventions-v1-45-0-stable-rpc-spans/</link><pubDate>Thu, 12 Nov 2026 07:16:01 +0000</pubDate><guid>https://denis256.dev/updates/semantic-conventions-v1-45-0-stable-rpc-spans/</guid><description>&lt;p&gt;OpenTelemetry semantic-conventions &lt;code&gt;v1.45.0&lt;/code&gt; was published on November 2, 2026. RPC spans and call duration metrics are now stable, including gRPC and Apache Dubbo. It is a stable release.&lt;/p&gt;</description></item><item><title>opentelemetry-operator Helm Chart 0.128.0 - Ruby Autoinstrumentation</title><link>https://denis256.dev/updates/opentelemetry-operator-helm-chart-0-128-0-ruby-instrumentation/</link><pubDate>Wed, 11 Nov 2026 07:02:07 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-operator-helm-chart-0-128-0-ruby-instrumentation/</guid><description>&lt;p&gt;The opentelemetry-operator Helm chart version 0.128.0 shipped on October 28, 2026. It is the chart that deploys the OpenTelemetry Operator on Kubernetes, and this release adds one user facing feature: support for Ruby autoinstrumentation. The chart is stable, not a prerelease.&lt;/p&gt;</description></item><item><title>open-telemetry/community This Week: Emeritus Script Fixes and Link Check Cleanup</title><link>https://denis256.dev/updates/opentelemetry-community-emeritus-script-and-link-check-fixes/</link><pubDate>Tue, 10 Nov 2026 07:05:38 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-community-emeritus-script-and-link-check-fixes/</guid><description/></item><item><title>OpenTelemetry .NET Instrumentation v1.18.0 - OpAMP Plugin Reporting and a Profiler Breaking Change</title><link>https://denis256.dev/updates/opentelemetry-dotnet-instrumentation-v1-18-0-release/</link><pubDate>Tue, 10 Nov 2026 07:02:57 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-dotnet-instrumentation-v1-18-0-release/</guid><description>&lt;p&gt;OpenTelemetry .NET Instrumentation v1.18.0 was published on October 27, 2026. This release extends the experimental OpAMP plugin support, adds scripts for assembly conflicts, and fixes SqlClient tracing gaps. It also contains one breaking change for continuous profiler exporters.&lt;/p&gt;</description></item><item><title>OpenTofu This Week: Plan Snapshot Fixes, State Bug Backports and a New Version Output</title><link>https://denis256.dev/updates/opentofu-week-plan-snapshot-and-state-fixes/</link><pubDate>Mon, 09 Nov 2026 07:08:19 +0000</pubDate><guid>https://denis256.dev/updates/opentofu-week-plan-snapshot-and-state-fixes/</guid><description>&lt;p&gt;I looked at the last week of commits in &lt;a href="https://github.com/opentofu/opentofu"&gt;opentofu/opentofu&lt;/a&gt;, the open source Terraform fork. Ten commits landed across 64 files, with two state handling bugs fixed and backported to the 1.12 and 1.13 branches, a plan snapshot fix, and a small user visible change: &lt;code&gt;tofu version&lt;/code&gt; now prints module versions. Here is what matters if you run OpenTofu in production.&lt;/p&gt;</description></item><item><title>kubernetes-client/java v28.0.0 - Kubernetes 1.37 Support and Informer Improvements</title><link>https://denis256.dev/updates/kubernetes-client-java-v28-0-0-release-notes/</link><pubDate>Mon, 09 Nov 2026 07:02:22 +0000</pubDate><guid>https://denis256.dev/updates/kubernetes-client-java-v28-0-0-release-notes/</guid><description>&lt;p&gt;The kubernetes-client/java project published v28.0.0 on October 27, 2026. The headline change is support for Kubernetes 1.37: the client models were regenerated from the release-1.37 API. Several library dependency updates ride along with it. This is a stable release, not a prerelease.&lt;/p&gt;
&lt;p&gt;The full release notes and downloads are on the &lt;a href="https://github.com/kubernetes-client/java/releases/tag/v28.0.0"&gt;GitHub release page&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>semantic-conventions v1.45.0 Week: Span Type Renames, HPA Attribute Fix and v2 Entity Cleanup</title><link>https://denis256.dev/updates/semantic-conventions-v1-45-span-type-renames-and-v2-entity-cleanup/</link><pubDate>Sun, 08 Nov 2026 07:09:53 +0000</pubDate><guid>https://denis256.dev/updates/semantic-conventions-v1-45-span-type-renames-and-v2-entity-cleanup/</guid><description>&lt;p&gt;&lt;a href="https://github.com/open-telemetry/semantic-conventions"&gt;open-telemetry/semantic-conventions&lt;/a&gt; is the shared registry of attribute, metric, span and entity names used across OpenTelemetry. In the last week it prepared v1.45.0 and landed several breaking edits. The headline is a rename of span types to a single &lt;code&gt;{area}.{kind}.{name}&lt;/code&gt; pattern.&lt;/p&gt;</description></item><item><title>shared-workflows v0.24.0 - Automatic Copilot reviews for Go</title><link>https://denis256.dev/updates/shared-workflows-v0-24-0-copilot-reviews-release/</link><pubDate>Sun, 08 Nov 2026 07:05:31 +0000</pubDate><guid>https://denis256.dev/updates/shared-workflows-v0-24-0-copilot-reviews-release/</guid><description>&lt;p&gt;OpenTelemetry shared-workflows v0.24.0, published on October 26, 2026, enables automatic Copilot reviews for Go repositories. The release also changes how Copilot feedback passes back to authors, makes pull request authors easier to identify, and skips the FOSSA check in forks.&lt;/p&gt;</description></item><item><title>opentelemetry-python: Sampler Tracestate Fix, View Unit Matching and Byte Truncation</title><link>https://denis256.dev/updates/opentelemetry-python-sampler-tracestate-and-attribute-fixes/</link><pubDate>Sat, 07 Nov 2026 07:10:16 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-python-sampler-tracestate-and-attribute-fixes/</guid><description>&lt;p&gt;&lt;a href="https://github.com/open-telemetry/opentelemetry-python"&gt;opentelemetry-python&lt;/a&gt; is the Python API and SDK for OpenTelemetry. Six commits landed in the last week, and the headline is &lt;a href="https://github.com/open-telemetry/opentelemetry-python/pull/5579"&gt;a fix so samplers actually receive the parent tracestate&lt;/a&gt;. The rest are small spec conformance and robustness fixes.&lt;/p&gt;</description></item><item><title>opentelemetry-opamp-client 0.5b0: Pure Python UUIDv7 Replaces uuid-utils</title><link>https://denis256.dev/updates/opentelemetry-opamp-client-0-5b0-python-release/</link><pubDate>Sat, 07 Nov 2026 07:02:00 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-opamp-client-0-5b0-python-release/</guid><description>&lt;p&gt;The maintainers of opentelemetry-python-contrib published opentelemetry-opamp-client 0.5b0 on October 26, 2026. It is a small dependency release: the OpAMP client no longer uses &lt;code&gt;uuid-utils&lt;/code&gt;, and the maintainers replaced it with a pure Python UUIDv7 backport taken from CPython.&lt;/p&gt;</description></item><item><title>opentelemetry-dart: GitHub Actions Bumps and Security Workflow Updates</title><link>https://denis256.dev/updates/opentelemetry-dart-github-actions-and-security-workflow-bumps/</link><pubDate>Fri, 06 Nov 2026 07:06:07 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-dart-github-actions-and-security-workflow-bumps/</guid><description>&lt;p&gt;The &lt;a href="https://github.com/open-telemetry/opentelemetry-dart"&gt;opentelemetry-dart&lt;/a&gt; SDK for Dart had a slow week. Exactly one commit landed in the last seven days, and it touches no Dart code at all. The change is still worth a look if you copy CI patterns from this repo, since it updates pinned security tooling in three workflow files. I read the diff so you do not have to.&lt;/p&gt;</description></item><item><title>Kubernetes This Week: Kubelet Volume Checkpoints, ResourceQuota Fix and DRA GA</title><link>https://denis256.dev/updates/kubernetes-this-week-kubelet-volume-checkpoints-and-fixes/</link><pubDate>Thu, 05 Nov 2026 07:10:19 +0000</pubDate><guid>https://denis256.dev/updates/kubernetes-this-week-kubelet-volume-checkpoints-and-fixes/</guid><description>&lt;p&gt;&lt;a href="https://github.com/kubernetes/kubernetes"&gt;Kubernetes&lt;/a&gt; is the container orchestrator that most of us run in some form. I looked at 183 commits and 15 merged pull requests from the last week. The headline is kubelet work on checkpointing pod volumes, with a few real bug fixes next to it.&lt;/p&gt;</description></item><item><title>terragrunt-infrastructure-catalog-example v1.2.0: Terragrunt 1.1.0 and a Catalog Ignore File</title><link>https://denis256.dev/updates/terragrunt-catalog-example-v1-2-0-release/</link><pubDate>Thu, 05 Nov 2026 07:02:12 +0000</pubDate><guid>https://denis256.dev/updates/terragrunt-catalog-example-v1-2-0-release/</guid><description>&lt;p&gt;The terragrunt-infrastructure-catalog-example repo published v1.2.0 on October 22, 2026. The release moves the catalog to Terragrunt 1.1.0 and adds a &lt;code&gt;.terragrunt-catalog-ignore&lt;/code&gt; file so the example works cleanly with the Terragrunt catalog command. It is a regular release, not a prerelease.&lt;/p&gt;
&lt;p&gt;The full release notes and downloads are on the &lt;a href="https://github.com/gruntwork-io/terragrunt-infrastructure-catalog-example/releases/tag/v1.2.0"&gt;GitHub release page&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>OpenTelemetry Specification v1.62.0 - OTLP timeout and shutdown rules</title><link>https://denis256.dev/updates/opentelemetry-specification-v1-62-0-release-timeout-rules/</link><pubDate>Wed, 04 Nov 2026 07:04:42 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-specification-v1-62-0-release-timeout-rules/</guid><description>&lt;p&gt;OpenTelemetry Specification &lt;code&gt;v1.62.0&lt;/code&gt; was published on October 22, 2026. Its most useful clarification for operators is that the OTLP exporter timeout covers a whole batch export, including every request attempt and wait between retries.&lt;/p&gt;</description></item><item><title>opentelemetry-php This Week: Per Package Changelogs, Config Validation, and a CI Segfault Fix</title><link>https://denis256.dev/updates/opentelemetry-php-changelogs-and-config-validation-week/</link><pubDate>Tue, 03 Nov 2026 07:08:38 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-php-changelogs-and-config-validation-week/</guid><description>&lt;p&gt;The &lt;a href="https://github.com/open-telemetry/opentelemetry-php"&gt;opentelemetry-php&lt;/a&gt; SDK saw six merged pull requests in the last week, with 112 files changed across the tree. The headline work is a new per package changelog system backed by a CI check, plus tighter validation in the declarative config SDK as it moves toward a release candidate. If you maintain code that depends on any of the split packages, the changelog change affects how you should read upcoming releases.&lt;/p&gt;</description></item><item><title>opentelemetry-exporter-otlp-metrics 0.15.0: Histogram Env Var and Redirect Fixes</title><link>https://denis256.dev/updates/opentelemetry-exporter-otlp-metrics-v0-15-0-release/</link><pubDate>Tue, 03 Nov 2026 07:02:11 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-exporter-otlp-metrics-v0-15-0-release/</guid><description>&lt;p&gt;The opentelemetry-ruby project published opentelemetry-exporter-otlp-metrics 0.15.0 on October 20, 2026. It is a small release with two changes that both matter if you run the OTLP metrics exporter in production: configurable default histogram aggregation and working HTTP redirect handling.&lt;/p&gt;</description></item><item><title>opentelemetry-announcements: Bootstrap, Checks, and Destination Config</title><link>https://denis256.dev/updates/opentelemetry-announcements-bootstrap-and-destination-config/</link><pubDate>Mon, 02 Nov 2026 07:03:55 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-announcements-bootstrap-and-destination-config/</guid><description>&lt;p&gt;The OpenTelemetry project now runs a dedicated announcements repo: &lt;a href="https://github.com/open-telemetry/opentelemetry-announcements"&gt;opentelemetry-announcements&lt;/a&gt;, a small tool that publishes project news to Bluesky, Mastodon, LinkedIn, Slack, and Google Groups from versioned YAML files. All three commits this window landed within three days, so this week is effectively the project taking shape. The headline change is a &lt;code&gt;config.yaml&lt;/code&gt; that defines named destinations per channel and lets any announcement skip them.&lt;/p&gt;</description></item><item><title>opentelemetry-dotnet core-1.20.1: Concurrency, Logging, and OTLP Fixes</title><link>https://denis256.dev/updates/opentelemetry-dotnet-core-1-20-1-release-fixes/</link><pubDate>Mon, 02 Nov 2026 07:02:00 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-dotnet-core-1-20-1-release-fixes/</guid><description>&lt;p&gt;opentelemetry-dotnet shipped core-1.20.1 on October 20, 2026. It is a patch release, but a busy one. The headline fix is a possible race condition on ARM64 that could record measurements incorrectly when multiple threads record the first measurement with no tags.&lt;/p&gt;
&lt;p&gt;The full notes and package downloads are on the &lt;a href="https://github.com/open-telemetry/opentelemetry-dotnet/releases/tag/core-1.20.1"&gt;GitHub release page&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Terragrunt v1.2.0: base64gzip Output Change, S3 Policy Fix and Catalog Format</title><link>https://denis256.dev/updates/terragrunt-v1-2-0-release-notes-breaking-changes/</link><pubDate>Sun, 01 Nov 2026 07:02:33 +0000</pubDate><guid>https://denis256.dev/updates/terragrunt-v1-2-0-release-notes-breaking-changes/</guid><description>&lt;p&gt;Looking for what changed in Terragrunt v1.2.0? The release was published on October 21, 2026 and is a large minor release. The two items to check before upgrading are the new &lt;code&gt;base64gzip()&lt;/code&gt; output and the removal of the S3 &lt;code&gt;RootAccess&lt;/code&gt; bucket policy statement.&lt;/p&gt;</description></item><item><title>semantic-conventions-java This Week: Weaver 0.28, Gradle 9.8.2 and Pinned Action Bumps</title><link>https://denis256.dev/updates/semantic-conventions-java-gradle-weaver-action-bumps/</link><pubDate>Sat, 31 Oct 2026 07:09:48 +0000</pubDate><guid>https://denis256.dev/updates/semantic-conventions-java-gradle-weaver-action-bumps/</guid><description>&lt;p&gt;&lt;a href="https://github.com/open-telemetry/semantic-conventions-java"&gt;semantic-conventions-java&lt;/a&gt; is the OpenTelemetry repo that publishes the Java artifacts for the semantic conventions. Its week was two Renovate merges: a Weaver bump, a Gradle patch release and a batch of pinned GitHub Actions. There is no change to the generated Java API in this window.&lt;/p&gt;</description></item><item><title>otel-arrow go/v0.60.1 - Go and HTTP/2 dependency updates</title><link>https://denis256.dev/updates/otel-arrow-go-v0-60-1-dependency-updates/</link><pubDate>Sat, 31 Oct 2026 07:04:36 +0000</pubDate><guid>https://denis256.dev/updates/otel-arrow-go-v0-60-1-dependency-updates/</guid><description>&lt;p&gt;otel-arrow &lt;code&gt;go/v0.60.1&lt;/code&gt;, published on October 20, 2026, updates Go dependencies, including security updates for the toolchain and HTTP/2 networking code. The release also brings CBOR decoding corrections that deserve attention when reviewing dependency behavior. GitHub does not mark this release as a prerelease.&lt;/p&gt;</description></item><item><title>opentelemetry-go-build-tools This Week: Precise Failing Job Links in issuegenerator</title><link>https://denis256.dev/updates/opentelemetry-go-build-tools-issuegenerator-failing-job-links/</link><pubDate>Fri, 30 Oct 2026 07:20:56 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-go-build-tools-issuegenerator-failing-job-links/</guid><description>&lt;p&gt;I looked at the last week of commits in &lt;a href="https://github.com/open-telemetry/opentelemetry-go-build-tools"&gt;opentelemetry-go-build-tools&lt;/a&gt;, the repo that holds the CI helper tools for the OpenTelemetry Go project. The headline change is in issuegenerator: when a build fails, generated issues now link to each failing job instead of the generic workflow run. Around that, Renovate landed 14 dependency pull requests and little else moved.&lt;/p&gt;</description></item><item><title>OpenTelemetry eBPF Instrumentation v0.15.2 - BPF loading and Collector upgrades</title><link>https://denis256.dev/updates/opentelemetry-ebpf-instrumentation-v0-15-2-collector-upgrades/</link><pubDate>Fri, 30 Oct 2026 07:06:37 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-ebpf-instrumentation-v0-15-2-collector-upgrades/</guid><description>&lt;p&gt;OpenTelemetry eBPF Instrumentation v0.15.2, published on October 16, 2026, restores BPF program loading after verifier failures blocked v0.15.0. It also fixes artifact version selection after the v0.15.1 build failed. Collector users and embedders should review the module and configuration changes alongside those fixes.&lt;/p&gt;</description></item><item><title>otel collector contrib: New OTTL UTF8 Converter, Cosign Verification, and Prometheus Fixes</title><link>https://denis256.dev/updates/otel-collector-contrib-ottl-utf8-and-cosign-changes/</link><pubDate>Thu, 29 Oct 2026 07:11:34 +0000</pubDate><guid>https://denis256.dev/updates/otel-collector-contrib-ottl-utf8-and-cosign-changes/</guid><description>&lt;p&gt;I looked at the last week of commits in &lt;a href="https://github.com/open-telemetry/opentelemetry-collector-contrib"&gt;opentelemetry-collector-contrib&lt;/a&gt;, the collection of receivers, processors, and exporters around the OpenTelemetry Collector. 148 commits landed. The headline items are a new experimental &lt;code&gt;ToValidUTF8&lt;/code&gt; OTTL converter, a Cosign package verifier for the OpAMP supervisor, and a batch of performance work in the prometheus receiver.&lt;/p&gt;</description></item><item><title>OpenTelemetry Collector Builder v0.163.0 - Choose resource detectors</title><link>https://denis256.dev/updates/opentelemetry-collector-releases-cmd-builder-v0-163-0-detectors/</link><pubDate>Thu, 29 Oct 2026 07:07:34 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-collector-releases-cmd-builder-v0-163-0-detectors/</guid><description>&lt;p&gt;OpenTelemetry Collector Builder &lt;code&gt;cmd/builder/v0.163.0&lt;/code&gt; was published on October 16, 2026. Its main builder change is &lt;code&gt;dist.resource.detection.detectors&lt;/code&gt;, which lets custom distributions select a smaller set of resource detectors through generated Go build tags. GitHub does not mark this release as a prerelease.&lt;/p&gt;</description></item><item><title>opentofu-schema: Output Type Inference Fix for Module Outputs</title><link>https://denis256.dev/updates/opentofu-schema-module-output-type-inference-fix/</link><pubDate>Wed, 28 Oct 2026 07:03:11 +0000</pubDate><guid>https://denis256.dev/updates/opentofu-schema-module-output-type-inference-fix/</guid><description>&lt;p&gt;The opentofu-schema project builds the schema that editors use to understand OpenTofu configuration. This week it had one small commit, but it touches a real edge case: module outputs that have no declared type. If you write &lt;code&gt;.tofu&lt;/code&gt; files and rely on completion and hover, it is worth a short read.&lt;/p&gt;</description></item><item><title>pipelines-workflows v4.31.0: Error Hooks and Clearer Terragrunt Failures</title><link>https://denis256.dev/updates/pipelines-workflows-v4-31-0-error-hooks/</link><pubDate>Wed, 28 Oct 2026 07:02:15 +0000</pubDate><guid>https://denis256.dev/updates/pipelines-workflows-v4-31-0-error-hooks/</guid><description>&lt;p&gt;pipelines-workflows v4.31.0 shipped on October 15, 2026. The headline change is error hooks: hooks that run when a &lt;code&gt;plan&lt;/code&gt; or &lt;code&gt;apply&lt;/code&gt; fails, matched against the error text. The default Pipelines CLI also moved to v0.69.1.&lt;/p&gt;
&lt;p&gt;The full release notes and downloads are on the &lt;a href="https://github.com/gruntwork-io/pipelines-workflows/releases/tag/v4.31.0"&gt;GitHub release page&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>opentelemetry-proto Weekly: Tooling Dependency Bumps Only</title><link>https://denis256.dev/updates/opentelemetry-proto-dependency-bumps-weekly/</link><pubDate>Tue, 27 Oct 2026 07:05:09 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-proto-dependency-bumps-weekly/</guid><description>&lt;p&gt;&lt;a href="https://github.com/open-telemetry/opentelemetry-proto"&gt;opentelemetry-proto&lt;/a&gt; defines the OTLP protocol that most OpenTelemetry SDKs and collectors speak. This week was quiet: three commits, all dependency bumps from renovate, and no changes to the &lt;code&gt;.proto&lt;/code&gt; files. If you generate code from these definitions, nothing changes for you.&lt;/p&gt;</description></item><item><title>shared-workflows v0.20.0: Dashboard Queueing and Storage Changes</title><link>https://denis256.dev/updates/shared-workflows-v0-20-0-dashboard-changes-release/</link><pubDate>Tue, 27 Oct 2026 07:02:15 +0000</pubDate><guid>https://denis256.dev/updates/shared-workflows-v0-20-0-dashboard-changes-release/</guid><description>&lt;p&gt;open-telemetry/shared-workflows published v0.20.0 on October 13, 2026. It is not a prerelease. The release is mostly about the pull request dashboard: cleaner separation between live refreshes and maintenance, isolated Git checkouts, and a new snapshot-only storage mode.&lt;/p&gt;
&lt;p&gt;The full release notes and assets are on the &lt;a href="https://github.com/open-telemetry/shared-workflows/releases/tag/v0.20.0"&gt;GitHub release page&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>opentelemetry-benchmarks Weekly: Ubuntu 26.04 Containers and a Dashboard Publishing Fix</title><link>https://denis256.dev/updates/opentelemetry-benchmarks-ci-bumps-dashboard-fix/</link><pubDate>Mon, 26 Oct 2026 07:09:20 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-benchmarks-ci-bumps-dashboard-fix/</guid><description>&lt;p&gt;I looked at the last week of commits in &lt;a href="https://github.com/open-telemetry/opentelemetry-benchmarks"&gt;opentelemetry-benchmarks&lt;/a&gt;, the project that benchmarks OpenTelemetry SDK performance from .NET, Rust, and other harnesses on bare metal runners. Eight commits landed, and only one of them touches benchmark code. The rest are dependency maintenance, plus one real fix that unblocks dashboard publishing.&lt;/p&gt;</description></item><item><title>opentelemetry-go-compile-instrumentation v1.2.0: Cassandra, Kafka, and SQL Instrumentation</title><link>https://denis256.dev/updates/opentelemetry-go-compile-instrumentation-v1-2-0-release/</link><pubDate>Mon, 26 Oct 2026 07:02:07 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-go-compile-instrumentation-v1-2-0-release/</guid><description>&lt;p&gt;opentelemetry-go-compile-instrumentation v1.2.0 shipped on October 12, 2026. This release adds compile time instrumentation for three new sources: the gocql Cassandra driver, kafka-go consumers, and connector based sql.OpenDB calls. It also fixes a gRPC bug where skipped RPCs touched the caller span. The full details are on the &lt;a href="https://github.com/open-telemetry/opentelemetry-go-compile-instrumentation/releases/tag/v1.2.0"&gt;GitHub release page&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>opentelemetry-android 1.9.0: Instrumentation Uninstall, Session Sampling, and a Config Default Flip</title><link>https://denis256.dev/updates/opentelemetry-android-1-9-0-uninstall-and-session-sampling/</link><pubDate>Sun, 25 Oct 2026 07:03:42 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-android-1-9-0-uninstall-and-session-sampling/</guid><description>&lt;p&gt;I looked at the last week of commits in &lt;a href="https://github.com/open-telemetry/opentelemetry-android"&gt;opentelemetry-android&lt;/a&gt;, the OpenTelemetry android agent for RUM telemetry. 21 commits landed, covering the v1.8.0 release, the version bump to v1.9.0 on main, and a batch of changes worth knowing about before you upgrade. The headline items: instrumentations can now be uninstalled at runtime, session sampling got a structural rework, and SDK initialization events are off by default.&lt;/p&gt;</description></item><item><title>opentelemetry-android v1.8.0: Session Fixes, Agent DSL Controls, and a Migration Note</title><link>https://denis256.dev/updates/opentelemetry-android-v1-8-0-release/</link><pubDate>Sun, 25 Oct 2026 07:02:04 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-android-v1-8-0-release/</guid><description>&lt;p&gt;opentelemetry-android v1.8.0 was published on October 22, 2026. It builds on OpenTelemetry Java Instrumentation 2.32.0 and the Java core 1.66.0, and it changes two behaviors you may notice after upgrade: SDK initialization events are off by default, and session ID lookups no longer keep background sessions alive. Full notes are on the &lt;a href="https://github.com/open-telemetry/opentelemetry-android/releases/tag/v1.8.0"&gt;GitHub release page&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>terragrunt-engine-go: A New flight-sync Example Engine</title><link>https://denis256.dev/updates/terragrunt-engine-go-flight-sync-example/</link><pubDate>Sat, 24 Oct 2026 07:03:54 +0000</pubDate><guid>https://denis256.dev/updates/terragrunt-engine-go-flight-sync-example/</guid><description>&lt;p&gt;I looked at the last week of commits in &lt;a href="https://github.com/gruntwork-io/terragrunt-engine-go"&gt;terragrunt-engine-go&lt;/a&gt;, the Go library home for Terragrunt Engine implementations and examples. Two commits landed, 21 files changed, about 1274 new lines. The headline is &lt;a href="https://github.com/gruntwork-io/terragrunt-engine-go/pull/73"&gt;the flight ID and token feature (#73)&lt;/a&gt;, which teaches engines to share one credential across all processes of a Terragrunt invocation.&lt;/p&gt;</description></item><item><title>boilerplate v0.17.0: Static Linux Binaries and Two Rendering Fixes</title><link>https://denis256.dev/updates/boilerplate-v0-17-0-release/</link><pubDate>Sat, 24 Oct 2026 07:02:09 +0000</pubDate><guid>https://denis256.dev/updates/boilerplate-v0-17-0-release/</guid><description>&lt;p&gt;boilerplate v0.17.0 landed on October 14, 2026. The change that will matter most to anyone deploying the tool: the linux/amd64 binary is now statically linked because cgo is disabled during the build. Alongside that, this release fixes two render time bugs and refreshes a long list of Go dependencies.&lt;/p&gt;
&lt;p&gt;The full release notes and downloads are on the &lt;a href="https://github.com/gruntwork-io/boilerplate/releases/tag/v0.17.0"&gt;GitHub release page&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>opentelemetry.io This Week: Pekko Docs, OBI v0.15.2, and a Big Localization Week</title><link>https://denis256.dev/updates/opentelemetry-io-docs-week-localization-and-pekko/</link><pubDate>Fri, 23 Oct 2026 01:11:10 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-io-docs-week-localization-and-pekko/</guid><description>&lt;p&gt;The &lt;a href="https://github.com/open-telemetry/opentelemetry.io"&gt;opentelemetry.io&lt;/a&gt; site is the documentation hub for OpenTelemetry, and this week it moved fast: 126 commits, 367 files changed, about 15.6k insertions. The useful bits for users are new Apache Pekko docs for Java, refreshed OBI documentation for v0.15.2, and a blog post on security hardening. Most of the rest is localization work across three languages.&lt;/p&gt;</description></item><item><title>opentelemetry-rust 0.33.1: OTLP Log and Metric Exporters Go Stable</title><link>https://denis256.dev/updates/opentelemetry-rust-0-33-1-otlp-exporters-stable/</link><pubDate>Fri, 23 Oct 2026 01:04:38 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-rust-0-33-1-otlp-exporters-stable/</guid><description>&lt;p&gt;opentelemetry-rust shipped version 0.33.1 on October 9, 2026. The headline change is short and significant: the OTLP exporters for Logs and Metrics are now stable. No more beta caveats on two of the three OTLP signals in Rust.&lt;/p&gt;</description></item><item><title>OpenTelemetry Java Contrib v1.61.0 - Sampling policy migration</title><link>https://denis256.dev/updates/opentelemetry-java-contrib-v1-61-0-sampling-migration/</link><pubDate>Thu, 22 Oct 2026 08:11:35 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-java-contrib-v1-61-0-sampling-migration/</guid><description>&lt;p&gt;OpenTelemetry Java Contrib v1.61.0, published on October 9, 2026, changes how dynamic control interprets trace sampling values. Existing ratio configurations need a migration: leaving a value of &lt;code&gt;0.5&lt;/code&gt; under &lt;code&gt;trace-sampling&lt;/code&gt; now means 0.5% sampling instead of 50%. This release also changes JMX metric selection and adds a way to detect unread data discarded from disk buffers.&lt;/p&gt;</description></item><item><title>OpenTelemetry Demo restores ad metrics and checks collector overlays</title><link>https://denis256.dev/updates/opentelemetry-demo-collector-fix-and-agent-metrics/</link><pubDate>Thu, 22 Oct 2026 07:19:58 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-demo-collector-fix-and-agent-metrics/</guid><description>&lt;p&gt;&lt;a href="https://github.com/open-telemetry/opentelemetry-demo"&gt;OpenTelemetry Demo&lt;/a&gt;, a distributed application for demonstrating telemetry, fixed a configuration bug that silently dropped ad service metrics. The October 15 to 21 activity also added a check for collector overlays and metrics for the agent, MCP, and chatbot services. These changes matter if you use the demo to test telemetry pipelines or copy its configuration into a fork.&lt;/p&gt;</description></item><item><title>Gruntwork docs v2.4.48 - Cost controls and hook diagnostics</title><link>https://denis256.dev/updates/gruntwork-docs-v2-4-48-cost-controls-release/</link><pubDate>Tue, 20 Oct 2026 07:04:10 +0000</pubDate><guid>https://denis256.dev/updates/gruntwork-docs-v2-4-48-cost-controls-release/</guid><description>&lt;p&gt;Gruntwork docs &lt;code&gt;v2.4.48&lt;/code&gt;, published on October 6, 2026, adds documentation for the Gruntwork provided Infracost hook and its warn and deny cost thresholds. These are the changes I would read first when reviewing cost checks in a pipeline. GitHub marks this documentation release as a regular release, with no prerelease flag.&lt;/p&gt;</description></item><item><title>opentelemetry-swift This Week: Session Sampling, Tracing Bridge Fix, Crash Reporter</title><link>https://denis256.dev/updates/opentelemetry-swift-sampling-and-tracing-bridge-fixes/</link><pubDate>Mon, 19 Oct 2026 07:13:44 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-swift-sampling-and-tracing-bridge-fixes/</guid><description>&lt;p&gt;I looked at the last week of activity in &lt;a href="https://github.com/open-telemetry/opentelemetry-swift"&gt;opentelemetry-swift&lt;/a&gt;, the OpenTelemetry SDK for Swift and iOS. Fourteen commits landed, touching 81 files with about 5,000 insertions. The headline work is in the Sessions instrumentation: sampling decisions are now persisted and shared across signals, so a trace, a log, and a metric recorded in the same session agree on what to keep. There is also a real fix in the Swift tracing bridge and a new crash reporter.&lt;/p&gt;</description></item><item><title>opentelemetry-metrics-api 0.9.0: Global Meter Provider Is Now Opt In</title><link>https://denis256.dev/updates/opentelemetry-ruby-metrics-api-v0-9-0-breaking-change/</link><pubDate>Mon, 19 Oct 2026 07:03:47 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-ruby-metrics-api-v0-9-0-breaking-change/</guid><description>&lt;p&gt;The OpenTelemetry Ruby project shipped opentelemetry-metrics-api 0.9.0 on October 5, 2026. It is a small release with one change that matters: the global meter provider is no longer loaded by default. You now need an explicit require to get it.&lt;/p&gt;</description></item><item><title>OpenTelemetry Dart Packages: A New Design Doc Lays Out the Namespace</title><link>https://denis256.dev/updates/opentelemetry-dart-package-layout-proposal/</link><pubDate>Sun, 18 Oct 2026 07:25:32 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-dart-package-layout-proposal/</guid><description>&lt;p&gt;OpenTelemetry for Dart is still early, and this week the &lt;a href="https://github.com/open-telemetry/opentelemetry-dart"&gt;open-telemetry/opentelemetry-dart&lt;/a&gt; repo shipped exactly one change: a design document. It landed as &lt;a href="https://github.com/open-telemetry/opentelemetry-dart/pull/7"&gt;the package namespaces proposal (#7)&lt;/a&gt;, merged on October 15 as &lt;a href="https://github.com/open-telemetry/opentelemetry-dart/commit/74827c2eb0e7aaa09c14d4144136feb74b28a4ab"&gt;commit 74827c2&lt;/a&gt;. The document now lives at &lt;a href="https://github.com/open-telemetry/opentelemetry-dart/blob/main/docs/design/packages.md"&gt;docs/design/packages.md&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;No code shipped. But for anyone planning to use or contribute to the Dart SDK, this document sets the names and structure that everything else will follow, so it is worth a read now while the shape is still open for discussion.&lt;/p&gt;</description></item><item><title>OpenTelemetry eBPF Instrumentation Helm Chart 0.14.3: App Version v0.14.0</title><link>https://denis256.dev/updates/opentelemetry-ebpf-instrumentation-0-14-3-helm-release/</link><pubDate>Sun, 18 Oct 2026 07:04:08 +0000</pubDate><guid>https://denis256.dev/updates/opentelemetry-ebpf-instrumentation-0-14-3-helm-release/</guid><description>&lt;p&gt;The open-telemetry project published the Helm chart &lt;code&gt;opentelemetry-ebpf-instrumentation-0.14.3&lt;/code&gt; on October 5, 2026. The important change for anyone running the chart is a version bump: the chart now deploys OBI itself at &lt;code&gt;v0.14.0&lt;/code&gt;, up from the previous packaged version. The chart version is &lt;code&gt;0.14.3&lt;/code&gt; and the app version is &lt;code&gt;v0.14.0&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;This is a small, focused release. It is not a prerelease, so it is safe to pin in existing installs.&lt;/p&gt;</description></item><item><title>OpenTofu Registry Weekly: New Providers, Modules, and Version Bumps</title><link>https://denis256.dev/updates/opentofu-registry-week-new-providers-and-bumps/</link><pubDate>Sat, 17 Oct 2026 07:11:48 +0000</pubDate><guid>https://denis256.dev/updates/opentofu-registry-week-new-providers-and-bumps/</guid><description>&lt;p&gt;I looked at the last seven days of commits in the &lt;a href="https://github.com/opentofu/registry"&gt;opentofu/registry&lt;/a&gt; repository, the open registry that serves provider and module metadata for OpenTofu. The repo saw about 300 commits in the window. Most of them are automated version bumps, but a steady stream of new providers and modules landed too, including the Anthropic provider and a Technitium provider. If you pin provider versions, this week probably already touched your lock files.&lt;/p&gt;</description></item><item><title>Database Lab Engine v4.2.1: Safer Clone Upgrades and Hardened Defaults</title><link>https://denis256.dev/updates/database-lab-engine-v4-2-1-release/</link><pubDate>Sat, 17 Oct 2026 07:05:12 +0000</pubDate><guid>https://denis256.dev/updates/database-lab-engine-v4-2-1-release/</guid><description>&lt;p&gt;Database Lab Engine v4.2.1 shipped on October 8, 2026. It is a patch release focused on correctness and hardening: clone upgrades no longer fail on TLS mounted instances, the engine&amp;rsquo;s state file is written atomically, and a background panic no longer kills the whole process. Not a prerelease.&lt;/p&gt;
&lt;p&gt;The full release notes and downloads are on the &lt;a href="https://github.com/postgres-ai/database-lab-engine/releases/tag/v4.2.1"&gt;GitHub release page&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>OpenTofu v1.12.8 Fixes HTTP2 CPU Issue in tofu init</title><link>https://denis256.dev/updates/opentofu-v1-12-8-security-patch-fixes/</link><pubDate>Sat, 17 Oct 2026 07:04:54 +0000</pubDate><guid>https://denis256.dev/updates/opentofu-v1-12-8-security-patch-fixes/</guid><description>&lt;p&gt;OpenTofu v1.12.8 landed on October 14 2026 as a small patch release. The headline item is a security advisory: earlier versions could hit excessive CPU usage when &lt;code&gt;tofu init&lt;/code&gt; connected to an attacker controlled HTTP2 server while installing dependencies. There is one bug fix on top.&lt;/p&gt;</description></item><item><title>kubernetes-client/java v27.0.1: Patch Release with a Cherrypicked Fix</title><link>https://denis256.dev/updates/kubernetes-client-java-v27-0-1-patch-release/</link><pubDate>Fri, 16 Oct 2026 07:03:09 +0000</pubDate><guid>https://denis256.dev/updates/kubernetes-client-java-v27-0-1-patch-release/</guid><description>&lt;p&gt;The Java client for Kubernetes got a patch release on October 14, 2026. &lt;code&gt;kubernetes-client/java&lt;/code&gt; v27.0.1 sits on top of v27.0.0 and ships a small number of changes, all visible on the &lt;a href="https://github.com/kubernetes-client/java/releases/tag/v27.0.1"&gt;GitHub release page&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>terragrunt-engine-terraform v0.1.0: Breaking Change Requires Terragrunt 0.99.0</title><link>https://denis256.dev/updates/terragrunt-engine-terraform-v0-1-0-release/</link><pubDate>Fri, 16 Oct 2026 07:02:56 +0000</pubDate><guid>https://denis256.dev/updates/terragrunt-engine-terraform-v0-1-0-release/</guid><description>&lt;p&gt;The terragrunt-engine-terraform project published v0.1.0 on October 6, 2026. The headline change is a compatibility break: after this release, the engine only works with Terragrunt v0.99.0 or newer. Anyone running an older Terragrunt version should pin the previous engine release instead of upgrading. Full details are on the &lt;a href="https://github.com/gruntwork-io/terragrunt-engine-terraform/releases/tag/v0.1.0"&gt;GitHub release page&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>terragrunt-engine-opentofu v0.2.0: Shared Provider Cache and tf_path</title><link>https://denis256.dev/updates/terragrunt-engine-opentofu-v0-2-0-release/</link><pubDate>Fri, 16 Oct 2026 07:02:38 +0000</pubDate><guid>https://denis256.dev/updates/terragrunt-engine-opentofu-v0-2-0-release/</guid><description>&lt;p&gt;The Terragrunt OpenTofu engine shipped v0.2.0 on October 8, 2026. The headline change: units now share a plugin provider cache, which cuts download time and disk usage when many units use the same providers. Both changes need some setup detail, so here is a quick summary.&lt;/p&gt;</description></item><item><title>Kubernetes Weekly: Deployment Timeout Fixes, StatefulSet Bugs, and kuberc Validation</title><link>https://denis256.dev/updates/kubernetes-weekly-deployment-statefulset-fixes/</link><pubDate>Thu, 15 Oct 2026 09:30:00 +0000</pubDate><guid>https://denis256.dev/updates/kubernetes-weekly-deployment-statefulset-fixes/</guid><description>&lt;p&gt;I looked at the last week of commits in &lt;a href="https://github.com/kubernetes/kubernetes"&gt;kubernetes/kubernetes&lt;/a&gt;, around 115 commits and 968 changed files. Three fixes stand out for anyone running workloads: Deployment rollouts now report timeouts even when ReplicaSet scale down fails, a StatefulSet pod name matching bug is fixed, and kubectl gains better validation around credential plugins. There is also solid hardening work in the apiserver storage layer.&lt;/p&gt;</description></item><item><title>Runbooks v0.25.0 Release: Iframe Exchanges, Linked Defaults, and Behavior Changes</title><link>https://denis256.dev/updates/runbooks-v0-25-0-release-behavior-changes/</link><pubDate>Thu, 08 Oct 2026 09:12:00 +0000</pubDate><guid>https://denis256.dev/updates/runbooks-v0-25-0-release-behavior-changes/</guid><description>&lt;p&gt;gruntwork-io released runbooks v0.25.0 on October 5, 2026. It is a smaller release aimed mostly at runbook authors. The headline change is that pages loaded from the runbook&amp;rsquo;s &lt;code&gt;assets/&lt;/code&gt; folder can now receive input values and set outputs, so they can serve as custom forms or pickers. There are also two behavior changes to review before you upgrade.&lt;/p&gt;
&lt;p&gt;The full release notes and downloads are on the &lt;a href="https://github.com/gruntwork-io/runbooks/releases/tag/v0.25.0"&gt;GitHub release page&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Runbooks v0.24.0: Log Files, Sensitive Outputs, and Three Behavior Changes</title><link>https://denis256.dev/updates/runbooks-v0-24-0-release-stability-changes/</link><pubDate>Wed, 07 Oct 2026 09:15:00 +0000</pubDate><guid>https://denis256.dev/updates/runbooks-v0-24-0-release-stability-changes/</guid><description>&lt;p&gt;Runbooks v0.24.0 landed on GitHub on October 2, 2026. It is a stability and usability release, and it ships three behavior changes that touch existing runbooks. The one most scripts will notice: the &lt;code&gt;log_*&lt;/code&gt; helpers no longer write to stdout, so &lt;code&gt;$(...)&lt;/code&gt; captures stay clean.&lt;/p&gt;
&lt;p&gt;The full notes and downloads are on the &lt;a href="https://github.com/gruntwork-io/runbooks/releases/tag/v0.24.0"&gt;GitHub release page&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>pipelines-workflows v4.30.0: Faster Auth and Better Hook Errors</title><link>https://denis256.dev/updates/pipelines-workflows-v4-30-0-release/</link><pubDate>Tue, 06 Oct 2026 09:15:00 +0000</pubDate><guid>https://denis256.dev/updates/pipelines-workflows-v4-30-0-release/</guid><description>&lt;p&gt;Gruntwork released pipelines-workflows v4.30.0 on October 5, 2026. The headline change is a rewrite of cloud authentication that only reads the configuration it needs, which speeds up consolidated plans and applies in large repositories. The release also improves what you see when a hook fails, and fixes a stale artifact cache bug.&lt;/p&gt;
&lt;p&gt;The full release notes are on the &lt;a href="https://github.com/gruntwork-io/pipelines-workflows/releases/tag/v4.30.0"&gt;GitHub release page&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Starting periodic updates</title><link>https://denis256.dev/updates/starting-periodic-updates/</link><pubDate>Tue, 01 Sep 2026 09:00:00 +0000</pubDate><guid>https://denis256.dev/updates/starting-periodic-updates/</guid><description>&lt;p&gt;Starting today I will post periodic updates on this page.&lt;/p&gt;
&lt;p&gt;Long technical posts stay on &lt;a href="https://blog.denis256.dev/"&gt;blog.denis256.dev&lt;/a&gt;: guides, release notes, ops lessons. This section is for smaller things that do not need a full article:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;what I am working on right now&lt;/li&gt;
&lt;li&gt;open-source changes and releases I took part in&lt;/li&gt;
&lt;li&gt;new projects and experiments&lt;/li&gt;
&lt;li&gt;new posts on the blog worth a mention&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Each update will be a few lines, with links to GitHub or the blog for details.&lt;/p&gt;</description></item></channel></rss>