Merge branch 'v1.18' into affinity-docs

Author: MyMirelHub

.github/workflows/website-v1-18.yml

@@ -12,7 +12,7 @@ on:
 
 jobs:
   build_and_deploy_job:
-    if: github.event_name == 'push' || (github.event_name == 'pull_request' && github.event.action != 'closed')
+    if: github.event.action != 'closed'
     runs-on: ubuntu-latest
     name: Build and Deploy Job
     steps:

daprdocs/content/en/developing-ai/dapr-agents/_index.md

@@ -3,14 +3,18 @@ type: docs
 title: "Dapr Agents"
 linkTitle: "Dapr Agents"
 weight: 25
-description: "A framework for building durable and resilient AI agent systems at scale"
+description: "A production-ready framework for building durable and resilient AI agent systems at scale"
 aliases:
   - /developing-applications/dapr-agents
 ---
 
 ![Concepts Agents](/images/dapr-agents/agents-blue.png)
 
+{{% alert title="Dapr Agents v1.0 — Generally Available" color="primary" %}}
+Dapr Agents is **v1.0** and production ready. The framework provides stable APIs, enterprise-grade reliability, and support for building and operating LLM-powered agentic systems at scale.
+{{% /alert %}}
+
 ###  What is Dapr Agents?
 
 Dapr Agents is a Python framework for building LLM-powered autonomous agentic applications using Dapr's distributed systems capabilities. It provides tools for creating AI agents that can execute durable tasks, make decisions, and collaborate through workflows, while leveraging Dapr's state management, messaging, and observability features for reliable execution at scale.
- 
+ 

daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-introduction.md

@@ -10,6 +10,9 @@ aliases:
 
 ![Agent Overview](/images/dapr-agents/concepts-agents-overview.png)
 
+{{% alert title="Dapr Agents v1.0 — Generally Available" color="primary" %}}
+Dapr Agents **v1.0** is production ready with stable APIs and enterprise-grade support for agentic workloads.
+{{% /alert %}}
 
 Dapr Agents is a developer framework for building durable and resilient AI agent systems powered by Large Language Models (LLMs). Built on the battle-tested Dapr project, it enables developers to create autonomous systems that have identity, reason through problems, make dynamic decisions, and collaborate seamlessly. It includes built-in observability and stateful workflow execution to ensure agentic workflows complete successfully, regardless of complexity. Whether you're developing single-agent applications or complex multi-agent workflows, Dapr Agents provides the infrastructure for intelligent, adaptive systems that scale across environments.
 
@@ -89,4 +92,4 @@ These capabilities enable teams to monitor agent performance, secure multi-agent
 
 Whether you're interested in enhancing the framework, adding new integrations, or improving documentation, we welcome contributions from the community.
 
-For development setup and guidelines, see our [Contributor Guide]({{% ref "contributing/dapr-agents.md" %}}).
+For development setup and guidelines, see our [Contributor Guide]({{% ref "contributing/dapr-agents.md" %}}).

daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-why.md

@@ -8,7 +8,7 @@ aliases:
   - /developing-applications/dapr-agents/dapr-agents-why
 ---
 
-Dapr Agents is an open-source framework for building and orchestrating LLM-based autonomous agents that leverages Dapr's proven distributed systems foundation. Unlike other agentic frameworks that require developers to build infrastructure from scratch, Dapr Agents enables teams to focus on agent intelligence by providing enterprise-grade scalability, state management, and messaging capabilities out of the box. This approach eliminates the complexity of recreating distributed system fundamentals while delivering agentic workflows powered by Dapr.
+Dapr Agents is a production-ready, open-source framework (v1.0) for building and orchestrating LLM-based autonomous agents that leverages Dapr's proven distributed systems foundation. Unlike other agentic frameworks that require developers to build infrastructure from scratch, Dapr Agents enables teams to focus on agent intelligence by providing enterprise-grade scalability, state management, and messaging capabilities out of the box. This approach eliminates the complexity of recreating distributed system fundamentals while delivering agentic workflows powered by Dapr.
 
 ### Challenges with Existing Frameworks
 
@@ -134,4 +134,4 @@ By building on Dapr, platform and infrastructure teams can apply Dapr's [resilie
 
 ### Vendor-Neutral and Open Source
 
-As part of the **CNCF**, Dapr Agents is vendor-neutral, eliminating concerns about lock-in, intellectual property risks, or proprietary restrictions. Organizations gain full flexibility and control over their AI applications using open-source software they can audit and contribute to.
+As part of the **CNCF**, Dapr Agents is vendor-neutral, eliminating concerns about lock-in, intellectual property risks, or proprietary restrictions. Organizations gain full flexibility and control over their AI applications using open-source software they can audit and contribute to.

daprdocs/content/en/reference/components-reference/supported-pubsub/setup-pulsar.md

@@ -81,11 +81,15 @@ The above example uses secrets as plain strings. It is recommended to use a [sec
 | persistent         | N  | Pulsar supports two kinds of topics: [persistent](https://pulsar.apache.org/docs/en/concepts-architecture-overview#persistent-storage) and [non-persistent](https://pulsar.apache.org/docs/en/concepts-messaging/#non-persistent-topics). With persistent topics, all messages are durably persisted on disks (if the broker is not standalone, messages are durably persisted on multiple disks), whereas data for non-persistent topics is not persisted to storage disks.
 | disableBatching | N | disable batching.When batching enabled default batch delay is set to 10 ms and default batch size is 1000 messages,Setting `disableBatching: true` will make the producer to send messages individually. Default: `"false"` | `"true"`, `"false"`|
 | receiverQueueSize | N | Sets the size of the consumer receiver queue. Controls how many messages can be accumulated by the consumer before it is explicitly called to read messages by Dapr. Default: `"1000"` | `"1000"` |
+| redeliveryDelay | N | Delay before redelivering a message that was not acknowledged by the app. Default: `"30s"` | `"30s"`, `"200ms"` |
 | batchingMaxPublishDelay | N | batchingMaxPublishDelay set the time period within which the messages sent will be batched,if batch messages are enabled. If set to a non zero value, messages will be queued until this time interval or  batchingMaxMessages (see below) or  batchingMaxSize (see below). There are two valid formats, one is the fraction with a unit suffix format, and the other is the pure digital format that is processed as milliseconds. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default: `"10ms"` | `"10ms"`, `"10"`|
 | batchingMaxMessages | N | batchingMaxMessages set the maximum number of messages permitted in a batch.If set to a value greater than 1, messages will be queued until this threshold is reached or  batchingMaxSize (see below) has been reached or the batch interval has elapsed. Default: `"1000"` | `"1000"`|
 | batchingMaxSize | N | batchingMaxSize sets the maximum number of bytes permitted in a batch. If set to a value greater than 1, messages will be queued until this threshold is reached or batchingMaxMessages (see above) has been reached or the batch interval has elapsed. Default: `"128KB"` | `"131072"`|
+| compressionType | N | Sets the compression type for messages sent by the producer. Default: `"none"` | `"none"`, `"lz4"`, `"zlib"`, `"zstd"` |
+| compressionLevel | N | Sets the compression level used when `compressionType` is enabled. Default: `"default"` | `"default"`, `"faster"`, `"better"` |
 | <topic-name>.jsonschema          | N  | Enforces JSON schema validation for the configured topic. |
 | <topic-name>.avroschema          | N  | Enforces Avro schema validation for the configured topic. |
+| <topic-name>.rawschema          | N  | Registers the provided Avro or JSON schema as-is instead of wrapping it in a CloudEvents envelope schema. Default: `"false"` | `"true"`, `"false"` |
 | publicKey          | N  | A public key to be used for publisher and consumer encryption. Value can be one of two options: file path for a local PEM cert, or the cert data string value  |
 | privateKey          | N  | A private key to be used for consumer encryption. Value can be one of two options: file path for a local PEM cert, or the cert data string value  |
 | keys          | N  | A comma delimited string containing names of [Pulsar session keys](https://pulsar.apache.org/docs/3.0.x/security-encryption/#how-it-works-in-pulsar). Used in conjunction with `publicKey` for publisher encryption |