BlackTreeLifecycle intelligence
Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT

VERIFIED PUBLISHER INTELLIGENCE

Release notes and known issues

Source-attributed product updates, affected versions, fixes and operational context. Update publication dates are kept separate from lifecycle boundaries.

85 official publisher sources registered · 83 collected automatically · 0 monitored for availability · 2 requires publisher access

1794 verified publisher records · Page 9 of 18

VEEAMKB4747

Build Numbers and Versions of Veeam Plug-In for Scale Computing HyperCore

Build Numbers and Versions of Veeam Plug-In for Scale Computing HyperCore KB ID: 4747 Product: Veeam Plug-in for Scale Computing HyperCore | 1.1 | 2 | 3 | 4 | 4.1 Published: 2025-09-22 Last Modified: 2026-09-24 This KB article lists all versions of the Veeam Plug-In for Scale Computing HyperCore and their respective worker build numbers. Version Plug-In / Worker Build Release Date Veeam Plug-In for Scale Computing HyperCore 4 Releases Veeam Plug-In for Scale Computing HyperCore 4.1 Independent Plug-In Release 13.4.1.328 2026-09-24 Veeam Plug-In for Scale Computing HyperCore 4.0 Included with Veeam Backup & Replication 13.1 13.4.0.327 2026-07-29 Veeam Plug-In for Scale Computing HyperCore 3 Releases Veeam Plug-In for Scale Computing HyperCore 3.2 Included with Veeam Backup & Replication 13.0.3 13.3.2.30 2026-08-25 Veeam Plug-In for Scale Computing HyperCore 3.1 Included with Veeam Backup & Replication 13.0.2 13.3.1.8 2026-05-27 Veeam Plug-In for Scale Computing HyperCore 3.0 Included with Veeam Backup & Replication 13.0.1 P2 13.3.0.81 2026-03-12 Veeam Plug-In for Scale Computing HyperCore 2 Releases Veeam Plug-In for Scale Computing HyperCore 2.1 Available to Veeam Software Appliance via Component Updater 13.2.1.6 2026-03-12 Veeam Plug-In for Scale Computing HyperCore 2.0 Included with Veeam Backup & Replication 13.0.1 13.2.0.245 2025-11-19 Veeam Plug-In for Scale Computing HyperCore 1 Releases Veeam Plug-In for Scale Computing HyperCore 1.1 Independent Plug-In Release 12.1.1.4 2025-09-17 Swipe to show more of the table Independent Plug-In releases are available in the My Account portal: My Account > My Products > Additional downloads > Virtualization Plug-ins Note: The additional downloads section is at the very bottom of the My Products page. Related Articles Build Numbers and Versions of Veeam Backup & Replication ├ Build Numbers and Versions of Veeam Plug-In for Nutanix AHV ├ Build Numbers and Versions of Veeam Plug-In for Proxmox VE ├ Build Numbers and Versions of Veeam Plug-In for oVirt KVM ├ Build Numbers and Versions of Veeam Plug-In for Scale Computing HyperCore ├ Build Numbers and Versions of Veeam Plug-In for HPE Morpheus VM Essentials ├ Build Numbers and Versions of Veeam Plug-In for Platform9 ├ Build Numbers and Versions of Veeam Plug-In for Sangfor aSV ├ Build Numbers and Versions of Veeam Plug-In for Verge OS ├ Build Numbers and Versions of Veeam Plug-In for Xen ├ Build Numbers and Versions of Veeam Plug-In for KubeVirt ├ Build Numbers and Versions of Veeam Plug-In for AWS ├ Build Numbers and Versions of Veeam Plug-In for Microsoft Azure └ Build Numbers and Versions of Veeam Plug-In for Google Cloud Build Numbers and Versions of Veeam ONE Build Numbers and Versions of Veeam Recovery Orchestrator Build Numbers and Versions of Veeam Service Provider Console Build Numbers and Versions of Veeam Agent for Microsoft Windows Build Numbers and Versions of Veeam Agent for Linux Build Numbers and Versions of Veeam Agent for Mac Build Numbers and Versions of Veeam Agent for IBM AIX Build Numbers and Versions of Veeam Agent for Oracle Solaris Build Numbers and Versions of Veeam Backup for Microsoft 365 Build Numbers and Versions of Veeam Backup for Salesforce Veeam Data Cloud for Microsoft 365 Release Information and Build Numbers Veeam Data Cloud for Microsoft Azure Release Information and Build Numbers If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case. To submit feedback regarding this article, please click this link: Send Article Feedback To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Published 24 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
PHPPHP-8.2.34

PHP 8.2.34

The PHP development team announces the immediate availability of PHP 8.2.34. This is a security release. All PHP 8.2 users are encouraged to upgrade to this version. For source downloads of PHP 8.2.34 please visit our downloads page , Windows source and binaries can also be found there . The list of changes is recorded in the ChangeLog .

Published Never · Source checked 28 Sep 2026

Release notes and known issues →
PHPPHP-8.3.35

PHP 8.3.35

The PHP development team announces the immediate availability of PHP 8.3.35. This is a security release. All PHP 8.3 users are encouraged to upgrade to this version. For source downloads of PHP 8.3.35 please visit our downloads page , Windows source and binaries can also be found there . The list of changes is recorded in the ChangeLog .

Published Never · Source checked 28 Sep 2026

Release notes and known issues →
BROADCOMSPRING-BOOT-4.2.0-M1

v4.2.0-M1

⭐ New Features Refine Forwarded headers configuration for Jetty servers #51148 Disable Micrometer global registry in tests by default #51142 Use GracefulHandler rather than StatisticsHandler to coordinate graceful shutdown of Jetty #51128 Deprecate RestTemplate support #51118 Update properties for forwarded headers to adapt to Reactor Netty changes #51031 Update properties for forwarded headers to adapt to Spring Framework changes #51030 Remove APIs that were deprecated for removal in 4.2 #50955 Add support for image-based build caches #50899 Provide plugin management for hibernate-maven-plugin #50892 Support timeout option in RetryPolicySettings #50891 Add self-reference to ApplicationContextAssertProvider #50500 Add configuration property for leaveGroupOnClose in Kafka Streams #50432 Expose Path getters on ApplicationHome and ApplicationTemp #50194 Introduce RabbitMQ AMQP 1.0 client support #49857 Introduce Generic AMQP 1.0 client support #49678 Rename spring-boot-amqp to spring-boot-rabbitmq #49677 Add support for AMQP 1.0 #49619 Deprecate TestRestTemplate in favor of RestTestClient #46632 Take target/test-classes into account when spring-boot.run.useTestClasspath is in effect #36115 🐞 Bug Fixes Structured logging: a failed JSON encode corrupts the next log event written on the same thread #51371 Kafka consumer-specific security protocol is not taken into account #51370 Exposing gRPC test server port should backoff if gRPC is not present #51291 Micrometer registries pin the application context #51136 Temporary file is not deleted when ExportedImageTar construction fails #51133 spring.grpc.server.health.include-overall-health is not taken into account #51106 Metadata annotation processor ignores getter-level @NestedConfigurationProperty for records #51099 spring-boot-h2-console pulls servlet-api as transitive dependency #51096 PropertiesLauncher does not log nested archive paths #51090 Methods that return the result of Map#remove are not declared with a @Nullable return type #51088 NativeImageResourceProvider flattens Flyway migration paths in subdirectories #50965 Fix ordering of Kotlinx Serialization CodecCustomizer #50962 JarFile is not closed when finding main class from archive #50960 📔 Documentation Description of spring.graphql.websocket.connection-init-timeout does not render correctly in the reference guide #51364 spring.profiles.group should have a 'spring-profile-name' hint provider #51285 Remove reference to removed InfluxDB auto-configuration #51177 Use JacksonJsonSerde in Kafka Streams documentation #51162 Document alternatives to HttpMessageConverters #51130 Fix stale type reference for OTLP logging transport metadata #51126 Metadata for spring.test.mockmvc.htmlunit.url declares the wrong type #51116 Caching documentation refers to AutoConfigureCache by its pre-4.0 package #51114 Fix examples in Metadata Format documentation chapter #51103 Improve discoverability of the AOT Cache How-to guides #51001 🔨 Dependency Upgrades Upgrade to ActiveMQ 6.3.1 #51334 Upgrade to Artemis 2.55.0 #51034 Upgrade to Byte Buddy 1.18.11 #51035 Upgrade to Commons Codec 1.22.1 #51198 Upgrade to Commons Logging 1.4.0 #51037 Upgrade to Couchbase Client 3.12.2 #51295 Upgrade to CycloneDX Maven Plugin 2.9.3 #51199 Upgrade to DB2 JDBC 12.1.5.0 #51039 Upgrade to Elasticsearch Client 9.5.0 #51335 Upgrade to Flyway 12.11.0 #51040 Upgrade to Groovy 5.0.8 #51200 Upgrade to Grpc Java 1.81.1 #51229 Upgrade to Grpc Java 1.83.1 #51362 Upgrade to Gson 2.14.0 #51042 Upgrade to Hazelcast 5.7.0 #51309 Upgrade to Hibernate 7.4.5.Final #51043 Upgrade to Hibernate Validator 9.1.3.Final #51201 Upgrade to HikariCP 7.1.0 #51045 Upgrade to HtmlUnit 5.4.0 #51313 Upgrade to HttpClient5 5.6.4 #51336 Upgrade to HttpCore5 5.4.3 #51047 Upgrade to Infinispan 16.2.2 #51203 Upgrade to Jackson 2 Bom 2.21.5 #51078 Upgrade to Jackson Bom 3.1.5 #51050 Upgrade to Jedis 8.0.0 #51337 Upgrade to Jetty 12.1.12 #51297 Upgrade to jOOQ 3.21.7 #51314 Upgrade to Json Path 3.0.0 #

Published Never · Source checked 28 Sep 2026

Release notes and known issues →
BROADCOMSPRING-BOOT-4.2.0-M2

v4.2.0-M2

⭐ New Features Deprecate AppOptics as it has retired #51810 Improve classpath entry lookup performance during jar creation and extraction #51787 Add spring.kafka.listener.await-async-results-on-stop property #51774 Rationalize Kafka configuration outside of KafkaProperties #51769 Make the active Observation LongTaskTimer on the auto-configured DefaultMeterObservationHandler opt-in #51762 Configure allowed HTTP methods in GraphQL transports #51732 Allow to use Mongo JobRepository with any PlatformTransactionManager #51725 Resolve property placeholders in constructor binding default values #51661 Add auto-configured BaggageTaggingSpanProcessor for OpenTelemetry tag fields #51656 Improve the performance of layer index creation #51654 Speed up layer lookups when extracting a layered jar #51653 Move Tomcat's servlet-specific properties beneath server.tomcat.servlet #51603 Align handling of null and empty values in SPRING_APPLICATION_JSON with YAML processing #51583 Remove Dependency Management for Janino #51567 Add jarmode tools command to print / export the SBOM #51505 Pick up all @TypeExcludeFilters annotations on test classes #51489 Make it easier to map MessageSourceProperties onto a user-provided AbstractResourceBasedMessageSource #51484 Support multi-segment additional health endpoint paths #51470 Honor spring.ldap.* properties in the Embedded LDAP server #51465 Add a configuration property for configuring embedded LDAP operation types that require authentication #51461 Add TWENTY_SEVEN to JavaVersion enum #51427 Automatically filter additional configuration metadata from Spring Boot-built archives #51386 Add SSL bundle support to LDAP auto-configuration #51382 Align the default for server.tomcat.use-relative-redirects with Tomcat's default #51173 Allow configuring Micrometer Tracing MDC keys #50595 Add common OTLP configuration for endpoint, compression and headers #50461 Retain probe defaults when configuring other properties on probe health groups #50296 Include security error body in WebFlux Cloud Foundry endpoint responses #50256 Provide a configuration property to switch from Micrometer to OpenTelemetry semantic conventions #49241 Support listener and template specific Kafka Admin properties #38830 🐞 Bug Fixes spring.http.clients.cookie-handling has no effect when using a reactive client backed by an HttpComponents connector #51767 NullPointerException can be thrown when using uber jars due to a race condition in NestedJarFileResources #51746 Connection fails when rabbitmq Docker Compose service is configured to use SSL #51668 SBOM-related manifest attributes are missing from Maven-packaged wars #51652 When server.reactive.session.cookie.same-site is not set, session cookies have no SameSite attribute #51640 OAuth2 resource server ignores authorities-claim-delimiter when set on its own #51631 developmentOnly and testAndDevelopmentOnly configurations do not specify any attributes causing potential resolution problems #51624 In a reactive web application, Cloud Foundry security integration returns a 500 rather than a 503 when the cloud controller URL is unavailable #51615 ReactiveOAuth2ResourceServerWebSecurityAutoConfiguration annotated with wrong condition #51588 WritableJson.toByteArray() may corrupt supplementary characters #51586 Layer temp file is not deleted when layer creation fails #51582 Docker Compose integration for RabbitMQ skips credential fallbacks when an environment variable has no value #51579 Some assertion messages name the wrong parameter #51575 OAuth2ResourceServerProperties.Jwt has a setter that does not match its getter #51566 jarmode tools commands print stacktrace instead of an error message #51548 Docker Compose ProcessRunner can hang or leave orphan processes #51539 NestedByteChannel.read(ByteBuffer) incorrectly returns 0 when buffer could not be filled #51521 Customizer null checks in HTTP client builders assert the wrong attribute #51514 SSL host config customizations may be lost during Tomca

Published Never · Source checked 28 Sep 2026

Release notes and known issues →
BROADCOMSPRING-FRAMEWORK-7.1.0-M2

v7.1.0-M2

⭐ New Features Align DispatcherServlet bean detection logs #37296 Extract bean property path support into PropertyPath #37275 Expose matched PathPattern as MVC request attribute #37272 Add a configurable limit for maximum nesting depth in property paths #37252 Enforce "data: " (with space) prefix for outgoing SSE data payloads #37242 Parse RFC 9651-like date headers #37224 Polish ScheduledAnnotationBeanPostProcessor to refine null-safety #37219 Add batch update support to JdbcClient #37216 Emit multipart parts with empty bodies in PartGenerator #37202 Upgrade to HtmlUnit 5 #37194 Ignore invalid SSE retry field #37193 Handle MIME type parameter names case-insensitively #37192 Deprecate SpelParserConfiguration constructors in favor of the builder API #37190 When connection to client is lost while writing JSON, it should not be logged as warning #37151 JMS SimpleMessageConverter.fromMessage() can return null despite @NullMarked package #37148 Avoid unnecessary allocations for cached annotation mappings #37141 Update MockCookie#parse(String) validation #37136 Add WebFlux OpenTelemetry observation convention #37131 Limit bracket depth in PropertyEditorRegistrySupport 's addStrippedPropertyPaths() #37020 Improve efficiency of map creation in DataBinder #37019 Reject overlapping declared and generated key columns in SimpleJdbcInsert #37014 Reject MIME type parameters differing only in case #37008 Use depth-aware bracket parsing in PropertyAccessorUtils #36999 Account for all array objects when checking array size in SpEL #36998 Align SpEL's default max auto-grow size with Spring data binding #36995 Avoid redundant registration of Date/Calendar/Long converters in DefaultFormattingConversionService #36951 Suppress CGLIB validation WARN for lifecycle callbacks #36935 Add Cache-Control must-understand directive #36918 validate samesite attribute in ResponseCookie #36905 Close contexts when clearing test context cache #36825 Use immutable map for static cache in TypeDescriptor #36813 Add a configurable limit for structural nesting depth in SpEL expressions #36723 Simplify programmatic scheduling of cron tasks with time zone #36556 Deprecate Derby support #36045 Add support for generating resources linked to a feature #35862 Add RFC 10008 (QUERY HTTP method) support #34993 🐞 Bug Fixes PartGenerator.switchToFile() doesn't count buffered bytes toward maxDiskUsagePerPart #37238 Reject write methods not starting with "set" in Property #37139 Meta-annotations with attributes are still unnecessarily synthesized in MergedAnnotations #37135 Use the 4-argument Property constructor in SpEL's ReflectivePropertyAccessor #37123 Fix BeanFactory.getBean(String, ParameterizedTypeReference) to respect AOP proxy #37047 Fix OptionalToObjectConverter applicability check #36913 Fix Property name resolution for record-style accessors #36911 📔 Documentation Fix RestClient API usage in documentation #37137 Add Validation section examples #36190 🔨 Dependency Upgrades Upgrade to Kotlin 2.4.20 #37271 Upgrade to Micrometer 1.18.0-M2 and Tracing 1.8.0-M2 #37288 Upgrade to Reactor 2026.0.0-M2 #37263 ❤️ Contributors Thank you to all the contributors who worked on this release: @DevJunz , @Eymenonar , @Sineaggi , @Will-thom , @blackdurumi , @cookie-meringue , @desiderantes , @dxbjavid , @froggy0m0 , @gregjotau , @heka1024 , @junhyeong9812 , @junhyung8795 , @kilink , @lArtiquel , @marschall , @mateo-maza , @ngocnhan-tran1996 , @noojung , @quaff , @sabberworm , @seonwooj0810 , @shaggyinsomniac , @verhasi , and @vpavic

Published Never · Source checked 28 Sep 2026

Release notes and known issues →
CANONICALUSN-8817-1

USN-8817-1: Linux kernel vulnerabilities

It was discovered that some Arm processors could complete a broadcast translation lookaside buffer (TLB) invalidation before memory writes made through the invalidated translation were globally observed. A local attacker could possibly use this to write to memory after permission to do so had been revoked, bypassing memory protections or escalating privileges. (CVE-2025-10263) Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems: - ARM64 architecture; - InfiniBand drivers; - Network drivers; - TCM subsystem; - B.A.T.M.A.N. meshing protocol; - HSR network protocol; - IPv4 networking; - IPv6 networking; - Netfilter; - RDS protocol; (CVE-2026-53131, CVE-2026-53186, CVE-2026-53216, CVE-2026-53221, CVE-2026-53354, CVE-2026-53355, CVE-2026-63886, CVE-2026-63887, CVE-2026-63888, CVE-2026-63912, CVE-2026-63922, CVE-2026-63924, CVE-2026-63984, CVE-2026-63992, CVE-2026-63993, CVE-2026-63994, CVE-2026-64000, CVE-2026-64007, CVE-2026-64091)

Published 24 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
CANONICALUSN-8818-1

USN-8818-1: Linux kernel vulnerabilities

It was discovered that some Arm processors could complete a broadcast translation lookaside buffer (TLB) invalidation before memory writes made through the invalidated translation were globally observed. A local attacker could possibly use this to write to memory after permission to do so had been revoked, bypassing memory protections or escalating privileges. (CVE-2025-10263) Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems: - ARM64 architecture; - InfiniBand drivers; - Network drivers; - TCM subsystem; - exFAT file system; - Network file system (NFS) client; - Network file system (NFS) server daemon; - B.A.T.M.A.N. meshing protocol; - IPv4 networking; - IPv6 networking; - Netfilter; - RDS protocol; (CVE-2026-53186, CVE-2026-53216, CVE-2026-53221, CVE-2026-53354, CVE-2026-53355, CVE-2026-53398, CVE-2026-63800, CVE-2026-63808, CVE-2026-63887, CVE-2026-63888, CVE-2026-63912, CVE-2026-63922, CVE-2026-63924, CVE-2026-63984, CVE-2026-63992, CVE-2026-63993, CVE-2026-63994, CVE-2026-64007, CVE-2026-64091)

Published 24 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
CANONICALUSN-8819-1

USN-8819-1: Linux kernel vulnerabilities

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems: - Network file system (NFS) server daemon; - IPv6 networking; - Netfilter; (CVE-2025-38724, CVE-2026-53131, CVE-2026-53221)

Published 24 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
CANONICALUSN-8820-1

USN-8820-1: curl vulnerabilities

Eunsoo Kim discovered that curl incorrectly handled SASL negotiation for LDAP authentication in certain circumstances. A machine-in-the-middle attacker could possibly use this issue to bypass peer validation. This issue only affected Ubuntu 24.04 LTS and Ubuntu 26.04 LTS. (CVE-2026-13608) Stephan Zeisberg discovered that curl incorrectly handled HTTP/2 Server Push streams when sharing connections between handles. A remote attacker could possibly use this issue to cause curl to crash, resulting in a denial of service, or execute arbitrary code. (CVE-2026-18924) Stanislav Fort discovered that curl incorrectly managed the lifetime of pooled TLS connections when using the multi interface. An attacker could possibly use this issue to cause curl to crash, resulting in a denial of service, or execute arbitrary code. This issue only affected Ubuntu 26.04 LTS. (CVE-2026-80229) Stanislav Fort discovered that curl did not properly enforce public key pinning when certificate verification was disabled in certain circumstances. A remote attacker could possibly use this issue to bypass pinning checks and cause curl to accept connections that should have been rejected. (CVE-2026-80230) Stanislav Fort discovered that curl incorrectly handled the Secure attribute of cookies in certain circumstances. A remote attacker could possibly use this issue to obtain sensitive information. This issue only affected Ubuntu 26.04 LTS. (CVE-2026-80255) Stanislav Fort discovered that curl did not properly enforce Public Suffix List boundaries when handling cookies in certain circumstances. A remote attacker could possibly use this issue to cause cookies to be sent to unrelated domains, resulting in sensitive information being exposed. This issue only affected Ubuntu 18.04 LTS, Ubuntu 20.04 LTS, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, and Ubuntu 26.04 LTS. (CVE-2026-82209) Ady Elouej discovered that curl did not clear proxy authentication state between requests when reusing a handle with environment-variable proxy configuration. A remote attacker could possibly use this issue to obtain sensitive credentials. This issue was previously fixed in USN-8487-1, but that fix was incomplete for Ubuntu 16.04 LTS. (CVE-2026-8927)

Published 24 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
CANONICALUSN-8821-1

USN-8821-1: OpenStack Swift vulnerability

It was discovered that OpenStack Swift incorrectly handled truncated aws-chunked PUT request bodies in its s3api middleware. An authenticated attacker could possibly use this issue to cause OpenStack Swift to use excessive resources, leading to a denial of service.

Published 24 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
AMAZON WEB SERVICESAMAZON-WEB-SERVICES-1166FA1E17C7E5AD

Amazon Connect Customer now provides routing step data in the analytics data lake

Amazon Connect Customer now provides routing step data in the analytics data lake, making it easier for customers to generate insights from routing decisions. Using the data lake, customers can leverage Amazon Athena and Amazon Quick to analyze trends, such as contacts queued and contacts joined at each routing step, without complex data pipelines. For example, an analyst can now report on how contacts progressed through each routing step, identify where agent matching criteria were relaxed, and measure the impact of routing step configurations on wait times and agent utilization. Routing step data is available in all AWS regions where Amazon Connect Customer data lake is offered. To learn more about Amazon Connect Customer data lake, see the Amazon Connect Customer Administrator Guide . To learn more about Amazon Connect Customer, visit the Amazon Connect Customer website .

Published 23 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
AMAZON WEB SERVICESAMAZON-WEB-SERVICES-150ADEBF8CC42997

Amazon CloudWatch Omni: AI-first observability for agents and applications

AWS announces the general availability of Amazon CloudWatch Omni, an evolution of Amazon CloudWatch. Omni is an AI-powered observability experience organized around your teams and the applications they run, so that you can observe and troubleshoot your applications and agents in one place. It combines the interoperability of OpenTelemetry with the scale and reliability of CloudWatch. And it meets you wherever you work: a standalone web experience with single sign-on (SSO) for your team, or a local IDE extension for getting hands-on with your agents. With CloudWatch Omni, you create spaces in your central accounts to see telemetry across your AWS accounts and Regions, as well as other clouds, including Azure workloads. Omni automatically discovers services, maps dependencies, and surfaces golden metrics to help streamline your operational workflows. Using Omni, you can interact with telemetry however you prefer: via chat, through a guided point-and-click path in the console, or directly from a tool of your choice leveraging Agent Toolkit for AWS. Ask a question in natural language and Omni finds the relevant telemetry, builds dynamic views of the signals you care about, and helps you get to root cause powered by AWS DevOps Agent. Prefer to drive yourself? Point and click through the signals that matter most, whether you're investigating a degrading application or diving deep into a trace or evaluation. Omni also features a dedicated agent observability experience with an evaluation-driven development workflow for AI workloads across frameworks including LangGraph, CrewAI, OpenAI Agents SDK, Vercel AI SDK, and Strands. For every prompt, model call, and tool invocation, Omni helps you evaluate quality and run experiments to validate fixes before you ship. To get started, create your Omni space from the CloudWatch console, configure SSO, and sign in to the standalone web experience. Agent developers can install the free CloudWatch Omni extension for VS Code, Cursor, and Kiro to instrument, debug, and evaluate agents locally (no AWS account required). CloudWatch Omni is generally available in US East (N. Virginia), US West (Oregon) and Europe (Ireland). To learn more, see the Amazon CloudWatch Omni product page and documentation . For pricing, see the CloudWatch Omni pricing page .

Published 23 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
AMAZON WEB SERVICESAMAZON-WEB-SERVICES-246D06BE149CF2B7

Amazon Bedrock Managed Knowledge Base now supports Salesforce and Zendesk as native data source connectors

AWS announces Salesforce and Zendesk data source connectors for Amazon Bedrock Managed Knowledge Base, a fully managed retrieval-augmented generation (RAG) service. Customers can now sync Salesforce knowledge articles and Zendesk articles and community posts directly into their managed knowledge base. Previously, bringing content from these platforms into Bedrock Knowledge Bases required building custom ingestion pipelines—now, you provide your instance credentials, and the connectors handle data crawling, metadata extraction, and incremental sync automatically. These connectors make it easy to build AI agents and assistants grounded in the support and product knowledge your teams already maintain in Salesforce and Zendesk. For example, power a customer-facing support bot with up-to-date Zendesk help center articles and community answers, or build an internal sales enablement assistant that retrieves relevant Salesforce knowledge articles during deal preparation. By keeping your knowledge base in sync with these platforms, your retrieval-augmented generation applications always reflect the latest content without manual intervention. To learn more, see Salesforce data source connector and Zendesk data source connector in the Amazon Bedrock User Guide. For more information about Amazon Bedrock Managed Knowledge Base, visit the Amazon Bedrock Knowledge Bases product page .

Published 23 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
AMAZON WEB SERVICESAMAZON-WEB-SERVICES-3B62DA26BC395051

Amazon EMR on EKS now supports IPv6 Amazon EKS clusters

Today, AWS announces that Amazon EMR on EKS now supports running workloads on IPv6 Amazon Elastic Kubernetes Service (Amazon EKS) clusters. Amazon EMR on EKS enables data platform and analytics teams to run open-source big data frameworks such as Apache Spark and Apache Flink on Amazon EKS. With IPv6 support, teams operating at scale can now run these workloads on IPv6 Amazon EKS clusters, giving them access to the vastly larger address space of IPv6 as their analytics workloads grow. You can now scale large Spark and Flink workloads using the expanded IPv6 address space, which removes the need for IPv4 conservation workarounds such as secondary CIDR ranges or prefix delegation. High-executor jobs, such as 500-executor Spark jobs, can run concurrently without planning around address limits. To submit workloads, use StartJobRun, Spark Connect Interactive Endpoints, and Amazon SageMaker Unified Studio with no additional configuration, while the Flink, Livy, and Spark Operators are also supported. This capability is available at no additional cost, starting with Amazon EMR releases emr-7.14.0 and emr-spark-8.0.0. IPv6 cluster support is available in all AWS Regions where Amazon EMR on EKS and IPv6 Amazon EKS clusters are available. Amazon EMR on EKS IPv6 cluster support includes detailed setup instructions and documentation on supported submission models. Visit the Amazon EMR on EKS product page and the IPv6 documentation to learn more.

Published 23 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
AMAZON WEB SERVICESAMAZON-WEB-SERVICES-7.14.0

Amazon EMR on EKS now supports IPv6 Amazon EKS clusters

Today, AWS announces that Amazon EMR on EKS now supports running workloads on IPv6 Amazon Elastic Kubernetes Service (Amazon EKS) clusters. Amazon EMR on EKS enables data platform and analytics teams to run open-source big data frameworks such as Apache Spark and Apache Flink on Amazon EKS. With IPv6 support, teams operating at scale can now run these workloads on IPv6 Amazon EKS clusters, giving them access to the vastly larger address space of IPv6 as their analytics workloads grow. You can now scale large Spark and Flink workloads using the expanded IPv6 address space, which removes the need for IPv4 conservation workarounds such as secondary CIDR ranges or prefix delegation. High-executor jobs, such as 500-executor Spark jobs, can run concurrently without planning around address limits. To submit workloads, use StartJobRun, Spark Connect Interactive Endpoints, and Amazon SageMaker Unified Studio with no additional configuration, while the Flink, Livy, and Spark Operators are also supported. This capability is available at no additional cost, starting with Amazon EMR releases emr-7.14.0 and emr-spark-8.0.0. IPv6 cluster support is available in all AWS Regions where Amazon EMR on EKS and IPv6 Amazon EKS clusters are available. Amazon EMR on EKS IPv6 cluster support includes detailed setup instructions and documentation on supported submission models. Visit the Amazon EMR on EKS product page and the IPv6 documentation to learn more.

Published 23 Sep 2026 · Source checked 26 Sep 2026

Release notes and known issues →
AMAZON WEB SERVICESAMAZON-WEB-SERVICES-B9506809E9C1C5B8

Amazon DynamoDB global tables with multi-Region strong consistency now supports additional AWS Regions and cross-continent configurations

Starting today, Amazon DynamoDB global tables with multi-Region strong consistency (MRSC) is available in five additional AWS Regions: Canada (Central), Europe (Stockholm), Europe (Spain), Asia Pacific (Mumbai), and Asia Pacific (Singapore), bringing the total number of supported Regions to 15. You can now create an MRSC global table in any three-Region configuration across the 15 supported AWS Regions, configured with either three replicas or two replicas and one witness Region. This includes configurations that span North America, Europe, and Asia Pacific. MRSC lets you build highly available multi-Region applications with a recovery point objective (RPO) of zero. By choosing replica Regions closer to your users in more geographies, you can route applications to nearby DynamoDB endpoints for strongly consistent reads while keeping your application available during Regional impairments. MRSC is ideal for global applications with strict consistency requirements, such as user profile management, inventory tracking, order state, and entitlement management. To get started and view the complete list of supported Regions and configuration options, see the DynamoDB Developer Guide . To learn more about building resilient multi-Region applications, visit the DynamoDB global tables page .

Published 23 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
AMAZON WEB SERVICESAMAZON-WEB-SERVICES-D11052EC1C1ED9D3

Amazon Kinesis Data Streams announces Service-Managed Partition Keys for simplified data ingestion

Amazon Kinesis Data Streams now supports service-managed partition keys for On-Demand Standard and On-Demand Advantage streams, automatically distributing records across shards without requiring customers to specify partition keys to publish data. This capability simplifies data ingestion for workloads where record ordering is not required, eliminating hot partition keys and reducing time to production for streaming workloads. Amazon Kinesis Data Streams is a serverless streaming data service that makes it easy to capture, process, and store data streams at any scale. Many streaming use cases such as log aggregation, metrics collection, and IoT telemetry do not require ordering guarantees and benefit from prewarmed capacity for instant scaling. Previously, customers generated random partition keys (such as UUIDs) to distribute data, but random partitioning can still produce uneven throughput across shards, causing throttling for some partition keys even when the stream has sufficient aggregate capacity. By opting into service-managed partition keys, customers no longer need to specify partition keys when publishing data to streams in on-demand mode. The service automatically distributes records based on available warm capacity, allowing customers to scale to gigabytes per second without maintaining any distribution logic. Customers who want to send records without specifying a partition key can simply upgrade to the latest AWS SDK or Kinesis Producer Library (KPL) version to benefit from this capability. Service-managed partition keys for Amazon Kinesis Data Streams is available today in all AWS commercial regions at no additional cost. To get started, visit the Amazon Kinesis Data Streams documentation ( https://aws.amazon.com/kinesis ).

Published 23 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
GOOGLEANGULAR-22.1.8

22.1.8

common Commit Description remove abort listener on the abort path too in httpResource compiler Commit Description add return type to pure functions avoid hitting TypeScript limits if template has many translations do not copy expression type into output AST variables guard unverified ctor parameter types in class metadata compiler-cli Commit Description output function return types in linker core Commit Description don't use plain objects as maps for jsaction data ensure references are cleared from idle scheduler loosen return types for arrow functions in generated code wait for app stability before cleaning up dehydrated views forms Commit Description create controls before listeners platform-server Commit Description preserve Unicode whitespace in ServerXhr URLs router Commit Description avoid dense elements allocation for numeric URL keys

Published Never · Source checked 28 Sep 2026

Release notes and known issues →
GOOGLEANGULAR-22.2.0

22.2.0

compiler Commit Description allow template to access private props do not encapsulate nested selectors if parent contains ::ng-deep scope nested CSS rules compiler-cli Commit Description add strictUnclaimedEventNames option to catch misspelled output bindings scope type-checking of keyed defer blocks deduplicate deferred imports across multiple blocks core Commit Description add ErrorBoundary programmatic APIs ( #70463 ) add utility for testing directives allow reading Injector from a view or content query support annotations in WebMCP tool declarations cancel leave animations in nested views during list reordering support function and signal bindings in animate.enter and animate.leave update FakeNavigation to match WHATWG HTML spec forms Commit Description allow permanent hidden fields in signal forms hard-code readOnlyHint and untrustedContentHint for WebMCP implicit signal forms language-service Commit Description add support for @boundary blocks ( #70463 ) router Commit Description add containsTree as public API allow throwing RedirectCommand to trigger redirects expose router resources in public API stabilize auto cleanup injectors feature determine blocking state solely by resource loading status expose reload method on ActivatedRoute resources maintain frozen state on rollback until resource loading completes mark router_resource module-level symbols as side-effect free

Published Never · Source checked 28 Sep 2026

Release notes and known issues →
ELASTICBEATS-8.19.22

Beats 8.19.22

Downloads: https://elastic.co/downloads/beats Release notes: https://www.elastic.co/guide/en/beats/libbeat/8.19/release-notes-8.19.22.html

Published Never · Source checked 28 Sep 2026

Release notes and known issues →
PALO ALTO NETWORKSCVE-2026-0307

GlobalProtect App: Local Privilege Escalation Vulnerabilities

Multiple local privilege escalation vulnerabilities in the Palo Alto Networks GlobalProtect™ app allows a local user to escalate their privileges to NT AUTHORITY\SYSTEM on Windows and root on macOS and Linux. This enables a non-administrative user to execute arbitrary commands with administrative privileges. This GlobalProtect app on iOS, Android and ChromeOS is not impacted.

Published 9 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
ELASTICELASTICSEARCH-8.19.22

Elasticsearch 8.19.22

Downloads: https://elastic.co/downloads/elasticsearch Release notes: https://www.elastic.co/guide/en/elasticsearch/reference/8.19/release-notes-8.19.22.html

Published Never · Source checked 28 Sep 2026

Release notes and known issues →
OPENJS FOUNDATIONELECTRON-45.0.0-ALPHA.11

electron v45.0.0-alpha.11

Note: This is an alpha release. Please file new issues for any bugs you find in it. This release is published to npm under the alpha tag and can be installed via npm install electron@alpha , or npm install electron@45.0.0-alpha.11 . Release Notes for v45.0.0-alpha.11 Other Changes Backported fixes from upstream ANGLE, Chromium, PDFium and V8. #54220

Published Never · Source checked 28 Sep 2026

Release notes and known issues →
GOOGLEGOOGLE-CHROME-13F0CEE5C2507C6C

Chrome Beta for iOS Update

Hi everyone! We've just released Chrome Beta 155 (155.0.8059.16) for iOS; it'll become available on App Store in the next few days. You can see a partial list of the changes in the Git log . If you find a new issue, please let us know by filing a bug . Chrome Release Team Google Chrome

Published 23 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
GOOGLEGOOGLE-CHROME-155.0.8059.12

Chrome Beta for Desktop Update

The Beta channel has been updated to 155.0.8059.12 for Windows, Mac and Linux. A partial list of changes is available in the Git log . Interested in switching release channels? Find out how . If you find a new issue, please let us know by filing a bug . The community help forum is also a great place to reach out for help or learn about common issues. Chrome Release Team Google Chrome

Published 23 Sep 2026 · Source checked 26 Sep 2026

Release notes and known issues →
GOOGLEGOOGLE-CHROME-155.0.8059.16

Chrome Beta for iOS Update

Hi everyone! We've just released Chrome Beta 155 (155.0.8059.16) for iOS; it'll become available on App Store in the next few days. You can see a partial list of the changes in the Git log . If you find a new issue, please let us know by filing a bug . Chrome Release Team Google Chrome

Published 23 Sep 2026 · Source checked 26 Sep 2026

Release notes and known issues →
GOOGLEGOOGLE-CHROME-65BBCF732F79B9CC

Early Stable Update for Desktop

The Stable channel has been updated to 155.0.8059.12/.13 for Windows and Mac a s part of our early stable release to a small percentage of users. A full list of changes in this build is available in the log . You can find more details about early Stable releases here . Interested in switching release channels? Find out how here . If you find a new issue, please let us know by filing a bug . The community help forum is also a great place to reach out for help or learn about common issues. Srinivas Sista Google Chrome

Published 23 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
GOOGLEGOOGLE-CHROME-AF032DF88A607893

Chrome Beta for Desktop Update

The Beta channel has been updated to 155.0.8059.12 for Windows, Mac and Linux. A partial list of changes is available in the Git log . Interested in switching release channels? Find out how . If you find a new issue, please let us know by filing a bug . The community help forum is also a great place to reach out for help or learn about common issues. Chrome Release Team Google Chrome

Published 23 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
GOOGLEGOOGLE-CHROME-B8D6DCF338FBB15A

Chrome for Android Update

Hello Everyone! We've just released Chrome 155 (155.0.8059.16) for Android to a small percentage of users. It'll become available on Google Play over the next few days. You can find more details about early Stable releases here . This release includes stability and performance improvements. You can see a full list of the changes in the Git log . If you find a new issue, please let us know by filing a bug . Harry Souders Google Chrome

Published 23 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
GOOGLEGOOGLE-CHROME-C2C321B8D5EEAB86

Chrome Beta for Android Update

Hi everyone! We've just released Chrome Beta 155 (155.0.8059.16) for Android. It's now available on Google Play . You can see a partial list of the changes in the Git log . For details on new features, check out the Chromium blog , and for details on web platform updates, check here . If you find a new issue, please let us know by filing a bug . Chrome Release Team Google Chrome

Published 23 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
GOOGLEGOOGLE-WORKSPACE-1.1

Gemini Omni 1.1 Flash now in Vids with improved extension quality, 1080p, and duration control

Users now have access to Gemini Omni 1.1 Flash directly within Google Vids. Omni 1.1 provides higher quality video extension with significant improvements in character and audio consistency. Additionally, Vids now supports generating AI videos and upscaling AI videos to 1080p to be publish ready. Omni in Vids user experience Extend scenes with smooth transitions: Make scenes last longer while keeping the visual context, lighting, characters’ appearance, and the environment consistent. Set super-specific durations: Choose the exact duration of your generated clip so it aligns precisely with your story and voiceover. Generate in 1080p full HD: Create brand-new AI video scenes in full 1080p HD, or upscale existing AI clips to blend seamlessly across your timeline. Getting started Admins: This feature does not have an admin control. End users: Visit the Help Center to learn more about using Omni in Vids . Rollout pace Rapid Release and Scheduled Release domains: Full rollout (1–3 days for feature visibility) starting on September 23, 2026 Availability Business: Business Starter, Standard, and Plus Enterprise: Enterprise Starter, Standard, and Plus Education: Education Plus Consumer: Users with personal Google accounts; Google AI Pro and Ultra Other Editions: Enterprise Essentials and Enterprise Essentials Plus; Nonprofits; Individual Education Add-ons: Google AI Pro for Education; Teaching and Learning Other Add-ons: AI Expanded Access* *Users with AI Expanded Access add-on licenses have higher limits on usage of Omni in Vids. Resources Google Vids AI Limits: Learn about availability of AI features Google Vids Editors Help: Use AI to generate video clips

Published 23 Sep 2026 · Source checked 26 Sep 2026

Release notes and known issues →
GOOGLEGOOGLE-WORKSPACE-76CCC1F07CFE9ED2

Occupancy counting now available for Google Meet on Logitech room hardware

Occupancy counting is now available for Android-based Logitech Gen 2 room hardware (starting with Logitech Rally Board 65) to help measure how meeting rooms are used. This feature brings the same occupancy counting capabilities found on ChromeOS devices to Android-based hardware. Support for occupancy counting will be added next year for earlier Gen 1 devices later as part of an upcoming CollabOS update. Understanding room occupancy helps organizations optimize real estate and room design based on user needs. For instance, organizations can track if rooms with older video hardware are being avoided in favor of rooms equipped with better tracking cameras and audio bars. Admins can review occupancy data in the Google Admin console and optionally download it as a spreadsheet. This feature does not collect or store any personally identifiable information (PII). Because occupancy detection processes data locally on the device, the camera LED indicator may remain off during counting depending on the hardware vendor. Refer to vendor documentation for device-specific information. Review room booking and occupancy in the Admin console Getting started Admins: This feature will be off by default and can be enabled at the domain, organizational unit (OU), or group level. Visit the Help Center to learn more about turning on occupancy detection . End users: There is no end-user setting for this feature. Rollout pace Rapid Release and Scheduled Release domains: Extended rollout (potentially longer than 15 days for feature visibility) starting on September 28, 2026 Availability Available now to all Google Workspace customers with Google Meet on Logitech Gen 2 AOSP hardware devices (Rally Board 65 or later) with support for earlier devices coming in a future CollabOS update. Resources Google Workspace Admin Help: Turn on occupancy detection Google Workspace Admin Help: Track room and device usage with Meet hardware

Published 23 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
GOOGLEGOOGLE-WORKSPACE-7C6195865FE0538F

Assign temporary administrator roles in the Google Admin console

Admins can now assign administrator roles to users, groups, or service accounts for a defined period of time. Once the expiration time is reached, the access granted by the role is automatically revoked. This feature helps minimize security risks by reducing standing privileges and ambient access throughout your organization. It also streamlines administrative overhead, removing the need to manually track and revoke temporary privileges for short-term projects, coverage during employee absences, or external audits. When assigning a role, super admins can choose from predefined durations (such as 30 days) or set a custom expiration date and time. Temporary roles cannot be assigned to the primary admin for your organization, as the primary admin requires permanent super admin privileges. Getting started Admins: Visit the Help Center to learn more about assigning admin roles for a specific duration . End users: There is no end user setting for this feature. Rollout pace Rapid Release and Scheduled Release domains: Available now Availability Available to all Google Workspace customers Resources Google Workspace Admin Help: Assign admin roles for a specific duration

Published 23 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
GOOGLEGOOGLE-WORKSPACE-84006E0543BD6258

Ground AI prompts in Google Docs on existing sources from Gemini Notebook

We are introducing the ability to use Gemini Notebook as a context source in Google Docs. Building on our Workspace Intelligence foundation, this feature bridges the gap between deep research and content creation by grounding your drafts in a curated knowledge base – all without the need to switch tabs or copy-paste between tools. If you’ve organized research in Gemini Notebook, you can now seamlessly tap into that library right where you write in Google Docs. Whether you're drafting a project proposal or a technical whitepaper, simply type "@" in the side panel or bottom bar to reference an existing Notebook. Gemini will ground its output in your sources and provide inline citations, making it easy to verify facts while staying in the flow of your work. Getting started Admins: These features are available by default if Gemini for Workspace in Drive is enabled. Visit the Help Center to learn more about managing access to Gemini features in Google Workspace . End users: You must have Workspace smart features enabled to use these features. Visit the Help Center to learn more about creating personalized documents with Gemini in Google Docs . Rollout pace Rapid Release and Scheduled Release domains: Available now Availability Business: Business Standard and Plus Enterprise: Enterprise Standard and Plus Education: Education Plus Consumer: Google AI Pro and Ultra Education Add-ons: Google AI Pro for Education, Teaching and Learning Other Add-ons: AI Expanded Access Resources Google Workspace Admin Help: Manage Gemini for Google Workspace Google Help: Respond to & manage comments with Gemini in Google Docs Google Docs Editors Help: Learn how Gemini in Gmail, Calendar, Chat, Docs, Drive, Sheets, Slides, Meet & Vids protects your data

Published 23 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
GOOGLEGOOGLE-WORKSPACE-8BC56019347D2DA8

Gemini Omni 1.1 Flash now in Vids with improved extension quality, 1080p, and duration control

Users now have access to Gemini Omni 1.1 Flash directly within Google Vids. Omni 1.1 provides higher quality video extension with significant improvements in character and audio consistency. Additionally, Vids now supports generating AI videos and upscaling AI videos to 1080p to be publish ready. Omni in Vids user experience Extend scenes with smooth transitions: Make scenes last longer while keeping the visual context, lighting, characters’ appearance, and the environment consistent. Set super-specific durations: Choose the exact duration of your generated clip so it aligns precisely with your story and voiceover. Generate in 1080p full HD: Create brand-new AI video scenes in full 1080p HD, or upscale existing AI clips to blend seamlessly across your timeline. Getting started Admins: This feature does not have an admin control. End users: Visit the Help Center to learn more about using Omni in Vids . Rollout pace Rapid Release and Scheduled Release domains: Full rollout (1–3 days for feature visibility) starting on September 23, 2026 Availability Business: Business Starter, Standard, and Plus Enterprise: Enterprise Starter, Standard, and Plus Education: Education Plus Consumer: Users with personal Google accounts; Google AI Pro and Ultra Other Editions: Enterprise Essentials and Enterprise Essentials Plus; Nonprofits; Individual Education Add-ons: Google AI Pro for Education; Teaching and Learning Other Add-ons: AI Expanded Access* *Users with AI Expanded Access add-on licenses have higher limits on usage of Omni in Vids. Resources Google Vids AI Limits: Learn about availability of AI features Google Vids Editors Help: Use AI to generate video clips

Published 23 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
GOOGLEGOOGLE-WORKSPACE-9BD9ADF2597FE775

Seamlessly import your emails from any IMAP server to Google Workspace

We’re excited to announce the GA release of a new, simplified way for Workspace admins to import their past emails from any IMAP-based email provider while setting up Google Workspace. By using this new feature, Google Workspace admins can import past emails seamlessly in a few clicks from multiple IMAP servers including Hostinger, Zoho, Yahoo!, iCloud, and many more. This significantly reduces the time and effort required to switch to Google Workspace, and consolidates your important emails into one secure location. You can start the import process in two simple steps: Connect to the IMAP server of your choice Type in your IMAP email address and password Example of email import process from any IMAP server Additional details You can now import past emails of only one user through this new feature. Visit the Help Center to learn how to import emails from multiple IMAP accounts . You can import users and data only after completing your domain verification and email activation. The data import process runs in the background while you can continue with your Workspace setup. Getting started Admins: This feature will be available in the setup process for Google Workspace. Once you’ve verified your domain and activated your email records, you will find an option to import from IMAP-based email provider to Google Workspace. Visit the Help Center to learn more about importing emails from IMAP account during setup . End users: This feature is for admins only. Rollout pace Rapid Release and Scheduled Release domains: Available now Availability Available to all Google Workspace customers Resources Google Workspace Admin Help: Import business data during setup

Published 23 Sep 2026 · Source checked 28 Sep 2026

Release notes and known issues →
ELASTICKIBANA-8.19.22

Kibana 8.19.22

Downloads: https://elastic.co/downloads/kibana Release notes: https://www.elastic.co/guide/en/kibana/8.19/release-notes-8.19.22.html

Published Never · Source checked 28 Sep 2026

Release notes and known issues →
KUBERNETESKUBERNETES-1.34.12

v1.34.12

See kubernetes-announce@ . Additional binary downloads are linked in the CHANGELOG . See the CHANGELOG for more details.

Published Never · Source checked 28 Sep 2026

Release notes and known issues →
KUBERNETESKUBERNETES-1.35.9

v1.35.9

See kubernetes-announce@ . Additional binary downloads are linked in the CHANGELOG . See the CHANGELOG for more details.

Published Never · Source checked 28 Sep 2026

Release notes and known issues →
KUBERNETESKUBERNETES-1.36.5

v1.36.5

See kubernetes-announce@ . Additional binary downloads are linked in the CHANGELOG . See the CHANGELOG for more details.

Published Never · Source checked 28 Sep 2026

Release notes and known issues →
KUBERNETESKUBERNETES-1.37.1

v1.37.1

See kubernetes-announce@ . Additional binary downloads are linked in the CHANGELOG . See the CHANGELOG for more details.

Published Never · Source checked 28 Sep 2026

Release notes and known issues →