docs: v0.0.66 release notes, state notifications & long poll ack, amorphie logo - #17
Merged
Merged
Conversation
…, amorphie logo - blog/2026-06-29-v0-0-66.md: release notes for v0.0.66 (runtime 0.0.66, schema 0.0.48) covering state-level notifications (#722), root instance ID propagation (#769), RawRequestBodyBufferingMiddleware perf fix (#773), and parallel extension fetch DbContext fix (#771) - docs/components/workflow.md + EN mirror: new "State Notifications" section documenting the `notifications` array on states (type/mapping/rule fields, JSON example, Dapr binding reference, IStateNotificationMapping link); state lifecycle diagram updated with "Notification Enqueue" step; long poll section extended with `longpoll/ack` endpoint and fallback behaviour - docs/concepts/user-integration.md + EN mirror: interaction loop diagram updated with "Ack gerekli mi? → PATCH longpoll/ack" flow; step 2 updated with ack endpoint and fallback description - static/img/logo.svg, logo-dark.svg: replaced placeholder SVG with amorphie_logo_v2 (light) and amorphie_logo_v2_W (dark); docusaurus.config.ts alt text updated to "amorphie Logo" - src/css/custom.css: moved backdrop-filter from .navbar to .navbar::before to fix mobile sidebar positioning — backdrop-filter on a positioned element creates a new containing block, causing the fixed sidebar to render as a popup overlay instead of full-screen Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Reviewer's GuideDocs update for v0.0.66: new release notes blog, Workflow/User Integration reference updates for state notifications and long-poll acknowledge, navbar logo swap to official amorphie assets, and a CSS tweak to fix the mobile sidebar popup behaviour. Sequence diagram for client long-poll acknowledge interactionsequenceDiagram
actor Client
participant StateFunction
participant LongpollAckEndpoint
Client->>StateFunction: GET /functions/state (long-poll)
StateFunction-->>Client: State response when transition or fallbackTimeoutSeconds
Client->>LongpollAckEndpoint: PATCH /api/v1/{domain}/workflows/{workflow}/instances/{instance}/longpoll/ack
LongpollAckEndpoint-->>Client: 200 OK
alt Client cannot send ack
StateFunction-->>StateFunction: [fallbackTimeoutSeconds elapsed]
StateFunction-->>Client: Close long-poll connection
end
Flow diagram for updated state lifecycle with notificationsflowchart TD
A[Transition pipeline completes] --> B[State OnEntries]
B --> C[State Notifications enqueue]
C --> D[State Type Check]
subgraph NotificationProcessing
C --> E[Process IStateNotificationMapping]
E --> F[Send notification durably]
end
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (7)
📝 WalkthroughWalkthroughAdds a v0.0.66 release blog post and updates TR/EN workflow and user-integration documentation to cover state-level notifications, long-poll acknowledge endpoint ( Changesv0.0.66 Docs: State Notifications, Long-Poll Ack, CSS
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey - I've found 1 issue, and left some high level feedback:
- In the Workflow docs, the "stateNotification" field table describes entries of the
notificationsarray but uses a different name; consider aligning the heading/field naming with thenotificationsproperty to avoid confusion. - The English "State Notifications" section links to
/docs/components/interfaceswithout the#istatenotificationmappinganchor used in TR; adding the anchor would make the reference more precise and easier to navigate. - In
custom.css,.navbar::beforeis positioned absolutely; double-check that.navbaralways has a non-static position (e.g.,relative) across themes/layouts to ensure the blur overlay behaves consistently.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- In the Workflow docs, the "stateNotification" field table describes entries of the `notifications` array but uses a different name; consider aligning the heading/field naming with the `notifications` property to avoid confusion.
- The English "State Notifications" section links to `/docs/components/interfaces` without the `#istatenotificationmapping` anchor used in TR; adding the anchor would make the reference more precise and easier to navigate.
- In `custom.css`, `.navbar::before` is positioned absolutely; double-check that `.navbar` always has a non-static position (e.g., `relative`) across themes/layouts to ensure the blur overlay behaves consistently.
## Individual Comments
### Comment 1
<location path="docusaurus.config.ts" line_range="213" />
<code_context>
title: 'vNext Docs',
logo: {
- alt: 'vNext Logo',
+ alt: 'amorphie Logo',
src: 'img/logo.svg',
srcDark: 'img/logo-dark.svg',
</code_context>
<issue_to_address>
**question:** Consider whether the new alt text best reflects the logo’s purpose for screen readers.
Given the site title is `vNext Docs`, consider whether the logo alt should convey that context (e.g., `amorphie vNext Docs` or `vNext Docs home`) rather than only the brand name, so screen readers better reflect its navigational role.
</issue_to_address>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
| title: 'vNext Docs', | ||
| logo: { | ||
| alt: 'vNext Logo', | ||
| alt: 'amorphie Logo', |
There was a problem hiding this comment.
question: Consider whether the new alt text best reflects the logo’s purpose for screen readers.
Given the site title is vNext Docs, consider whether the logo alt should convey that context (e.g., amorphie vNext Docs or vNext Docs home) rather than only the brand name, so screen readers better reflect its navigational role.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request documents the v0.0.66 release, introducing state-level notifications and a new long-poll acknowledge endpoint. It updates Turkish and English documentation, flowcharts, and step-by-step guides accordingly. Additionally, it updates the site's branding to 'amorphie' with new SVG logos, adjusts the navbar CSS to resolve a mobile sidebar positioning issue, and updates the Docusaurus configuration. Feedback suggests adding a tip to the English workflow documentation to maintain consistency with the Turkish version regarding when the notification rule is evaluated.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| } | ||
| ``` | ||
|
|
||
| See [IStateNotificationMapping](/docs/components/interfaces) · [Notification Task](./tasks/notification). |
There was a problem hiding this comment.
The corresponding Turkish documentation (docs/components/workflow.md) includes a :::tip admonition in this section to clarify when the rule is used. To maintain consistency between language versions and improve clarity for English readers, a similar tip should be added here.
Suggested change
| See [IStateNotificationMapping](/docs/components/interfaces) · [Notification Task](./tasks/notification). | |
| See [IStateNotificationMapping](/docs/components/interfaces) · [Notification Task](./tasks/notification). | |
| :::tip | |
| The `rule` field is used to send notifications only under specific conditions (e.g., when arriving from a particular transition). If `rule` is omitted, a notification is enqueued on every state entry. | |
| ::: |
12 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
0.0.66, schema0.0.48)notificationsarray on states, lifecycle diagram updatedPATCH longpoll/ackendpoint added to Long Poll section and User Integration loop diagramamorphie_logo_v2(light/dark variants)backdrop-filtermoved from.navbarto.navbar::beforeto fix mobile sidebar popup issueWhat changed and why
Blog: v0.0.66 Release Notes (
blog/2026-06-29-v0-0-66.md)New release post for runtime
0.0.66/ schema0.0.48:notificationsarray on states, durable enqueue after pipelineRawRequestBodyBufferingMiddlewareWorkflow & User Integration docs (TR + EN)
docs/components/workflow.md: new State Notifications section (field table, JSON example, Dapr binding note,IStateNotificationMappingreference);notificationsfield added to State Alanları table; lifecycle diagram gains a "Notification Enqueue" step between OnEntries and State Type Check; Long Poll section extended withlongpoll/ackendpoint description and fallback behaviourdocs/concepts/user-integration.md: interaction loop diagram updated with Ack branch; step 2 updated with ack endpoint and fallback descriptionLogo update
Replaced placeholder
vNext Docstext SVGs with official amorphie branding:static/img/logo.svg→amorphie_logo_v2.svg(light mode, black text + coloured graphic)static/img/logo-dark.svg→amorphie_logo_v2_W.svg(dark mode, all white)docusaurus.config.tsalt text →amorphie Logov2 variant chosen over v1 for its horizontal proportions (895×154 vs 720×566) — better fit for navbar.
Mobile navbar fix (
src/css/custom.css)backdrop-filterapplied directly to aposition: sticky/fixedelement creates a new CSS containing block. Docusaurus's mobile sidebar usesposition: fixedand positions relative to its containing block — which was the navbar instead of the viewport, making it render as a small popup overlay.Fix:
backdrop-filtermoved to.navbar::before(absolute,inset: 0,z-index: -1) — same visual blur effect, no containing block side-effect.Reviewer notes
npm run build(both locales, no new broken links)Summary by Sourcery
Document state-level notifications and long-poll acknowledge behavior, add v0.0.66 release notes, and update branding and navbar styling.
Enhancements:
Documentation:
Summary by CodeRabbit
New Features
Bug Fixes
Documentation
Style