5 Commits

Include renames

Author	SHA1	Message	Date
4 people	1135deb1ec	docs: Fix typo in user management use case description (#10837) ... # Which Problems Are Solved - spelling error in the word **created** # How the Problems Are Solved - the spelling error was corrected Co-authored-by: elinashoko <[email protected]> Co-authored-by: Marco A. <[email protected]>	2025-10-07 13:58:21 +00:00
Gayathri VijayanandGitHub	6a93950b64	docs: fix the example docs related to set execution api (actions) (#10359) ... # Which Problems Are Solved Fix docs related to Actions V2 SetExecution API [endpoint](https://zitadel.com/docs/apis/resources/action_service_v2/action-service-set-execution) # How the Problems Are Solved The examples are updated # Additional Changes N/A # Additional Context - Closes #10320	2025-07-31 10:50:17 +02:00
Fabienne BühlerandGitHub	b8ff83454e	docs: product roadmap and zitadel versions (#9838) ... # Which Problems Are Solved The current public roadmap can be hard to understand for customers and it doesn't show the timelines for the different versions. which results in a lot of requests. It only outlines what is already fixed on the timeline, but doesn't give any possibilities to outline future topics / features, which not yet have a timeline # How the Problems Are Solved A new roadmap page is added - Outline for each version when it will have which state - Outline different zitadel versions with its features, deprecations, breaking changes, etc. - Show future topics, which are not yet on the roadmap	2025-06-03 13:44:04 +00:00
3 people	b8ba7bd5ba	fix: remove action feature flag and include execution (#9727) ... # Which Problems Are Solved Actions v2 is not a feature flag anymore, include functionality on executions is not used and json tags of proto messages are handled incorrectly. # How the Problems Are Solved - Remove actions from the feature flags on system and instance level - Remove include type on executions, only in the API, later maybe in the handling logic as well - Use protojson in request and response handling of actions v2 # Additional Changes - Correct integration tests for request and response handling - Use json.RawMessage for events, so that the event payload is not base64 encoded - Added separate context for async webhook calls, that executions are not cancelled when called async # Additional Context Related to #9759 Closes #9710 --------- Co-authored-by: Livio Spring <[email protected]>	2025-04-28 11:24:50 +02:00
+212 people	8fdd58f506	docs: add actions v2 docs (#9652) ... # Which Problems Are Solved There is no documentation yet for Actions v2 regarding the different usable types and for migrating from Actions v1 to v2. # How the Problems Are Solved Add documentation for all use-cases. # Additional Changes None # Additional Context Closes #9456 --------- Co-authored-by: Livio Spring <[email protected]> Co-authored-by: Silvan <[email protected]> Co-authored-by: Ramon <[email protected]> Co-authored-by: Elio Bischof <[email protected]> Co-authored-by: Kenta Yamaguchi <[email protected]> Co-authored-by: Harsha Reddy <[email protected]> Co-authored-by: Livio Spring <[email protected]> Co-authored-by: Max Peintner <[email protected]> Co-authored-by: Iraq <[email protected]> Co-authored-by: Copilot <[email protected]>	2025-04-09 13:29:58 +02:00