➔ n8n 2.28.3 Release Notes: Partial Install Recovery
n8n [email protected] was published on June 29, 2026, as a small patch release for operators who run community packages. The key change is a startup guard for cases where a community package install is left in a partial state, which previously could stop n8n from starting. That makes this release more about recovery behavior than new workflow features.
➔ n8n 2.27.5 - Startup Fix for Community Packages
n8n [email protected] was published on June 29, 2026, with a focused startup fix for community package installs. The release prevents a startup failure when a community package is only partially installed, which matters most to operators who run n8n with custom nodes enabled.
➔ ingestr v1.0.49 - Schema Evolution Fixes for BigQuery
ingestr v1.0.49 was published on June 29, 2026, and it is mostly a schema evolution fix release for data pipeline operators. The main user facing change is safer BigQuery merge behavior around integer primary keys, with smaller updates for destination specific type handling and the MongoDB driver. It is not marked as a prerelease.
➔ Unison v0.93.0 - DPI and Layout Fixes
Unison v0.93.0 was published on June 28, 2026, with a practical set of layout, table, dock, and window fixes. The main user impact is better behavior around cached table row heights, dock redraws, Linux frame sizing, and Windows mixed DPI setups.
➔ pandas v3.0.4 - Regression and Bug Fixes
pandas v3.0.4 was published on June 28, 2026, as a stable patch release for the pandas 3.0.x line. The main fix to notice is in DataFrame.to_sql() and read_sql_table() with ADBC engines, where table and schema identifiers are now quoted instead of being passed through in a way that could fail on reserved words or spaces and expose a SQL injection risk. For the source release entry, see the pandas v3.0.4 GitHub release.
➔ Terratest v1.0.1 - Maintenance Phase and Deprecations
Terratest v1.0.1 was published on June 27, 2026, and it marks the start of the v1 maintenance phase for the Gruntwork test library. The main user visible change is a set of deprecation annotations that point users away from helper packages planned for removal in v2, while keeping this release safe for current v1 users. It is not marked as a prerelease.
➔ Great Expectations 1.18.2 - Spark Connect Fix
Great Expectations 1.18.2 was published on June 26, 2026, with a targeted Spark Connect compatibility fix for Spark distinct value metrics. The release also clears BigQuery and Python 3.13 maintenance friction, fixes scheduled CI noise, and updates the docs build stack. It is a small patch release, but it touches the kind of edges that show up in real data validation work.
➔ GopherJS v1.21.0 - Go 1.21.13 Support
GopherJS v1.21.0 was published on June 26, 2026, and moves the project to Go 1.21.13 support. The most important change is the compiler and runtime update for Go 1.21, with matching work across builtins, reflect, slices, maps, unsafe handling, testing, and native overrides. This is a stable release, not a prerelease.
➔ ingestr v1.0.48 - Vitess and PlanetScale Support
ingestr v1.0.48 was published on June 26, 2026, with a focused update for database ingestion paths. The main change is Vitess and PlanetScale support in the MySQL source, backed by tests for detection and OLAP row cap behavior. The release also tightens PostgreSQL CDC slot handling after a successful batch run, and it is not marked as a prerelease.
➔ wgpu v0.30.4 - Metal Stencil State Fix
wgpu v0.30.4 was published on June 25, 2026, with a focused Metal backend fix for stencil behavior on macOS. The main change is that CreateRenderPipeline now translates StencilFront and StencilBack into MTLDepthStencilState, so stencil tests no longer stay silently inert on the Metal path. For apps using stencil masks, clipped content, or rounded UI panels, this is the fix that changes what users actually see.
➔ Dagster 1.13.11 - Virtualized Asset Catalog and Insights Metadata
Dagster 1.13.11 was published on June 25, 2026, as the core release paired with library version 0.29.11. The main user facing change is in the asset catalog, where the UI now renders a single virtualized list so large workspaces do not stall when users expand many asset groups or code locations. For operators, the release also tightens asset check history cleanup and adds better selection counts for GraphQL clients.
➔ ingestr v1.0.47 - Reddit Ads OAuth and Chargebee Source
ingestr v1.0.47 was published on June 25, 2026, with user visible work around Reddit Ads authentication, account discovery, and the new Chargebee source. The main change is OAuth refresh token support for Reddit Ads, because it makes recurring ad data jobs less dependent on manual credential handling. This release is not marked as a prerelease.
➔ Terraform v1.15.7 - Parser and Init Fixes
Terraform v1.15.7 was published on June 24, 2026, with two focused bug fixes for users who run Terraform in real automation. The main change is concurrency safety for configs.Parser and SourceBundleParser, which matters when tooling parses Terraform configuration from shared code paths. Read the full notes on the GitHub release page.
➔ ingestr v1.0.45 - Catalog Table Names and Braze Segments
ingestr v1.0.45, published on June 24, 2026, is a focused release for destination naming and Braze exports. The main user visible change is support for three component destination names, so warehouse targets can carry catalog, schema, and table parts without being flattened into the wrong shape. It is not marked as a prerelease.
➔ ingestr v1.0.44 - Streaming Sources and Braze Series
ingestr v1.0.44 was published on June 24, 2026, with streaming platform sources as the main user visible change. The release also extends the Braze source with more series tables, so teams moving event and marketing data through ingestr have a wider surface to sync. It is not marked as a prerelease.
➔ Polars py-1.42.0 - Cloud IO and SQL Fixes
Polars py-1.42.0 was published on June 24, 2026, as the Python Polars 1.42.0 release. The main user visible work is a mix of cloud IO control, early out of core spilling, SQL fixes, and query optimizer correctness. The release is not marked as a prerelease, so teams using Python Polars should treat it as the current stable release train and read the migration notes before upgrading.
➔ ingestr v1.0.42 - GitLab Users and Fan Out
ingestr v1.0.42 was published on June 24, 2026. This regular release is mainly about the GitLab source, with per project fan out for issue and merge request reads, a GitLab users table, and error handling cleanup. For teams moving GitLab data into a warehouse with ingestr, this is the part to check before the next scheduled sync.
➔ ingestr v1.0.41 - GitLab Source and Braze User Data
ingestr v1.0.41 was published on June 23, 2026, with a practical set of connector and loader changes. The main user facing change is a new GitLab source, backed by Braze user_data work and an optimization for BigQuery merge partition pruning.
➔ OpenTofu v1.11.11 - OTEL Dependency Upgrade Fix
OpenTofu v1.11.11 was published on June 23, 2026 as a stable patch release for the v1.11 line. The main change is small but practical: the maintainers fixed an incomplete OTEL dependency upgrade left from the previous patch release.
➔ Jenkins 2.570 - SSH Key Search and UI Fixes
Jenkins published the jenkins-2.570 release on June 23, 2026. This weekly release is not marked as a prerelease, and the most useful operator change is broader SSH key discovery for ECDSA and Ed25519 keys. It also cleans up several UI bugs around Build History, build logs, and dynamic form lists.
➔ ingestr v1.0.40 - Braze Source and KPI Window Fix
ingestr v1.0.40 was published on June 23, 2026, with a small but practical set of changes for teams moving product and marketing data. The main user visible item is a new Braze source, backed by catalog wiring so server based connector discovery can expose it. The same release also fixes a KPI window bug that could drop the start day from a metric range.
➔ n8n 2.26.9 - Sparse Release Notes and Review Links
n8n [email protected] was published on June 22, 2026 as a stable GitHub release, not a prerelease. The visible release notes do not name a bug fix, feature, breaking change, migration step, or security patch, so the practical headline is release traceability rather than a documented product change. For teams searching what changed in n8n 2.26.9, the useful work is to follow the official release page and compare range, then treat the tag as a small maintenance release until the project publishes more detail.
➔ go-micro v6.2.1 - Blocking Lint and Doc Updates
go-micro v6.2.1 was published on June 22, 2026, with a small but useful maintenance set for Go service teams. The main change is CI hygiene: the lint backlog is cleared and golangci-lint now blocks CI, which should make future regressions louder before they reach users. The full notes are on the GitHub release page.
➔ go-micro v6.2.0 - Agent DX and Scaffolding Updates
go-micro v6.2.0 was published on June 22, 2026, with a small set of updates around agent developer experience, examples, and service scaffolding. The most useful change for users is the improved support agent material, because it gives maintainers a clearer path from concept to working example. GitHub does not mark this release as a prerelease.
➔ n8n 1.123.60 - Billing Count and Security Fixes
n8n [email protected] was published on June 22, 2026 as a focused stable release for the workflow automation project. The most important user visible change is in core billing: error workflow executions are excluded from billable execution counts, while the rest of the release tightens dependency security.
➔ go-elasticsearch v9.4.2 - BulkIndexer Routing Fix
elastic/go-elasticsearch v9.4.2 was published on June 22, 2026. This Go client release focuses on one esutil bug fix: BulkIndexer now omits an empty routing query param when no routing value is set. The original entry is on the GitHub release page.
➔ go-elasticsearch v9.3.5 - BulkIndexer Routing Param Fix
Elastic released go-elasticsearch v9.3.5 on June 22, 2026. This is a focused patch for esutil.BulkIndexer: it stops sending an empty routing query param when no routing value is set. If you are checking what changed in go-elasticsearch v9.3.5, this release is about bulk indexing request correctness, not a broad client update.
➔ n8n 2.26.8 - Form Trigger Crash Fix
n8n [email protected] was published on June 19, 2026, with a focused fix for the Form Trigger Node. The patch adds a default value for the authentication parameter so old workflows do not crash when they are opened or run against newer node code. It is not marked as a prerelease, and the scope is narrow enough that operators should read it as a compatibility repair rather than a feature release.
➔ CloudQuery PostgreSQL v8.15.0 - Databricks Lakebase Support
CloudQuery released plugins-destination-postgresql-v8.15.0 on June 19, 2026, for the PostgreSQL destination plugin in cloudquery/cloudquery. The main change is support for Databricks Lakebase as a destination, with a plugin-sdk update underneath. This release is not marked as a prerelease.
➔ ingestr v1.0.38 - SQL Server and SharePoint Sources
ingestr v1.0.38 was published on June 19, 2026, with two practical source additions: SQL Server Change Tracking and SharePoint. The release also tightens sports data sources, with schema inference work and safer interval handling across api-football and football-data. It is a regular release, not a prerelease.
➔ Nokogiri v1.19.4 - CRuby and JRuby Security Fixes
Nokogiri v1.19.4 was published on June 18, 2026, with security fixes for Ruby XML users on CRuby and JRuby. The most important item is the medium severity bounds fix in XML::NodeSet#[], because the same path is also exposed through #slice. This release is not marked as a prerelease.
➔ Dagster 1.13.10 - Backfill and Asset State Fixes
Dagster 1.13.10 was published on June 18, 2026, with core package version 1.13.10 and library package version 0.29.10. This release is not marked as a prerelease, and its most important fix is for stale latest materialization state after assets or partitions are wiped. For operators, that is the kind of bug that can make a healthy asset graph look wrong, or worse, make a wrong one look healthy.
➔ ingestr v1.0.37 - ESPN URI Param Fix
ingestr v1.0.37 was published on June 18, 2026, for the bruin-data/ingestr project. The main change is small but concrete: the ESPN source drops the dates URI param from its request path, so teams using that source should check any jobs that depend on date scoped ESPN pulls. This release is not marked as a prerelease.
➔ Ingestr v1.0.33 - Db2 Source and BigQuery Loader Fixes
Ingestr v1.0.33 adds a native Db2 source and ships several fixes for BigQuery, Databricks, and SQL Server loaders. The release landed on June 15, 2026 as a stable build, not a prerelease. For operators running mixed enterprise databases, the Db2 connector is the item worth upgrading for first.
➔ Great Expectations 1.18.1 - Data Docs Regex Fix and Doc Cleanup
Great Expectations 1.18.1 is a patch release published on June 11, 2026. The change most teams will notice is a Data Docs bug fix: regex patterns that contain angle brackets were not HTML escaped, which could break or misrender validation reports. The rest of the release is documentation housekeeping and temporary CI test skips for BigQuery and Snowflake.
➔ Dask 2026.6.0 - DataFrame Merge Fix and Pandas 3.1 Prep
Dask 2026.6.0 shipped on June 11, 2026 with a fix for a silent DataFrame merge bug that dropped rows at specific partition counts. The release also patches Series.map for misaligned inputs, tightens quantile behavior, and starts adapting to upcoming Pandas 3.1 deprecations.
➔ Dagster 1.13.9 - Hierarchical Asset Groups and Scheduler Fixes
Dagster 1.13.9 shipped on 11 June 2026 as a stable release (core 1.13.9, libraries 0.29.9). The headline change is hierarchical asset groups: you can use / in group names and select whole subtrees with wildcards in the asset graph.
➔ Jenkins 2.568 - Deserialization and XSS Security Fixes
Jenkins weekly release jenkins-2.568 shipped on June 10, 2026 as a security focused update. The headline fix is a high severity deserialization flaw in config.xml handling that could let authenticated users impersonate others or read controller files. Operators on weekly 2.567 or earlier should plan an upgrade before the next maintenance window.
➔ Argo Workflows v3.7.15 - Semaphore Fixes and Security Patches
Argo Workflows v3.7.15 shipped on June 10, 2026 as a stable patch on the 3.7 line. The headline fix is semaphore and mutex initialization soundness, which matters if you run workflows that depend on sync limits across controllers.
➔ Ingestr v1.0.39 - MongoDB CDC and Twilio Sources
ingestr v1.0.39 was published on June 23 2026. The release adds MongoDB change data capture support, a Twilio source, and streaming queue broker sources. It also adds an ingestr load timestamp column and updates the server UI to match CLI capabilities.
➔ Selenium 4.45.0 - Atoms Migration and Grid Redis Updates
The Selenium project released version 4.45.0 on June 16, 2026, bringing a major update to internal browser atoms and Grid infrastructure. This release focuses on moving core logic to TypeScript and bundling Redis session management for distributed testing environments.
➔ cloud-nuke v0.52.0 - Parallel Scanning and Deletion
The cloud-nuke project released version v0.52.0 on June 13, 2026, delivering a significant performance improvement for engineers cleaning up large AWS environments. This update introduces parallel resource scanning and deletion, allowing operators to clear out stale infrastructure much faster than before.
➔ Apache Airflow Helm Chart 1.22.0 - Image and Version Bumps
Apache Airflow Helm Chart 1.22.0 was released on June 13, 2026. This version bumps the default Airflow image to 3.2.2 and sets a new minimum requirement for the Helm binary itself.
➔ Kubernetes v1.36.2 - Dynamic Resource Allocation Fixes and CSI Stability
Kubernetes v1.36.2 arrived on June 12, 2026, as the second patch release for the 1.36 branch. This update delivers critical fixes for the Dynamic Resource Allocation system and addresses a storage issue that could lead to stale volume data.
➔ OpenTofu v1.11.9 Release - Critical Security Patches and Bug Fixes
OpenTofu v1.11.9 is now available, bringing essential security updates and stability improvements to the v1.11 series. Published on June 12, 2026, this release addresses vulnerabilities in SSH handling and state encryption that could lead to panics or hangs in specific scenarios.
➔ OpenTofu v1.12.2 - Security Patches and Deadlock Fixes
OpenTofu v1.12.2 was released on June 12 2026 to address several security concerns and stability issues in the v1.12 series. This update includes critical fixes for state encryption when using the OpenBao key provider and resolves a kernel deadlock bug during provider installation on Unix systems. It is a mandatory update for anyone using the latest feature set in production environments.
➔ Kubernetes v1.34.9 Release - Binary Secret Fix and Go Update
Kubernetes v1.34.9 arrived on June 12, 2026, delivering a set of critical stability fixes for production clusters and a toolchain update to Go 1.25.11. This patch release specifically addresses a nasty regression involving binary data in Secret objects and a storage bug that could leave volumes in a stale state after transient failures.
➔ Kubernetes v1.35.6 Release - Critical CSI Fix and Go Update
Kubernetes v1.35.6 arrived on June 12, 2026, as a standard patch release for the current stable branch. This update is particularly important for clusters using CSI drivers due to a bug that could lead to stale volume data. It also updates the build environment to Go 1.25.11 and addresses several panics in the scheduler and networking components.
➔ Kubernetes v1.33.13 Release Notes: Security Fixes and Kubeadm Stability
Kubernetes v1.33.13 is out today, providing a critical security patch for stream multiplexing and fixing a cluster initialization bug in kubeadm. As the v1.33 series approaches end of life later this month, this update ensures stability for production clusters running on the Octarine release line.
➔ Terragrunt v1.0.8 - Faster Read Tracking and S3 Virtual Hosting
Terragrunt v1.0.8 arrived on June 10 2026 with performance improvements for large module sources and better support for S3 virtual hosted style URLs. This release also fixes a long standing issue with assume role list attributes and improves how completed experiments are handled during HCL validation.
➔ Terraform v1.15.6 - JSON Plan and Console Panic Fixes
The HashiCorp team released Terraform v1.15.6 on June 10, 2026, delivering several critical bug fixes for operators managing infrastructure at scale. This patch update focuses on improving the reliability of state management blocks and fixing stability issues in the interactive console.
➔ cloud-nuke v0.51.0: AWS Backup Plans and Dry Run for Defaults
The cloud-nuke project released version v0.51.0 on June 10, 2026, introducing support for AWS Backup plans and a new preview mode for default resource cleanup. This update also brings critical fixes for SageMaker endpoint deletion and IAM instance profile tagging. This release marks another step in making the tool more robust for automated environment cleanup in complex AWS accounts.
➔ Prefect 3.7.4 - Lifecycle Events and Cleanup Delivery
Prefect 3.7.4 was published on June 5, 2026, with a practical set of changes for teams running Prefect in production. The main user visible change is broader lifecycle event emission for domain objects, while the operator side gets more cleanup delivery work around Redis, worker channels, leases, retries, and recovery.
➔ Apache Airflow Ctl 0.1.5 - CLI, Dag Run, and API Updates
Apache Airflow Ctl airflow-ctl/0.1.5 was published on June 3, 2026. This release gives airflowctl users more direct Dag and Dag Run operations, cleaner generated command arguments, and fixes a few rough edges that matter when the tool is used in scripts.
➔ Terragrunt v1.0.7: Optional tfr Versions, CAS Beyond Git, and Stack Dependency Cleanup
Terragrunt v1.0.7 shipped on 2026-06-01 with one ergonomic change to tfr:// source URLs, a meaningful expansion of the content addressing experiment, four bug fixes that stop crashes and hangs, and a cleanup pass on the stack-dependencies experiment.
➔ Kubernetes Python Client v36.0.2 Patch Release
The Kubernetes Python client shipped v36.0.2 on June 1, 2026. This is the third tag in the v36.0.x line, landing about a week after v36.0.0 and four days after v36.0.1. The release notes from GitHub do not list individual fixes; the actual diff lives in the release-36.0 branch changelog, and this post walks through how to pull it in and where to look for the details.
➔ Apache Airflow 3.2.2: SMTP Validation, Triggerer Watchdog, and Prefix Search
Apache Airflow 3.2.2 was published on May 29 2026 with a mix of security tightening, a triggerer reliability fix, and a UI search behavior change that operators of large deployments should know about.
➔ Kubernetes Python Client v36.0.1 Stable Release
The kubernetes-client/python project published the v36.0.1 stable tag on May 20, 2026. This is a patch release in the 36.0.x line, marked as non prerelease, so it is intended for production installs rather than testing.
➔ OpenTofu 1.12.1 Release: Security Patch and v1.12.0 Regression Fixes
OpenTofu v1.12.1 shipped on May 27, 2026 as a patch release for the 1.12 line. The headline is a security advisory covering SSH handling in tofu generate and a CA SignatureKey revocation gap. The release also clears two regressions introduced in v1.12.0 and fixes the Azure key provider configuration.
➔ Terragrunt v1.0.6 - Bug Fixes and New Experiments
Terragrunt v1.0.6 shipped on May 25, 2026. It is mostly a bug fix wave plus two new experiments and a TUI update for the catalog redesign. The download_dir hang on a non hidden subdirectory and the race in parallel stack parsing are the headline fixes.
➔ Kubernetes Python Client v36.0.0 Stable Release Notes
The official Kubernetes Python client tagged v36.0.0 on May 20, 2026. The published GitHub release is intentionally short and points users at the install commands and the full changelog on the release-36.0 branch. This post collects what is on the release page, plus the practical bits operators usually want before bumping the version in production code.
➔ Playwright Python 1.60.0 release with HAR tracing and drop locators
Playwright Python 1.60.0 ships HAR recording as a tracing API, a new drop() method on locators, and soft assertions for pytest. The release was published on May 18, 2026 and pulls the bundled browsers up to Chromium 148, Firefox 150, and WebKit 26.4.
➔ OpenTofu 1.12.0 Brings Dynamic prevent_destroy and Provider Checksum Fixes
OpenTofu 1.12.0 landed on May 14, 2026, and it pulls a few sharp edges out of day to day usage. The headline items: prevent_destroy can now reference variables, the provider registry ships complete checksums, and a new -json-into=FILENAME flag lets you keep JSON output alongside the normal terminal UI.
➔ Prefect 3.7.1 Release Notes - Worker Channel and Orchestration Fixes
PrefectHQ shipped Prefect 3.7.1 on May 16, 2026, a point release that ships the first batch of worker channel infrastructure and clears out a stack of orchestration, concurrency, and result data bugs. Anyone running self hosted workers or pinning Python 3.13 should read this one carefully.
➔ Selenium 4.44.0 - new CLI, Redis Grid distributor, BiDi cleanup
Selenium 4.44.0 shipped on May 12, 2026. The release introduces an initial Selenium CLI tool, makes the Redis backed Grid Distributor a built in option, and lands a long round of dotnet and Python BiDi cleanup. It is a regular release, not a prerelease.
➔ Terragrunt v1.0.5 release notes and key changes
Terragrunt v1.0.5 from gruntwork-io shipped on May 18, 2026. The headline change: when the provider cache server talks to the OpenTofu registry, a single terragrunt init now writes a .terraform.lock.hcl with h1: hashes for every platform the registry supports, so you no longer need to run tofu providers lock -platform=... for each target architecture.
➔ OpenTofu v1.10.10 - Two Bug Fixes for Caching and Import Blocks
OpenTofu shipped v1.10.10 on May 11, 2026 as a small patch focused on two bug fixes. The provider cache now refuses to silently overwrite a mismatched entry, and a long standing crash in import blocks that used provider defined functions is gone.