Conversation
Bumps [amannn/action-semantic-pull-request](https://github.com/amannn/action-semantic-pull-request) from 5 to 6. - [Release notes](https://github.com/amannn/action-semantic-pull-request/releases) - [Changelog](https://github.com/amannn/action-semantic-pull-request/blob/main/CHANGELOG.md) - [Commits](amannn/action-semantic-pull-request@v5...v6) --- updated-dependencies: - dependency-name: amannn/action-semantic-pull-request dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
cschiewek
changed the title
cschiewek
approved these changes
Dec 9, 2025
cschiewek
deleted the
dependabot/github_actions/amannn/action-semantic-pull-request-6
branch
benwilson512
pushed a commit
that referenced
this pull request
Mar 15, 2026
* feat: Add :registry_partition_strategy option to Absinthe.Subscription (#1395) * feat: Add :keys option to Absinthe.Subscription * change option for specifying how the registry is partitioned * chore(ci): Enable dependabot updates for github actions (#1397) * Bump actions/checkout from 3 to 6 (#1398) Bumps [actions/checkout](https://github.com/actions/checkout) from 3 to 6. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v3...v6) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(ci): Bump amannn/action-semantic-pull-request from 5 to 6 (#1399) Bumps [amannn/action-semantic-pull-request](https://github.com/amannn/action-semantic-pull-request) from 5 to 6. - [Release notes](https://github.com/amannn/action-semantic-pull-request/releases) - [Changelog](https://github.com/amannn/action-semantic-pull-request/blob/main/CHANGELOG.md) - [Commits](amannn/action-semantic-pull-request@v5...v6) --- updated-dependencies: - dependency-name: amannn/action-semantic-pull-request dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * fix: only null values should also trigger error (#1394) Co-authored-by: Peter Arentsen <peter.arentsen@bettyblocks.com> * feat: Implement @defer and @stream directives for incremental delivery (#1377) * update * fix introspection * add claude.md * Fix mix tasks to respect schema adapter for proper naming conventions - Fix mix absinthe.schema.json to use schema's adapter for introspection - Fix mix absinthe.schema.sdl to use schema's adapter for directive names - Update SDL renderer to accept adapter parameter and use it for directive definitions - Ensure directive names follow naming conventions (camelCase, etc.) in generated SDL 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * feat: Add field description inheritance from referenced types When a field has no description, it now inherits the description from its referenced type during introspection. This provides better documentation for GraphQL APIs by automatically propagating type descriptions to fields. - Modified __field introspection resolver to fall back to type descriptions - Handles wrapped types (non_null, list_of) correctly by unwrapping first - Added comprehensive test coverage for various inheritance scenarios - Updated field documentation to explain the new behavior 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * gitignore local settings * fix sdl render * feat: Add @defer and @stream directive support for incremental delivery - Add @defer directive for deferred fragment execution - Add @stream directive for incremental list delivery - Implement streaming resolution phase - Add incremental response builder - Add transport abstraction layer - Implement Dataloader integration for streaming - Add error handling and resource management - Add complexity analysis for streaming operations - Add auto-optimization middleware - Add comprehensive test suite - Add performance benchmarks - Add pipeline integration hooks - Add configuration system * docs: Add comprehensive incremental delivery documentation - Complete usage guide with examples - API reference for @defer and @stream directives - Performance optimization guidelines - Transport configuration details - Troubleshooting and monitoring guidance 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * fix: Correct Elixir syntax errors in incremental delivery implementation - Fix Ruby-style return statements in auto_defer_stream middleware - Correct Elixir typespec syntax in response module - Mark unused variables with underscore prefix - Remove invalid optional() syntax from typespecs 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * fix: Update test infrastructure for incremental delivery - Fix supervisor startup handling in tests - Simplify test helpers to use standard Absinthe.run - Enable basic test execution for incremental delivery features - Address compilation issues and warnings Tests now run successfully and provide baseline for further development. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * feat: Complete @defer and @stream directive implementation This commit finalizes the implementation of GraphQL @defer and @stream directives for incremental delivery in Absinthe: - Fix streaming resolution phase to properly handle defer/stream flags - Update projector to gracefully handle defer/stream flags without crashing - Improve telemetry phases to handle missing blueprint context gracefully - Add comprehensive test infrastructure for incremental delivery - Create debug script for testing directive processing - Add BuiltIns module for proper directive loading The @defer and @stream directives now work correctly according to the GraphQL specification, allowing for incremental query result delivery. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * docs: Add comprehensive incremental delivery guide Add detailed guide for @defer and @stream directives following the same structure as other Absinthe feature guides. Includes: - Basic usage examples - Configuration options - Transport integration (WebSocket, SSE) - Advanced patterns (conditional, nested) - Error handling - Performance considerations - Relay integration - Testing approaches - Migration guidance 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Add incremental delivery guide to documentation extras Include guides/incremental-delivery.md in the mix.exs extras list so it appears in the generated documentation alongside other guides. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Remove automatic field description inheritance Based on community feedback from PR #1373, automatic field description inheritance was not well received. The community preferred explicit field descriptions that are specific to each field's context rather than automatically inheriting from the referenced type. This commit: - Reverts the automatic inheritance behavior in introspection - Removes the associated test file - Returns to the standard field description handling 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Fix code formatting Run mix format to fix formatting issues detected by CI. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * fix dialyzer * remove elixir 1.19 * fix: resolve @defer/@stream incremental delivery issues - Fix Absinthe.Type.list?/1 undefined function by using pattern matching - Fix directive expand callbacks to return node directly (not {:ok, node}) - Add missing analyze_node clauses for Operation and Fragment.Named nodes - Fix defer depth tracking for nested defers - Fix projector to only skip __skip_initial__ flagged nodes, not all defer/stream - Update introspection tests for new @defer/@stream directives - Remove duplicate documentation files per PR review - Add comprehensive complexity analysis tests Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: clarify supervisor startup and dataloader integration Address review comments: - Add detailed documentation on how to start the Incremental Supervisor - Include configuration options and examples in supervisor docs - Add usage documentation for Dataloader integration - Explain how streaming-aware resolvers work with batching Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * chore: remove debug test file * feat: add on_event callback for monitoring integrations Add an `on_event` callback option to the incremental delivery system that allows sending defer/stream events to external monitoring services like Sentry, DataDog, or custom telemetry systems. The callback is invoked at each stage of incremental delivery: - `:initial` - When the initial response is sent - `:incremental` - When each deferred/streamed payload is delivered - `:complete` - When the stream completes successfully - `:error` - When an error occurs during streaming Each event includes payload data and metadata such as: - `operation_id` - Unique identifier for tracking - `path` - GraphQL path to the deferred field - `label` - Label from @defer/@stream directive - `duration_ms` - Time taken for the operation - `task_type` - `:defer` or `:stream` Example usage: Absinthe.run(query, schema, on_event: fn :error, payload, metadata -> Sentry.capture_message("GraphQL streaming error", extra: %{payload: payload, metadata: metadata} ) _, _, _ -> :ok end ) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * feat: add telemetry events for incremental delivery instrumentation Add telemetry events for the incremental delivery transport layer to enable integration with instrumentation libraries like opentelemetry_absinthe. New telemetry events: - `[:absinthe, :incremental, :delivery, :initial]` Emitted when initial response is sent with has_next, pending_count - `[:absinthe, :incremental, :delivery, :payload]` Emitted for each @defer/@stream payload with path, label, task_type, duration, and success status - `[:absinthe, :incremental, :delivery, :complete]` Emitted when streaming completes successfully with total duration - `[:absinthe, :incremental, :delivery, :error]` Emitted on errors with reason and message All events include operation_id for correlation across spans. Events follow the same pattern as existing Absinthe telemetry events with measurements (system_time, duration) and metadata. This enables opentelemetry_absinthe and other instrumentation libraries to create proper spans for @defer/@stream operations. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: add incremental delivery telemetry documentation Update the telemetry guide to document the new @defer/@stream events: - [:absinthe, :incremental, :delivery, :initial] - [:absinthe, :incremental, :delivery, :payload] - [:absinthe, :incremental, :delivery, :complete] - [:absinthe, :incremental, :delivery, :error] Includes detailed documentation of measurements and metadata for each event, plus examples for attaching handlers and using the on_event callback for custom monitoring integrations. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: add incremental delivery to CHANGELOG Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: clarify @defer/@stream are draft/RFC, not finalized spec The incremental delivery directives are still in the RFC stage and not yet part of the finalized GraphQL specification. Updated documentation to make this clear and link to the actual RFC. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * feat: make @defer/@stream directives opt-in Move @defer and @stream directives from core built-ins to a new opt-in module Absinthe.Type.BuiltIns.IncrementalDirectives. Since @defer/@stream are draft-spec features (not yet finalized), users must now explicitly opt-in by adding: import_types Absinthe.Type.BuiltIns.IncrementalDirectives to their schema definition. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * chore: fix formatting across incremental delivery files Run mix format to fix whitespace and formatting issues that were causing CI to fail. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * ci: restore Elixir 1.19 support Restore Elixir 1.19 to the CI matrix to match upstream main. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * feat: unify streaming architecture for subscriptions and incremental delivery - Add Absinthe.Streaming module with shared abstractions - Add Absinthe.Streaming.Executor behaviour for pluggable task execution - Add Absinthe.Streaming.TaskExecutor as default executor (Task.async_stream) - Add Absinthe.Streaming.Delivery for pubsub incremental delivery - Enable @defer/@stream in subscriptions (automatic multi-payload delivery) - Refactor Transport to use shared TaskExecutor - Update Subscription.Local to detect and handle incremental directives - Add comprehensive backwards compatibility tests - Update guides and documentation Subscriptions with @defer/@stream now automatically deliver multiple payloads using the standard GraphQL incremental format. Existing PubSub implementations work unchanged - publish_subscription/2 is called multiple times. Custom executors (Oban, RabbitMQ, etc.) can be configured via: - Schema attribute: @streaming_executor MyApp.ObanExecutor - Context: context: %{streaming_executor: MyApp.ObanExecutor} - Application config: config :absinthe, :streaming_executor, MyApp.ObanExecutor Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * refactor: extract middleware and telemetry modules for better discoverability - Move Absinthe.Middleware.IncrementalComplexity to its own file in lib/absinthe/middleware/ - Move Absinthe.Incremental.TelemetryReporter to its own file in lib/absinthe/incremental/ - Improves code organization and makes these modules easier to find Addresses PR review feedback from @bryanjos Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com> * Break function dispatch into groups Currently Absinthe may generate thousands of clauses for a single function, each with a distinct tagged tuple type. While the Elixir team aims to improve the type system performance across all cases, it is undeniable that these many clauses put pressure on both the compiler and the type system, so we split them by identifier in Absinthe itself. * mix format --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Bryan Joseph <bryanjos@gmail.com> Co-authored-by: Curtis Schiewek <curtis.schiewek@hey.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: nulian <peter.arentsen@quicknet.nl> Co-authored-by: Peter Arentsen <peter.arentsen@bettyblocks.com> Co-authored-by: Jason Waldrip <jason@waldrip.net> Co-authored-by: Claude <noreply@anthropic.com>
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.
Bumps amannn/action-semantic-pull-request from 5 to 6.
Release notes
Sourced from amannn/action-semantic-pull-request's releases.
... (truncated)
Changelog
Sourced from amannn/action-semantic-pull-request's changelog.
... (truncated)
Commits
48f2562chore: Release 6.1.1 [skip ci]800da4cfix: ParseheaderPatternCorrespondenceproperly (#295)677b895test: Fix broken test24e6f01ci: Fix permissions for tagger7f33ba7chore: Release 6.1.0 [skip ci]afa4edbfix: Remove trailing whitespace from "unknown release type" error message (#291)a30288bfeat: Support providing regexps for types (#292)a46a7c8build: Move Vitest todevDependencies(#290)fdd4d3dchore: Release 6.0.1 [skip ci]58e4ab4fix: Actually execute action (#289)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)