{"prototype_id": "2dust__v2rayNG_release_window", "repo": "2dust/v2rayNG", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the 2dust/v2rayNG releases, which release introduces WebDAV remote backup and a new tabbed main interface for grouping by subscription?", "options": [{"option_id": "A", "text": "2.0.13"}, {"option_id": "B", "text": "2.0.14"}, {"option_id": "C", "text": "2.0.15"}, {"option_id": "D", "text": "2.0.16"}], "correct_option_id": "A", "expected_answer": "2.0.13", "source_chunk_ids": ["2dust__v2rayNG__release__2_0_13"], "answer_support": [{"memory_node_id": "2dust__v2rayNG__release__2_0_13", "answer_text": "WebDAV remote backup, a new tabbed main interface for grouping by subscription"}]}
{"prototype_id": "2dust__v2rayNG_release_window", "repo": "2dust/v2rayNG", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the 2dust/v2rayNG release window, order the following release-content states from earliest to latest: (1) a release that adds chain proxy and a concurrency option for real connection latency tests, (2) a release that adds Browser Dialer, (3) a release that adds log sharing, (4) a release that adds pull-down subscription update and a locate selected server function.", "options": [{"option_id": "A", "text": "4 -> 1 -> 2 -> 3"}, {"option_id": "B", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "C", "text": "4 -> 2 -> 1 -> 3"}, {"option_id": "D", "text": "3 -> 4 -> 1 -> 2"}], "correct_option_id": "A", "expected_answer": "4 -> 1 -> 2 -> 3", "source_chunk_ids": ["2dust__v2rayNG__release__2_0_15", "2dust__v2rayNG__release__2_1_5", "2dust__v2rayNG__release__2_1_6", "2dust__v2rayNG__release__2_2_1"], "answer_support": [{"memory_node_id": "2dust__v2rayNG__release__2_0_15", "answer_text": "Pull-down subscription update and a locate selected server function were added"}, {"memory_node_id": "2dust__v2rayNG__release__2_1_5", "answer_text": "Chain proxy was added. A concurrency option for real connection latency tests was added"}, {"memory_node_id": "2dust__v2rayNG__release__2_1_6", "answer_text": "Browser Dialer was added"}, {"memory_node_id": "2dust__v2rayNG__release__2_2_1", "answer_text": "Log sharing was added"}]}
{"prototype_id": "aaif_goose__goose_release_window", "repo": "aaif-goose/goose", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the aaif-goose/goose releases, which release introduces slash commands such as /prompts, /prompt, /compact, and /clear?", "options": [{"option_id": "A", "text": "v1.17.0"}, {"option_id": "B", "text": "v1.18.0"}, {"option_id": "C", "text": "v1.19.0"}, {"option_id": "D", "text": "v1.20.0"}], "correct_option_id": "B", "expected_answer": "v1.18.0", "source_chunk_ids": ["aaif_goose__goose__release__v1_18_0"], "answer_support": [{"memory_node_id": "aaif_goose__goose__release__v1_18_0", "answer_text": "slash commands are introduced: /prompts, /prompt, /compact, /clear"}]}
{"prototype_id": "agno_agi__agno_release_window", "repo": "agno-agi/agno", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the agno-agi/agno releases, which release introduces Team execution modes (coordinate, route, broadcast, tasks) along with an Approval system using the @approval decorator?", "options": [{"option_id": "A", "text": "v2.4.8"}, {"option_id": "B", "text": "v2.5.0"}, {"option_id": "C", "text": "v2.5.1"}, {"option_id": "D", "text": "v2.5.2"}], "correct_option_id": "B", "expected_answer": "v2.5.0", "source_chunk_ids": ["agno_agi__agno__release__v2_5_0"], "answer_support": [{"memory_node_id": "agno_agi__agno__release__v2_5_0", "answer_text": "new features introduce Team execution modes (coordinate, route, broadcast, tasks) ... an Approval system with @approval decorator"}]}
{"prototype_id": "agno_agi__agno_release_window", "repo": "agno-agi/agno", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the agno-agi/agno releases, how does the license change in v2.5.2 differ from the breaking change regarding session types in v2.6.0?", "options": [{"option_id": "A", "text": "v2.5.2 changes the license from MPL 2.0 to Apache Software License, while v2.6.0 makes the /sessions endpoint return all session types by default instead of filtering."}, {"option_id": "B", "text": "v2.5.2 introduces a new license for contributions, while v2.6.0 removes the /sessions endpoint entirely."}, {"option_id": "C", "text": "Both releases only update documentation without functional changes."}, {"option_id": "D", "text": "v2.5.2 adds a proprietary license, while v2.6.0 restricts sessions to agent type only."}], "correct_option_id": "A", "expected_answer": "v2.5.2 changes the license from MPL 2.0 to Apache Software License, while v2.6.0 makes the /sessions endpoint return all session types by default instead of filtering.", "source_chunk_ids": ["agno_agi__agno__release__v2_5_2", "agno_agi__agno__release__v2_6_0"], "answer_support": [{"memory_node_id": "agno_agi__agno__release__v2_5_2", "answer_text": "the license is changed from Mozilla Public License 2.0 (MPL 2.0) to Apache Software License"}, {"memory_node_id": "agno_agi__agno__release__v2_6_0", "answer_text": "Breaking change: /sessions endpoint now returns all session types by default"}]}
{"prototype_id": "agno_agi__agno_release_window", "repo": "agno-agi/agno", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the agno-agi/agno release window, order the following release-content states from earliest to latest: (1) a release that adds CEL support for workflow steps and a Neosantara model provider, (2) a release that introduces Team execution modes and an Approval system, (3) a release that adds Fallback Models for Agents and Teams, (4) a release that adds multi-framework support in AgentOS and Context Provider.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["agno_agi__agno__release__v2_4_8", "agno_agi__agno__release__v2_5_0", "agno_agi__agno__release__v2_5_14", "agno_agi__agno__release__v2_6_0"], "answer_support": [{"memory_node_id": "agno_agi__agno__release__v2_4_8", "answer_text": "new features include CEL support for workflow steps, a Neosantara model provider"}, {"memory_node_id": "agno_agi__agno__release__v2_5_0", "answer_text": "new features introduce Team execution modes ... an Approval system"}, {"memory_node_id": "agno_agi__agno__release__v2_5_14", "answer_text": "new features add Fallback Models for Agents and Teams"}, {"memory_node_id": "agno_agi__agno__release__v2_6_0", "answer_text": "new features add ... multi-framework support in AgentOS ... Context Provider"}]}
{"prototype_id": "Aider_AI__aider_release_window", "repo": "Aider-AI/aider", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the Aider-AI/aider releases, which release introduces the Architect/Editor model pair for improved coding?", "options": [{"option_id": "A", "text": "v0.57.0"}, {"option_id": "B", "text": "v0.58.0"}, {"option_id": "C", "text": "v0.59.0"}, {"option_id": "D", "text": "v0.60.0"}], "correct_option_id": "B", "expected_answer": "v0.58.0", "source_chunk_ids": ["Aider_AI__aider__release__v0_58_0"], "answer_support": [{"memory_node_id": "Aider_AI__aider__release__v0_58_0", "answer_text": "a pair of Architect/Editor models for improved coding"}]}
{"prototype_id": "Aider_AI__aider_release_window", "repo": "Aider-AI/aider", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the Aider-AI/aider releases, how does the watch files feature in v0.67.0 differ from the watch files improvements in v0.69.0?", "options": [{"option_id": "A", "text": "v0.67.0 introduces AI! comments to trigger aider, while v0.69.0 adds AI? comments for asking questions and extends watching to all files."}, {"option_id": "B", "text": "v0.67.0 adds AI? comments, while v0.69.0 removes watch files support."}, {"option_id": "C", "text": "Both releases only add support for new models without changing watch files."}, {"option_id": "D", "text": "v0.67.0 watches all files, while v0.69.0 restricts watching to source files only."}], "correct_option_id": "A", "expected_answer": "v0.67.0 introduces AI! comments to trigger aider, while v0.69.0 adds AI? comments for asking questions and extends watching to all files.", "source_chunk_ids": ["Aider_AI__aider__release__v0_67_0", "Aider_AI__aider__release__v0_69_0"], "answer_support": [{"memory_node_id": "Aider_AI__aider__release__v0_67_0", "answer_text": "One-liner '# ...' or '// ...' comments that start or end with 'AI' are instructions to aider. When aider sees 'AI!' it reads and follows all the instructions in AI comments."}, {"memory_node_id": "Aider_AI__aider__release__v0_69_0", "answer_text": "Use '# ... AI?' comments to trigger aider and ask questions about your code. Now watches *all* files, not just certain source files."}]}
{"prototype_id": "Aider_AI__aider_release_window", "repo": "Aider-AI/aider", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the Aider-AI/aider release window, order the following release-content states from earliest to latest: (1) a release that adds support for GPT-5 models, (2) a release that adds support for GPT 4.1, mini and nano, (3) a release that adds full support for o3-mini with a --reasoning-effort argument.", "options": [{"option_id": "A", "text": "3 -> 2 -> 1"}, {"option_id": "B", "text": "2 -> 3 -> 1"}, {"option_id": "C", "text": "1 -> 2 -> 3"}, {"option_id": "D", "text": "2 -> 1 -> 3"}], "correct_option_id": "A", "expected_answer": "3 -> 2 -> 1", "source_chunk_ids": ["Aider_AI__aider__release__v0_73_0", "Aider_AI__aider__release__v0_82_0", "Aider_AI__aider__release__v0_86_0"], "answer_support": [{"memory_node_id": "Aider_AI__aider__release__v0_73_0", "answer_text": "Full support for o3-mini: `aider --model o3-mini` ... New `--reasoning-effort` argument: low, medium, high."}, {"memory_node_id": "Aider_AI__aider__release__v0_82_0", "answer_text": "Support for GPT 4.1, mini and nano."}, {"memory_node_id": "Aider_AI__aider__release__v0_86_0", "answer_text": "Added support for all GPT-5 models."}]}
{"prototype_id": "airbnb__lottie_android_release_window", "repo": "airbnb/lottie-android", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the airbnb/lottie-android releases, which release adds support for gaussian blur effects and drop shadow effects?", "options": [{"option_id": "A", "text": "4.0.0"}, {"option_id": "B", "text": "4.1.0"}, {"option_id": "C", "text": "4.2.0"}, {"option_id": "D", "text": "4.2.1"}], "correct_option_id": "B", "expected_answer": "4.1.0", "source_chunk_ids": ["airbnb__lottie_android__release__v4_1_0"], "answer_support": [{"memory_node_id": "airbnb__lottie_android__release__v4_1_0", "answer_text": "Added support for gaussian blur effects and drop shadow effects"}]}
{"prototype_id": "airbnb__lottie_android_release_window", "repo": "airbnb/lottie-android", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the airbnb/lottie-android releases, how does the rendering mode change in 5.0.1 differ from the multithreaded update feature introduced in 6.1.0?", "options": [{"option_id": "A", "text": "5.0.1 removes setScale APIs and overhauls rendering to reduce memory, while 6.1.0 adds asyncUpdates to move the update phase off the main thread."}, {"option_id": "B", "text": "5.0.1 introduces asyncUpdates, while 6.1.0 removes setScale APIs."}, {"option_id": "C", "text": "Both releases only fix NPEs without changing rendering."}, {"option_id": "D", "text": "5.0.1 adds 3D animation support, while 6.1.0 adds blend modes."}], "correct_option_id": "A", "expected_answer": "5.0.1 removes setScale APIs and overhauls rendering to reduce memory, while 6.1.0 adds asyncUpdates to move the update phase off the main thread.", "source_chunk_ids": ["airbnb__lottie_android__release__v5_0_1", "airbnb__lottie_android__release__v6_1_0"], "answer_support": [{"memory_node_id": "airbnb__lottie_android__release__v5_0_1", "answer_text": "Removed the setScale(float) APIs ... rendering mode handling is overhauled to reduce memory consumption"}, {"memory_node_id": "airbnb__lottie_android__release__v6_1_0", "answer_text": "New multithreaded asyncUpdates feature which moves the entire update phase of an animation off of the main thread"}]}
{"prototype_id": "airbnb__lottie_android_release_window", "repo": "airbnb/lottie-android", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the airbnb/lottie-android release window, order the following release-content states from earliest to latest: (1) a release that adds support for gaussian blur and drop shadow effects, (2) a release that introduces a Compose breaking change where LottieAnimation takes progress as a () -> Float, (3) a release that adds initial support for 3D animations.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["airbnb__lottie_android__release__v4_1_0", "airbnb__lottie_android__release__v5_2_0", "airbnb__lottie_android__release__v6_7_0"], "answer_support": [{"memory_node_id": "airbnb__lottie_android__release__v4_1_0", "answer_text": "Added support for gaussian blur effects and drop shadow effects"}, {"memory_node_id": "airbnb__lottie_android__release__v5_2_0", "answer_text": "Compose Breaking Change: LottieAnimation now takes progress as a () -> Float"}, {"memory_node_id": "airbnb__lottie_android__release__v6_7_0", "answer_text": "Initial support for 3D animations"}]}
{"prototype_id": "ajeetdsouza__zoxide_release_window", "repo": "ajeetdsouza/zoxide", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the ajeetdsouza/zoxide releases, which release adds support for the Korn shell (ksh)?", "options": [{"option_id": "A", "text": "v0.9.5"}, {"option_id": "B", "text": "v0.9.8"}, {"option_id": "C", "text": "v0.9.7"}, {"option_id": "D", "text": "v0.9.9"}], "correct_option_id": "A", "expected_answer": "v0.9.5", "source_chunk_ids": ["ajeetdsouza__zoxide__release__v0_9_5"], "answer_support": [{"memory_node_id": "ajeetdsouza__zoxide__release__v0_9_5", "answer_text": "ksh: added support for the Korn shell."}]}
{"prototype_id": "ajeetdsouza__zoxide_release_window", "repo": "ajeetdsouza/zoxide", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the ajeetdsouza/zoxide release window, order the following release-content states from earliest to latest: (1) a release that adds support for PowerShell, (2) a release that adds support for the xonsh shell, (3) a release that adds support for Nushell and Elvish.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["ajeetdsouza__zoxide__release__v0_4_1", "ajeetdsouza__zoxide__release__v0_5_0", "ajeetdsouza__zoxide__release__v0_6_0"], "answer_support": [{"memory_node_id": "ajeetdsouza__zoxide__release__v0_4_1", "answer_text": "Support for PowerShell."}, {"memory_node_id": "ajeetdsouza__zoxide__release__v0_5_0", "answer_text": "Support for the xonsh shell."}, {"memory_node_id": "ajeetdsouza__zoxide__release__v0_6_0", "answer_text": "Support for Nushell and Elvish."}]}
{"prototype_id": "alacritty__alacritty_release_window", "repo": "alacritty/alacritty", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the alacritty/alacritty releases, which release adds support for fractional scaling on Wayland with wp-fractional-scale protocol?", "options": [{"option_id": "A", "text": "v0.12.0"}, {"option_id": "B", "text": "v0.13.0"}, {"option_id": "C", "text": "v0.14.0"}, {"option_id": "D", "text": "v0.15.0"}], "correct_option_id": "A", "expected_answer": "v0.12.0", "source_chunk_ids": ["alacritty__alacritty__release__v0_12_0"], "answer_support": [{"memory_node_id": "alacritty__alacritty__release__v0_12_0", "answer_text": "support for fractional scaling on Wayland with wp-fractional-scale protocol"}]}
{"prototype_id": "alacritty__alacritty_release_window", "repo": "alacritty/alacritty", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the alacritty/alacritty releases, how does the configuration file format change described in v0.13.0 differ from the configuration-related change described in v0.14.0?", "options": [{"option_id": "A", "text": "v0.13.0 switches from YAML to TOML, while v0.14.0 moves several config options to a new general section."}, {"option_id": "B", "text": "v0.13.0 introduces TOML support, while v0.14.0 removes TOML support."}, {"option_id": "C", "text": "Both releases only add new keybindings without configuration changes."}, {"option_id": "D", "text": "v0.13.0 deprecates all mouse bindings, while v0.14.0 restores YAML configuration."}], "correct_option_id": "A", "expected_answer": "v0.13.0 switches from YAML to TOML, while v0.14.0 moves several config options to a new general section.", "source_chunk_ids": ["alacritty__alacritty__release__v0_13_0", "alacritty__alacritty__release__v0_14_0"], "answer_support": [{"memory_node_id": "alacritty__alacritty__release__v0_13_0", "answer_text": "Configuration file now uses TOML instead of YAML"}, {"memory_node_id": "alacritty__alacritty__release__v0_14_0", "answer_text": "Moved config options import, working_directory, live_config_reload, and ipc_socket to the new general section"}]}
{"prototype_id": "Alamofire__Alamofire_release_window", "repo": "Alamofire/Alamofire", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the Alamofire/Alamofire releases, which release adds Combine support with DataResponsePublisher, DownloadResponsePublisher, and DataStreamPublisher?", "options": [{"option_id": "A", "text": "5.1.0"}, {"option_id": "B", "text": "5.2.0"}, {"option_id": "C", "text": "5.3.0"}, {"option_id": "D", "text": "5.4.0"}], "correct_option_id": "B", "expected_answer": "5.2.0", "source_chunk_ids": ["Alamofire__Alamofire__release__5_2_0"], "answer_support": [{"memory_node_id": "Alamofire__Alamofire__release__5_2_0", "answer_text": "adds Combine support with DataResponsePublisher, DownloadResponsePublisher, and DataStreamPublisher"}]}
{"prototype_id": "Alamofire__Alamofire_release_window", "repo": "Alamofire/Alamofire", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the Alamofire/Alamofire release window, order the following release-content states from earliest to latest: (1) a release that adds request body compression support, (2) a release that adds Combine support with publishers, (3) a release that adds experimental WebSocketRequest, (4) a release that adds full Swift concurrency support with Sendable requirements.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "B", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "C", "text": "2 -> 3 -> 1 -> 4"}, {"option_id": "D", "text": "3 -> 2 -> 1 -> 4"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3 -> 4", "source_chunk_ids": ["Alamofire__Alamofire__release__5_2_0", "Alamofire__Alamofire__release__5_7_0", "Alamofire__Alamofire__release__5_9_0", "Alamofire__Alamofire__release__5_10_0"], "answer_support": [{"memory_node_id": "Alamofire__Alamofire__release__5_2_0", "answer_text": "adds Combine support with DataResponsePublisher, DownloadResponsePublisher, and DataStreamPublisher"}, {"memory_node_id": "Alamofire__Alamofire__release__5_7_0", "answer_text": "adds request body compression support"}, {"memory_node_id": "Alamofire__Alamofire__release__5_9_0", "answer_text": "adds experimental WebSocketRequest"}, {"memory_node_id": "Alamofire__Alamofire__release__5_10_0", "answer_text": "adds full Swift concurrency support with Sendable requirements"}]}
{"prototype_id": "alibaba__arthas_release_window", "repo": "alibaba/arthas", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the alibaba/arthas releases, which release adds the jfr command and upgrades asm to 9.3 to support Java 19?", "options": [{"option_id": "A", "text": "arthas-all-3.6.5"}, {"option_id": "B", "text": "arthas-all-3.6.7"}, {"option_id": "C", "text": "arthas-all-3.6.8"}, {"option_id": "D", "text": "arthas-all-4.0.0"}], "correct_option_id": "A", "expected_answer": "arthas-all-3.6.5", "source_chunk_ids": ["alibaba__arthas__release__arthas_all_3_6_5"], "answer_support": [{"memory_node_id": "alibaba__arthas__release__arthas_all_3_6_5", "answer_text": "a jfr command is added, asm is upgraded to 9.3 supporting Java 19"}]}
{"prototype_id": "alibaba__arthas_release_window", "repo": "alibaba/arthas", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the alibaba/arthas releases, how does the profiler-related change in arthas-all-4.0.2 differ from the profiler-related change in arthas-all-4.2.0?", "options": [{"option_id": "A", "text": "4.0.2 upgrades async profiler to 3.0 and adds --wall option, while 4.2.0 upgrades async-profiler to 4.4, removes check action, and updates --cstack options."}, {"option_id": "B", "text": "4.0.2 removes profiler command, while 4.2.0 adds profiler command."}, {"option_id": "C", "text": "Both releases only fix profiler documentation without functional changes."}, {"option_id": "D", "text": "4.0.2 downgrades async profiler to 2.9, while 4.2.0 upgrades to 3.0."}], "correct_option_id": "A", "expected_answer": "4.0.2 upgrades async profiler to 3.0 and adds --wall option, while 4.2.0 upgrades async-profiler to 4.4, removes check action, and updates --cstack options.", "source_chunk_ids": ["alibaba__arthas__release__arthas_all_4_0_2", "alibaba__arthas__release__arthas_all_4_2_0"], "answer_support": [{"memory_node_id": "alibaba__arthas__release__arthas_all_4_0_2", "answer_text": "async profiler is upgraded to 3.0, profiler command adds new options such as --wall"}, {"memory_node_id": "alibaba__arthas__release__arthas_all_4_2_0", "answer_text": "profiler upgrades built-in async-profiler to 4.4, removes deprecated check action, updates --cstack options to fp|dwarf|vm|vmx|no"}]}
{"prototype_id": "AlistGo__alist_release_window", "repo": "AlistGo/alist", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the AlistGo/alist releases, which release adds FTP server and SFTP server support?", "options": [{"option_id": "A", "text": "v3.39.1"}, {"option_id": "B", "text": "v3.40.0"}, {"option_id": "C", "text": "v3.41.0"}, {"option_id": "D", "text": "v3.42.0"}], "correct_option_id": "C", "expected_answer": "v3.41.0", "source_chunk_ids": ["AlistGo__alist__release__v3_41_0"], "answer_support": [{"memory_node_id": "AlistGo__alist__release__v3_41_0", "answer_text": "FTP server and SFTP server support are added."}]}
{"prototype_id": "AlistGo__alist_release_window", "repo": "AlistGo/alist", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the AlistGo/alist releases, how does the offline download feature change from v3.38.0 to v3.42.0?", "options": [{"option_id": "A", "text": "v3.38.0 adds transmission support to offline_download, while v3.42.0 allows using offline download tools in any storage."}, {"option_id": "B", "text": "v3.38.0 removes offline download, and v3.42.0 reintroduces it with FTP support."}, {"option_id": "C", "text": "Both releases only fix bugs in offline download without adding features."}, {"option_id": "D", "text": "v3.38.0 adds offline download for the first time, and v3.42.0 removes it."}], "correct_option_id": "A", "expected_answer": "v3.38.0 adds transmission support to offline_download, while v3.42.0 allows using offline download tools in any storage.", "source_chunk_ids": ["AlistGo__alist__release__v3_38_0", "AlistGo__alist__release__v3_42_0"], "answer_support": [{"memory_node_id": "AlistGo__alist__release__v3_38_0", "answer_text": "the offline_download feature adds transmission support"}, {"memory_node_id": "AlistGo__alist__release__v3_42_0", "answer_text": "offline-download allows using offline download tools in any storage"}]}
{"prototype_id": "AlistGo__alist_release_window", "repo": "AlistGo/alist", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the AlistGo/alist release window, order the following release-content states from earliest to latest: (1) a release that adds a febbox driver, (2) a release that adds a Doubao driver, (3) a release that adds a pCloud driver, (4) a release that adds a Gitee driver.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "C", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["AlistGo__alist__release__v3_39_1", "AlistGo__alist__release__v3_44_0", "AlistGo__alist__release__v3_54_0", "AlistGo__alist__release__v3_55_0"], "answer_support": [{"memory_node_id": "AlistGo__alist__release__v3_39_1", "answer_text": "a new febbox driver is added"}, {"memory_node_id": "AlistGo__alist__release__v3_44_0", "answer_text": "A Doubao driver is added"}, {"memory_node_id": "AlistGo__alist__release__v3_54_0", "answer_text": "pCloud driver support is added"}, {"memory_node_id": "AlistGo__alist__release__v3_55_0", "answer_text": "A Gitee driver is added"}]}
{"prototype_id": "angular__angular_release_window", "repo": "angular/angular", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the angular/angular releases, which release introduces the @Service decorator and updates Testability to use PendingTasks for stability indicator?", "options": [{"option_id": "A", "text": "22.0.0-next.9"}, {"option_id": "B", "text": "22.0.0-next.10"}, {"option_id": "C", "text": "22.0.0-rc.0"}, {"option_id": "D", "text": "21.2.12"}], "correct_option_id": "A", "expected_answer": "22.0.0-next.9", "source_chunk_ids": ["angular__angular__release__v22_0_0_next_9"], "answer_support": [{"memory_node_id": "angular__angular__release__v22_0_0_next_9", "answer_text": "introduces the @Service decorator and updates Testability to use PendingTasks for stability indicator"}]}
{"prototype_id": "angular__angular_release_window", "repo": "angular/angular", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the angular/angular releases, how does the handling of event attribute bindings in host bindings differ between release 20.3.20 and release 22.0.0-next.12?", "options": [{"option_id": "A", "text": "20.3.20 disallows event attribute bindings in host bindings unconditionally, while 22.0.0-next.12 allows them with a warning."}, {"option_id": "B", "text": "20.3.20 disallows event attribute bindings in host bindings unconditionally, while 22.0.0-next.12 also disallows them unconditionally."}, {"option_id": "C", "text": "20.3.20 allows event attribute bindings in host bindings, while 22.0.0-next.12 disallows them unconditionally."}, {"option_id": "D", "text": "20.3.20 does not mention event attribute bindings, while 22.0.0-next.12 disallows them unconditionally."}], "correct_option_id": "B", "expected_answer": "20.3.20 disallows event attribute bindings in host bindings unconditionally, while 22.0.0-next.12 also disallows them unconditionally.", "source_chunk_ids": ["angular__angular__release__v20_3_20", "angular__angular__release__v22_0_0_next_12"], "answer_support": [{"memory_node_id": "angular__angular__release__v20_3_20", "answer_text": "disallows event attribute bindings in host bindings unconditionally"}, {"memory_node_id": "angular__angular__release__v22_0_0_next_12", "answer_text": "disallows event attribute bindings in host bindings unconditionally"}]}
{"prototype_id": "anomalyco__opencode_release_window", "repo": "anomalyco/opencode", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the anomalyco/opencode releases, which release introduces the Scout agent for repo research, docs lookup, and dependency-source inspection?", "options": [{"option_id": "A", "text": "v1.14.42"}, {"option_id": "B", "text": "v1.14.49"}, {"option_id": "C", "text": "v1.15.0"}, {"option_id": "D", "text": "v1.15.6"}], "correct_option_id": "A", "expected_answer": "v1.14.42", "source_chunk_ids": ["anomalyco__opencode__release__v1_14_42"], "answer_support": [{"memory_node_id": "anomalyco__opencode__release__v1_14_42", "answer_text": "add the Scout agent for repo research, docs lookup, and dependency-source inspection"}]}
{"prototype_id": "anomalyco__opencode_release_window", "repo": "anomalyco/opencode", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the anomalyco/opencode releases, how does the image attachment handling differ between v1.14.47 and v1.14.48?", "options": [{"option_id": "A", "text": "v1.14.47 auto-resizes large image attachments before sending, while v1.14.48 preserves original image attachments instead of resizing them."}, {"option_id": "B", "text": "v1.14.47 preserves original image attachments, while v1.14.48 auto-resizes them."}, {"option_id": "C", "text": "Both releases remove image attachment support entirely."}, {"option_id": "D", "text": "v1.14.47 adds PDF attachment support, while v1.14.48 adds image resizing."}], "correct_option_id": "A", "expected_answer": "v1.14.47 auto-resizes large image attachments before sending, while v1.14.48 preserves original image attachments instead of resizing them.", "source_chunk_ids": ["anomalyco__opencode__release__v1_14_47", "anomalyco__opencode__release__v1_14_48"], "answer_support": [{"memory_node_id": "anomalyco__opencode__release__v1_14_47", "answer_text": "Large image attachments are now auto-resized before sending, with configurable size limits"}, {"memory_node_id": "anomalyco__opencode__release__v1_14_48", "answer_text": "Preserve original image attachments instead of resizing them before sending them to the model"}]}
{"prototype_id": "ant_design__ant_design_release_window", "repo": "ant-design/ant-design", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the ant-design/ant-design releases, which release introduces the BorderBeam component for animated border beam effect?", "options": [{"option_id": "A", "text": "6.3.0"}, {"option_id": "B", "text": "6.4.0"}, {"option_id": "C", "text": "6.2.0"}, {"option_id": "D", "text": "6.1.0"}], "correct_option_id": "B", "expected_answer": "6.4.0", "source_chunk_ids": ["ant_design__ant_design__release__6_4_0"], "answer_support": [{"memory_node_id": "ant_design__ant_design__release__6_4_0", "answer_text": "BorderBeam component added for animated border beam effect"}]}
{"prototype_id": "ant_design__ant_design_release_window", "repo": "ant-design/ant-design", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the ant-design/ant-design releases, how does the Splitter component change from release 5.28.0 to release 6.4.0?", "options": [{"option_id": "A", "text": "5.28.0 adds onCollapse prop, while 6.4.0 adds destroyOnHidden prop and smooth transition animation for collapsible panels."}, {"option_id": "B", "text": "5.28.0 removes Splitter, while 6.4.0 reintroduces it with new features."}, {"option_id": "C", "text": "5.28.0 adds resizable prop, while 6.4.0 deprecates it."}, {"option_id": "D", "text": "Both releases only fix Splitter bugs without adding new features."}], "correct_option_id": "A", "expected_answer": "5.28.0 adds onCollapse prop, while 6.4.0 adds destroyOnHidden prop and smooth transition animation for collapsible panels.", "source_chunk_ids": ["ant_design__ant_design__release__5_28_0", "ant_design__ant_design__release__6_4_0"], "answer_support": [{"memory_node_id": "ant_design__ant_design__release__5_28_0", "answer_text": "Splitter supports onCollapse prop"}, {"memory_node_id": "ant_design__ant_design__release__6_4_0", "answer_text": "Splitter adds destroyOnHidden prop, smooth transition animation for collapsible panels"}]}
{"prototype_id": "apache__dubbo_release_window", "repo": "apache/dubbo", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the apache/dubbo releases, which release introduces the Triple X protocol with gRPC compatibility and support for HTTP/1, HTTP/2, and HTTP/3?", "options": [{"option_id": "A", "text": "dubbo-3.3.0-beta.1"}, {"option_id": "B", "text": "dubbo-3.3.0"}, {"option_id": "C", "text": "dubbo-3.3.1"}, {"option_id": "D", "text": "dubbo-3.3.2"}], "correct_option_id": "B", "expected_answer": "dubbo-3.3.0", "source_chunk_ids": ["apache__dubbo__release__dubbo_3_3_0"], "answer_support": [{"memory_node_id": "apache__dubbo__release__dubbo_3_3_0", "answer_text": "Triple X protocol which provides comprehensive traffic support, gRPC compatibility, and built on HTTP/1, HTTP/2, and HTTP/3"}]}
{"prototype_id": "apache__dubbo_release_window", "repo": "apache/dubbo", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the apache/dubbo releases, how does the feature set of dubbo-3.3.0-beta.1 differ from that of dubbo-3.3.0?", "options": [{"option_id": "A", "text": "dubbo-3.3.0-beta.1 introduces the new Triple protocol and GraalVM Native Image support, while dubbo-3.3.0 announces the Triple X protocol with HTTP/3 support and Project Loom integration."}, {"option_id": "B", "text": "dubbo-3.3.0-beta.1 focuses on bug fixes for the 3.2.x line, while dubbo-3.3.0 is a minor patch release."}, {"option_id": "C", "text": "Both releases are identical in features, only differing in version number."}, {"option_id": "D", "text": "dubbo-3.3.0-beta.1 removes the Triple protocol, while dubbo-3.3.0 reintroduces it."}], "correct_option_id": "A", "expected_answer": "dubbo-3.3.0-beta.1 introduces the new Triple protocol and GraalVM Native Image support, while dubbo-3.3.0 announces the Triple X protocol with HTTP/3 support and Project Loom integration.", "source_chunk_ids": ["apache__dubbo__release__dubbo_3_3_0_beta_1", "apache__dubbo__release__dubbo_3_3_0"], "answer_support": [{"memory_node_id": "apache__dubbo__release__dubbo_3_3_0_beta_1", "answer_text": "New features include a new Triple protocol fully compatible with gRPC while supporting direct access from cURL and browser, GraalVM Native Image support with Dubbo AOT"}, {"memory_node_id": "apache__dubbo__release__dubbo_3_3_0", "answer_text": "Triple X protocol which provides comprehensive traffic support, gRPC compatibility, and built on HTTP/1, HTTP/2, and HTTP/3; Project Loom integration for optimized concurrency"}]}
{"prototype_id": "appsmithorg__appsmith_release_window", "repo": "appsmithorg/appsmith", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the appsmithorg/appsmith releases, which release introduces a multi-organization login page?", "options": [{"option_id": "A", "text": "v1.73"}, {"option_id": "B", "text": "v1.74"}, {"option_id": "C", "text": "v1.75"}, {"option_id": "D", "text": "v1.76"}], "correct_option_id": "B", "expected_answer": "v1.74", "source_chunk_ids": ["appsmithorg__appsmith__release__v1_74"], "answer_support": [{"memory_node_id": "appsmithorg__appsmith__release__v1_74", "answer_text": "Introduced multi-organization login page"}]}
{"prototype_id": "appsmithorg__appsmith_release_window", "repo": "appsmithorg/appsmith", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the appsmithorg/appsmith releases, how does the handling of user sessions differ between v1.73 and v1.74?", "options": [{"option_id": "A", "text": "v1.73 logs out users with expired sessions between page navigations, while v1.74 logs out users with expired sessions between page switches."}, {"option_id": "B", "text": "v1.73 introduces multi-organization login, while v1.74 removes session expiration entirely."}, {"option_id": "C", "text": "Both releases handle session expiration identically by redirecting to the signup page."}, {"option_id": "D", "text": "v1.73 adds a non-null check for published actions, while v1.74 adds type checking for Mixpanel session recording."}], "correct_option_id": "A", "expected_answer": "v1.73 logs out users with expired sessions between page navigations, while v1.74 logs out users with expired sessions between page switches.", "source_chunk_ids": ["appsmithorg__appsmith__release__v1_73", "appsmithorg__appsmith__release__v1_74"], "answer_support": [{"memory_node_id": "appsmithorg__appsmith__release__v1_73", "answer_text": "Logged out users automatically if their session has expired between page navigations."}, {"memory_node_id": "appsmithorg__appsmith__release__v1_74", "answer_text": "Logged out users if their session has expired between page switches"}]}
{"prototype_id": "appsmithorg__appsmith_release_window", "repo": "appsmithorg/appsmith", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the appsmithorg/appsmith release window, order the following release-content states from earliest to latest: (1) a release that adds a premium feature tag for paid external SaaS plugins in the Data Side Pane, (2) a release that introduces a multi-organization login page, (3) a release that adds an upgrade button to the editor header for easier plan upgrades, (4) a release that adds a Redeploy button to sync the latest changes to App view mode.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "B", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "C", "text": "2 -> 3 -> 1 -> 4"}, {"option_id": "D", "text": "3 -> 2 -> 1 -> 4"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3 -> 4", "source_chunk_ids": ["appsmithorg__appsmith__release__v1_74", "appsmithorg__appsmith__release__v1_82", "appsmithorg__appsmith__release__v1_83", "appsmithorg__appsmith__release__v1_94"], "answer_support": [{"memory_node_id": "appsmithorg__appsmith__release__v1_74", "answer_text": "Introduced multi-organization login page"}, {"memory_node_id": "appsmithorg__appsmith__release__v1_82", "answer_text": "Add premium feature tag for paid external SaaS plugins in the Data Side Pane"}, {"memory_node_id": "appsmithorg__appsmith__release__v1_83", "answer_text": "Added an upgrade button to the editor header for easier access to plan upgrades"}, {"memory_node_id": "appsmithorg__appsmith__release__v1_94", "answer_text": "Added a Redeploy button to allow users to sync the latest changes to App view mode"}]}
{"prototype_id": "aquasecurity__trivy_release_window", "repo": "aquasecurity/trivy", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the aquasecurity/trivy releases, which release introduces a dedicated SBOM command and adds vulnerabilities to CycloneDX?", "options": [{"option_id": "A", "text": "v0.24.0"}, {"option_id": "B", "text": "v0.25.0"}, {"option_id": "C", "text": "v0.23.0"}, {"option_id": "D", "text": "v0.26.0"}], "correct_option_id": "B", "expected_answer": "v0.25.0", "source_chunk_ids": ["aquasecurity__trivy__release__v0_25_0"], "answer_support": [{"memory_node_id": "aquasecurity__trivy__release__v0_25_0", "answer_text": "adding a dedicated SBOM command, adding vulnerabilities to CycloneDX"}]}
{"prototype_id": "aquasecurity__trivy_release_window", "repo": "aquasecurity/trivy", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the aquasecurity/trivy releases, how does the SARIF-related change in v0.21.0 differ from the SARIF-related change in v0.23.0?", "options": [{"option_id": "A", "text": "v0.21.0 fixes SARIF validation errors and uses a stable SARIF identifier, while v0.23.0 migrates the SARIF template to Go code as a breaking change."}, {"option_id": "B", "text": "v0.21.0 removes SARIF support entirely, while v0.23.0 adds it back."}, {"option_id": "C", "text": "Both releases only update the SARIF help field without other changes."}, {"option_id": "D", "text": "v0.21.0 migrates the SARIF template to Go code, while v0.23.0 fixes validation errors."}], "correct_option_id": "A", "expected_answer": "v0.21.0 fixes SARIF validation errors and uses a stable SARIF identifier, while v0.23.0 migrates the SARIF template to Go code as a breaking change.", "source_chunk_ids": ["aquasecurity__trivy__release__v0_21_0", "aquasecurity__trivy__release__v0_23_0"], "answer_support": [{"memory_node_id": "aquasecurity__trivy__release__v0_21_0", "answer_text": "fix for SARIF validation errors, using a stable SARIF identifier"}, {"memory_node_id": "aquasecurity__trivy__release__v0_23_0", "answer_text": "BREAKING: migrate the sarif template to Go code"}]}
{"prototype_id": "aquasecurity__trivy_release_window", "repo": "aquasecurity/trivy", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the aquasecurity/trivy release window, order the following release-content states from earliest to latest: (1) a release that adds support for config scanning and SBOM generation, (2) a release that adds a dedicated SBOM command and enables filesystem scanning in client/server mode, (3) a release that adds support for CycloneDX reports and s390x container images.", "options": [{"option_id": "A", "text": "1 -> 3 -> 2"}, {"option_id": "B", "text": "3 -> 1 -> 2"}, {"option_id": "C", "text": "1 -> 2 -> 3"}, {"option_id": "D", "text": "2 -> 1 -> 3"}], "correct_option_id": "A", "expected_answer": "1 -> 3 -> 2", "source_chunk_ids": ["aquasecurity__trivy__release__v0_19_0", "aquasecurity__trivy__release__v0_24_0", "aquasecurity__trivy__release__v0_25_0"], "answer_support": [{"memory_node_id": "aquasecurity__trivy__release__v0_19_0", "answer_text": "support config scanning, Generate SBOM"}, {"memory_node_id": "aquasecurity__trivy__release__v0_24_0", "answer_text": "add support for CycloneDX, add s390x container images"}, {"memory_node_id": "aquasecurity__trivy__release__v0_25_0", "answer_text": "add a dedicated sbom command, filesystem scanning in client/server mode"}]}
{"prototype_id": "argoproj__argo_cd_release_window", "repo": "argoproj/argo-cd", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the argoproj/argo-cd releases, how does the handling of automatic refreshes differ between v3.2.9 and v3.2.10?", "options": [{"option_id": "A", "text": "v3.2.9 prevents automatic refreshes from informer resync and status updates, while v3.2.10 reverts that prevention."}, {"option_id": "B", "text": "v3.2.9 introduces automatic refreshes, while v3.2.10 removes them entirely."}, {"option_id": "C", "text": "Both releases have identical handling of automatic refreshes."}, {"option_id": "D", "text": "v3.2.9 reverts automatic refreshes, while v3.2.10 prevents them."}], "correct_option_id": "A", "expected_answer": "v3.2.9 prevents automatic refreshes from informer resync and status updates, while v3.2.10 reverts that prevention.", "source_chunk_ids": ["argoproj__argo_cd__release__v3_2_9", "argoproj__argo_cd__release__v3_2_10"], "answer_support": [{"memory_node_id": "argoproj__argo_cd__release__v3_2_9", "answer_text": "preventing automatic refreshes from informer resync and status updates"}, {"memory_node_id": "argoproj__argo_cd__release__v3_2_10", "answer_text": "Revert \"fix: prevent automatic refreshes from informer resync and status updates"}]}
{"prototype_id": "aristocratos__btop_release_window", "repo": "aristocratos/btop", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the aristocratos/btop releases, which release adds support for OSX?", "options": [{"option_id": "A", "text": "v1.1.0"}, {"option_id": "B", "text": "v1.2.0"}, {"option_id": "C", "text": "v1.3.0"}, {"option_id": "D", "text": "v1.4.0"}], "correct_option_id": "A", "expected_answer": "v1.1.0", "source_chunk_ids": ["aristocratos__btop__release__v1_1_0"], "answer_support": [{"memory_node_id": "aristocratos__btop__release__v1_1_0", "answer_text": "adds support for OSX"}]}
{"prototype_id": "aristocratos__btop_release_window", "repo": "aristocratos/btop", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the aristocratos/btop releases, how does the GPU-related change in v1.3.0 differ from the GPU-related change in v1.4.0?", "options": [{"option_id": "A", "text": "v1.3.0 adds GPU support for Linux, while v1.4.0 adds Intel GPU support."}, {"option_id": "B", "text": "v1.3.0 adds Intel GPU support, while v1.4.0 adds GPU support for Linux."}, {"option_id": "C", "text": "Both releases add the same GPU support for AMD GPUs."}, {"option_id": "D", "text": "v1.3.0 removes GPU support, while v1.4.0 restores it."}], "correct_option_id": "A", "expected_answer": "v1.3.0 adds GPU support for Linux, while v1.4.0 adds Intel GPU support.", "source_chunk_ids": ["aristocratos__btop__release__v1_3_0", "aristocratos__btop__release__v1_4_0"], "answer_support": [{"memory_node_id": "aristocratos__btop__release__v1_3_0", "answer_text": "adds GPU support for Linux"}, {"memory_node_id": "aristocratos__btop__release__v1_4_0", "answer_text": "adds Intel GPU support"}]}
{"prototype_id": "aristocratos__btop_release_window", "repo": "aristocratos/btop", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the aristocratos/btop release window, order the following release-content states from earliest to latest: (1) a release that adds support for FreeBSD, (2) a release that adds GPU support for Linux, (3) a release that adds Intel GPU support, (4) a release that adds Apple Silicon GPU support via IOReport API.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["aristocratos__btop__release__v1_2_0", "aristocratos__btop__release__v1_3_0", "aristocratos__btop__release__v1_4_0", "aristocratos__btop__release__v1_4_7"], "answer_support": [{"memory_node_id": "aristocratos__btop__release__v1_2_0", "answer_text": "adds support for FreeBSD"}, {"memory_node_id": "aristocratos__btop__release__v1_3_0", "answer_text": "adds GPU support for Linux"}, {"memory_node_id": "aristocratos__btop__release__v1_4_0", "answer_text": "adds Intel GPU support"}, {"memory_node_id": "aristocratos__btop__release__v1_4_7", "answer_text": "adds Apple Silicon GPU support via IOReport API"}]}
{"prototype_id": "aseprite__aseprite_release_window", "repo": "aseprite/aseprite", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the aseprite/aseprite releases, which release introduces a new Text tool with the T key and diagonal symmetry?", "options": [{"option_id": "A", "text": "v1.3.10"}, {"option_id": "B", "text": "v1.3.11-beta1"}, {"option_id": "C", "text": "v1.3.11"}, {"option_id": "D", "text": "v1.3.12-beta1"}], "correct_option_id": "B", "expected_answer": "v1.3.11-beta1", "source_chunk_ids": ["aseprite__aseprite__release__v1_3_11_beta1"], "answer_support": [{"memory_node_id": "aseprite__aseprite__release__v1_3_11_beta1", "answer_text": "introduces a new Text tool with T key, new diagonal symmetry"}]}
{"prototype_id": "aseprite__aseprite_release_window", "repo": "aseprite/aseprite", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the aseprite/aseprite releases, how does the feature addition in v1.3.11-beta1 differ from the feature addition in v1.3.16-beta1 regarding UI customization?", "options": [{"option_id": "A", "text": "v1.3.11-beta1 adds a 'Transform' checkbox to move slices with its content, while v1.3.16-beta1 makes all elements on screen dockable/movable/resizable."}, {"option_id": "B", "text": "v1.3.11-beta1 adds dockable UI, while v1.3.16-beta1 adds a Text tool."}, {"option_id": "C", "text": "Both releases add the same UI customization features."}, {"option_id": "D", "text": "v1.3.11-beta1 adds a 'Run Command' window, while v1.3.16-beta1 adds diagonal symmetry."}], "correct_option_id": "A", "expected_answer": "v1.3.11-beta1 adds a 'Transform' checkbox to move slices with its content, while v1.3.16-beta1 makes all elements on screen dockable/movable/resizable.", "source_chunk_ids": ["aseprite__aseprite__release__v1_3_11_beta1", "aseprite__aseprite__release__v1_3_16_beta2"], "answer_support": [{"memory_node_id": "aseprite__aseprite__release__v1_3_11_beta1", "answer_text": "adds 'Transform' checkbox to move slices with its content"}, {"memory_node_id": "aseprite__aseprite__release__v1_3_16_beta2", "answer_text": "adds UI customization by making all elements on screen dockable/movable/resizable"}]}
{"prototype_id": "aseprite__aseprite_release_window", "repo": "aseprite/aseprite", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the aseprite/aseprite release window, order the following release-content states from earliest to latest: (1) a release that adds a new Text tool with T key and diagonal symmetry, (2) a release that adds a 'Run Command' window and dockable UI, (3) a release that adds a Search field to Edit > Preferences and a 'Widget Zoo' command.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["aseprite__aseprite__release__v1_3_11_beta1", "aseprite__aseprite__release__v1_3_16_beta2", "aseprite__aseprite__release__v1_3_18_beta1"], "answer_support": [{"memory_node_id": "aseprite__aseprite__release__v1_3_11_beta1", "answer_text": "introduces a new Text tool with T key, new diagonal symmetry"}, {"memory_node_id": "aseprite__aseprite__release__v1_3_16_beta2", "answer_text": "adds 'Run Command' window ... adds UI customization by making all elements on screen dockable/movable/resizable"}, {"memory_node_id": "aseprite__aseprite__release__v1_3_18_beta1", "answer_text": "adds a Search field to Edit > Preferences ... adds a new 'Widget Zoo' command"}]}
{"prototype_id": "astral_sh__ruff_release_window", "repo": "astral-sh/ruff", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the astral-sh/ruff releases, which release introduces the rule RUF066 to detect unnecessary class properties?", "options": [{"option_id": "A", "text": "0.14.7"}, {"option_id": "B", "text": "0.14.8"}, {"option_id": "C", "text": "0.14.9"}, {"option_id": "D", "text": "0.14.10"}], "correct_option_id": "A", "expected_answer": "0.14.7", "source_chunk_ids": ["astral_sh__ruff__release__0_14_7"], "answer_support": [{"memory_node_id": "astral_sh__ruff__release__0_14_7", "answer_text": "RUF066 detects unnecessary class properties"}]}
{"prototype_id": "astral_sh__ruff_release_window", "repo": "astral-sh/ruff", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the astral-sh/ruff release window, order the following release-content states from earliest to latest: (1) a release that adds fluent formatting of method chains, (2) a release that introduces block suppression comments, (3) a release that implements #ruff:file-ignore file-level suppressions, (4) a release that adds support for lazy import parsing.", "options": [{"option_id": "A", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "C", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "D", "text": "2 -> 1 -> 4 -> 3"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 4 -> 3", "source_chunk_ids": ["astral_sh__ruff__release__0_14_10", "astral_sh__ruff__release__0_15_0", "astral_sh__ruff__release__0_15_6", "astral_sh__ruff__release__0_15_12"], "answer_support": [{"memory_node_id": "astral_sh__ruff__release__0_14_10", "answer_text": "fluent formatting of method chains"}, {"memory_node_id": "astral_sh__ruff__release__0_15_0", "answer_text": "block suppression comments"}, {"memory_node_id": "astral_sh__ruff__release__0_15_6", "answer_text": "support for lazy import parsing"}, {"memory_node_id": "astral_sh__ruff__release__0_15_12", "answer_text": "#ruff:file-ignore file-level suppressions"}]}
{"prototype_id": "astral_sh__uv_release_window", "repo": "astral-sh/uv", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the astral-sh/uv releases, which release adds support for ROCm 7.2 and implements support for PEP 803?", "options": [{"option_id": "A", "text": "0.11.3"}, {"option_id": "B", "text": "0.11.4"}, {"option_id": "C", "text": "0.11.5"}, {"option_id": "D", "text": "0.11.6"}], "correct_option_id": "A", "expected_answer": "0.11.3", "source_chunk_ids": ["astral_sh__uv__release__0_11_3"], "answer_support": [{"memory_node_id": "astral_sh__uv__release__0_11_3", "answer_text": "adds support for ROCm 7.2 ... implements support for PEP 803"}]}
{"prototype_id": "astral_sh__uv_release_window", "repo": "astral-sh/uv", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the astral-sh/uv releases, how does the TLS certificate handling change described in release 0.11.0 differ from the TLS-related improvements in release 0.11.7?", "options": [{"option_id": "A", "text": "0.11.0 switches to rustls-platform-verifier and deprecates --native-tls, while 0.11.7 further improves TLS certificate validation messages and filters invalid certificates."}, {"option_id": "B", "text": "0.11.0 removes all TLS support, while 0.11.7 adds it back."}, {"option_id": "C", "text": "Both releases only update the cryptography backend without changing certificate verification."}, {"option_id": "D", "text": "0.11.0 introduces TLS certificate validation, and 0.11.7 removes it."}], "correct_option_id": "A", "expected_answer": "0.11.0 switches to rustls-platform-verifier and deprecates --native-tls, while 0.11.7 further improves TLS certificate validation messages and filters invalid certificates.", "source_chunk_ids": ["astral_sh__uv__release__0_11_0", "astral_sh__uv__release__0_11_7"], "answer_support": [{"memory_node_id": "astral_sh__uv__release__0_11_0", "answer_text": "rustls-platform-verifier is used instead of rustls-native-certs and webpki for certificate verification ... --native-tls is deprecated in favor of --system-certs"}, {"memory_node_id": "astral_sh__uv__release__0_11_7", "answer_text": "further improves TLS certificate validation messages ... filters and warns on invalid TLS certificates"}]}
{"prototype_id": "astral_sh__uv_release_window", "repo": "astral-sh/uv", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the astral-sh/uv release window, order the following release-content states from earliest to latest: (1) a release that adds CPython 3.15.0a6 and avoids opening file locks for writing, (2) a release that adds CPython 3.15.0a7 and adds --outdated flag to uv tool list, (3) a release that adds CPython 3.15.0b1 and adds --no-editable support to uv pip install, (4) a release that adds CPython 3.14.5 and includes data files in editable builds.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["astral_sh__uv__release__0_10_3", "astral_sh__uv__release__0_10_10", "astral_sh__uv__release__0_11_12", "astral_sh__uv__release__0_11_13"], "answer_support": [{"memory_node_id": "astral_sh__uv__release__0_10_3", "answer_text": "adds CPython 3.15.0a6 ... Don't open file locks for writing"}, {"memory_node_id": "astral_sh__uv__release__0_10_10", "answer_text": "Add CPython 3.15.0a7 ... Add --outdated flag to uv tool list"}, {"memory_node_id": "astral_sh__uv__release__0_11_12", "answer_text": "Add CPython 3.15.0b1 ... Add --no-editable support to uv pip install"}, {"memory_node_id": "astral_sh__uv__release__0_11_13", "answer_text": "Add CPython 3.14.5 ... Include data files in editable builds"}]}
{"prototype_id": "authelia__authelia_release_window", "repo": "authelia/authelia", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the authelia/authelia releases, which release introduces LDAP connection pooling and reusable configuration definitions?", "options": [{"option_id": "A", "text": "v4.38.18"}, {"option_id": "B", "text": "v4.39.0"}, {"option_id": "C", "text": "v4.39.1"}, {"option_id": "D", "text": "v4.39.2"}], "correct_option_id": "B", "expected_answer": "v4.39.0", "source_chunk_ids": ["authelia__authelia__release__v4_39_0"], "answer_support": [{"memory_node_id": "authelia__authelia__release__v4_39_0", "answer_text": "new features such as ... LDAP connection pooling ... reusable configuration definitions"}]}
{"prototype_id": "authelia__authelia_release_window", "repo": "authelia/authelia", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the authelia/authelia releases, how does the OIDC-related change in v4.39.2 differ from the OIDC-related change in v4.39.6?", "options": [{"option_id": "A", "text": "v4.39.2 inadvertently removes legacy OIDC endpoints, while v4.39.6 disallows 'none' as an authorization_signed_response_alg value."}, {"option_id": "B", "text": "v4.39.2 adds device authorization flow, while v4.39.6 removes it."}, {"option_id": "C", "text": "Both releases only fix consent form restoration."}, {"option_id": "D", "text": "v4.39.2 introduces configurable rate limits, while v4.39.6 fixes missing grant handlers."}], "correct_option_id": "A", "expected_answer": "v4.39.2 inadvertently removes legacy OIDC endpoints, while v4.39.6 disallows 'none' as an authorization_signed_response_alg value.", "source_chunk_ids": ["authelia__authelia__release__v4_39_2", "authelia__authelia__release__v4_39_6"], "answer_support": [{"memory_node_id": "authelia__authelia__release__v4_39_2", "answer_text": "inadvertent removal of legacy OpenID Connect 1.0 endpoints"}, {"memory_node_id": "authelia__authelia__release__v4_39_6", "answer_text": "disallowing 'none' as an authorization_signed_response_alg value in OIDC client registrations"}]}
{"prototype_id": "authelia__authelia_release_window", "repo": "authelia/authelia", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the authelia/authelia release window, order the following release-content states from earliest to latest: (1) a release that fixes a missing query in the ACL check command, (2) a release that introduces LDAP connection pooling and reusable configuration definitions, (3) a release that fixes an incorrect response code check for successful Duo API calls, (4) a release that contains important security fixes for edge case access control rule domain miss and missing username canonicalization in basic auth with LDAP.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 2 -> 1 -> 3"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["authelia__authelia__release__v4_38_14", "authelia__authelia__release__v4_39_0", "authelia__authelia__release__v4_39_18", "authelia__authelia__release__v4_39_20"], "answer_support": [{"memory_node_id": "authelia__authelia__release__v4_38_14", "answer_text": "bug fix for a missing query in the ACL check command"}, {"memory_node_id": "authelia__authelia__release__v4_39_0", "answer_text": "new features such as ... LDAP connection pooling ... reusable configuration definitions"}, {"memory_node_id": "authelia__authelia__release__v4_39_18", "answer_text": "bug fix for removing an incorrect response code check for successful Duo API calls"}, {"memory_node_id": "authelia__authelia__release__v4_39_20", "answer_text": "important security fixes for edge case access control rule domain miss and missing username canonicalization in basic auth with LDAP"}]}
{"prototype_id": "AvaloniaUI__Avalonia_release_window", "repo": "AvaloniaUI/Avalonia", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the AvaloniaUI/Avalonia releases, which release introduces the Container Queries feature?", "options": [{"option_id": "A", "text": "11.3.0-beta2"}, {"option_id": "B", "text": "11.3.0-rc1"}, {"option_id": "C", "text": "11.3.0"}, {"option_id": "D", "text": "11.2.8"}], "correct_option_id": "C", "expected_answer": "11.3.0", "source_chunk_ids": ["AvaloniaUI__Avalonia__release__11_3_0"], "answer_support": [{"memory_node_id": "AvaloniaUI__Avalonia__release__11_3_0", "answer_text": "features include ... Container Queries"}]}
{"prototype_id": "AvaloniaUI__Avalonia_release_window", "repo": "AvaloniaUI/Avalonia", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the AvaloniaUI/Avalonia releases, how does the clipboard-related change in 11.3.7 differ from the clipboard-related change in 11.3.9?", "options": [{"option_id": "A", "text": "11.3.7 reworks the clipboard, while 11.3.9 adds support for reading from and copying images to the clipboard."}, {"option_id": "B", "text": "11.3.7 adds image clipboard support, while 11.3.9 reworks the clipboard."}, {"option_id": "C", "text": "Both releases only fix clipboard bitmap pixel shift."}, {"option_id": "D", "text": "11.3.7 removes clipboard support, while 11.3.9 restores it."}], "correct_option_id": "A", "expected_answer": "11.3.7 reworks the clipboard, while 11.3.9 adds support for reading from and copying images to the clipboard.", "source_chunk_ids": ["AvaloniaUI__Avalonia__release__11_3_7", "AvaloniaUI__Avalonia__release__11_3_9"], "answer_support": [{"memory_node_id": "AvaloniaUI__Avalonia__release__11_3_7", "answer_text": "features include a clipboard rework"}, {"memory_node_id": "AvaloniaUI__Avalonia__release__11_3_9", "answer_text": "enhancements include ... support for reading from and copying images to clipboard"}]}
{"prototype_id": "axios__axios_release_window", "repo": "axios/axios", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the axios/axios releases, which release adds HTTP2 support to the http adapter?", "options": [{"option_id": "A", "text": "v1.12.0"}, {"option_id": "B", "text": "v1.13.0"}, {"option_id": "C", "text": "v1.13.2"}, {"option_id": "D", "text": "v1.14.0"}], "correct_option_id": "B", "expected_answer": "v1.13.0", "source_chunk_ids": ["axios__axios__release__v1_13_0"], "answer_support": [{"memory_node_id": "axios__axios__release__v1_13_0", "answer_text": "HTTP2 support is added to the http adapter."}]}
{"prototype_id": "axios__axios_release_window", "repo": "axios/axios", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the axios/axios releases, how does the security fix in v0.30.3 differ from the security fix in v1.13.5?", "options": [{"option_id": "A", "text": "v0.30.3 backports a DoS fix via __proto__ key in merge config for the v0.x line, while v1.13.5 fixes a potential DoS via __proto__ key in mergeConfig and also resolves a missing status field in AxiosError on and after v1.13.3."}, {"option_id": "B", "text": "v0.30.3 adds HTTP2 support, while v1.13.5 adds React Native Blob support."}, {"option_id": "C", "text": "Both releases only update CI workflows without any security fixes."}, {"option_id": "D", "text": "v0.30.3 fixes a header injection vulnerability, while v1.13.5 fixes a prototype pollution in formDataToJSON."}], "correct_option_id": "A", "expected_answer": "v0.30.3 backports a DoS fix via __proto__ key in merge config for the v0.x line, while v1.13.5 fixes a potential DoS via __proto__ key in mergeConfig and also resolves a missing status field in AxiosError on and after v1.13.3.", "source_chunk_ids": ["axios__axios__release__v0_30_3", "axios__axios__release__v1_13_5"], "answer_support": [{"memory_node_id": "axios__axios__release__v0_30_3", "answer_text": "a critical security vulnerability involving prototype pollution that could lead to a Denial of Service is fixed by backporting the DoS fix via the __proto__ key in merge config"}, {"memory_node_id": "axios__axios__release__v1_13_5", "answer_text": "a potential Denial of Service issue involving the __proto__ key in mergeConfig is fixed, an issue where AxiosError could be missing the status field on and after v1.13.3 is resolved"}]}
{"prototype_id": "axios__axios_release_window", "repo": "axios/axios", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the axios/axios release window, order the following release-content states from earliest to latest: (1) a release that adds a module entry point for React Native, (2) a release that adds React Native Blob support, (3) a release that adds compatibility checks and documentation for Deno and Bun environments, (4) a release that adds support for the QUERY HTTP method.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["axios__axios__release__v1_10_0", "axios__axios__release__v1_13_6", "axios__axios__release__v1_15_0", "axios__axios__release__v1_16_0"], "answer_support": [{"memory_node_id": "axios__axios__release__v1_10_0", "answer_text": "a module entry point for React Native is added to the package"}, {"memory_node_id": "axios__axios__release__v1_13_6", "answer_text": "React Native Blob support is added"}, {"memory_node_id": "axios__axios__release__v1_15_0", "answer_text": "compatibility checks and documentation for Deno and Bun environments are added"}, {"memory_node_id": "axios__axios__release__v1_16_0", "answer_text": "support for the QUERY HTTP method is added"}]}
{"prototype_id": "Blankj__AndroidUtilCode_release_window", "repo": "Blankj/AndroidUtilCode", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the Blankj/AndroidUtilCode releases, which release adds BrightnessUtils and FlashlightUtils?", "options": [{"option_id": "A", "text": "1.23.2"}, {"option_id": "B", "text": "1.23.3"}, {"option_id": "C", "text": "1.23.4"}, {"option_id": "D", "text": "1.23.5"}], "correct_option_id": "A", "expected_answer": "1.23.2", "source_chunk_ids": ["Blankj__AndroidUtilCode__release__1_23_2"], "answer_support": [{"memory_node_id": "Blankj__AndroidUtilCode__release__1_23_2", "answer_text": "adds ... BrightnessUtils and FlashlightUtils"}]}
{"prototype_id": "Blankj__AndroidUtilCode_release_window", "repo": "Blankj/AndroidUtilCode", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the Blankj/AndroidUtilCode releases, how does the change to LogUtils in release 1.23.7 differ from the change to LogUtils in release 1.24.1?", "options": [{"option_id": "A", "text": "1.23.7 adds multi-process support and fixes LogUtils#file, while 1.24.1 fixes LogUtils writing to file."}, {"option_id": "B", "text": "1.23.7 fixes LogUtils writing to file, while 1.24.1 adds multi-process support."}, {"option_id": "C", "text": "Both releases only fix LogUtils format for JSON."}, {"option_id": "D", "text": "1.23.7 removes LogUtils, while 1.24.1 adds LogUtils back."}], "correct_option_id": "A", "expected_answer": "1.23.7 adds multi-process support and fixes LogUtils#file, while 1.24.1 fixes LogUtils writing to file.", "source_chunk_ids": ["Blankj__AndroidUtilCode__release__1_23_7", "Blankj__AndroidUtilCode__release__1_24_1"], "answer_support": [{"memory_node_id": "Blankj__AndroidUtilCode__release__1_23_7", "answer_text": "adds multi-process support to LogUtils and fixes LogUtils#file"}, {"memory_node_id": "Blankj__AndroidUtilCode__release__1_24_1", "answer_text": "fixes LogUtils writing to file"}]}
{"prototype_id": "Blankj__AndroidUtilCode_release_window", "repo": "Blankj/AndroidUtilCode", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the Blankj/AndroidUtilCode release window, order the following release-content states from earliest to latest: (1) a release that adds RomUtils, (2) a release that adds ContainerUtils, (3) a release that adds NumberUtils.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["Blankj__AndroidUtilCode__release__1_23_4", "Blankj__AndroidUtilCode__release__1_25_2", "Blankj__AndroidUtilCode__release__1_28_0"], "answer_support": [{"memory_node_id": "Blankj__AndroidUtilCode__release__1_23_4", "answer_text": "adds RomUtils"}, {"memory_node_id": "Blankj__AndroidUtilCode__release__1_25_2", "answer_text": "adds ContainerUtils"}, {"memory_node_id": "Blankj__AndroidUtilCode__release__1_28_0", "answer_text": "adds NumberUtils"}]}
{"prototype_id": "browser_use__browser_use_release_window", "repo": "browser-use/browser-use", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the browser-use/browser-use releases, which release introduces the Browser Use CLI and skill for Claude Code/Codex agents?", "options": [{"option_id": "A", "text": "0.11.4"}, {"option_id": "B", "text": "0.12.3"}, {"option_id": "C", "text": "0.11.8"}, {"option_id": "D", "text": "0.11.0"}], "correct_option_id": "A", "expected_answer": "0.11.4", "source_chunk_ids": ["browser_use__browser_use__release__0_11_4"], "answer_support": [{"memory_node_id": "browser_use__browser_use__release__0_11_4", "answer_text": "introduces a Browser Use CLI and skill, enabling Claude Code/Codex agents to access local and remote browsers"}]}
{"prototype_id": "browser_use__browser_use_release_window", "repo": "browser-use/browser-use", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the browser-use/browser-use releases, how does the CLI change described in release 0.12.3 differ from the CLI introduced in release 0.11.4?", "options": [{"option_id": "A", "text": "0.11.4 introduces the initial CLI with basic commands, while 0.12.3 introduces CLI 2.0 built on direct CDP for faster automation and adds real Chrome and cloud browser modes."}, {"option_id": "B", "text": "0.11.4 removes the CLI, and 0.12.3 reintroduces it with fewer features."}, {"option_id": "C", "text": "Both releases describe identical CLI functionality without any differences."}, {"option_id": "D", "text": "0.11.4 focuses on cloud browsers only, while 0.12.3 removes cloud support."}], "correct_option_id": "A", "expected_answer": "0.11.4 introduces the initial CLI with basic commands, while 0.12.3 introduces CLI 2.0 built on direct CDP for faster automation and adds real Chrome and cloud browser modes.", "source_chunk_ids": ["browser_use__browser_use__release__0_11_4", "browser_use__browser_use__release__0_12_3"], "answer_support": [{"memory_node_id": "browser_use__browser_use__release__0_11_4", "answer_text": "introduces a Browser Use CLI and skill, enabling Claude Code/Codex agents to access local and remote browsers with commands like open, state, click, type, screenshot, and close, and supports multiple browser modes and sessions."}, {"memory_node_id": "browser_use__browser_use__release__0_12_3", "answer_text": "introduces Browser Use CLI 2.0 built on direct CDP for faster automation, supports multiple browser modes including real Chrome and cloud, and provides form filling and file upload capabilities."}]}
{"prototype_id": "browser_use__browser_use_release_window", "repo": "browser-use/browser-use", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the browser-use/browser-use release window, order the following release-content states from earliest to latest: (1) a release that adds automatic LLM-as-a-judge for monitoring agent run success, (2) a release that introduces skills integration, (3) a release that announces the bu-2-0 premium model with 83.3% accuracy, (4) a release that removes litellm from core dependencies due to a supply chain attack.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["browser_use__browser_use__release__0_9_6", "browser_use__browser_use__release__0_11_0", "browser_use__browser_use__release__0_11_5", "browser_use__browser_use__release__0_12_5"], "answer_support": [{"memory_node_id": "browser_use__browser_use__release__0_9_6", "answer_text": "adds automatic LLM-as-a-judge for monitoring agent run success"}, {"memory_node_id": "browser_use__browser_use__release__0_11_0", "answer_text": "introduces skills integration"}, {"memory_node_id": "browser_use__browser_use__release__0_11_5", "answer_text": "announces the bu-2-0 premium model with 83.3% accuracy"}, {"memory_node_id": "browser_use__browser_use__release__0_12_5", "answer_text": "removes litellm from core dependencies in response to a supply chain attack"}]}
{"prototype_id": "bumptech__glide_release_window", "repo": "bumptech/glide", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the bumptech/glide releases, which release introduces a clearOnDetach() API on ViewTarget and a waitForLayout() API on ViewTarget?", "options": [{"option_id": "A", "text": "v4.4.0"}, {"option_id": "B", "text": "v4.5.0"}, {"option_id": "C", "text": "v4.6.0"}, {"option_id": "D", "text": "v4.7.0"}], "correct_option_id": "A", "expected_answer": "v4.4.0", "source_chunk_ids": ["bumptech__glide__release__v4_4_0"], "answer_support": [{"memory_node_id": "bumptech__glide__release__v4_4_0", "answer_text": "Added an API to ViewTarget called clearOnDetach() ... Added an API to ViewTarget called waitForLayout()"}]}
{"prototype_id": "bumptech__glide_release_window", "repo": "bumptech/glide", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the bumptech/glide releases, how does the AVIF support introduced in v4.13.0 differ from the AVIF support added in v4.15.0?", "options": [{"option_id": "A", "text": "v4.13.0 adds an integration library for AVIF decoding, while v4.15.0 adds support for animated AVIF and RGB_565 in Avif."}, {"option_id": "B", "text": "v4.13.0 adds animated AVIF support, while v4.15.0 adds an integration library for AVIF decoding."}, {"option_id": "C", "text": "Both releases only fix AVIF dependency issues without adding new AVIF features."}, {"option_id": "D", "text": "v4.13.0 adds AVIF support for Compose, while v4.15.0 adds AVIF support for Views."}], "correct_option_id": "A", "expected_answer": "v4.13.0 adds an integration library for AVIF decoding, while v4.15.0 adds support for animated AVIF and RGB_565 in Avif.", "source_chunk_ids": ["bumptech__glide__release__v4_13_0", "bumptech__glide__release__v4_15_0"], "answer_support": [{"memory_node_id": "bumptech__glide__release__v4_13_0", "answer_text": "Add an integration library to support decoding AVIF"}, {"memory_node_id": "bumptech__glide__release__v4_15_0", "answer_text": "adds support for animated AVIF, and adds support for RGB_565 in Avif"}]}
{"prototype_id": "bumptech__glide_release_window", "repo": "bumptech/glide", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the bumptech/glide release window, order the following release-content states from earliest to latest: (1) a release that adds a Cronet integration library, (2) a release that adds an alpha version of a Compose integration, (3) a release that adds a Compose Transition API and CrossFade Transition, (4) a release that adds a Painter variant of the placeholder APIs in the Compose integration.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["bumptech__glide__release__v4_12_0", "bumptech__glide__release__v4_14_0", "bumptech__glide__release__v4_16_0", "bumptech__glide__release__v5_0_0_rc01"], "answer_support": [{"memory_node_id": "bumptech__glide__release__v4_12_0", "answer_text": "Add a Cronet integration library"}, {"memory_node_id": "bumptech__glide__release__v4_14_0", "answer_text": "Add an alpha version of a Compose integration"}, {"memory_node_id": "bumptech__glide__release__v4_16_0", "answer_text": "Add a Transition API and a CrossFade Transition for Compose"}, {"memory_node_id": "bumptech__glide__release__v5_0_0_rc01", "answer_text": "Add a Painter variant of the placeholder APIs in the Compose integration"}]}
{"prototype_id": "caddyserver__caddy_release_window", "repo": "caddyserver/caddy", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the caddyserver/caddy releases, which release introduces Encrypted ClientHello (ECH) and post-quantum key exchange with x25519mlkem768?", "options": [{"option_id": "A", "text": "v2.8.0"}, {"option_id": "B", "text": "v2.9.0"}, {"option_id": "C", "text": "v2.10.0"}, {"option_id": "D", "text": "v2.11.1"}], "correct_option_id": "C", "expected_answer": "v2.10.0", "source_chunk_ids": ["caddyserver__caddy__release__v2_10_0"], "answer_support": [{"memory_node_id": "caddyserver__caddy__release__v2_10_0", "answer_text": "Caddy 2.10 featuring Encrypted ClientHello (ECH), post-quantum (PQC) key exchange with x25519mlkem768"}]}
{"prototype_id": "carbon_language__carbon_lang_release_window", "repo": "carbon-language/carbon-lang", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the carbon-language/carbon-lang releases, which release includes the addition of a text mode for fingerprinting?", "options": [{"option_id": "A", "text": "v0.0.0-0.nightly.2026.05.19"}, {"option_id": "B", "text": "v0.0.0-0.nightly.2026.05.20"}, {"option_id": "C", "text": "v0.0.0-0.nightly.2026.05.21"}, {"option_id": "D", "text": "v0.0.0-0.nightly.2026.05.22"}], "correct_option_id": "B", "expected_answer": "v0.0.0-0.nightly.2026.05.20", "source_chunk_ids": ["carbon_language__carbon_lang__release__v0_0_0_0_nightly_2026_05_20"], "answer_support": [{"memory_node_id": "carbon_language__carbon_lang__release__v0_0_0_0_nightly_2026_05_20", "answer_text": "adding a text mode for fingerprinting"}]}
{"prototype_id": "carbon_language__carbon_lang_release_window", "repo": "carbon-language/carbon-lang", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the carbon-language/carbon-lang release window, order the following release-content states from earliest to latest: (1) a release that adds support for field initializers, (2) a release that implements `static var` class fields, (3) a release that adds FieldStore and fixes field initializer imports.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "B", "expected_answer": "2 -> 1 -> 3", "source_chunk_ids": ["carbon_language__carbon_lang__release__v0_0_0_0_nightly_2026_05_19", "carbon_language__carbon_lang__release__v0_0_0_0_nightly_2026_05_22", "carbon_language__carbon_lang__release__v0_0_0_0_nightly_2026_06_02"], "answer_support": [{"memory_node_id": "carbon_language__carbon_lang__release__v0_0_0_0_nightly_2026_05_19", "answer_text": "Implement `static var` class fields"}, {"memory_node_id": "carbon_language__carbon_lang__release__v0_0_0_0_nightly_2026_05_22", "answer_text": "Add support for field initializers"}, {"memory_node_id": "carbon_language__carbon_lang__release__v0_0_0_0_nightly_2026_06_02", "answer_text": "Add FieldStore and fix field initializer imports"}]}
{"prototype_id": "ccfos__nightingale_release_window", "repo": "ccfos/nightingale", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the ccfos/nightingale releases, which release introduces a new dashboard datasource selector and changes the default execution frequency of alert rules to 60 seconds?", "options": [{"option_id": "A", "text": "v8.0.0-beta.10"}, {"option_id": "B", "text": "v8.0.0-beta.11"}, {"option_id": "C", "text": "v8.0.0-beta.9"}, {"option_id": "D", "text": "v8.0.0-beta.8"}], "correct_option_id": "A", "expected_answer": "v8.0.0-beta.10", "source_chunk_ids": ["ccfos__nightingale__release__v8_0_0_beta_10"], "answer_support": [{"memory_node_id": "ccfos__nightingale__release__v8_0_0_beta_10", "answer_text": "introduces a new dashboard datasource selector ... changes default execution frequency of alert rules to 60 seconds"}]}
{"prototype_id": "ccfos__nightingale_release_window", "repo": "ccfos/nightingale", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the ccfos/nightingale releases, how does the notification channel change in v8.0.0-beta.8.3 differ from the notification channel change in v8.0.0-beta.8?", "options": [{"option_id": "A", "text": "v8.0.0-beta.8 adds a Discord notification channel, while v8.0.0-beta.8.3 adds built-in notification media for Feishu app, Slack, Mattermost, and Callback."}, {"option_id": "B", "text": "v8.0.0-beta.8 adds Feishu app, Slack, Mattermost, and Callback, while v8.0.0-beta.8.3 adds Discord."}, {"option_id": "C", "text": "Both releases only fix notification bugs without adding new channels."}, {"option_id": "D", "text": "v8.0.0-beta.8 adds email notification records, while v8.0.0-beta.8.3 adds Discord."}], "correct_option_id": "A", "expected_answer": "v8.0.0-beta.8 adds a Discord notification channel, while v8.0.0-beta.8.3 adds built-in notification media for Feishu app, Slack, Mattermost, and Callback.", "source_chunk_ids": ["ccfos__nightingale__release__v8_0_0_beta_8", "ccfos__nightingale__release__v8_0_0_beta_8_3"], "answer_support": [{"memory_node_id": "ccfos__nightingale__release__v8_0_0_beta_8", "answer_text": "adds a Discord notification channel"}, {"memory_node_id": "ccfos__nightingale__release__v8_0_0_beta_8_3", "answer_text": "adds built-in notification media for Feishu app, Slack, Mattermost, and Callback"}]}
{"prototype_id": "ccfos__nightingale_release_window", "repo": "ccfos/nightingale", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the ccfos/nightingale release window, order the following release-content states from earliest to latest: (1) a release that adds support for ClickHouse data source alerts, (2) a release that introduces Nightingale AI with built-in AI assistant and Skills marketplace, (3) a release that adds a 'Table NG' panel type to dashboards, (4) a release that adds support for VictoriaLogs data source for alert rules.", "options": [{"option_id": "A", "text": "1 -> 3 -> 4 -> 2"}, {"option_id": "B", "text": "3 -> 1 -> 4 -> 2"}, {"option_id": "C", "text": "1 -> 4 -> 3 -> 2"}, {"option_id": "D", "text": "2 -> 1 -> 3 -> 4"}], "correct_option_id": "A", "expected_answer": "1 -> 3 -> 4 -> 2", "source_chunk_ids": ["ccfos__nightingale__release__v8_0_0_beta_11", "ccfos__nightingale__release__v8_3_0", "ccfos__nightingale__release__v8_5_0", "ccfos__nightingale__release__v9_0_0_beta_1"], "answer_support": [{"memory_node_id": "ccfos__nightingale__release__v8_0_0_beta_11", "answer_text": "adds support for ClickHouse data source alerts"}, {"memory_node_id": "ccfos__nightingale__release__v8_3_0", "answer_text": "adds a 'Table NG' panel type to dashboards"}, {"memory_node_id": "ccfos__nightingale__release__v8_5_0", "answer_text": "adds support for VictoriaLogs data source for alert rules"}, {"memory_node_id": "ccfos__nightingale__release__v9_0_0_beta_1", "answer_text": "introduces Nightingale AI with built-in AI assistant, Skills marketplace"}]}
{"prototype_id": "ccxt__ccxt_release_window", "repo": "ccxt/ccxt", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the ccxt/ccxt releases, which release introduces the Zebpay exchange integration?", "options": [{"option_id": "A", "text": "v4.5.27"}, {"option_id": "B", "text": "v4.5.28"}, {"option_id": "C", "text": "v4.5.29"}, {"option_id": "D", "text": "v4.5.30"}], "correct_option_id": "A", "expected_answer": "v4.5.27", "source_chunk_ids": ["ccxt__ccxt__release__v4_5_27"], "answer_support": [{"memory_node_id": "ccxt__ccxt__release__v4_5_27", "answer_text": "adds a new Zebpay exchange integration"}]}
{"prototype_id": "ccxt__ccxt_release_window", "repo": "ccxt/ccxt", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the ccxt/ccxt releases, how does the exchange integration added in v4.5.30 differ from the exchange integration added in v4.5.32?", "options": [{"option_id": "A", "text": "v4.5.30 integrates bydfi, while v4.5.32 integrates aster."}, {"option_id": "B", "text": "v4.5.30 integrates aster, while v4.5.32 integrates bydfi."}, {"option_id": "C", "text": "Both releases integrate the same exchange."}, {"option_id": "D", "text": "v4.5.30 integrates zebpay, while v4.5.32 integrates aftermath."}], "correct_option_id": "A", "expected_answer": "v4.5.30 integrates bydfi, while v4.5.32 integrates aster.", "source_chunk_ids": ["ccxt__ccxt__release__v4_5_30", "ccxt__ccxt__release__v4_5_32"], "answer_support": [{"memory_node_id": "ccxt__ccxt__release__v4_5_30", "answer_text": "integrates the bydfi exchange"}, {"memory_node_id": "ccxt__ccxt__release__v4_5_32", "answer_text": "integrates the aster exchange"}]}
{"prototype_id": "ccxt__ccxt_release_window", "repo": "ccxt/ccxt", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the ccxt/ccxt release window, order the following release-content states from earliest to latest: (1) a release that adds the Zebpay exchange integration, (2) a release that adds the bydfi exchange integration, (3) a release that adds the aster exchange integration, (4) a release that adds the aftermath exchange integration.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["ccxt__ccxt__release__v4_5_27", "ccxt__ccxt__release__v4_5_30", "ccxt__ccxt__release__v4_5_32", "ccxt__ccxt__release__v4_5_43"], "answer_support": [{"memory_node_id": "ccxt__ccxt__release__v4_5_27", "answer_text": "adds a new Zebpay exchange integration"}, {"memory_node_id": "ccxt__ccxt__release__v4_5_30", "answer_text": "integrates the bydfi exchange"}, {"memory_node_id": "ccxt__ccxt__release__v4_5_32", "answer_text": "integrates the aster exchange"}, {"memory_node_id": "ccxt__ccxt__release__v4_5_43", "answer_text": "integrates the aftermath exchange"}]}
{"prototype_id": "charmbracelet__bubbletea_release_window", "repo": "charmbracelet/bubbletea", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the charmbracelet/bubbletea releases, which release introduces the new Cursed Renderer and a declarative view API?", "options": [{"option_id": "A", "text": "v2.0.0-beta.1"}, {"option_id": "B", "text": "v2.0.0-rc.1"}, {"option_id": "C", "text": "v2.0.0"}, {"option_id": "D", "text": "v2.0.3"}], "correct_option_id": "C", "expected_answer": "v2.0.0", "source_chunk_ids": ["charmbracelet__bubbletea__release__v2_0_0"], "answer_support": [{"memory_node_id": "charmbracelet__bubbletea__release__v2_0_0", "answer_text": "features the new Cursed Renderer, improved key handling with progressive keyboard enhancements, built-in color downsampling, a declarative view API"}]}
{"prototype_id": "charmbracelet__bubbletea_release_window", "repo": "charmbracelet/bubbletea", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the charmbracelet/bubbletea releases, how does the interrupt handling change described in v1.3.0 differ from the keyboard enhancement changes described in v2.0.0-beta.3?", "options": [{"option_id": "A", "text": "v1.3.0 introduces a tea.Interrupt command for graceful ctrl+c handling, while v2.0.0-beta.3 enables key disambiguation by default and always enables basic keyboard enhancements."}, {"option_id": "B", "text": "v1.3.0 removes interrupt handling, while v2.0.0-beta.3 disables keyboard enhancements."}, {"option_id": "C", "text": "Both releases only fix Windows input issues without changing interrupt or keyboard behavior."}, {"option_id": "D", "text": "v1.3.0 adds keyboard enhancements, while v2.0.0-beta.3 adds interrupt handling."}], "correct_option_id": "A", "expected_answer": "v1.3.0 introduces a tea.Interrupt command for graceful ctrl+c handling, while v2.0.0-beta.3 enables key disambiguation by default and always enables basic keyboard enhancements.", "source_chunk_ids": ["charmbracelet__bubbletea__release__v1_3_0", "charmbracelet__bubbletea__release__v2_0_0_beta_3"], "answer_support": [{"memory_node_id": "charmbracelet__bubbletea__release__v1_3_0", "answer_text": "refined interrupt handling is introduced, allowing graceful handling of ctrl+c or interrupt signals via a new tea.Interrupt command"}, {"memory_node_id": "charmbracelet__bubbletea__release__v2_0_0_beta_3", "answer_text": "key disambiguation is enabled by default when supported, and basic keyboard enhancements are always enabled to disambiguate keys"}]}
{"prototype_id": "charmbracelet__bubbletea_release_window", "repo": "charmbracelet/bubbletea", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the charmbracelet/bubbletea release window, order the following release-content states from earliest to latest: (1) a release that fixes canceling terminal input reads on Windows, (2) a release that restores deprecated program options, (3) a release that fixes an issue where the mouse is always enabled on Windows even if not requested, (4) a release that fixes function key recognition on Windows and concurrency bugs.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["charmbracelet__bubbletea__release__v1_3_2", "charmbracelet__bubbletea__release__v1_3_3", "charmbracelet__bubbletea__release__v1_3_4", "charmbracelet__bubbletea__release__v1_3_5"], "answer_support": [{"memory_node_id": "charmbracelet__bubbletea__release__v1_3_2", "answer_text": "fix is provided for canceling terminal input reads on Windows"}, {"memory_node_id": "charmbracelet__bubbletea__release__v1_3_3", "answer_text": "program options that were deprecated in previous releases are restored"}, {"memory_node_id": "charmbracelet__bubbletea__release__v1_3_4", "answer_text": "issue on Windows is fixed where the mouse is always enabled even if not requested"}, {"memory_node_id": "charmbracelet__bubbletea__release__v1_3_5", "answer_text": "important bug on Windows is fixed where function keys (F1..F20) were not recognized, and multiple concurrency bugs are resolved"}]}
{"prototype_id": "chartjs__Chart_js_release_window", "repo": "chartjs/Chart.js", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the chartjs/Chart.js releases, which release adds a selfJoin option for doughnut graphs?", "options": [{"option_id": "A", "text": "v4.4.9"}, {"option_id": "B", "text": "v4.5.0"}, {"option_id": "C", "text": "v4.4.8"}, {"option_id": "D", "text": "v4.5.1"}], "correct_option_id": "B", "expected_answer": "v4.5.0", "source_chunk_ids": ["chartjs__Chart_js__release__v4_5_0"], "answer_support": [{"memory_node_id": "chartjs__Chart_js__release__v4_5_0", "answer_text": "adding selfJoin option for doughnut graphs"}]}
{"prototype_id": "chartjs__Chart_js_release_window", "repo": "chartjs/Chart.js", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the chartjs/Chart.js releases, how does the change related to tooltips in v4.4.1 differ from the change related to tooltips in v4.4.4?", "options": [{"option_id": "A", "text": "v4.4.1 fixes tooltips for null controller and null getParsed, while v4.4.4 fixes tooltip show for all invisible."}, {"option_id": "B", "text": "v4.4.1 adds tooltip callbacks fallback, while v4.4.4 removes tooltip constructor fallbacks."}, {"option_id": "C", "text": "Both releases only update tooltip documentation without functional changes."}, {"option_id": "D", "text": "v4.4.1 changes tooltip mode type, while v4.4.4 adds tooltip positioner for no valid data."}], "correct_option_id": "A", "expected_answer": "v4.4.1 fixes tooltips for null controller and null getParsed, while v4.4.4 fixes tooltip show for all invisible.", "source_chunk_ids": ["chartjs__Chart_js__release__v4_4_1", "chartjs__Chart_js__release__v4_4_4"], "answer_support": [{"memory_node_id": "chartjs__Chart_js__release__v4_4_1", "answer_text": "fix tooltips (getLabelAndValue on null controller, null getParsed)"}, {"memory_node_id": "chartjs__Chart_js__release__v4_4_4", "answer_text": "fix tooltip show for all invisible"}]}
{"prototype_id": "chartjs__Chart_js_release_window", "repo": "chartjs/Chart.js", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the chartjs/Chart.js release window, order the following release-content states from earliest to latest: (1) a release that adds a clip option to scale configuration to allow unclipped scales, (2) a release that adds a selfJoin option for doughnut graphs, (3) a release that fixes applyStack() returning the sum of all values for hidden dataset indices, (4) a release that fixes tooltip show for all invisible.", "options": [{"option_id": "A", "text": "1 -> 4 -> 3 -> 2"}, {"option_id": "B", "text": "4 -> 1 -> 3 -> 2"}, {"option_id": "C", "text": "1 -> 3 -> 4 -> 2"}, {"option_id": "D", "text": "3 -> 1 -> 4 -> 2"}], "correct_option_id": "A", "expected_answer": "1 -> 4 -> 3 -> 2", "source_chunk_ids": ["chartjs__Chart_js__release__v4_4_0", "chartjs__Chart_js__release__v4_4_4", "chartjs__Chart_js__release__v4_4_6", "chartjs__Chart_js__release__v4_5_0"], "answer_support": [{"memory_node_id": "chartjs__Chart_js__release__v4_4_0", "answer_text": "add clip option to scale configuration to allow unclipped scales"}, {"memory_node_id": "chartjs__Chart_js__release__v4_4_4", "answer_text": "fix tooltip show for all invisible"}, {"memory_node_id": "chartjs__Chart_js__release__v4_4_6", "answer_text": "fix applyStack() returned the sum of all values for hidden dataset indices"}, {"memory_node_id": "chartjs__Chart_js__release__v4_5_0", "answer_text": "adding selfJoin option for doughnut graphs"}]}
{"prototype_id": "ChatGPTNextWeb__NextChat_release_window", "repo": "ChatGPTNextWeb/NextChat", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the ChatGPTNextWeb/NextChat releases, which release introduces a plugin system based on function calls similar to GPTs actions?", "options": [{"option_id": "A", "text": "v2.14.0"}, {"option_id": "B", "text": "v2.15.0"}, {"option_id": "C", "text": "v2.15.2"}, {"option_id": "D", "text": "v2.16.0"}], "correct_option_id": "B", "expected_answer": "v2.15.0", "source_chunk_ids": ["ChatGPTNextWeb__NextChat__release__v2_15_0"], "answer_support": [{"memory_node_id": "ChatGPTNextWeb__NextChat__release__v2_15_0", "answer_text": "introduces a plugin system (GPTs-like actions based on function calls)"}]}
{"prototype_id": "ChatGPTNextWeb__NextChat_release_window", "repo": "ChatGPTNextWeb/NextChat", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the ChatGPTNextWeb/NextChat releases, how does the model support change described in v2.10.1 differ from the model support change described in v2.12.2?", "options": [{"option_id": "A", "text": "v2.10.1 adds Google Gemini Pro support, while v2.12.2 adds Anthropic Claude and gpt-4-turbo support."}, {"option_id": "B", "text": "v2.10.1 adds Azure support, while v2.12.2 adds Ollama support."}, {"option_id": "C", "text": "Both releases add the same set of models."}, {"option_id": "D", "text": "v2.10.1 adds Claude support, while v2.12.2 adds Gemini support."}], "correct_option_id": "A", "expected_answer": "v2.10.1 adds Google Gemini Pro support, while v2.12.2 adds Anthropic Claude and gpt-4-turbo support.", "source_chunk_ids": ["ChatGPTNextWeb__NextChat__release__v2_10_1", "ChatGPTNextWeb__NextChat__release__v2_12_2"], "answer_support": [{"memory_node_id": "ChatGPTNextWeb__NextChat__release__v2_10_1", "answer_text": "adds support for the Google Gemini Pro model"}, {"memory_node_id": "ChatGPTNextWeb__NextChat__release__v2_12_2", "answer_text": "adds support for Anthropic Claude and gpt-4-turbo"}]}
{"prototype_id": "ChatGPTNextWeb__NextChat_release_window", "repo": "ChatGPTNextWeb/NextChat", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the ChatGPTNextWeb/NextChat release window, order the following release-content states from earliest to latest: (1) a release that adds support for the Google Gemini Pro model, (2) a release that adds support for the OpenAI o1 model, (3) a release that adds support for the OpenAI Realtime API, (4) a release that adds DeepSeek as a new model provider.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "C", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["ChatGPTNextWeb__NextChat__release__v2_10_1", "ChatGPTNextWeb__NextChat__release__v2_15_2", "ChatGPTNextWeb__NextChat__release__v2_15_8", "ChatGPTNextWeb__NextChat__release__v2_16_0"], "answer_support": [{"memory_node_id": "ChatGPTNextWeb__NextChat__release__v2_10_1", "answer_text": "adds support for the Google Gemini Pro model"}, {"memory_node_id": "ChatGPTNextWeb__NextChat__release__v2_15_2", "answer_text": "adds support for the OpenAI o1 model"}, {"memory_node_id": "ChatGPTNextWeb__NextChat__release__v2_15_8", "answer_text": "adds support for the OpenAI Realtime API"}, {"memory_node_id": "ChatGPTNextWeb__NextChat__release__v2_16_0", "answer_text": "adds DeepSeek as a new model provider"}]}
{"prototype_id": "ChromeDevTools__chrome_devtools_mcp_release_window", "repo": "ChromeDevTools/chrome-devtools-mcp", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the ChromeDevTools/chrome-devtools-mcp releases, which release introduces geolocation emulation and support for --user-data-dir?", "options": [{"option_id": "A", "text": "v0.10.2"}, {"option_id": "B", "text": "v0.11.0"}, {"option_id": "C", "text": "v0.12.0"}, {"option_id": "D", "text": "v0.13.0"}], "correct_option_id": "B", "expected_answer": "v0.11.0", "source_chunk_ids": ["ChromeDevTools__chrome_devtools_mcp__release__chrome_devtools_mcp_v0_11_0"], "answer_support": [{"memory_node_id": "ChromeDevTools__chrome_devtools_mcp__release__chrome_devtools_mcp_v0_11_0", "answer_text": "new features include geolocation emulation, integration of DevTools issues into console tools, and support for --user-data-dir"}]}
{"prototype_id": "ChromeDevTools__chrome_devtools_mcp_release_window", "repo": "ChromeDevTools/chrome-devtools-mcp", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the ChromeDevTools/chrome-devtools-mcp releases, how does the feature set of v0.18.0 differ from that of v0.19.0?", "options": [{"option_id": "A", "text": "v0.18.0 introduces --slim mode and accessibility debugging skill, while v0.19.0 adds pageId routing for parallel multi-agent workflows and integrates Lighthouse audits."}, {"option_id": "B", "text": "v0.18.0 adds Lighthouse integration, while v0.19.0 introduces --slim mode."}, {"option_id": "C", "text": "Both releases only contain documentation updates."}, {"option_id": "D", "text": "v0.18.0 adds geolocation emulation, while v0.19.0 adds --auto-connect."}], "correct_option_id": "A", "expected_answer": "v0.18.0 introduces --slim mode and accessibility debugging skill, while v0.19.0 adds pageId routing for parallel multi-agent workflows and integrates Lighthouse audits.", "source_chunk_ids": ["ChromeDevTools__chrome_devtools_mcp__release__chrome_devtools_mcp_v0_18_0", "ChromeDevTools__chrome_devtools_mcp__release__chrome_devtools_mcp_v0_19_0"], "answer_support": [{"memory_node_id": "ChromeDevTools__chrome_devtools_mcp__release__chrome_devtools_mcp_v0_18_0", "answer_text": "features include --slim mode for maximum token savings, a new skill for accessibility debugging and auditing"}, {"memory_node_id": "ChromeDevTools__chrome_devtools_mcp__release__chrome_devtools_mcp_v0_19_0", "answer_text": "features add pageId routing for parallel multi-agent workflows, a skill for onboarding of the mcp server, and integrate Lighthouse audits"}]}
{"prototype_id": "cilium__cilium_release_window", "repo": "cilium/cilium", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the cilium/cilium releases, which release introduces a ztunnel daemonset controller and an xds control-plane for ztunnel?", "options": [{"option_id": "A", "text": "v1.19.0-pre.3"}, {"option_id": "B", "text": "v1.19.0-pre.4"}, {"option_id": "C", "text": "v1.19.0-rc.0"}, {"option_id": "D", "text": "v1.19.0"}], "correct_option_id": "A", "expected_answer": "v1.19.0-pre.3", "source_chunk_ids": ["cilium__cilium__release__v1_19_0_pre_3"], "answer_support": [{"memory_node_id": "cilium__cilium__release__v1_19_0_pre_3", "answer_text": "major changes include adding an xds control-plane for ztunnel and a ztunnel daemonset controller"}]}
{"prototype_id": "cilium__cilium_release_window", "repo": "cilium/cilium", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the cilium/cilium releases, how does the handling of Helm chart publishing differ between v1.18.6 and v1.19.0-rc.0?", "options": [{"option_id": "A", "text": "v1.18.6 publishes Helm charts to OCI registries as a major change, while v1.19.0-rc.0 also publishes Helm charts to OCI registries as a major change."}, {"option_id": "B", "text": "v1.18.6 does not mention Helm chart publishing, while v1.19.0-rc.0 introduces it as a minor change."}, {"option_id": "C", "text": "v1.18.6 publishes Helm charts to OCI registries as a minor change, while v1.19.0-rc.0 does not mention it."}, {"option_id": "D", "text": "v1.18.6 removes Helm chart publishing, while v1.19.0-rc.0 restores it."}], "correct_option_id": "A", "expected_answer": "v1.18.6 publishes Helm charts to OCI registries as a major change, while v1.19.0-rc.0 also publishes Helm charts to OCI registries as a major change.", "source_chunk_ids": ["cilium__cilium__release__v1_18_6", "cilium__cilium__release__v1_19_0_rc_0"], "answer_support": [{"memory_node_id": "cilium__cilium__release__v1_18_6", "answer_text": "a major change is publishing Helm charts to OCI registries"}, {"memory_node_id": "cilium__cilium__release__v1_19_0_rc_0", "answer_text": "a major change is publishing Helm charts to OCI registries"}]}
{"prototype_id": "clash_verge_rev__clash_verge_rev_release_window", "repo": "clash-verge-rev/clash-verge-rev", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the clash-verge-rev/clash-verge-rev releases, which release introduces a new IPC communication mechanism and a redesigned traffic monitoring interface?", "options": [{"option_id": "A", "text": "v2.3.0"}, {"option_id": "B", "text": "v2.4.0"}, {"option_id": "C", "text": "v2.4.1"}, {"option_id": "D", "text": "v2.5.0"}], "correct_option_id": "B", "expected_answer": "v2.4.0", "source_chunk_ids": ["clash_verge_rev__clash_verge_rev__release__v2_4_0"], "answer_support": [{"memory_node_id": "clash_verge_rev__clash_verge_rev__release__v2_4_0", "answer_text": "major improvements including a new IPC communication mechanism, redesigned traffic monitoring interface"}]}
{"prototype_id": "clash_verge_rev__clash_verge_rev_release_window", "repo": "clash-verge-rev/clash-verge-rev", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the clash-verge-rev/clash-verge-rev releases, how does the system proxy setting method in v2.4.4 differ from that in v2.0.1?", "options": [{"option_id": "A", "text": "v2.0.1 uses sysproxy.exe for Windows system proxy, while v2.4.4 no longer depends on sysproxy.exe."}, {"option_id": "B", "text": "v2.0.1 removes system proxy support, while v2.4.4 adds it back."}, {"option_id": "C", "text": "Both versions use the same system proxy method."}, {"option_id": "D", "text": "v2.0.1 uses a custom proxy script, while v2.4.4 uses sysproxy.exe."}], "correct_option_id": "A", "expected_answer": "v2.0.1 uses sysproxy.exe for Windows system proxy, while v2.4.4 no longer depends on sysproxy.exe.", "source_chunk_ids": ["clash_verge_rev__clash_verge_rev__release__v2_0_1", "clash_verge_rev__clash_verge_rev__release__v2_4_4"], "answer_support": [{"memory_node_id": "clash_verge_rev__clash_verge_rev__release__v2_0_1", "answer_text": "Win 下的系统代理替换为 Shadowsocks/CFW/v2rayN 等成熟的 sysproxy.exe 方案"}, {"memory_node_id": "clash_verge_rev__clash_verge_rev__release__v2_4_4", "answer_text": "优化 Windows 系统代理设置，不再依赖 sysproxy.exe 来设置代理"}]}
{"prototype_id": "cli__cli_release_window", "repo": "cli/cli", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the cli/cli releases, which release introduces the agent-task commandset for managing coding agent tasks?", "options": [{"option_id": "A", "text": "v2.79.0"}, {"option_id": "B", "text": "v2.80.0"}, {"option_id": "C", "text": "v2.81.0"}, {"option_id": "D", "text": "v2.82.0"}], "correct_option_id": "B", "expected_answer": "v2.80.0", "source_chunk_ids": ["cli__cli__release__v2_80_0"], "answer_support": [{"memory_node_id": "cli__cli__release__v2_80_0", "answer_text": "introduces the agent-task commandset for managing coding agent tasks"}]}
{"prototype_id": "cli__cli_release_window", "repo": "cli/cli", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the cli/cli releases, how does the Copilot-related change in v2.76.0 differ from the Copilot-related change in v2.87.0?", "options": [{"option_id": "A", "text": "v2.76.0 allows assigning issues to Copilot during issue creation, while v2.87.0 adds support for Copilot Code Review as a reviewer in gh pr edit."}, {"option_id": "B", "text": "v2.76.0 introduces the agent-task commandset, while v2.87.0 adds the gh copilot command."}, {"option_id": "C", "text": "Both releases only update Copilot-related documentation without functional changes."}, {"option_id": "D", "text": "v2.76.0 removes Copilot support, while v2.87.0 restores it."}], "correct_option_id": "A", "expected_answer": "v2.76.0 allows assigning issues to Copilot during issue creation, while v2.87.0 adds support for Copilot Code Review as a reviewer in gh pr edit.", "source_chunk_ids": ["cli__cli__release__v2_76_0", "cli__cli__release__v2_87_0"], "answer_support": [{"memory_node_id": "cli__cli__release__v2_76_0", "answer_text": "announces Copilot Coding Agent Support, allowing ... assign issues to Copilot during issue creation"}, {"memory_node_id": "cli__cli__release__v2_87_0", "answer_text": "adds support for Copilot Code Review as a reviewer in gh pr edit"}]}
{"prototype_id": "cli__cli_release_window", "repo": "cli/cli", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the cli/cli release window, order the following release-content states from earliest to latest: (1) a release that introduces the gh skill command group for managing agent skills, (2) a release that introduces the agent-task commandset for managing coding agent tasks, (3) a release that adds support for Copilot Code Review as a reviewer in gh pr edit, (4) a release that announces that GitHub CLI now collects pseudonymous telemetry.", "options": [{"option_id": "A", "text": "2 -> 3 -> 1 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "C", "text": "3 -> 2 -> 4 -> 1"}, {"option_id": "D", "text": "1 -> 2 -> 3 -> 4"}], "correct_option_id": "A", "expected_answer": "2 -> 3 -> 1 -> 4", "source_chunk_ids": ["cli__cli__release__v2_80_0", "cli__cli__release__v2_87_0", "cli__cli__release__v2_90_0", "cli__cli__release__v2_91_0"], "answer_support": [{"memory_node_id": "cli__cli__release__v2_80_0", "answer_text": "introduces the agent-task commandset"}, {"memory_node_id": "cli__cli__release__v2_87_0", "answer_text": "adds support for Copilot Code Review as a reviewer in gh pr edit"}, {"memory_node_id": "cli__cli__release__v2_90_0", "answer_text": "introduces the gh skill command group"}, {"memory_node_id": "cli__cli__release__v2_91_0", "answer_text": "announces that GitHub CLI now collects pseudonymous telemetry"}]}
{"prototype_id": "clockworklabs__SpacetimeDB_release_window", "repo": "clockworklabs/SpacetimeDB", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the clockworklabs/SpacetimeDB releases, which release introduces the spacetime dev command that automates the development loop?", "options": [{"option_id": "A", "text": "v1.6.0"}, {"option_id": "B", "text": "v1.7.0"}, {"option_id": "C", "text": "v1.8.0"}, {"option_id": "D", "text": "v1.9.0"}], "correct_option_id": "B", "expected_answer": "v1.7.0", "source_chunk_ids": ["clockworklabs__SpacetimeDB__release__v1_7_0"], "answer_support": [{"memory_node_id": "clockworklabs__SpacetimeDB__release__v1_7_0", "answer_text": "a new CLI command spacetime dev is introduced, automating the development loop by generating types, building, publishing, subscribing to logs, and watching for file changes."}]}
{"prototype_id": "clockworklabs__SpacetimeDB_release_window", "repo": "clockworklabs/SpacetimeDB", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the clockworklabs/SpacetimeDB releases, how does the TypeScript module support introduced in v1.6.0 differ from the TypeScript/JavaScript support in v2.0.1?", "options": [{"option_id": "A", "text": "v1.6.0 introduces TypeScript Modules in beta with a new runtime, while v2.0.1 announces TypeScript/JavaScript support leaving beta and includes web framework integrations."}, {"option_id": "B", "text": "v1.6.0 removes TypeScript support entirely, while v2.0.1 reintroduces it."}, {"option_id": "C", "text": "Both releases only update the TypeScript SDK without module support."}, {"option_id": "D", "text": "v1.6.0 adds TypeScript client SDK, while v2.0.1 adds TypeScript server modules."}], "correct_option_id": "A", "expected_answer": "v1.6.0 introduces TypeScript Modules in beta with a new runtime, while v2.0.1 announces TypeScript/JavaScript support leaving beta and includes web framework integrations.", "source_chunk_ids": ["clockworklabs__SpacetimeDB__release__v1_6_0", "clockworklabs__SpacetimeDB__release__v2_0_1"], "answer_support": [{"memory_node_id": "clockworklabs__SpacetimeDB__release__v1_6_0", "answer_text": "TypeScript Modules (Beta) are introduced, adding a new server module language with a new runtime shipping with v8."}, {"memory_node_id": "clockworklabs__SpacetimeDB__release__v2_0_1", "answer_text": "TypeScript/JavaScript support leaves beta, web framework integrations are built for Angular, React, Nuxt, Vue, Next.js, Node, Deno, TanStack, Remix, Svelte, and Bun."}]}
{"prototype_id": "clockworklabs__SpacetimeDB_release_window", "repo": "clockworklabs/SpacetimeDB", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the clockworklabs/SpacetimeDB release window, order the following release-content states from earliest to latest: (1) a release that introduces row-level security and enum index keys, (2) a release that introduces procedures and HTTP requests, (3) a release that introduces typed query builders for Rust and TypeScript modules, (4) a release that introduces client-side typed query builders and Vue/Svelte SDKs.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "3 -> 1 -> 4 -> 2"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["clockworklabs__SpacetimeDB__release__v1_1_0", "clockworklabs__SpacetimeDB__release__v1_10_0", "clockworklabs__SpacetimeDB__release__v1_11_0", "clockworklabs__SpacetimeDB__release__v1_12_0"], "answer_support": [{"memory_node_id": "clockworklabs__SpacetimeDB__release__v1_1_0", "answer_text": "public access for row-level security is introduced. ... support for enums as index keys"}, {"memory_node_id": "clockworklabs__SpacetimeDB__release__v1_10_0", "answer_text": "procedures and HTTP requests are introduced"}, {"memory_node_id": "clockworklabs__SpacetimeDB__release__v1_11_0", "answer_text": "typed query builders for Rust and TypeScript modules are released"}, {"memory_node_id": "clockworklabs__SpacetimeDB__release__v1_12_0", "answer_text": "client-side typed query builders are added for TypeScript, Rust, and C#. New front-end framework SDKs for Vue and Svelte are introduced."}]}
{"prototype_id": "coder__code_server_release_window", "repo": "coder/code-server", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the coder/code-server releases, how does the change to --app-name in v4.122.0 differ from the change to --app-name in v4.111.0?", "options": [{"option_id": "A", "text": "v4.111.0 makes --app-name affect the error page title, while v4.122.0 makes it affect window titles within the editor and adds the CODE_SERVER_APP_NAME environment variable."}, {"option_id": "B", "text": "v4.111.0 removes --app-name entirely, while v4.122.0 reintroduces it for window titles."}, {"option_id": "C", "text": "Both releases only update the underlying Code version without changing --app-name behavior."}, {"option_id": "D", "text": "v4.111.0 adds the CODE_SERVER_APP_NAME environment variable, while v4.122.0 makes --app-name affect the error page title."}], "correct_option_id": "A", "expected_answer": "v4.111.0 makes --app-name affect the error page title, while v4.122.0 makes it affect window titles within the editor and adds the CODE_SERVER_APP_NAME environment variable.", "source_chunk_ids": ["coder__code_server__release__v4_111_0", "coder__code_server__release__v4_122_0"], "answer_support": [{"memory_node_id": "coder__code_server__release__v4_111_0", "answer_text": "--app-name now affects the error page title"}, {"memory_node_id": "coder__code_server__release__v4_122_0", "answer_text": "--app-name will now affect window titles within the editor ... app name can now be set with the CODE_SERVER_APP_NAME environment variable"}]}
{"prototype_id": "Comfy_Org__ComfyUI_release_window", "repo": "Comfy-Org/ComfyUI", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the Comfy-Org/ComfyUI releases, which release adds a Math Expression node with simpleeval evaluation?", "options": [{"option_id": "A", "text": "v0.16.4"}, {"option_id": "B", "text": "v0.17.0"}, {"option_id": "C", "text": "v0.15.0"}, {"option_id": "D", "text": "v0.14.0"}], "correct_option_id": "A", "expected_answer": "v0.16.4", "source_chunk_ids": ["Comfy_Org__ComfyUI__release__v0_16_4"], "answer_support": [{"memory_node_id": "Comfy_Org__ComfyUI__release__v0_16_4", "answer_text": "adds a Math Expression node with simpleeval evaluation"}]}
{"prototype_id": "Comfy_Org__ComfyUI_release_window", "repo": "Comfy-Org/ComfyUI", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the Comfy-Org/ComfyUI release window, order the following release-content states from earliest to latest: (1) a release that adds a VideoSlice node, (2) a release that adds a Math Expression node with simpleeval evaluation, (3) a release that adds a CURVE node, (4) a release that adds a ResolutionSelector node for aspect ratio presets.", "options": [{"option_id": "A", "text": "1 -> 4 -> 2 -> 3"}, {"option_id": "B", "text": "4 -> 1 -> 2 -> 3"}, {"option_id": "C", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "D", "text": "2 -> 1 -> 3 -> 4"}], "correct_option_id": "A", "expected_answer": "1 -> 4 -> 2 -> 3", "source_chunk_ids": ["Comfy_Org__ComfyUI__release__v0_14_0", "Comfy_Org__ComfyUI__release__v0_16_0", "Comfy_Org__ComfyUI__release__v0_16_4", "Comfy_Org__ComfyUI__release__v0_19_0"], "answer_support": [{"memory_node_id": "Comfy_Org__ComfyUI__release__v0_14_0", "answer_text": "Add a VideoSlice node"}, {"memory_node_id": "Comfy_Org__ComfyUI__release__v0_16_0", "answer_text": "adds ResolutionSelector node for aspect ratio presets"}, {"memory_node_id": "Comfy_Org__ComfyUI__release__v0_16_4", "answer_text": "adds a Math Expression node with simpleeval evaluation"}, {"memory_node_id": "Comfy_Org__ComfyUI__release__v0_19_0", "answer_text": "adds CURVE node"}]}
{"prototype_id": "conductor_oss__conductor_release_window", "repo": "conductor-oss/conductor", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the conductor-oss/conductor releases, which release introduces the Workflow Message Queue (WMQ) feature to push messages into running workflows?", "options": [{"option_id": "A", "text": "v3.22.3"}, {"option_id": "B", "text": "v3.23.0"}, {"option_id": "C", "text": "v3.3.0.rc8"}, {"option_id": "D", "text": "v3.30.0"}], "correct_option_id": "C", "expected_answer": "v3.3.0.rc8", "source_chunk_ids": ["conductor_oss__conductor__release__v3_3_0_rc8"], "answer_support": [{"memory_node_id": "conductor_oss__conductor__release__v3_3_0_rc8", "answer_text": "introduced the Workflow Message Queue (WMQ) feature to push messages into running workflows"}]}
{"prototype_id": "conductor_oss__conductor_release_window", "repo": "conductor-oss/conductor", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the conductor-oss/conductor releases, how does the AI-related change in v3.30.1 differ from the AI-related change in v3.30.0.rc14?", "options": [{"option_id": "A", "text": "v3.30.1 rewrites thinkingTokenLimit to adaptive thinking on Claude Opus 4.7, while v3.30.0.rc14 adds reasoning / chain-of-thought summary support across all AI providers."}, {"option_id": "B", "text": "v3.30.1 adds reasoning / chain-of-thought summary support, while v3.30.0.rc14 rewrites thinkingTokenLimit."}, {"option_id": "C", "text": "Both releases only update AI provider SDKs without functional changes."}, {"option_id": "D", "text": "v3.30.1 removes AI features, while v3.30.0.rc14 adds them."}], "correct_option_id": "A", "expected_answer": "v3.30.1 rewrites thinkingTokenLimit to adaptive thinking on Claude Opus 4.7, while v3.30.0.rc14 adds reasoning / chain-of-thought summary support across all AI providers.", "source_chunk_ids": ["conductor_oss__conductor__release__v3_30_1", "conductor_oss__conductor__release__v3_30_0_rc14"], "answer_support": [{"memory_node_id": "conductor_oss__conductor__release__v3_30_1", "answer_text": "rewrote thinkingTokenLimit to adaptive thinking on Claude Opus 4.7"}, {"memory_node_id": "conductor_oss__conductor__release__v3_30_0_rc14", "answer_text": "added reasoning / chain-of-thought summary support across all AI providers"}]}
{"prototype_id": "continuedev__continue_release_window", "repo": "continuedev/continue", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the continuedev/continue releases, which release introduces the Nous Research Hermes models as a provider and adds OpenRouter Provider Support with Dynamic Model Loading?", "options": [{"option_id": "A", "text": "@continuedev/config-yaml@1.41.0"}, {"option_id": "B", "text": "@continuedev/config-yaml@1.42.0"}, {"option_id": "C", "text": "v1.3.31-vscode"}, {"option_id": "D", "text": "v1.2.15-vscode"}], "correct_option_id": "B", "expected_answer": "@continuedev/config-yaml@1.42.0", "source_chunk_ids": ["continuedev__continue__release__continuedev_config_yaml_1_42_0"], "answer_support": [{"memory_node_id": "continuedev__continue__release__continuedev_config_yaml_1_42_0", "answer_text": "New features added were Nous Research Hermes models as a provider and OpenRouter Provider Support with Dynamic Model Loading."}]}
{"prototype_id": "coollabsio__coolify_release_window", "repo": "coollabsio/coolify", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the coollabsio/coolify releases, which release adds a developer view for shared environment variables and custom docker entrypoint support?", "options": [{"option_id": "A", "text": "v4.0.0-beta.448"}, {"option_id": "B", "text": "v4.0.0-beta.449"}, {"option_id": "C", "text": "v4.0.0-beta.450"}, {"option_id": "D", "text": "v4.0.0-beta.451"}], "correct_option_id": "B", "expected_answer": "v4.0.0-beta.449", "source_chunk_ids": ["coollabsio__coolify__release__v4_0_0_beta_449"], "answer_support": [{"memory_node_id": "coollabsio__coolify__release__v4_0_0_beta_449", "answer_text": "New features include a developer view for shared environment variables and custom docker entrypoint support."}]}
{"prototype_id": "coollabsio__coolify_release_window", "repo": "coollabsio/coolify", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the coollabsio/coolify releases, how does the security fix in v4.0.0-beta.451 differ from the security fix in v4.0.0-beta.456?", "options": [{"option_id": "A", "text": "v4.0.0-beta.451 validates and escapes database names, file paths, and proxy configuration filenames to prevent command injection, while v4.0.0-beta.456 adds automatic PII/secret sanitization in logs for GitHub, GitLab, AWS tokens and URL passwords."}, {"option_id": "B", "text": "v4.0.0-beta.451 fixes Docker command failures on non-root servers, while v4.0.0-beta.456 fixes server resources tab 500 error."}, {"option_id": "C", "text": "Both releases only update Umami to address CVEs."}, {"option_id": "D", "text": "v4.0.0-beta.451 adds automatic PII sanitization, while v4.0.0-beta.456 validates database names."}], "correct_option_id": "A", "expected_answer": "v4.0.0-beta.451 validates and escapes database names, file paths, and proxy configuration filenames to prevent command injection, while v4.0.0-beta.456 adds automatic PII/secret sanitization in logs for GitHub, GitLab, AWS tokens and URL passwords.", "source_chunk_ids": ["coollabsio__coolify__release__v4_0_0_beta_451", "coollabsio__coolify__release__v4_0_0_beta_456"], "answer_support": [{"memory_node_id": "coollabsio__coolify__release__v4_0_0_beta_451", "answer_text": "Enhanced security by validating and escaping database names, file paths, and proxy configuration filenames to prevent command injection"}, {"memory_node_id": "coollabsio__coolify__release__v4_0_0_beta_456", "answer_text": "Automatic PII/secret sanitization in logs for GitHub, GitLab, AWS tokens and URL passwords"}]}
{"prototype_id": "coollabsio__coolify_release_window", "repo": "coollabsio/coolify", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the coollabsio/coolify release window, order the following release-content states from earliest to latest: (1) a release that adds Docker build cache preservation toggles and fixes proxy startup failures due to bash syntax errors, (2) a release that adds a developer view for shared environment variables and custom docker entrypoint support, (3) a release that adds Garage (S3-compatible distributed storage) and RustFS (S3-compatible storage) as new services, (4) a release that adds Hetzner server provisioning API endpoints and fixes concurrent builds being ignored.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "B", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "C", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "D", "text": "1 -> 2 -> 3 -> 4"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3 -> 4", "source_chunk_ids": ["coollabsio__coolify__release__v4_0_0_beta_449", "coollabsio__coolify__release__v4_0_0_beta_450", "coollabsio__coolify__release__v4_0_0_beta_453", "coollabsio__coolify__release__v4_0_0_beta_454"], "answer_support": [{"memory_node_id": "coollabsio__coolify__release__v4_0_0_beta_449", "answer_text": "New features include a developer view for shared environment variables and custom docker entrypoint support."}, {"memory_node_id": "coollabsio__coolify__release__v4_0_0_beta_450", "answer_text": "Added Docker build cache preservation toggles ... Fixed proxy startup failures due to bash syntax errors"}, {"memory_node_id": "coollabsio__coolify__release__v4_0_0_beta_453", "answer_text": "Added Garage (S3-compatible distributed storage) ... Added RustFS (S3-compatible storage)"}, {"memory_node_id": "coollabsio__coolify__release__v4_0_0_beta_454", "answer_text": "Add Hetzner server provisioning API endpoints ... Fix concurrent builds being ignored"}]}
{"prototype_id": "dani_garcia__vaultwarden_release_window", "repo": "dani-garcia/vaultwarden", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the dani-garcia/vaultwarden releases, which release adds a CLI option to backup the SQLite database?", "options": [{"option_id": "A", "text": "1.32.0"}, {"option_id": "B", "text": "1.32.1"}, {"option_id": "C", "text": "1.33.0"}, {"option_id": "D", "text": "1.34.0"}], "correct_option_id": "B", "expected_answer": "1.32.1", "source_chunk_ids": ["dani_garcia__vaultwarden__release__1_32_1"], "answer_support": [{"memory_node_id": "dani_garcia__vaultwarden__release__1_32_1", "answer_text": "Added CLI option to backup SQLite database"}]}
{"prototype_id": "dani_garcia__vaultwarden_release_window", "repo": "dani-garcia/vaultwarden", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the dani-garcia/vaultwarden releases, how does the web-vault update in release 1.31.0 differ from the web-vault update in release 1.32.0?", "options": [{"option_id": "A", "text": "1.31.0 updates to v2024.5.1, while 1.32.0 updates to v2024.6.2."}, {"option_id": "B", "text": "1.31.0 updates to v2024.6.2, while 1.32.0 updates to v2025.1.1."}, {"option_id": "C", "text": "Both releases update to the same web-vault version."}, {"option_id": "D", "text": "1.31.0 does not update the web-vault, while 1.32.0 updates to v2024.6.2."}], "correct_option_id": "A", "expected_answer": "1.31.0 updates to v2024.5.1, while 1.32.0 updates to v2024.6.2.", "source_chunk_ids": ["dani_garcia__vaultwarden__release__1_31_0", "dani_garcia__vaultwarden__release__1_32_0"], "answer_support": [{"memory_node_id": "dani_garcia__vaultwarden__release__1_31_0", "answer_text": "updated included web vault to 2024.5.1"}, {"memory_node_id": "dani_garcia__vaultwarden__release__1_32_0", "answer_text": "Updated web-vault to v2024.6.2"}]}
{"prototype_id": "dani_garcia__vaultwarden_release_window", "repo": "dani-garcia/vaultwarden", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the dani-garcia/vaultwarden release window, order the following release-content states from earliest to latest: (1) a release that adds SSH-Key storage support, (2) a release that implements SSO support with OpenID Connect, (3) a release that adds a CLI option to backup SQLite database, (4) a release that adds initial support for beta releases of new native mobile apps.", "options": [{"option_id": "A", "text": "4 -> 3 -> 1 -> 2"}, {"option_id": "B", "text": "3 -> 4 -> 1 -> 2"}, {"option_id": "C", "text": "4 -> 1 -> 3 -> 2"}, {"option_id": "D", "text": "1 -> 4 -> 3 -> 2"}], "correct_option_id": "A", "expected_answer": "4 -> 3 -> 1 -> 2", "source_chunk_ids": ["dani_garcia__vaultwarden__release__1_31_0", "dani_garcia__vaultwarden__release__1_32_1", "dani_garcia__vaultwarden__release__1_32_5", "dani_garcia__vaultwarden__release__1_35_0"], "answer_support": [{"memory_node_id": "dani_garcia__vaultwarden__release__1_31_0", "answer_text": "Initial support for the beta releases of the new native mobile apps"}, {"memory_node_id": "dani_garcia__vaultwarden__release__1_32_1", "answer_text": "Added CLI option to backup SQLite database"}, {"memory_node_id": "dani_garcia__vaultwarden__release__1_32_5", "answer_text": "Added SSH-Key storage support"}, {"memory_node_id": "dani_garcia__vaultwarden__release__1_35_0", "answer_text": "Implemented support for SSO with OpenID Connect"}]}
{"prototype_id": "danielmiessler__Fabric_release_window", "repo": "danielmiessler/Fabric", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the danielmiessler/Fabric releases, which release adds a Polish (pl) locale with a complete translation file containing all 683 keys?", "options": [{"option_id": "A", "text": "v1.4.425"}, {"option_id": "B", "text": "v1.4.428"}, {"option_id": "C", "text": "v1.4.430"}, {"option_id": "D", "text": "v1.4.440"}], "correct_option_id": "B", "expected_answer": "v1.4.428", "source_chunk_ids": ["danielmiessler__Fabric__release__v1_4_428"], "answer_support": [{"memory_node_id": "danielmiessler__Fabric__release__v1_4_428", "answer_text": "Add Polish (pl) locale with a complete translation file containing all 683 keys"}]}
{"prototype_id": "danielmiessler__Fabric_release_window", "repo": "danielmiessler/Fabric", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the danielmiessler/Fabric releases, how does the MiniMax model change in v1.4.439 differ from the MiniMax model change in v1.4.436?", "options": [{"option_id": "A", "text": "v1.4.436 adds MiniMax-M2.5-highspeed, while v1.4.439 upgrades the default model to M2.7 and adds M2.7 variants."}, {"option_id": "B", "text": "v1.4.436 removes all MiniMax models, while v1.4.439 restores them."}, {"option_id": "C", "text": "Both releases only update the MiniMax API endpoint without model changes."}, {"option_id": "D", "text": "v1.4.436 upgrades the default model to M2.7, while v1.4.439 adds M2.5-highspeed."}], "correct_option_id": "A", "expected_answer": "v1.4.436 adds MiniMax-M2.5-highspeed, while v1.4.439 upgrades the default model to M2.7 and adds M2.7 variants.", "source_chunk_ids": ["danielmiessler__Fabric__release__v1_4_436", "danielmiessler__Fabric__release__v1_4_439"], "answer_support": [{"memory_node_id": "danielmiessler__Fabric__release__v1_4_436", "answer_text": "Added the MiniMax-M2.5-highspeed model variant"}, {"memory_node_id": "danielmiessler__Fabric__release__v1_4_439", "answer_text": "Upgraded the MiniMax default model to M2.7 ... Added MiniMax-M2.7 and MiniMax-M2.7-highspeed"}]}
{"prototype_id": "danielmiessler__Fabric_release_window", "repo": "danielmiessler/Fabric", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the danielmiessler/Fabric release window, order the following release-content states from earliest to latest: (1) a release that adds a Git CLI fallback to FetchFilesFromRepo, (2) a release that implements visual text extraction from YouTube videos via FFmpeg and OCR, (3) a release that adds GrokAI search grounding via xAI's Responses API, (4) a release that adds Claude Opus 4.8 model support.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["danielmiessler__Fabric__release__v1_4_427", "danielmiessler__Fabric__release__v1_4_443", "danielmiessler__Fabric__release__v1_4_450", "danielmiessler__Fabric__release__v1_4_453"], "answer_support": [{"memory_node_id": "danielmiessler__Fabric__release__v1_4_427", "answer_text": "Add Git CLI Fallback to FetchFilesFromRepo"}, {"memory_node_id": "danielmiessler__Fabric__release__v1_4_443", "answer_text": "Implement visual text extraction via FFmpeg and OCR"}, {"memory_node_id": "danielmiessler__Fabric__release__v1_4_450", "answer_text": "Add GrokAI search grounding via xAI Responses API"}, {"memory_node_id": "danielmiessler__Fabric__release__v1_4_453", "answer_text": "Add Claude Opus 4.8 model"}]}
{"prototype_id": "danielmiessler__SecLists_release_window", "repo": "danielmiessler/SecLists", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the danielmiessler/SecLists releases, which release adds the '2024-200_most_used_passwords.txt' wordlist and removes the '.fuzz' suffix from many wordlists?", "options": [{"option_id": "A", "text": "2025.1"}, {"option_id": "B", "text": "2025.2"}, {"option_id": "C", "text": "2025.3"}, {"option_id": "D", "text": "2026.1"}], "correct_option_id": "A", "expected_answer": "2025.1", "source_chunk_ids": ["danielmiessler__SecLists__release__2025_1"], "answer_support": [{"memory_node_id": "danielmiessler__SecLists__release__2025_1", "answer_text": "addition of the '2024-200_most_used_passwords.txt' wordlist ... removal of the '.fuzz' suffix from many wordlists"}]}
{"prototype_id": "danielmiessler__SecLists_release_window", "repo": "danielmiessler/SecLists", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the danielmiessler/SecLists releases, how does the content focus of release 2025.2 differ from that of release 2025.3?", "options": [{"option_id": "A", "text": "2025.2 adds two 10 Million+ subdomain wordlists and new wordlist tools, while 2025.3 deprecates DirBuster wordlists and warns about dangerous SQLi payloads."}, {"option_id": "B", "text": "2025.2 removes the '.fuzz' suffix, while 2025.3 adds the '2024-200_most_used_passwords.txt' wordlist."}, {"option_id": "C", "text": "Both releases focus primarily on adding documentation for existing wordlists without any new wordlist additions."}, {"option_id": "D", "text": "2025.2 introduces AI ethical testing wordlists, while 2025.3 adds Kubernetes and Docker wordlists."}], "correct_option_id": "A", "expected_answer": "2025.2 adds two 10 Million+ subdomain wordlists and new wordlist tools, while 2025.3 deprecates DirBuster wordlists and warns about dangerous SQLi payloads.", "source_chunk_ids": ["danielmiessler__SecLists__release__2025_2", "danielmiessler__SecLists__release__2025_3"], "answer_support": [{"memory_node_id": "danielmiessler__SecLists__release__2025_2", "answer_text": "two 10 Million+ subdomain fuzzing wordlists ... addition of two new wordlist tools (CeWL and WL)"}, {"memory_node_id": "danielmiessler__SecLists__release__2025_3", "answer_text": "deprecation of DirBuster wordlists ... warning about dangerous SQLi payloads"}]}
{"prototype_id": "danielmiessler__SecLists_release_window", "repo": "danielmiessler/SecLists", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the danielmiessler/SecLists release window, order the following release-content states from earliest to latest: (1) a release that adds the '2024-200_most_used_passwords.txt' wordlist and removes the '.fuzz' suffix, (2) a release that deprecates DirBuster wordlists and warns about dangerous SQLi payloads, (3) a release that adds AI ethical and safety boundary testing wordlists and wordlists for Kubernetes and Docker.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["danielmiessler__SecLists__release__2025_1", "danielmiessler__SecLists__release__2025_3", "danielmiessler__SecLists__release__2026_1"], "answer_support": [{"memory_node_id": "danielmiessler__SecLists__release__2025_1", "answer_text": "addition of the '2024-200_most_used_passwords.txt' wordlist ... removal of the '.fuzz' suffix"}, {"memory_node_id": "danielmiessler__SecLists__release__2025_3", "answer_text": "deprecation of DirBuster wordlists ... warning about dangerous SQLi payloads"}, {"memory_node_id": "danielmiessler__SecLists__release__2026_1", "answer_text": "AI ethical and safety boundary testing wordlists ... wordlists for Kubernetes, Docker"}]}
{"prototype_id": "daytonaio__daytona_release_window", "repo": "daytonaio/daytona", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the daytonaio/daytona releases, which release introduces a Java SDK implementation?", "options": [{"option_id": "A", "text": "v0.161.0"}, {"option_id": "B", "text": "v0.162.0"}, {"option_id": "C", "text": "v0.163.0"}, {"option_id": "D", "text": "v0.164.0"}], "correct_option_id": "A", "expected_answer": "v0.161.0", "source_chunk_ids": ["daytonaio__daytona__release__v0_161_0"], "answer_support": [{"memory_node_id": "daytonaio__daytona__release__v0_161_0", "answer_text": "a Java SDK is implemented"}]}
{"prototype_id": "daytonaio__daytona_release_window", "repo": "daytonaio/daytona", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the daytonaio/daytona releases, how does the GPU-related change in v0.174.0 differ from the GPU-related change in v0.181.0?", "options": [{"option_id": "A", "text": "v0.174.0 introduces an NVIDIA GPU-enabled runner, while v0.181.0 assigns one physical GPU per sandbox on multi-GPU runners."}, {"option_id": "B", "text": "v0.174.0 adds GPU snapshots, while v0.181.0 removes GPU support."}, {"option_id": "C", "text": "Both releases only update GPU documentation without functional changes."}, {"option_id": "D", "text": "v0.174.0 adds GPU region quota, while v0.181.0 adds GPU capacity count exclusion."}], "correct_option_id": "A", "expected_answer": "v0.174.0 introduces an NVIDIA GPU-enabled runner, while v0.181.0 assigns one physical GPU per sandbox on multi-GPU runners.", "source_chunk_ids": ["daytonaio__daytona__release__v0_174_0", "daytonaio__daytona__release__v0_181_0"], "answer_support": [{"memory_node_id": "daytonaio__daytona__release__v0_174_0", "answer_text": "the API and runner add NVIDIA GPU-enabled runner"}, {"memory_node_id": "daytonaio__daytona__release__v0_181_0", "answer_text": "the API and runner assign one physical GPU per sandbox on multi-GPU runner"}]}
{"prototype_id": "daytonaio__daytona_release_window", "repo": "daytonaio/daytona", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the daytonaio/daytona release window, order the following release-content states from earliest to latest: (1) a release that adds a Java SDK implementation, (2) a release that introduces sandbox classes and linked sandboxes, (3) a release that adds an NVIDIA GPU-enabled runner, (4) a release that moves sandbox list to cursor pagination.", "options": [{"option_id": "A", "text": "1 -> 3 -> 4 -> 2"}, {"option_id": "B", "text": "1 -> 4 -> 3 -> 2"}, {"option_id": "C", "text": "3 -> 1 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 2 -> 1 -> 3"}], "correct_option_id": "A", "expected_answer": "1 -> 3 -> 4 -> 2", "source_chunk_ids": ["daytonaio__daytona__release__v0_161_0", "daytonaio__daytona__release__v0_174_0", "daytonaio__daytona__release__v0_180_0", "daytonaio__daytona__release__v0_183_0"], "answer_support": [{"memory_node_id": "daytonaio__daytona__release__v0_161_0", "answer_text": "a Java SDK is implemented"}, {"memory_node_id": "daytonaio__daytona__release__v0_174_0", "answer_text": "the API and runner add NVIDIA GPU-enabled runner"}, {"memory_node_id": "daytonaio__daytona__release__v0_180_0", "answer_text": "sandbox list moves to cursor pagination"}, {"memory_node_id": "daytonaio__daytona__release__v0_183_0", "answer_text": "sandbox classes and linked sandboxes are introduced"}]}
{"prototype_id": "dbeaver__dbeaver_release_window", "repo": "dbeaver/dbeaver", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the dbeaver/dbeaver releases, which release adds support for Common Table Expressions (CTE) by semantic analysis and autocompletion in the SQL Editor?", "options": [{"option_id": "A", "text": "25.0.4"}, {"option_id": "B", "text": "25.0.5"}, {"option_id": "C", "text": "25.1.0"}, {"option_id": "D", "text": "25.1.1"}], "correct_option_id": "A", "expected_answer": "25.0.4", "source_chunk_ids": ["dbeaver__dbeaver__release__25_0_4"], "answer_support": [{"memory_node_id": "dbeaver__dbeaver__release__25_0_4", "answer_text": "SQL Editor: Added support for Common Table Expressions (CTE) by semantic analysis and autocompletion"}]}
{"prototype_id": "dbeaver__dbeaver_release_window", "repo": "dbeaver/dbeaver", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the dbeaver/dbeaver releases, how does the AI assistant change described in release 25.1.3 differ from the AI assistant change described in release 25.2.0?", "options": [{"option_id": "A", "text": "25.1.3 includes AI integration in the Community packaging without needing an extension, while 25.2.0 adds query preview to the @ai command and AI chat query confirmation."}, {"option_id": "B", "text": "25.1.3 removes AI integration entirely, while 25.2.0 reintroduces it with custom OpenAI API base URL support."}, {"option_id": "C", "text": "Both releases only update the GitHub Copilot authorization dialog."}, {"option_id": "D", "text": "25.1.3 adds support for custom OpenAI API base URL, while 25.2.0 includes AI integration in the Community packaging."}], "correct_option_id": "A", "expected_answer": "25.1.3 includes AI integration in the Community packaging without needing an extension, while 25.2.0 adds query preview to the @ai command and AI chat query confirmation.", "source_chunk_ids": ["dbeaver__dbeaver__release__25_1_3", "dbeaver__dbeaver__release__25_2_0"], "answer_support": [{"memory_node_id": "dbeaver__dbeaver__release__25_1_3", "answer_text": "AI integration is now included in the Community packaging, extension install is not needed anymore"}, {"memory_node_id": "dbeaver__dbeaver__release__25_2_0", "answer_text": "AI Assistant: Added query preview to the @ai command and AI chat query confirmation"}]}
{"prototype_id": "dbeaver__dbeaver_release_window", "repo": "dbeaver/dbeaver", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the dbeaver/dbeaver release window, order the following release-content states from earliest to latest: (1) a release that adds support for Common Table Expressions (CTE) by semantic analysis and autocompletion, (2) a release that significantly improves CTE completion and navigation support, (3) a release that adds support for column expansion for CTEs.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["dbeaver__dbeaver__release__25_0_4", "dbeaver__dbeaver__release__25_0_5", "dbeaver__dbeaver__release__25_1_1"], "answer_support": [{"memory_node_id": "dbeaver__dbeaver__release__25_0_4", "answer_text": "SQL Editor: Added support for Common Table Expressions (CTE) by semantic analysis and autocompletion"}, {"memory_node_id": "dbeaver__dbeaver__release__25_0_5", "answer_text": "CTE completion and navigation support was significantly improved"}, {"memory_node_id": "dbeaver__dbeaver__release__25_1_1", "answer_text": "Added support for column expansion for CTEs"}]}
{"prototype_id": "denoland__deno_release_window", "repo": "denoland/deno", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the denoland/deno releases, which release adds the `deno create` command and stabilizes the Temporal API?", "options": [{"option_id": "A", "text": "v2.6.0"}, {"option_id": "B", "text": "v2.7.0"}, {"option_id": "C", "text": "v2.8.0"}, {"option_id": "D", "text": "v2.7.2"}], "correct_option_id": "B", "expected_answer": "v2.7.0", "source_chunk_ids": ["denoland__deno__release__v2_7_0"], "answer_support": [{"memory_node_id": "denoland__deno__release__v2_7_0", "answer_text": "adds deno create command ... stabilizes Temporal API"}]}
{"prototype_id": "denoland__deno_release_window", "repo": "denoland/deno", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the denoland/deno releases, how does the HTTP-related change described in v2.7.13 differ from the HTTP-related change described in v2.8.0?", "options": [{"option_id": "A", "text": "v2.7.13 rewrites node:http with llhttp and native TCPWrap, while v2.8.0 emits Network.* inspector events for node:http."}, {"option_id": "B", "text": "v2.7.13 removes HTTP/2 support, while v2.8.0 adds HTTP/3."}, {"option_id": "C", "text": "Both releases only update HTTP parser error messages without functional changes."}, {"option_id": "D", "text": "v2.7.13 adds brotli compression to HTTP, while v2.8.0 removes keep-alive support."}], "correct_option_id": "A", "expected_answer": "v2.7.13 rewrites node:http with llhttp and native TCPWrap, while v2.8.0 emits Network.* inspector events for node:http.", "source_chunk_ids": ["denoland__deno__release__v2_7_13", "denoland__deno__release__v2_8_0"], "answer_support": [{"memory_node_id": "denoland__deno__release__v2_7_13", "answer_text": "rewrites node:http with llhttp and native TCPWrap"}, {"memory_node_id": "denoland__deno__release__v2_8_0", "answer_text": "emits Network.* inspector events for node:http"}]}
{"prototype_id": "derailed__k9s_release_window", "repo": "derailed/k9s", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the derailed/k9s releases, which release introduces full custom columns support allowing users to add columns for labels, annotations, or other resource fields in views.yaml?", "options": [{"option_id": "A", "text": "v0.40.1"}, {"option_id": "B", "text": "v0.40.0"}, {"option_id": "C", "text": "v0.50.0"}, {"option_id": "D", "text": "v0.40.6"}], "correct_option_id": "B", "expected_answer": "v0.40.0", "source_chunk_ids": ["derailed__k9s__release__v0_40_0"], "answer_support": [{"memory_node_id": "derailed__k9s__release__v0_40_0", "answer_text": "introduces full custom columns support. Users can now customize views for a given resource by adding definitions in views.yaml, including the ability to add columns for labels, annotations, or other resource fields."}]}
{"prototype_id": "derailed__k9s_release_window", "repo": "derailed/k9s", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the derailed/k9s releases, how does the custom view enhancement in v0.40.6 differ from the custom view feature introduced in v0.40.0?", "options": [{"option_id": "A", "text": "v0.40.0 introduces basic custom columns, while v0.40.6 adds namespace-specific column definitions and a 'Show' attribute to override wide mode."}, {"option_id": "B", "text": "v0.40.0 adds JQ query support, while v0.40.6 removes custom columns entirely."}, {"option_id": "C", "text": "Both releases only fix bugs related to custom views without adding new features."}, {"option_id": "D", "text": "v0.40.0 introduces namespace-specific views, while v0.40.6 adds basic custom columns."}], "correct_option_id": "A", "expected_answer": "v0.40.0 introduces basic custom columns, while v0.40.6 adds namespace-specific column definitions and a 'Show' attribute to override wide mode.", "source_chunk_ids": ["derailed__k9s__release__v0_40_0", "derailed__k9s__release__v0_40_6"], "answer_support": [{"memory_node_id": "derailed__k9s__release__v0_40_0", "answer_text": "introduces full custom columns support. Users can now customize views for a given resource by adding definitions in views.yaml, including the ability to add columns for labels, annotations, or other resource fields."}, {"memory_node_id": "derailed__k9s__release__v0_40_6", "answer_text": "adds namespace-specific column definitions for custom views, allowing different column configurations per namespace (e.g., v1/pods@fred). A new column attribute 'Show' (S) overrides the default wide attribute."}]}
{"prototype_id": "derailed__k9s_release_window", "repo": "derailed/k9s", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the derailed/k9s release window, order the following release-content states from earliest to latest: (1) a release that introduces namespace-specific column definitions and a 'Show' attribute, (2) a release that introduces full custom columns support, (3) a release that introduces 'Super Column Blow' with JQ query support in custom views.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3"}, {"option_id": "B", "text": "1 -> 2 -> 3"}, {"option_id": "C", "text": "3 -> 1 -> 2"}, {"option_id": "D", "text": "2 -> 3 -> 1"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3", "source_chunk_ids": ["derailed__k9s__release__v0_40_0", "derailed__k9s__release__v0_40_6", "derailed__k9s__release__v0_50_0"], "answer_support": [{"memory_node_id": "derailed__k9s__release__v0_40_0", "answer_text": "introduces full custom columns support."}, {"memory_node_id": "derailed__k9s__release__v0_40_6", "answer_text": "adds namespace-specific column definitions and a 'Show' attribute."}, {"memory_node_id": "derailed__k9s__release__v0_50_0", "answer_text": "introduces 'Super Column Blow', allowing JQ queries in custom views."}]}
{"prototype_id": "dgtlmoon__changedetection_io_release_window", "repo": "dgtlmoon/changedetection.io", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the dgtlmoon/changedetection.io releases, which release introduces AI/LLM rulesets for change detection and text summary using LiteLLM?", "options": [{"option_id": "A", "text": "0.54.9"}, {"option_id": "B", "text": "0.55.1"}, {"option_id": "C", "text": "0.55.4"}, {"option_id": "D", "text": "0.55.6"}], "correct_option_id": "B", "expected_answer": "0.55.1", "source_chunk_ids": ["dgtlmoon__changedetection_io__release__0_55_1"], "answer_support": [{"memory_node_id": "dgtlmoon__changedetection_io__release__0_55_1", "answer_text": "introduces AI/LLM rulesets for change detection and text summary using LiteLLM"}]}
{"prototype_id": "dgtlmoon__changedetection_io_release_window", "repo": "dgtlmoon/changedetection.io", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the dgtlmoon/changedetection.io releases, how does the datastore change in release 0.53.1 differ from the security fix in release 0.54.1?", "options": [{"option_id": "A", "text": "0.53.1 splits watch data into separate JSON files, while 0.54.1 addresses SSRF and Reflected XSS vulnerabilities."}, {"option_id": "B", "text": "0.53.1 adds AI/LLM rulesets, while 0.54.1 fixes a memory leak."}, {"option_id": "C", "text": "Both releases only update translations."}, {"option_id": "D", "text": "0.53.1 removes the queuing system, while 0.54.1 introduces a new UI theme."}], "correct_option_id": "A", "expected_answer": "0.53.1 splits watch data into separate JSON files, while 0.54.1 addresses SSRF and Reflected XSS vulnerabilities.", "source_chunk_ids": ["dgtlmoon__changedetection_io__release__0_53_1", "dgtlmoon__changedetection_io__release__0_54_1"], "answer_support": [{"memory_node_id": "dgtlmoon__changedetection_io__release__0_53_1", "answer_text": "splits the info into uuid/watch.json and uuid/tag.json"}, {"memory_node_id": "dgtlmoon__changedetection_io__release__0_54_1", "answer_text": "CVE-2026-27696 - Server-Side Request Forgery (SSRF) via Watch URLs ... CVE-2026-27645 - Reflected XSS in RSS Single Watch request"}]}
{"prototype_id": "dgtlmoon__changedetection_io_release_window", "repo": "dgtlmoon/changedetection.io", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the dgtlmoon/changedetection.io release window, order the following release-content states from earliest to latest: (1) a release that fixes Traditional Chinese locale mapping, (2) a release that introduces AI/LLM rulesets for change detection, (3) a release that addresses CVE-2026-27696 (SSRF via Watch URLs), (4) a release that adds a master on/off switch for LLM.", "options": [{"option_id": "A", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "3 -> 1 -> 2 -> 4"}, {"option_id": "D", "text": "1 -> 2 -> 3 -> 4"}], "correct_option_id": "A", "expected_answer": "1 -> 3 -> 2 -> 4", "source_chunk_ids": ["dgtlmoon__changedetection_io__release__0_52_4", "dgtlmoon__changedetection_io__release__0_54_1", "dgtlmoon__changedetection_io__release__0_55_1", "dgtlmoon__changedetection_io__release__0_55_5"], "answer_support": [{"memory_node_id": "dgtlmoon__changedetection_io__release__0_52_4", "answer_text": "Fixing Traditional Chinese locale mapping"}, {"memory_node_id": "dgtlmoon__changedetection_io__release__0_54_1", "answer_text": "CVE-2026-27696 - Server-Side Request Forgery (SSRF) via Watch URLs"}, {"memory_node_id": "dgtlmoon__changedetection_io__release__0_55_1", "answer_text": "AI / LLM rulesets - Set your AI change detection rules and text summary rules"}, {"memory_node_id": "dgtlmoon__changedetection_io__release__0_55_5", "answer_text": "LLM - Master on/off switch (enable/disable)"}]}
{"prototype_id": "directus__directus_release_window", "repo": "directus/directus", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the directus/directus releases, which release introduces a Content Comparison Modal for side-by-side review of version and revision changes?", "options": [{"option_id": "A", "text": "v11.12.0"}, {"option_id": "B", "text": "v11.13.0"}, {"option_id": "C", "text": "v11.14.0"}, {"option_id": "D", "text": "v11.15.0"}], "correct_option_id": "B", "expected_answer": "v11.13.0", "source_chunk_ids": ["directus__directus__release__v11_13_0"], "answer_support": [{"memory_node_id": "directus__directus__release__v11_13_0", "answer_text": "Introduced the Content Comparison Modal for side-by-side review of version and revision changes."}]}
{"prototype_id": "directus__directus_release_window", "repo": "directus/directus", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the directus/directus releases, how does the AI-related change in v11.14.0 differ from the AI-related change in v11.15.0?", "options": [{"option_id": "A", "text": "v11.14.0 adds an AI chat sidebar, while v11.15.0 adds multi-provider AI support with Google and OpenAI-compatible providers and a new @directus/ai package."}, {"option_id": "B", "text": "v11.14.0 adds multi-provider AI support, while v11.15.0 adds an AI chat sidebar."}, {"option_id": "C", "text": "Both releases only update AI SDK dependencies without new features."}, {"option_id": "D", "text": "v11.14.0 removes AI features, while v11.15.0 reintroduces them."}], "correct_option_id": "A", "expected_answer": "v11.14.0 adds an AI chat sidebar, while v11.15.0 adds multi-provider AI support with Google and OpenAI-compatible providers and a new @directus/ai package.", "source_chunk_ids": ["directus__directus__release__v11_14_0", "directus__directus__release__v11_15_0"], "answer_support": [{"memory_node_id": "directus__directus__release__v11_14_0", "answer_text": "Added AI chat sidebar"}, {"memory_node_id": "directus__directus__release__v11_15_0", "answer_text": "Added multi-provider AI support with Google and OpenAI-compatible providers. Extracted shared AI types into new @directus/ai package."}]}
{"prototype_id": "directus__directus_release_window", "repo": "directus/directus", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the directus/directus release window, order the following release-content states from earliest to latest: (1) a release that adds support for LDAP login and updates refresh/logout command parameters, (2) a release that introduces a global draft version automatically available for all items when versioning is enabled, (3) a release that adds a deployment module for triggering deployments with Vercel as the first supported provider, (4) a release that adds an AI chat sidebar.", "options": [{"option_id": "A", "text": "1 -> 4 -> 3 -> 2"}, {"option_id": "B", "text": "4 -> 1 -> 2 -> 3"}, {"option_id": "C", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "D", "text": "2 -> 1 -> 3 -> 4"}], "correct_option_id": "A", "expected_answer": "1 -> 4 -> 3 -> 2", "source_chunk_ids": ["directus__directus__release__v11_9_0", "directus__directus__release__v11_14_0", "directus__directus__release__v11_15_0", "directus__directus__release__v11_16_0"], "answer_support": [{"memory_node_id": "directus__directus__release__v11_9_0", "answer_text": "Added support for LDAP login and enhanced parameter consistency for refresh/logout commands."}, {"memory_node_id": "directus__directus__release__v11_14_0", "answer_text": "Added AI chat sidebar"}, {"memory_node_id": "directus__directus__release__v11_15_0", "answer_text": "Added deployment module for triggering deployments from Directus with Vercel as first supported provider"}, {"memory_node_id": "directus__directus__release__v11_16_0", "answer_text": "Added support for a global draft version that is automatically available for all items when versioning is enabled"}]}
{"prototype_id": "dokku__dokku_release_window", "repo": "dokku/dokku", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the dokku/dokku releases, which release introduces the ability to disable letsencrypt for a given application or globally?", "options": [{"option_id": "A", "text": "v0.36.9"}, {"option_id": "B", "text": "v0.36.10"}, {"option_id": "C", "text": "v0.37.0"}, {"option_id": "D", "text": "v0.36.11"}], "correct_option_id": "A", "expected_answer": "v0.36.9", "source_chunk_ids": ["dokku__dokku__release__v0_36_9"], "answer_support": [{"memory_node_id": "dokku__dokku__release__v0_36_9", "answer_text": "Add ability to disable letsencrypt for a given application or globally"}]}
{"prototype_id": "dokku__dokku_release_window", "repo": "dokku/dokku", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the dokku/dokku releases, how does the storage-related change in v0.37.5 differ from the storage-related change in v0.38.13?", "options": [{"option_id": "A", "text": "v0.37.5 rewrites the storage plugin in golang, while v0.38.13 adds --volume-options flag to storage:mount."}, {"option_id": "B", "text": "v0.37.5 adds storage:destroy confirmation, while v0.38.13 rewrites the storage plugin in golang."}, {"option_id": "C", "text": "Both releases only update storage-related dependencies."}, {"option_id": "D", "text": "v0.37.5 removes storage plugin, while v0.38.13 reintroduces it."}], "correct_option_id": "A", "expected_answer": "v0.37.5 rewrites the storage plugin in golang, while v0.38.13 adds --volume-options flag to storage:mount.", "source_chunk_ids": ["dokku__dokku__release__v0_37_5", "dokku__dokku__release__v0_38_13"], "answer_support": [{"memory_node_id": "dokku__dokku__release__v0_37_5", "answer_text": "Rewrite the storage plugin in golang"}, {"memory_node_id": "dokku__dokku__release__v0_38_13", "answer_text": "Add --volume-options flag to storage:mount"}]}
{"prototype_id": "dokku__dokku_release_window", "repo": "dokku/dokku", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the dokku/dokku release window, order the following release-content states from earliest to latest: (1) a release that adds the ability to disable letsencrypt for a given application or globally, (2) a release that introduces backwards compatibility breaks including renaming scheduler-k3s:cluster-* commands, (3) a release that adds docker healthcheck to dokku container, (4) a release that adds scheduler-k3s annotations:report and labels:report.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["dokku__dokku__release__v0_36_9", "dokku__dokku__release__v0_37_0", "dokku__dokku__release__v0_38_3", "dokku__dokku__release__v0_38_14"], "answer_support": [{"memory_node_id": "dokku__dokku__release__v0_36_9", "answer_text": "Add ability to disable letsencrypt for a given application or globally"}, {"memory_node_id": "dokku__dokku__release__v0_37_0", "answer_text": "Rename the scheduler-k3s:cluster-* commands to use a : instead of - for a delimiter"}, {"memory_node_id": "dokku__dokku__release__v0_38_3", "answer_text": "Add docker healthcheck to dokku container"}, {"memory_node_id": "dokku__dokku__release__v0_38_14", "answer_text": "Add scheduler-k3s annotations:report and labels:report"}]}
{"prototype_id": "Dokploy__dokploy_release_window", "repo": "Dokploy/dokploy", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the Dokploy/dokploy releases, which release introduces custom build servers and multi-administrator management?", "options": [{"option_id": "A", "text": "v0.25.11"}, {"option_id": "B", "text": "v0.26.0"}, {"option_id": "C", "text": "v0.26.1"}, {"option_id": "D", "text": "v0.27.0"}], "correct_option_id": "B", "expected_answer": "v0.26.0", "source_chunk_ids": ["Dokploy__dokploy__release__v0_26_0"], "answer_support": [{"memory_node_id": "Dokploy__dokploy__release__v0_26_0", "answer_text": "introduces custom build servers, multi-administrator management"}]}
{"prototype_id": "Dokploy__dokploy_release_window", "repo": "Dokploy/dokploy", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the Dokploy/dokploy releases, how does the rollback mechanism change from v0.26.0 to v0.28.4?", "options": [{"option_id": "A", "text": "v0.26.0 introduces registry-based rollbacks, while v0.28.4 adds docker login before rollback and fixes execAsyncRemote argument order."}, {"option_id": "B", "text": "v0.26.0 removes rollbacks entirely, and v0.28.4 restores them with local storage."}, {"option_id": "C", "text": "Both releases only update Helm chart images without rollback changes."}, {"option_id": "D", "text": "v0.26.0 deprecates rollbacks, and v0.28.4 introduces a new rollback UI."}], "correct_option_id": "A", "expected_answer": "v0.26.0 introduces registry-based rollbacks, while v0.28.4 adds docker login before rollback and fixes execAsyncRemote argument order.", "source_chunk_ids": ["Dokploy__dokploy__release__v0_26_0", "Dokploy__dokploy__release__v0_28_4"], "answer_support": [{"memory_node_id": "Dokploy__dokploy__release__v0_26_0", "answer_text": "reworked rollback mechanism using registry-based rollbacks"}, {"memory_node_id": "Dokploy__dokploy__release__v0_28_4", "answer_text": "adds docker login before rollback and fix execAsyncRemote argument order"}]}
{"prototype_id": "Dokploy__dokploy_release_window", "repo": "Dokploy/dokploy", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the Dokploy/dokploy release window, order the following release-content states from earliest to latest: (1) a release that adds Pushover notification provider and bumps default Postgres version to 18, (2) a release that introduces AI log and build error analysis, (3) a release that adds a dashboard home page and fixes preview deployments broken on v0.29.0, (4) a release that adds self-hosted enterprise restrictions (remote-servers-only, enforce-sso).", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["Dokploy__dokploy__release__v0_26_7", "Dokploy__dokploy__release__v0_29_0", "Dokploy__dokploy__release__v0_29_1", "Dokploy__dokploy__release__v0_29_6"], "answer_support": [{"memory_node_id": "Dokploy__dokploy__release__v0_26_7", "answer_text": "adds Pushover notification provider, bumps default Postgres version to 18"}, {"memory_node_id": "Dokploy__dokploy__release__v0_29_0", "answer_text": "introduces AI log and build error analysis"}, {"memory_node_id": "Dokploy__dokploy__release__v0_29_1", "answer_text": "adds a dashboard home page, fixes preview deployments broken on v0.29.0"}, {"memory_node_id": "Dokploy__dokploy__release__v0_29_6", "answer_text": "adds self-hosted enterprise restrictions (remote-servers-only, enforce-sso)"}]}
{"prototype_id": "duckdb__duckdb_release_window", "repo": "duckdb/duckdb", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the duckdb/duckdb releases, which release introduces the FILL window function?", "options": [{"option_id": "A", "text": "DuckDB 1.3.0 \"Ossivalis\""}, {"option_id": "B", "text": "DuckDB 1.4.0 \"Andium\""}, {"option_id": "C", "text": "DuckDB 1.2.0 \"Histrionicus\""}, {"option_id": "D", "text": "DuckDB 1.5.0 \"Variegata\""}], "correct_option_id": "B", "expected_answer": "DuckDB 1.4.0 \"Andium\"", "source_chunk_ids": ["duckdb__duckdb__release__v1_4_0"], "answer_support": [{"memory_node_id": "duckdb__duckdb__release__v1_4_0", "answer_text": "introduces a new sorting implementation, the FILL window function, and support for glibc 2.28 environments."}]}
{"prototype_id": "duckdb__duckdb_release_window", "repo": "duckdb/duckdb", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the duckdb/duckdb releases, how does the on-disk storage format change described in DuckDB 0.8.0 \"Fulvigula\" differ from the storage format change described in DuckDB 0.10.0 \"Fusca\"?", "options": [{"option_id": "A", "text": "0.8.0 introduces a backwards-incompatible storage format change, while 0.10.0 is backwards-compatible with the 0.9 releases."}, {"option_id": "B", "text": "0.8.0 is backwards-compatible with 0.7.0, while 0.10.0 introduces a backwards-incompatible change."}, {"option_id": "C", "text": "Both releases introduce backwards-incompatible storage format changes."}, {"option_id": "D", "text": "0.8.0 drops the 'Preview' designation, while 0.10.0 introduces a new storage format."}], "correct_option_id": "A", "expected_answer": "0.8.0 introduces a backwards-incompatible storage format change, while 0.10.0 is backwards-compatible with the 0.9 releases.", "source_chunk_ids": ["duckdb__duckdb__release__v0_8_0", "duckdb__duckdb__release__v0_10_0"], "answer_support": [{"memory_node_id": "duckdb__duckdb__release__v0_8_0", "answer_text": "introduces a backwards-incompatible on-disk storage format change"}, {"memory_node_id": "duckdb__duckdb__release__v0_10_0", "answer_text": "The on-disk storage format is backwards-compatible with the 0.9 releases"}]}
{"prototype_id": "duckdb__duckdb_release_window", "repo": "duckdb/duckdb", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the duckdb/duckdb release window, order the following release-content states from earliest to latest: (1) a release that introduces the FILL window function, (2) a release that introduces ALTER DATABASE RENAME TO, (3) a release that introduces ATTACH OR REPLACE database.", "options": [{"option_id": "A", "text": "3 -> 1 -> 2"}, {"option_id": "B", "text": "1 -> 2 -> 3"}, {"option_id": "C", "text": "2 -> 3 -> 1"}, {"option_id": "D", "text": "1 -> 3 -> 2"}], "correct_option_id": "A", "expected_answer": "3 -> 1 -> 2", "source_chunk_ids": ["duckdb__duckdb__release__v1_3_0", "duckdb__duckdb__release__v1_4_0", "duckdb__duckdb__release__v1_5_0"], "answer_support": [{"memory_node_id": "duckdb__duckdb__release__v1_3_0", "answer_text": "introduces features such as ATTACH OR REPLACE database"}, {"memory_node_id": "duckdb__duckdb__release__v1_4_0", "answer_text": "introduces a new sorting implementation, the FILL window function"}, {"memory_node_id": "duckdb__duckdb__release__v1_5_0", "answer_text": "introduces features such as ALTER DATABASE RENAME TO"}]}
{"prototype_id": "ethereum__go_ethereum_release_window", "repo": "ethereum/go-ethereum", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the ethereum/go-ethereum releases, which release introduces a new filtermaps index for log filtering and releases abigen v2?", "options": [{"option_id": "A", "text": "v1.15.6"}, {"option_id": "B", "text": "v1.16.0"}, {"option_id": "C", "text": "v1.15.11"}, {"option_id": "D", "text": "v1.16.2"}], "correct_option_id": "A", "expected_answer": "v1.15.6", "source_chunk_ids": ["ethereum__go_ethereum__release__v1_15_6"], "answer_support": [{"memory_node_id": "ethereum__go_ethereum__release__v1_15_6", "answer_text": "introduces a new filtermaps index for log filtering with huge performance improvements, releases abigen v2"}]}
{"prototype_id": "evanw__esbuild_release_window", "repo": "evanw/esbuild", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the evanw/esbuild releases, which release adds support for the new TypeScript 5.5 feature ${configDir} in tsconfig.json files?", "options": [{"option_id": "A", "text": "v0.21.4"}, {"option_id": "B", "text": "v0.21.5"}, {"option_id": "C", "text": "v0.22.0"}, {"option_id": "D", "text": "v0.23.0"}], "correct_option_id": "B", "expected_answer": "v0.21.5", "source_chunk_ids": ["evanw__esbuild__release__v0_21_5"], "answer_support": [{"memory_node_id": "evanw__esbuild__release__v0_21_5", "answer_text": "The new TypeScript 5.5 feature ${configDir} is supported in tsconfig.json baseUrl and paths."}]}
{"prototype_id": "evanw__esbuild_release_window", "repo": "evanw/esbuild", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the evanw/esbuild releases, how does the change to the default package bundling behavior for node in v0.22.0 differ from the change in v0.23.0?", "options": [{"option_id": "A", "text": "v0.22.0 makes --packages=external the default for node, while v0.23.0 reverts that change, restoring --packages=bundle as the default."}, {"option_id": "B", "text": "v0.22.0 drops support for older Windows versions, while v0.23.0 drops support for macOS Catalina."}, {"option_id": "C", "text": "v0.22.0 fixes a JSX whitespace bug, while v0.23.0 fixes a for await label bug."}, {"option_id": "D", "text": "v0.22.0 adds support for import attributes in glob imports, while v0.23.0 adds support for the node: import prefix."}], "correct_option_id": "A", "expected_answer": "v0.22.0 makes --packages=external the default for node, while v0.23.0 reverts that change, restoring --packages=bundle as the default.", "source_chunk_ids": ["evanw__esbuild__release__v0_22_0", "evanw__esbuild__release__v0_23_0"], "answer_support": [{"memory_node_id": "evanw__esbuild__release__v0_22_0", "answer_text": "a breaking change makes --packages=external the default for --platform=node"}, {"memory_node_id": "evanw__esbuild__release__v0_23_0", "answer_text": "the recent change making --packages=external the default for node is reverted, restoring --packages=bundle as the default"}]}
{"prototype_id": "evanw__esbuild_release_window", "repo": "evanw/esbuild", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the evanw/esbuild release window, order the following release-content states from earliest to latest: (1) a release that adds support for 'with { type: 'bytes' }' imports, (2) a release that adds support for 'with { type: 'text' }' imports, (3) a release that adds basic syntax support for JavaScript import phases 'defer' and 'source'.", "options": [{"option_id": "A", "text": "1 -> 3 -> 2"}, {"option_id": "B", "text": "3 -> 1 -> 2"}, {"option_id": "C", "text": "2 -> 1 -> 3"}, {"option_id": "D", "text": "1 -> 2 -> 3"}], "correct_option_id": "B", "expected_answer": "3 -> 1 -> 2", "source_chunk_ids": ["evanw__esbuild__release__v0_25_7", "evanw__esbuild__release__v0_25_11", "evanw__esbuild__release__v0_28_0"], "answer_support": [{"memory_node_id": "evanw__esbuild__release__v0_25_7", "answer_text": "basic syntax support for JavaScript import phases 'defer' and 'source' is added"}, {"memory_node_id": "evanw__esbuild__release__v0_25_11", "answer_text": "support for 'with { type: 'bytes' }' imports is added"}, {"memory_node_id": "evanw__esbuild__release__v0_28_0", "answer_text": "support for 'with { type: 'text' }' imports is added"}]}
{"prototype_id": "exelban__stats_release_window", "repo": "exelban/stats", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the exelban/stats releases, which release adds a gradient style to the line chart?", "options": [{"option_id": "A", "text": "v2.11.54"}, {"option_id": "B", "text": "v2.11.58"}, {"option_id": "C", "text": "v2.12.0"}, {"option_id": "D", "text": "v2.12.14"}], "correct_option_id": "B", "expected_answer": "v2.11.58", "source_chunk_ids": ["exelban__stats__release__v2_11_58"], "answer_support": [{"memory_node_id": "exelban__stats__release__v2_11_58", "answer_text": "added gradient style to the line chart"}]}
{"prototype_id": "exelban__stats_release_window", "repo": "exelban/stats", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the exelban/stats releases, how does the handling of macOS widget updates differ between v2.11.60 and v2.11.61?", "options": [{"option_id": "A", "text": "v2.11.60 unlocks widgets updates after chronod fix, while v2.11.61 reverts enabling widget updates due to ongoing chronod problems."}, {"option_id": "B", "text": "v2.11.60 disables widgets updates, while v2.11.61 enables them."}, {"option_id": "C", "text": "Both releases add new widget styles."}, {"option_id": "D", "text": "v2.11.60 adds widget previews, while v2.11.61 removes them."}], "correct_option_id": "A", "expected_answer": "v2.11.60 unlocks widgets updates after chronod fix, while v2.11.61 reverts enabling widget updates due to ongoing chronod problems.", "source_chunk_ids": ["exelban__stats__release__v2_11_60", "exelban__stats__release__v2_11_61"], "answer_support": [{"memory_node_id": "exelban__stats__release__v2_11_60", "answer_text": "unlocked widgets updates since the chronod was fixed in macOS 26.1"}, {"memory_node_id": "exelban__stats__release__v2_11_61", "answer_text": "reverted enabling macOS widget updates since there is still a problem with chronod"}]}
{"prototype_id": "exelban__stats_release_window", "repo": "exelban/stats", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the exelban/stats release window, order the following release-content states from earliest to latest: (1) a release that adds CPU average load to the Remote protocol and moves App settings to the sidebar, (2) a release that changes the minimum macOS version to Big Sur and adds better fan control for M3/M4, (3) a release that adds a Dot widget to the RAM module and initializes a CPU preview component, (4) a release that adds custom colors for widgets and moves Settings windows to lazy-loaded initialization.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["exelban__stats__release__v2_11_54", "exelban__stats__release__v2_12_0", "exelban__stats__release__v2_12_8", "exelban__stats__release__v2_12_14"], "answer_support": [{"memory_node_id": "exelban__stats__release__v2_11_54", "answer_text": "added CPU average load to the Remote protocol ... moved App settings from the menu to the bottom part of the sidebar"}, {"memory_node_id": "exelban__stats__release__v2_12_0", "answer_text": "changed minimum macOS version to macOS 11.15 (Big Sur) ... added better fan control for M3/M4 Apple Silicon"}, {"memory_node_id": "exelban__stats__release__v2_12_8", "answer_text": "added Dot widget to the RAM module ... initialized CPU preview component"}, {"memory_node_id": "exelban__stats__release__v2_12_14", "answer_text": "added custom colors for widgets ... moved Settings, Update, Setup, and Support windows to lazy-loaded initialization"}]}
{"prototype_id": "expressjs__express_release_window", "repo": "expressjs/express", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the expressjs/express releases, which release adds express.raw and express.text to parse bodies into Buffer and string respectively?", "options": [{"option_id": "A", "text": "4.16.3"}, {"option_id": "B", "text": "4.17.0"}, {"option_id": "C", "text": "4.18.0"}, {"option_id": "D", "text": "4.19.0"}], "correct_option_id": "B", "expected_answer": "4.17.0", "source_chunk_ids": ["expressjs__express__release__4_17_0"], "answer_support": [{"memory_node_id": "expressjs__express__release__4_17_0", "answer_text": "Add express.raw to parse bodies into Buffer, Add express.text to parse bodies into string"}]}
{"prototype_id": "expressjs__express_release_window", "repo": "expressjs/express", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the expressjs/express release window, order the following release-content states from earliest to latest: (1) a release that fixes handling of undefined in res.jsonp and incorrect middleware execution with unanchored RegExps, (2) a release that adds a 'root' option to res.download and deprecates string and non-integer arguments to res.status, (3) a release that deprecates the 'back' magic string in redirects and upgrades qs to 6.13.0.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["expressjs__express__release__4_17_2", "expressjs__express__release__4_18_0", "expressjs__express__release__4_21_0"], "answer_support": [{"memory_node_id": "expressjs__express__release__4_17_2", "answer_text": "Fix handling of undefined in res.jsonp, Fix incorrect middleware execution with unanchored RegExps"}, {"memory_node_id": "expressjs__express__release__4_18_0", "answer_text": "Add \"root\" option to res.download, Deprecate string and non-integer arguments to res.status"}, {"memory_node_id": "expressjs__express__release__4_21_0", "answer_text": "Deprecate \"back\" magic string in redirects, Upgraded dependency qs to 6.13.0"}]}
{"prototype_id": "facebook__react_release_window", "repo": "facebook/react", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the facebook/react releases, which release introduces the Owner Stack feature?", "options": [{"option_id": "A", "text": "v19.0.0"}, {"option_id": "B", "text": "v19.1.0"}, {"option_id": "C", "text": "v19.2.0"}, {"option_id": "D", "text": "v18.3.0"}], "correct_option_id": "B", "expected_answer": "v19.1.0", "source_chunk_ids": ["facebook__react__release__v19_1_0"], "answer_support": [{"memory_node_id": "facebook__react__release__v19_1_0", "answer_text": "introduces Owner Stack, a development-only stack trace identifying components responsible for rendering"}]}
{"prototype_id": "facebook__react_release_window", "repo": "facebook/react", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the facebook/react releases, how does the eslint-plugin-react-hooks@5.0.0 release differ from the eslint-plugin-react-hooks@7.1.0 release?", "options": [{"option_id": "A", "text": "5.0.0 adds support for ESLint v9 and renames useEvent to useEffectEvent, while 7.1.0 adds ESLint v10 support and improves set-state-in-effect validation."}, {"option_id": "B", "text": "5.0.0 introduces the Owner Stack feature, while 7.1.0 adds the Activity API."}, {"option_id": "C", "text": "Both releases only update the React core without changes to the ESLint plugin."}, {"option_id": "D", "text": "5.0.0 removes the component-hook-factories rule, while 7.1.0 adds it back."}], "correct_option_id": "A", "expected_answer": "5.0.0 adds support for ESLint v9 and renames useEvent to useEffectEvent, while 7.1.0 adds ESLint v10 support and improves set-state-in-effect validation.", "source_chunk_ids": ["facebook__react__release__eslint_plugin_react_hooks_5_0_0", "facebook__react__release__eslint_plugin_react_hooks_7_1_0"], "answer_support": [{"memory_node_id": "facebook__react__release__eslint_plugin_react_hooks_5_0_0", "answer_text": "adds support for ESLint v9, renames experimental useEvent to useEffectEvent"}, {"memory_node_id": "facebook__react__release__eslint_plugin_react_hooks_7_1_0", "answer_text": "adds ESLint v10 support, improved set-state-in-effect validation with fewer false negatives"}]}
{"prototype_id": "facebook__react_native_release_window", "repo": "facebook/react-native", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the facebook/react-native releases, which release introduces a fix for the 'Loading from Metro...' banner getting stuck after reloads in quick succession?", "options": [{"option_id": "A", "text": "0.83.6"}, {"option_id": "B", "text": "0.84.0-rc.4"}, {"option_id": "C", "text": "0.85.3"}, {"option_id": "D", "text": "0.86.0-rc.1"}], "correct_option_id": "A", "expected_answer": "0.83.6", "source_chunk_ids": ["facebook__react_native__release__v0_83_6"], "answer_support": [{"memory_node_id": "facebook__react_native__release__v0_83_6", "answer_text": "Fix \"Loading from Metro...\" banner getting stuck after reloads in quick succession."}]}
{"prototype_id": "facebook__react_native_release_window", "repo": "facebook/react-native", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the facebook/react-native releases, how does the Android-specific fix in 0.84.1 differ from the Android-specific fix in 0.83.3 regarding hermesV1Enabled?", "options": [{"option_id": "A", "text": "0.84.1 fixes ReactPlugin.kt always setting hermesV1Enabled to true, while 0.83.3 fixes included-build gradle.properties resolution for monorepos so hermesV1Enabled can be inherited correctly."}, {"option_id": "B", "text": "0.84.1 provides symbol fallbacks for inspector-modern when HermesV1 is disabled, while 0.83.3 adds support for custom header in devsupport."}, {"option_id": "C", "text": "0.84.1 fixes included-build gradle.properties resolution, while 0.83.3 fixes ReactPlugin.kt always setting hermesV1Enabled to true."}, {"option_id": "D", "text": "Both releases only update Hermes dSYMS without any code changes."}], "correct_option_id": "A", "expected_answer": "0.84.1 fixes ReactPlugin.kt always setting hermesV1Enabled to true, while 0.83.3 fixes included-build gradle.properties resolution for monorepos so hermesV1Enabled can be inherited correctly.", "source_chunk_ids": ["facebook__react_native__release__v0_84_1", "facebook__react_native__release__v0_83_3"], "answer_support": [{"memory_node_id": "facebook__react_native__release__v0_84_1", "answer_text": "ReactPlugin.kt always setting hermesV1Enabled to true"}, {"memory_node_id": "facebook__react_native__release__v0_83_3", "answer_text": "Fix included-build gradle.properties resolution for monorepos by reading from parent Gradle start parameters ... so hermesV1Enabled can be inherited correctly."}]}
{"prototype_id": "facebook__react_native_release_window", "repo": "facebook/react-native", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the facebook/react-native release window, order the following release-content states from earliest to latest: (1) a release that makes Hermes V1 the default engine for iOS, (2) a release that fixes Hermes builds for Mac Catalyst, (3) a release that fixes an empty screen for RNDT Network and Performance panels.", "options": [{"option_id": "A", "text": "1 -> 3 -> 2"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "3 -> 1 -> 2"}, {"option_id": "D", "text": "1 -> 2 -> 3"}], "correct_option_id": "A", "expected_answer": "1 -> 3 -> 2", "source_chunk_ids": ["facebook__react_native__release__v0_84_0_rc_1", "facebook__react_native__release__v0_84_0_rc_2", "facebook__react_native__release__v0_84_0_rc_5"], "answer_support": [{"memory_node_id": "facebook__react_native__release__v0_84_0_rc_1", "answer_text": "Make Hermes V1 the default engine for iOS"}, {"memory_node_id": "facebook__react_native__release__v0_84_0_rc_2", "answer_text": "Fix empty screen for RNDT Network and Performance panels"}, {"memory_node_id": "facebook__react_native__release__v0_84_0_rc_5", "answer_text": "Fix Hermes builds for Mac Catalyst"}]}
{"prototype_id": "facebook__rocksdb_release_window", "repo": "facebook/rocksdb", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the facebook/rocksdb releases, how does the handling of obsolete blob files differ between v9.6.2 and v9.7.4?", "options": [{"option_id": "A", "text": "v9.6.2 fixes a leak of obsolete blob files left open until DB::Close, while v9.7.4 also fixes the same leak but additionally preserves OPTIONS file for remote worker."}, {"option_id": "B", "text": "v9.6.2 introduces blob file garbage collection, while v9.7.4 removes blob file support entirely."}, {"option_id": "C", "text": "v9.6.2 only addresses blob file leaks in best-efforts recovery, while v9.7.4 addresses them in all scenarios."}, {"option_id": "D", "text": "v9.6.2 does not mention blob files, while v9.7.4 adds blob file compression."}], "correct_option_id": "A", "expected_answer": "v9.6.2 fixes a leak of obsolete blob files left open until DB::Close, while v9.7.4 also fixes the same leak but additionally preserves OPTIONS file for remote worker.", "source_chunk_ids": ["facebook__rocksdb__release__v9_6_2", "facebook__rocksdb__release__v9_7_4"], "answer_support": [{"memory_node_id": "facebook__rocksdb__release__v9_6_2", "answer_text": "Fix a leak of obsolete blob files left open until DB::Close(). This bug was introduced in version 9.4.0."}, {"memory_node_id": "facebook__rocksdb__release__v9_7_4", "answer_text": "Fix a leak of obsolete blob files left open until DB::Close(). This bug was introduced in version 9.4.0. ... OPTIONS file to be loaded by remote worker is now preserved so that it does not get purged by the primary host."}]}
{"prototype_id": "farion1231__cc_switch_release_window", "repo": "farion1231/cc-switch", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the farion1231/cc-switch releases, which release introduces a local API proxy with per-app takeover and automatic failover with circuit breaker?", "options": [{"option_id": "A", "text": "v3.6.0"}, {"option_id": "B", "text": "v3.9.0"}, {"option_id": "C", "text": "v3.10.0"}, {"option_id": "D", "text": "v3.11.0"}], "correct_option_id": "B", "expected_answer": "v3.9.0", "source_chunk_ids": ["farion1231__cc_switch__release__v3_9_0"], "answer_support": [{"memory_node_id": "farion1231__cc_switch__release__v3_9_0", "answer_text": "introduces a local API proxy with per-app takeover, automatic failover with circuit breaker"}]}
{"prototype_id": "farion1231__cc_switch_release_window", "repo": "farion1231/cc-switch", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the farion1231/cc-switch release window, order the following release-content states from earliest to latest: (1) a release that introduces OpenCode support as the fourth managed CLI application, (2) a release that introduces a local API proxy with per-app takeover and automatic failover, (3) a release that introduces OpenClaw support as the fifth managed application, (4) a release that introduces Hermes Agent as the sixth managed app.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "B", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "C", "text": "2 -> 3 -> 1 -> 4"}, {"option_id": "D", "text": "1 -> 3 -> 2 -> 4"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3 -> 4", "source_chunk_ids": ["farion1231__cc_switch__release__v3_9_0", "farion1231__cc_switch__release__v3_10_0", "farion1231__cc_switch__release__v3_11_0", "farion1231__cc_switch__release__v3_14_0"], "answer_support": [{"memory_node_id": "farion1231__cc_switch__release__v3_9_0", "answer_text": "introduces a local API proxy with per-app takeover, automatic failover"}, {"memory_node_id": "farion1231__cc_switch__release__v3_10_0", "answer_text": "introduces OpenCode support, becoming the fourth managed CLI application"}, {"memory_node_id": "farion1231__cc_switch__release__v3_11_0", "answer_text": "adds full management support for OpenClaw as the fifth application"}, {"memory_node_id": "farion1231__cc_switch__release__v3_14_0", "answer_text": "onboarding Hermes Agent as the 6th first-class managed app"}]}
{"prototype_id": "fastapi__fastapi_release_window", "repo": "fastapi/fastapi", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the fastapi/fastapi releases, which release adds support for Server Sent Events?", "options": [{"option_id": "A", "text": "0.134.0"}, {"option_id": "B", "text": "0.135.0"}, {"option_id": "C", "text": "0.136.0"}, {"option_id": "D", "text": "0.133.0"}], "correct_option_id": "B", "expected_answer": "0.135.0", "source_chunk_ids": ["fastapi__fastapi__release__0_135_0"], "answer_support": [{"memory_node_id": "fastapi__fastapi__release__0_135_0", "answer_text": "adds support for Server Sent Events"}]}
{"prototype_id": "fastapi__fastapi_release_window", "repo": "fastapi/fastapi", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the fastapi/fastapi releases, how does the breaking change in 0.128.0 differ from the breaking change in 0.129.0?", "options": [{"option_id": "A", "text": "0.128.0 drops support for pydantic.v1, while 0.129.0 drops support for Python 3.9."}, {"option_id": "B", "text": "0.128.0 drops support for Python 3.9, while 0.129.0 drops support for pydantic.v1."}, {"option_id": "C", "text": "Both releases drop support for the same feature."}, {"option_id": "D", "text": "0.128.0 adds deprecation warnings, while 0.129.0 adds a new feature."}], "correct_option_id": "A", "expected_answer": "0.128.0 drops support for pydantic.v1, while 0.129.0 drops support for Python 3.9.", "source_chunk_ids": ["fastapi__fastapi__release__0_128_0", "fastapi__fastapi__release__0_129_0"], "answer_support": [{"memory_node_id": "fastapi__fastapi__release__0_128_0", "answer_text": "drops support for pydantic.v1"}, {"memory_node_id": "fastapi__fastapi__release__0_129_0", "answer_text": "drops support for Python 3.9"}]}
{"prototype_id": "fastapi__fastapi_release_window", "repo": "fastapi/fastapi", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the fastapi/fastapi release window, order the following release-content states from earliest to latest: (1) a release that adds support for streaming JSON Lines and binary data with yield, (2) a release that adds support for Server Sent Events, (3) a release that adds support for free-threaded Python 3.14t.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["fastapi__fastapi__release__0_134_0", "fastapi__fastapi__release__0_135_0", "fastapi__fastapi__release__0_136_0"], "answer_support": [{"memory_node_id": "fastapi__fastapi__release__0_134_0", "answer_text": "adds support for streaming JSON Lines and binary data with yield"}, {"memory_node_id": "fastapi__fastapi__release__0_135_0", "answer_text": "adds support for Server Sent Events"}, {"memory_node_id": "fastapi__fastapi__release__0_136_0", "answer_text": "adds support for free-threaded Python 3.14t"}]}
{"prototype_id": "fastlane__fastlane_release_window", "repo": "fastlane/fastlane", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the fastlane/fastlane releases, which release introduces a new Apple ID authentication method using SRP with SHA-256 and 2048 bit hashing?", "options": [{"option_id": "A", "text": "2.225.0"}, {"option_id": "B", "text": "2.220.0"}, {"option_id": "C", "text": "2.230.0"}, {"option_id": "D", "text": "2.215.1"}], "correct_option_id": "A", "expected_answer": "2.225.0", "source_chunk_ids": ["fastlane__fastlane__release__2_225_0"], "answer_support": [{"memory_node_id": "fastlane__fastlane__release__2_225_0", "answer_text": "spaceship introduces new Apple ID authentication with SRP using SHA-256 and 2048 bit hashing"}]}
{"prototype_id": "fastlane__fastlane_release_window", "repo": "fastlane/fastlane", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the fastlane/fastlane releases, how does the match caching improvement in 2.218.0 differ from the match performance change in 2.220.0?", "options": [{"option_id": "A", "text": "2.218.0 adds a caching layer for up to 100x performance improvement, while 2.220.0 removes the renew_expired_certs option and reverts default behavior."}, {"option_id": "B", "text": "2.218.0 removes the caching layer, while 2.220.0 adds it back."}, {"option_id": "C", "text": "Both releases only update documentation for match."}, {"option_id": "D", "text": "2.218.0 fixes a missing job-token error, while 2.220.0 adds visionOS device support."}], "correct_option_id": "A", "expected_answer": "2.218.0 adds a caching layer for up to 100x performance improvement, while 2.220.0 removes the renew_expired_certs option and reverts default behavior.", "source_chunk_ids": ["fastlane__fastlane__release__2_218_0", "fastlane__fastlane__release__2_220_0"], "answer_support": [{"memory_node_id": "fastlane__fastlane__release__2_218_0", "answer_text": "match adds a caching layer to significantly improve performance by up to 100x"}, {"memory_node_id": "fastlane__fastlane__release__2_220_0", "answer_text": "match removes the renew_expired_certs option introduced in #21691 and reverts the default behavior"}]}
{"prototype_id": "fastlane__fastlane_release_window", "repo": "fastlane/fastlane", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the fastlane/fastlane release window, order the following release-content states from earliest to latest: (1) a release that adds a caching layer to match for up to 100x performance improvement, (2) a release that introduces new Apple ID authentication with SRP, (3) a release that removes the hipchat action and fixes an issue with template_name in provisioning profiles, (4) a release that adds support for App Clips default experience metadata.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "3 -> 1 -> 2 -> 4"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["fastlane__fastlane__release__2_218_0", "fastlane__fastlane__release__2_225_0", "fastlane__fastlane__release__2_228_0", "fastlane__fastlane__release__2_235_0"], "answer_support": [{"memory_node_id": "fastlane__fastlane__release__2_218_0", "answer_text": "match adds a caching layer to significantly improve performance by up to 100x"}, {"memory_node_id": "fastlane__fastlane__release__2_225_0", "answer_text": "spaceship introduces new Apple ID authentication with SRP"}, {"memory_node_id": "fastlane__fastlane__release__2_228_0", "answer_text": "hipchat action is removed and sigh and match fix issue where unknown attribute template_name is sent"}, {"memory_node_id": "fastlane__fastlane__release__2_235_0", "answer_text": "spaceship, deliver, and pilot add support for App Clips default experience metadata"}]}
{"prototype_id": "fatedier__frp_release_window", "repo": "fatedier/frp", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the fatedier/frp releases, which release introduces the `--strict_config` command line parameter to enable strict configuration validation mode?", "options": [{"option_id": "A", "text": "v0.52.0"}, {"option_id": "B", "text": "v0.53.0"}, {"option_id": "C", "text": "v0.54.0"}, {"option_id": "D", "text": "v0.55.0"}], "correct_option_id": "B", "expected_answer": "v0.53.0", "source_chunk_ids": ["fatedier__frp__release__v0_53_0"], "answer_support": [{"memory_node_id": "fatedier__frp__release__v0_53_0", "answer_text": "a new command line parameter `--strict_config` enables strict configuration validation mode"}]}
{"prototype_id": "fatedier__frp_release_window", "repo": "fatedier/frp", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the fatedier/frp releases, how does the configuration format change described in v0.52.0 differ from the strict configuration behavior change described in v0.55.0?", "options": [{"option_id": "A", "text": "v0.52.0 adds TOML/YAML/JSON support and deprecates INI, while v0.55.0 changes the default of --strict-config from false to true."}, {"option_id": "B", "text": "v0.52.0 removes range ports mapping, while v0.55.0 adds range ports mapping back."}, {"option_id": "C", "text": "Both releases only update the minimum Go version without configuration changes."}, {"option_id": "D", "text": "v0.52.0 introduces --strict-config, while v0.55.0 removes it."}], "correct_option_id": "A", "expected_answer": "v0.52.0 adds TOML/YAML/JSON support and deprecates INI, while v0.55.0 changes the default of --strict-config from false to true.", "source_chunk_ids": ["fatedier__frp__release__v0_52_0", "fatedier__frp__release__v0_55_0"], "answer_support": [{"memory_node_id": "fatedier__frp__release__v0_52_0", "answer_text": "configuration now supports TOML, YAML, and JSON formats, while INI is deprecated"}, {"memory_node_id": "fatedier__frp__release__v0_55_0", "answer_text": "The default value of `--strict-config` changes from false to true"}]}
{"prototype_id": "fatedier__frp_release_window", "repo": "fatedier/frp", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the fatedier/frp release window, order the following release-content states from earliest to latest: (1) a release that adds support for TOML, YAML, and JSON configuration formats, (2) a release that introduces Feature Gates and the VirtualNet feature gate, (3) a release that adds a built-in store capability for frpc with CRUD admin APIs, (4) a release that introduces wire protocol v2 and a compatibility policy.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 2 -> 1 -> 3"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["fatedier__frp__release__v0_52_0", "fatedier__frp__release__v0_62_0", "fatedier__frp__release__v0_68_0", "fatedier__frp__release__v0_69_0"], "answer_support": [{"memory_node_id": "fatedier__frp__release__v0_52_0", "answer_text": "configuration now supports TOML, YAML, and JSON formats"}, {"memory_node_id": "fatedier__frp__release__v0_62_0", "answer_text": "Feature Gates are introduced ... The first available feature gate is `VirtualNet`"}, {"memory_node_id": "fatedier__frp__release__v0_68_0", "answer_text": "a built-in `store` capability is added for frpc, including persisted store source, Store CRUD admin APIs"}, {"memory_node_id": "fatedier__frp__release__v0_69_0", "answer_text": "Wire protocol v2 is introduced ... a compatibility policy is introduced"}]}
{"prototype_id": "files_community__Files_release_window", "repo": "files-community/Files", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the files-community/Files releases, which release introduces a slider to control item size and a new 'Layout' settings page?", "options": [{"option_id": "A", "text": "v3.2"}, {"option_id": "B", "text": "v3.3"}, {"option_id": "C", "text": "v3.4"}, {"option_id": "D", "text": "v3.5"}], "correct_option_id": "B", "expected_answer": "v3.3", "source_chunk_ids": ["files_community__Files__release__v3_3"], "answer_support": [{"memory_node_id": "files_community__Files__release__v3_3", "answer_text": "Added slider to control item size ... Created new 'Layout' settings page"}]}
{"prototype_id": "files_community__Files_release_window", "repo": "files-community/Files", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the files-community/Files releases, how does the feature set in v3.4 differ from the feature set in v3.5 regarding personalization and design?", "options": [{"option_id": "A", "text": "v3.4 adds custom background images and keyboard shortcut remapping, while v3.5 updates the design with rounded corners and adds a network locations widget."}, {"option_id": "B", "text": "v3.4 introduces rounded corners and a network locations widget, while v3.5 adds custom background images and keyboard shortcut remapping."}, {"option_id": "C", "text": "Both releases only add localization updates without any personalization features."}, {"option_id": "D", "text": "v3.4 adds a slider to control item size, while v3.5 adds support for hiding the toolbar."}], "correct_option_id": "A", "expected_answer": "v3.4 adds custom background images and keyboard shortcut remapping, while v3.5 updates the design with rounded corners and adds a network locations widget.", "source_chunk_ids": ["files_community__Files__release__v3_4", "files_community__Files__release__v3_5"], "answer_support": [{"memory_node_id": "files_community__Files__release__v3_4", "answer_text": "Added support for personalizing Files with a custom background image ... Added support for remapping keyboard shortcuts"}, {"memory_node_id": "files_community__Files__release__v3_5", "answer_text": "Updated the design with rounded corners ... Added a network locations widget to the home page"}]}
{"prototype_id": "files_community__Files_release_window", "repo": "files-community/Files", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the files-community/Files release window, order the following release-content states from earliest to latest: (1) a release that adds support for pinning executable shortcuts to start and a List View layout, (2) a release that adds a slider to control item size and a new 'Layout' settings page, (3) a release that adds support for personalizing Files with a custom background image and remapping keyboard shortcuts.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["files_community__Files__release__v3_2", "files_community__Files__release__v3_3", "files_community__Files__release__v3_4"], "answer_support": [{"memory_node_id": "files_community__Files__release__v3_2", "answer_text": "Added support for pinning executable shortcuts to start ... Added a List View layout"}, {"memory_node_id": "files_community__Files__release__v3_3", "answer_text": "Added slider to control item size ... Created new 'Layout' settings page"}, {"memory_node_id": "files_community__Files__release__v3_4", "answer_text": "Added support for personalizing Files with a custom background image ... Added support for remapping keyboard shortcuts"}]}
{"prototype_id": "firecrawl__firecrawl_release_window", "repo": "firecrawl/firecrawl", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the firecrawl/firecrawl releases, which release introduces the /extract endpoint as an official release, enabling structured web data extraction with a prompt?", "options": [{"option_id": "A", "text": "v1.2.1"}, {"option_id": "B", "text": "v1.3.0"}, {"option_id": "C", "text": "v1.4.0"}, {"option_id": "D", "text": "v1.4.1"}], "correct_option_id": "C", "expected_answer": "v1.4.0", "source_chunk_ids": ["firecrawl__firecrawl__release__v1_4_0"], "answer_support": [{"memory_node_id": "firecrawl__firecrawl__release__v1_4_0", "answer_text": "the /extract endpoint is officially released, enabling structured web data extraction with a prompt"}]}
{"prototype_id": "firecrawl__firecrawl_release_window", "repo": "firecrawl/firecrawl", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the firecrawl/firecrawl releases, how does the /extract endpoint change from v1.2.1 to v1.4.0?", "options": [{"option_id": "A", "text": "v1.2.1 makes /extract asynchronous with an ID-based status check, while v1.4.0 officially releases /extract with prompt-based structured data extraction and custom schemas."}, {"option_id": "B", "text": "v1.2.1 removes /extract, and v1.4.0 reintroduces it with web search capabilities."}, {"option_id": "C", "text": "Both releases only add caching improvements to /extract without changing its core functionality."}, {"option_id": "D", "text": "v1.2.1 introduces multi-entity extraction, while v1.4.0 deprecates the /extract endpoint."}], "correct_option_id": "A", "expected_answer": "v1.2.1 makes /extract asynchronous with an ID-based status check, while v1.4.0 officially releases /extract with prompt-based structured data extraction and custom schemas.", "source_chunk_ids": ["firecrawl__firecrawl__release__v1_2_1", "firecrawl__firecrawl__release__v1_4_0"], "answer_support": [{"memory_node_id": "firecrawl__firecrawl__release__v1_2_1", "answer_text": "the /extract endpoint is updated to be asynchronous, returning an ID for status checks"}, {"memory_node_id": "firecrawl__firecrawl__release__v1_4_0", "answer_text": "the /extract endpoint is officially released, enabling structured web data extraction with a prompt"}]}
{"prototype_id": "firecrawl__firecrawl_release_window", "repo": "firecrawl/firecrawl", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the firecrawl/firecrawl release window, order the following release-content states from earliest to latest: (1) a release that introduces the Search API endpoint combining web search with scraping, (2) a release that makes the /extract endpoint asynchronous, (3) a release that officially releases the /extract endpoint with prompt-based extraction, (4) a release that adds web search capabilities to the extract endpoint via enableWebSearch.", "options": [{"option_id": "A", "text": "2 -> 3 -> 4 -> 1"}, {"option_id": "B", "text": "3 -> 2 -> 1 -> 4"}, {"option_id": "C", "text": "1 -> 4 -> 2 -> 3"}, {"option_id": "D", "text": "4 -> 1 -> 3 -> 2"}], "correct_option_id": "A", "expected_answer": "2 -> 3 -> 4 -> 1", "source_chunk_ids": ["firecrawl__firecrawl__release__v1_2_1", "firecrawl__firecrawl__release__v1_4_0", "firecrawl__firecrawl__release__v1_4_2", "firecrawl__firecrawl__release__v1_10_0"], "answer_support": [{"memory_node_id": "firecrawl__firecrawl__release__v1_2_1", "answer_text": "the /extract endpoint is updated to be asynchronous"}, {"memory_node_id": "firecrawl__firecrawl__release__v1_4_0", "answer_text": "the /extract endpoint is officially released"}, {"memory_node_id": "firecrawl__firecrawl__release__v1_4_2", "answer_text": "web search capabilities for the extract endpoint via enableWebSearch"}, {"memory_node_id": "firecrawl__firecrawl__release__v1_10_0", "answer_text": "a new Search API endpoint is launched, combining web search with scraping capabilities"}]}
{"prototype_id": "FortAwesome__Font_Awesome_release_window", "repo": "FortAwesome/Font-Awesome", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the FortAwesome/Font-Awesome releases, which release adds the user-unlock, mixer brand, coffin-cross, instagram-square, shopify, and dailymotion icons?", "options": [{"option_id": "A", "text": "Release 5.12.0"}, {"option_id": "B", "text": "Release 5.12.1"}, {"option_id": "C", "text": "Release 5.13.0"}, {"option_id": "D", "text": "Release 5.13.1"}], "correct_option_id": "B", "expected_answer": "Release 5.12.1", "source_chunk_ids": ["FortAwesome__Font_Awesome__release__5_12_1"], "answer_support": [{"memory_node_id": "FortAwesome__Font_Awesome__release__5_12_1", "answer_text": "new icons added include user-unlock, mixer brand, coffin-cross, instagram-square, shopify, and dailymotion"}]}
{"prototype_id": "FortAwesome__Font_Awesome_release_window", "repo": "FortAwesome/Font-Awesome", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the FortAwesome/Font-Awesome releases, how does the handling of the tripadvisor brand icon differ between release 5.14.0 and release 5.15.4?", "options": [{"option_id": "A", "text": "5.14.0 corrects a rendering issue with the tripadvisor icon in Windows 10, while 5.15.4 removes the tripadvisor brand icon entirely by request of Tripadvisor."}, {"option_id": "B", "text": "5.14.0 adds the tripadvisor icon, while 5.15.4 updates its design."}, {"option_id": "C", "text": "Both releases only update the tripadvisor icon without removal."}, {"option_id": "D", "text": "5.14.0 removes the tripadvisor icon, while 5.15.4 restores it."}], "correct_option_id": "A", "expected_answer": "5.14.0 corrects a rendering issue with the tripadvisor icon in Windows 10, while 5.15.4 removes the tripadvisor brand icon entirely by request of Tripadvisor.", "source_chunk_ids": ["FortAwesome__Font_Awesome__release__5_14_0", "FortAwesome__Font_Awesome__release__5_15_4"], "answer_support": [{"memory_node_id": "FortAwesome__Font_Awesome__release__5_14_0", "answer_text": "Corrected rendering issue with the tripadvisor brand icon in Windows 10"}, {"memory_node_id": "FortAwesome__Font_Awesome__release__5_15_4", "answer_text": "Removed the tripadvisor brand icon by request of Tripadvisor"}]}
{"prototype_id": "FortAwesome__Font_Awesome_release_window", "repo": "FortAwesome/Font-Awesome", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the FortAwesome/Font-Awesome release window, order the following release-content states from earliest to latest: (1) a release that adds COVID-19 related icons and the ability to specify mask ID and title ID for SVG with JS, (2) a release that adds new science fiction and household icons and renames haykal to bahai, (3) a release that adds the user-unlock, mixer brand, coffin-cross, instagram-square, shopify, and dailymotion icons.", "options": [{"option_id": "A", "text": "2 -> 3 -> 1"}, {"option_id": "B", "text": "1 -> 2 -> 3"}, {"option_id": "C", "text": "3 -> 1 -> 2"}, {"option_id": "D", "text": "2 -> 1 -> 3"}], "correct_option_id": "A", "expected_answer": "2 -> 3 -> 1", "source_chunk_ids": ["FortAwesome__Font_Awesome__release__5_12_0", "FortAwesome__Font_Awesome__release__5_12_1", "FortAwesome__Font_Awesome__release__5_13_0"], "answer_support": [{"memory_node_id": "FortAwesome__Font_Awesome__release__5_12_0", "answer_text": "new science fiction and household icons were added ... haykal icon was renamed to bahai"}, {"memory_node_id": "FortAwesome__Font_Awesome__release__5_12_1", "answer_text": "new icons added include user-unlock, mixer brand, coffin-cross, instagram-square, shopify, and dailymotion"}, {"memory_node_id": "FortAwesome__Font_Awesome__release__5_13_0", "answer_text": "New icons related to COVID-19 ... ability to specify mask ID and title ID for SVG with JS"}]}
{"prototype_id": "FuelLabs__fuel_core_release_window", "repo": "FuelLabs/fuel-core", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the FuelLabs/fuel-core releases, which release adds support for posting blocks to the shared sequencer?", "options": [{"option_id": "A", "text": "v0.40.0"}, {"option_id": "B", "text": "v0.40.1"}, {"option_id": "C", "text": "v0.40.2"}, {"option_id": "D", "text": "v0.40.3"}], "correct_option_id": "B", "expected_answer": "v0.40.1", "source_chunk_ids": ["FuelLabs__fuel_core__release__v0_40_1"], "answer_support": [{"memory_node_id": "FuelLabs__fuel_core__release__v0_40_1", "answer_text": "Added support for posting blocks to the shared sequencer."}]}
{"prototype_id": "FuelLabs__fuel_core_release_window", "repo": "FuelLabs/fuel-core", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the FuelLabs/fuel-core releases, how does the change to the `balance` endpoint in v0.44.0 differ from the change to the `AssetDetails` endpoint in v0.46.0?", "options": [{"option_id": "A", "text": "v0.44.0 changes the return type from u64 to u128, while v0.46.0 fixes the endpoint to match GraphQL standards."}, {"option_id": "B", "text": "v0.44.0 adds a new `balance` endpoint, while v0.46.0 removes the `AssetDetails` endpoint."}, {"option_id": "C", "text": "Both releases only update the underlying fuel-vm dependency without endpoint changes."}, {"option_id": "D", "text": "v0.44.0 deprecates the `balance` endpoint, while v0.46.0 introduces the `AssetDetails` endpoint."}], "correct_option_id": "A", "expected_answer": "v0.44.0 changes the return type from u64 to u128, while v0.46.0 fixes the endpoint to match GraphQL standards.", "source_chunk_ids": ["FuelLabs__fuel_core__release__v0_44_0", "FuelLabs__fuel_core__release__v0_46_0"], "answer_support": [{"memory_node_id": "FuelLabs__fuel_core__release__v0_44_0", "answer_text": "Changed return type of `balance` endpoint from `u64` to `u128`"}, {"memory_node_id": "FuelLabs__fuel_core__release__v0_46_0", "answer_text": "Fix the `AssetDetails` endpoint to match GraphQL standards"}]}
{"prototype_id": "FuelLabs__fuel_core_release_window", "repo": "FuelLabs/fuel-core", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the FuelLabs/fuel-core release window, order the following release-content states from earliest to latest: (1) a release that adds a GraphQL complexity histogram to metrics and introduces a `graphql-number-of-threads` CLI flag, (2) a release that adds support for posting blocks to the shared sequencer, (3) a release that hardcodes the timestamp of the genesis block, (4) a release that adds txpool stats to the node_info GraphQL endpoint.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["FuelLabs__fuel_core__release__v0_40_0", "FuelLabs__fuel_core__release__v0_40_1", "FuelLabs__fuel_core__release__v0_40_2", "FuelLabs__fuel_core__release__v0_40_3"], "answer_support": [{"memory_node_id": "FuelLabs__fuel_core__release__v0_40_0", "answer_text": "Add GraphQL complexity histogram to metrics ... Added a new CLI flag `graphql-number-of-threads`"}, {"memory_node_id": "FuelLabs__fuel_core__release__v0_40_1", "answer_text": "Added support for posting blocks to the shared sequencer."}, {"memory_node_id": "FuelLabs__fuel_core__release__v0_40_2", "answer_text": "Hardcode the timestamp of the genesis block."}, {"memory_node_id": "FuelLabs__fuel_core__release__v0_40_3", "answer_text": "Add txpool stats to the node_info GraphQL endpoint"}]}
{"prototype_id": "FuelLabs__fuels_rs_release_window", "repo": "FuelLabs/fuels-rs", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the FuelLabs/fuels-rs releases, which release introduces support for Upload and Upgrade transactions?", "options": [{"option_id": "A", "text": "v0.62.0"}, {"option_id": "B", "text": "v0.63.0"}, {"option_id": "C", "text": "v0.64.0"}, {"option_id": "D", "text": "v0.65.0"}], "correct_option_id": "B", "expected_answer": "v0.63.0", "source_chunk_ids": ["FuelLabs__fuels_rs__release__v0_63_0"], "answer_support": [{"memory_node_id": "FuelLabs__fuels_rs__release__v0_63_0", "answer_text": "adds support for Upload and Upgrade transactions"}]}
{"prototype_id": "FuelLabs__fuels_rs_release_window", "repo": "FuelLabs/fuels-rs", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the FuelLabs/fuels-rs release window, order the following release-content states from earliest to latest: (1) a release that adds support for AWS KMS and Google KMS, (2) a release that adds support for preconfirmations via send_transaction_and_await_status and subscribe_transaction_status, (3) a release that adds support for the new ABI errors and renames LogFormatter constructors.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["FuelLabs__fuels_rs__release__v0_71_0", "FuelLabs__fuels_rs__release__v0_72_0", "FuelLabs__fuels_rs__release__v0_73_0"], "answer_support": [{"memory_node_id": "FuelLabs__fuels_rs__release__v0_71_0", "answer_text": "adds support for AWS KMS and Google KMS"}, {"memory_node_id": "FuelLabs__fuels_rs__release__v0_72_0", "answer_text": "adds send_transaction_and_await_status and subscribe_transaction_status functions in the Provider to access preconfirmations"}, {"memory_node_id": "FuelLabs__fuels_rs__release__v0_73_0", "answer_text": "adds support for the new ABI errors, renames LogFormatter constructors to new_log and new_error"}]}
{"prototype_id": "FuelLabs__sway_release_window", "repo": "FuelLabs/sway", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the FuelLabs/sway releases, which release introduces the `crypto` module with expanded cryptographic functions and auto-generation of DWARF debug symbols in debug builds?", "options": [{"option_id": "A", "text": "v0.66.5"}, {"option_id": "B", "text": "v0.66.6"}, {"option_id": "C", "text": "v0.66.7"}, {"option_id": "D", "text": "v0.66.8"}], "correct_option_id": "C", "expected_answer": "v0.66.7", "source_chunk_ids": ["FuelLabs__sway__release__v0_66_7"], "answer_support": [{"memory_node_id": "FuelLabs__sway__release__v0_66_7", "answer_text": "introduces a crypto module with expanded cryptographic functions, auto-generation of DWARF debug symbols in debug builds"}]}
{"prototype_id": "FuelLabs__sway_release_window", "repo": "FuelLabs/sway", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the FuelLabs/sway releases, how does the handling of `panic` differ between v0.68.2 and v0.69.0?", "options": [{"option_id": "A", "text": "v0.68.2 implements `panic` as an expression, while v0.69.0 makes `panic` a keyword."}, {"option_id": "B", "text": "v0.68.2 removes `panic`, while v0.69.0 reintroduces it as a built-in function."}, {"option_id": "C", "text": "Both releases treat `panic` identically as a standard library function."}, {"option_id": "D", "text": "v0.68.2 deprecates `panic`, while v0.69.0 stabilizes it as an attribute."}], "correct_option_id": "A", "expected_answer": "v0.68.2 implements `panic` as an expression, while v0.69.0 makes `panic` a keyword.", "source_chunk_ids": ["FuelLabs__sway__release__v0_68_2", "FuelLabs__sway__release__v0_69_0"], "answer_support": [{"memory_node_id": "FuelLabs__sway__release__v0_68_2", "answer_text": "implementing panic expression"}, {"memory_node_id": "FuelLabs__sway__release__v0_69_0", "answer_text": "Breaking changes include panic becoming a keyword"}]}
{"prototype_id": "FuelLabs__sway_release_window", "repo": "FuelLabs/sway", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the FuelLabs/sway release window, order the following release-content states from earliest to latest: (1) a release that merges `std` and `core` libraries and splits the `Eq` trait into `Eq` and `PartialEq`, (2) a release that introduces the `crypto` module with expanded cryptographic functions and auto-generation of DWARF debug symbols, (3) a release that implements dynamic storage opcodes in the compiler and dynamic storage based `StorageVec`, (4) a release that stabilizes `new_hashing` and bumps Rust version to 1.90.", "options": [{"option_id": "A", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "B", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "C", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "D", "text": "1 -> 2 -> 4 -> 3"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 4 -> 3", "source_chunk_ids": ["FuelLabs__sway__release__v0_66_7", "FuelLabs__sway__release__v0_67_0", "FuelLabs__sway__release__v0_70_0", "FuelLabs__sway__release__v0_71_1"], "answer_support": [{"memory_node_id": "FuelLabs__sway__release__v0_66_7", "answer_text": "introduces a crypto module with expanded cryptographic functions, auto-generation of DWARF debug symbols"}, {"memory_node_id": "FuelLabs__sway__release__v0_67_0", "answer_text": "merging of std and core libraries, splitting of the Eq trait into Eq and PartialEq"}, {"memory_node_id": "FuelLabs__sway__release__v0_70_0", "answer_text": "stabilizing new_hashing, bumping Rust version to 1.90"}, {"memory_node_id": "FuelLabs__sway__release__v0_71_1", "answer_text": "implementing dynamic storage opcodes in the compiler, implementing dynamic storage based StorageVec"}]}
{"prototype_id": "gatsbyjs__gatsby_release_window", "repo": "gatsbyjs/gatsby", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the gatsbyjs/gatsby releases, which release introduces Custom Image and File CDN URL generators?", "options": [{"option_id": "A", "text": "gatsby@5.12.0"}, {"option_id": "B", "text": "gatsby@5.13.0"}, {"option_id": "C", "text": "gatsby@5.14.0"}, {"option_id": "D", "text": "gatsby@5.15.0"}], "correct_option_id": "B", "expected_answer": "gatsby@5.13.0", "source_chunk_ids": ["gatsbyjs__gatsby__release__gatsby_5_13_0"], "answer_support": [{"memory_node_id": "gatsbyjs__gatsby__release__gatsby_5_13_0", "answer_text": "the key highlight is the introduction of Custom Image and File CDN URL generators"}]}
{"prototype_id": "gatsbyjs__gatsby_release_window", "repo": "gatsbyjs/gatsby", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the gatsbyjs/gatsby releases, how does the feature introduced in gatsby@5.12.0 differ from the feature introduced in gatsby@5.13.0?", "options": [{"option_id": "A", "text": "5.12.0 introduces Adapters, while 5.13.0 introduces Custom Image and File CDN URL generators."}, {"option_id": "B", "text": "5.12.0 introduces Custom Image and File CDN URL generators, while 5.13.0 introduces Adapters."}, {"option_id": "C", "text": "Both releases introduce the same feature: Adapters."}, {"option_id": "D", "text": "5.12.0 introduces Node.js 22 support, while 5.13.0 introduces React 19 support."}], "correct_option_id": "A", "expected_answer": "5.12.0 introduces Adapters, while 5.13.0 introduces Custom Image and File CDN URL generators.", "source_chunk_ids": ["gatsbyjs__gatsby__release__gatsby_5_12_0", "gatsbyjs__gatsby__release__gatsby_5_13_0"], "answer_support": [{"memory_node_id": "gatsbyjs__gatsby__release__gatsby_5_12_0", "answer_text": "the key highlight is the introduction of Adapters"}, {"memory_node_id": "gatsbyjs__gatsby__release__gatsby_5_13_0", "answer_text": "the key highlight is the introduction of Custom Image and File CDN URL generators"}]}
{"prototype_id": "gatsbyjs__gatsby_release_window", "repo": "gatsbyjs/gatsby", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the gatsbyjs/gatsby release window, order the following release-content states from earliest to latest: (1) a release that introduces Adapters, (2) a release that introduces Custom Image and File CDN URL generators, (3) a release that formally introduces Node.js 22 support.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["gatsbyjs__gatsby__release__gatsby_5_12_0", "gatsbyjs__gatsby__release__gatsby_5_13_0", "gatsbyjs__gatsby__release__gatsby_5_15_0"], "answer_support": [{"memory_node_id": "gatsbyjs__gatsby__release__gatsby_5_12_0", "answer_text": "the key highlight is the introduction of Adapters"}, {"memory_node_id": "gatsbyjs__gatsby__release__gatsby_5_13_0", "answer_text": "the key highlight is the introduction of Custom Image and File CDN URL generators"}, {"memory_node_id": "gatsbyjs__gatsby__release__gatsby_5_15_0", "answer_text": "the release formally introduces Node.js 22 support"}]}
{"prototype_id": "Genymobile__scrcpy_release_window", "repo": "Genymobile/scrcpy", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the Genymobile/scrcpy releases, which release introduces the ability to mirror the device camera instead of the screen?", "options": [{"option_id": "A", "text": "v2.1"}, {"option_id": "B", "text": "v2.2"}, {"option_id": "C", "text": "v2.3"}, {"option_id": "D", "text": "v2.4"}], "correct_option_id": "B", "expected_answer": "v2.2", "source_chunk_ids": ["Genymobile__scrcpy__release__v2_2"], "answer_support": [{"memory_node_id": "Genymobile__scrcpy__release__v2_2", "answer_text": "Add option to mirror camera"}]}
{"prototype_id": "Genymobile__scrcpy_release_window", "repo": "Genymobile/scrcpy", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the Genymobile/scrcpy release window, order the following release-content states from earliest to latest: (1) a release that adds HID keyboard support on Linux, (2) a release that adds UHID keyboard and mouse support, (3) a release that migrates from SDL2 to SDL3.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["Genymobile__scrcpy__release__v1_20", "Genymobile__scrcpy__release__v2_4", "Genymobile__scrcpy__release__v4_0"], "answer_support": [{"memory_node_id": "Genymobile__scrcpy__release__v1_20", "answer_text": "Add HID keyboard support on Linux"}, {"memory_node_id": "Genymobile__scrcpy__release__v2_4", "answer_text": "Add UHID keyboard and mouse support"}, {"memory_node_id": "Genymobile__scrcpy__release__v4_0", "answer_text": "Migrate from SDL2 to SDL3"}]}
{"prototype_id": "getsentry__sentry_release_window", "repo": "getsentry/sentry", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the getsentry/sentry releases, which release introduces the ability to create new environments in the API and adds a 'moved' badge to the old alerts nav item?", "options": [{"option_id": "A", "text": "26.3.0"}, {"option_id": "B", "text": "26.4.0"}, {"option_id": "C", "text": "26.2.0"}, {"option_id": "D", "text": "26.1.0"}], "correct_option_id": "B", "expected_answer": "26.4.0", "source_chunk_ids": ["getsentry__sentry__release__26_4_0"], "answer_support": [{"memory_node_id": "getsentry__sentry__release__26_4_0", "answer_text": "adding ability to create new environments in the API, adding 'moved' badge to old alerts nav item"}]}
{"prototype_id": "getsentry__sentry_release_window", "repo": "getsentry/sentry", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the getsentry/sentry releases, how does the approach to alerting in release 26.2.0 differ from the approach in release 26.4.0?", "options": [{"option_id": "A", "text": "26.2.0 focuses on adding issue type conditions and publishing workflow engine API docs, while 26.4.0 focuses on adding onboarding banners and inline environment creation."}, {"option_id": "B", "text": "26.2.0 removes all alerting features, while 26.4.0 reintroduces them."}, {"option_id": "C", "text": "Both releases only update dashboard widgets without any alerting changes."}, {"option_id": "D", "text": "26.2.0 deprecates the workflow engine, while 26.4.0 removes it entirely."}], "correct_option_id": "A", "expected_answer": "26.2.0 focuses on adding issue type conditions and publishing workflow engine API docs, while 26.4.0 focuses on adding onboarding banners and inline environment creation.", "source_chunk_ids": ["getsentry__sentry__release__26_2_0", "getsentry__sentry__release__26_4_0"], "answer_support": [{"memory_node_id": "getsentry__sentry__release__26_2_0", "answer_text": "adding issue type condition to new Alerts UI, publishing workflow engine API docs"}, {"memory_node_id": "getsentry__sentry__release__26_4_0", "answer_text": "adding onboarding banner, adding ability to create new environments in the API"}]}
{"prototype_id": "getsentry__sentry_release_window", "repo": "getsentry/sentry", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the getsentry/sentry release window, order the following release-content states from earliest to latest: (1) a release that adds support for streamed output in autofix and configures workflow notifications by group type for metric-issues, (2) a release that adds a 'new' badge for logs in the sidebar and flattens visualize yaxes into multiple in explore, (3) a release that adds a warning message when action is not compatible with metric detectors and adds sorting for connected alerts, (4) a release that adds inline alert creation to monitor details page and adds admin audit log tab to customer details view.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["getsentry__sentry__release__24_12_0", "getsentry__sentry__release__25_5_0", "getsentry__sentry__release__26_1_0", "getsentry__sentry__release__26_4_2"], "answer_support": [{"memory_node_id": "getsentry__sentry__release__24_12_0", "answer_text": "adding support for streamed output in autofix, configuring workflow notifications by group type for metric-issues"}, {"memory_node_id": "getsentry__sentry__release__25_5_0", "answer_text": "adding a new badge for logs in the sidebar, flattening visualize yaxes into multiple in explore"}, {"memory_node_id": "getsentry__sentry__release__26_1_0", "answer_text": "adding warning message when action is not compatible with metric detectors, adding sorting for connected alerts"}, {"memory_node_id": "getsentry__sentry__release__26_4_2", "answer_text": "adding inline alert creation to monitor details page, adding admin audit log tab to customer details view"}]}
{"prototype_id": "ggml_org__llama_cpp_release_window", "repo": "ggml-org/llama.cpp", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the ggml-org/llama.cpp releases, which release adds tokenizer support for the jina-embeddings-v2-base-zh model?", "options": [{"option_id": "A", "text": "b9442"}, {"option_id": "B", "text": "b9444"}, {"option_id": "C", "text": "b9451"}, {"option_id": "D", "text": "b9453"}], "correct_option_id": "A", "expected_answer": "b9442", "source_chunk_ids": ["ggml_org__llama_cpp__release__b9442"], "answer_support": [{"memory_node_id": "ggml_org__llama_cpp__release__b9442", "answer_text": "tokenizer support is added for the jina-embeddings-v2-base-zh model"}]}
{"prototype_id": "ggml_org__llama_cpp_release_window", "repo": "ggml-org/llama.cpp", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the ggml-org/llama.cpp releases, how does the Vulkan optimization in b9452 differ from the Vulkan change in b9458?", "options": [{"option_id": "A", "text": "b9452 block-loads Q3_K/Q6_K data and subtracts on 32-bit ints for performance, while b9458 avoids holding the device mutex during pipeline compilation."}, {"option_id": "B", "text": "b9452 removes unused functions, while b9458 reduces host memory lock contention."}, {"option_id": "C", "text": "Both releases only update CI configurations for Vulkan builds."}, {"option_id": "D", "text": "b9452 adds bf16 support, while b9458 templates GLU kernels."}], "correct_option_id": "A", "expected_answer": "b9452 block-loads Q3_K/Q6_K data and subtracts on 32-bit ints for performance, while b9458 avoids holding the device mutex during pipeline compilation.", "source_chunk_ids": ["ggml_org__llama_cpp__release__b9452", "ggml_org__llama_cpp__release__b9458"], "answer_support": [{"memory_node_id": "ggml_org__llama_cpp__release__b9452", "answer_text": "block-load Q3_K/Q6_K block data and subtract on 32b ints"}, {"memory_node_id": "ggml_org__llama_cpp__release__b9458", "answer_text": "don't hold the device mutex while compiling pipelines"}]}
{"prototype_id": "ggml_org__llama_cpp_release_window", "repo": "ggml-org/llama.cpp", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the ggml-org/llama.cpp release window, order the following release-content states from earliest to latest: (1) a release that adds LoongArch LSX support, (2) a release that deprecates llama_set_warmup, (3) a release that adds a Thinking mode toggle in the UI, (4) a release that fixes TP granularity for Qwen 3.5/3.6 with 3 GPUs.", "options": [{"option_id": "A", "text": "1 -> 4 -> 2 -> 3"}, {"option_id": "B", "text": "4 -> 1 -> 3 -> 2"}, {"option_id": "C", "text": "1 -> 3 -> 4 -> 2"}, {"option_id": "D", "text": "4 -> 2 -> 1 -> 3"}], "correct_option_id": "A", "expected_answer": "1 -> 4 -> 2 -> 3", "source_chunk_ids": ["ggml_org__llama_cpp__release__b9430", "ggml_org__llama_cpp__release__b9434", "ggml_org__llama_cpp__release__b9471", "ggml_org__llama_cpp__release__b9474"], "answer_support": [{"memory_node_id": "ggml_org__llama_cpp__release__b9430", "answer_text": "adds some lsx support"}, {"memory_node_id": "ggml_org__llama_cpp__release__b9434", "answer_text": "TP: fix granularity for Qwen 3.5/3.6 + 3 GPUs"}, {"memory_node_id": "ggml_org__llama_cpp__release__b9471", "answer_text": "deprecate llama_set_warmup"}, {"memory_node_id": "ggml_org__llama_cpp__release__b9474", "answer_text": "Add Thinking mode toggle with reasoning effort levels"}]}
{"prototype_id": "ggml_org__whisper_cpp_release_window", "repo": "ggml-org/whisper.cpp", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the ggml-org/whisper.cpp releases, which release introduces integer quantization allowing models to be converted to 4, 5, or 8-bit integer weights?", "options": [{"option_id": "A", "text": "v1.2.0"}, {"option_id": "B", "text": "v1.3.0"}, {"option_id": "C", "text": "v1.4.0"}, {"option_id": "D", "text": "v1.5.0"}], "correct_option_id": "C", "expected_answer": "v1.4.0", "source_chunk_ids": ["ggml_org__whisper_cpp__release__v1_4_0"], "answer_support": [{"memory_node_id": "ggml_org__whisper_cpp__release__v1_4_0", "answer_text": "integer quantization is introduced, allowing models to be converted to 4, 5, or 8-bit integer weights"}]}
{"prototype_id": "ggml_org__whisper_cpp_release_window", "repo": "ggml-org/whisper.cpp", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the ggml-org/whisper.cpp releases, how does the GPU support described in v1.4.0 differ from the GPU support described in v1.5.0?", "options": [{"option_id": "A", "text": "v1.4.0 adds partial GPU (NVIDIA) support via cuBLAS, while v1.5.0 adds full GPU processing of Encoder and Decoder with CUDA and Metal."}, {"option_id": "B", "text": "v1.4.0 adds full GPU processing, while v1.5.0 only adds partial GPU support."}, {"option_id": "C", "text": "Both releases add identical GPU support."}, {"option_id": "D", "text": "v1.4.0 adds Metal support, while v1.5.0 adds Vulkan support."}], "correct_option_id": "A", "expected_answer": "v1.4.0 adds partial GPU (NVIDIA) support via cuBLAS, while v1.5.0 adds full GPU processing of Encoder and Decoder with CUDA and Metal.", "source_chunk_ids": ["ggml_org__whisper_cpp__release__v1_4_0", "ggml_org__whisper_cpp__release__v1_5_0"], "answer_support": [{"memory_node_id": "ggml_org__whisper_cpp__release__v1_4_0", "answer_text": "Partial GPU (NVIDIA) support via cuBLAS is added"}, {"memory_node_id": "ggml_org__whisper_cpp__release__v1_5_0", "answer_text": "Full GPU processing of the Encoder and the Decoder with CUDA and Metal is now supported"}]}
{"prototype_id": "github__spec_kit_release_window", "repo": "github/spec-kit", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the github/spec-kit releases, which release adds the `specify integration` subcommand for post-init integration management?", "options": [{"option_id": "A", "text": "v0.5.1"}, {"option_id": "B", "text": "v0.6.0"}, {"option_id": "C", "text": "v0.7.0"}, {"option_id": "D", "text": "v0.8.0"}], "correct_option_id": "A", "expected_answer": "v0.5.1", "source_chunk_ids": ["github__spec_kit__release__v0_5_1"], "answer_support": [{"memory_node_id": "github__spec_kit__release__v0_5_1", "answer_text": "Add `specify integration` subcommand for post-init integration management"}]}
{"prototype_id": "github__spec_kit_release_window", "repo": "github/spec-kit", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the github/spec-kit releases, how does the agent context update mechanism change between v0.8.18 and v0.9.0?", "options": [{"option_id": "A", "text": "v0.8.18 adds support for SPECKIT_WORKFLOW_RUN_ID override, while v0.9.0 migrates agent context updates to the agent-context extension and deprecates the old behavior."}, {"option_id": "B", "text": "v0.8.18 removes agent context updates entirely, while v0.9.0 reintroduces them via a new extension."}, {"option_id": "C", "text": "Both releases only update community extension versions without changing agent context handling."}, {"option_id": "D", "text": "v0.8.18 introduces the agent-context extension, while v0.9.0 removes it."}], "correct_option_id": "A", "expected_answer": "v0.8.18 adds support for SPECKIT_WORKFLOW_RUN_ID override, while v0.9.0 migrates agent context updates to the agent-context extension and deprecates the old behavior.", "source_chunk_ids": ["github__spec_kit__release__v0_8_18", "github__spec_kit__release__v0_9_0"], "answer_support": [{"memory_node_id": "github__spec_kit__release__v0_8_18", "answer_text": "Support is added for SPECKIT_WORKFLOW_RUN_ID override"}, {"memory_node_id": "github__spec_kit__release__v0_9_0", "answer_text": "Agent context updates are migrated to the agent-context extension, which is auto-enabled to preserve existing behavior; this compatibility fallback is deprecated and will be removed in v0.12.0."}]}
{"prototype_id": "github__spec_kit_release_window", "repo": "github/spec-kit", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the github/spec-kit release window, order the following release-content states from earliest to latest: (1) a release that adds the `specify integration` subcommand, (2) a release that adds a workflow engine with catalog system, (3) a release that adds composition strategies (prepend, append, wrap) for presets, (4) a release that migrates agent context updates to the agent-context extension.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["github__spec_kit__release__v0_5_1", "github__spec_kit__release__v0_7_0", "github__spec_kit__release__v0_8_0", "github__spec_kit__release__v0_9_0"], "answer_support": [{"memory_node_id": "github__spec_kit__release__v0_5_1", "answer_text": "Add `specify integration` subcommand for post-init integration management"}, {"memory_node_id": "github__spec_kit__release__v0_7_0", "answer_text": "Add workflow engine with catalog system"}, {"memory_node_id": "github__spec_kit__release__v0_8_0", "answer_text": "Composition strategies (prepend, append, wrap) for templates, commands, and scripts are added for presets"}, {"memory_node_id": "github__spec_kit__release__v0_9_0", "answer_text": "Agent context updates are migrated to the agent-context extension"}]}
{"prototype_id": "gkd_kit__gkd_release_window", "repo": "gkd-kit/gkd", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the gkd-kit/gkd releases, how does the Shizuku-related change in v1.11.0-beta.1 differ from the Shizuku-related fix in v1.10.1?", "options": [{"option_id": "A", "text": "v1.11.0-beta.1 refactors Shizuku authorization to a single 'Enable Optimization' switch, while v1.10.1 fixes a crash when calling Shizuku on Samsung OneUi."}, {"option_id": "B", "text": "v1.11.0-beta.1 removes Shizuku support entirely, while v1.10.1 adds initial Shizuku integration."}, {"option_id": "C", "text": "Both releases only update the Shizuku library version without functional changes."}, {"option_id": "D", "text": "v1.11.0-beta.1 introduces a Shizuku crash fix, while v1.10.1 adds a new Shizuku permission dialog."}], "correct_option_id": "A", "expected_answer": "v1.11.0-beta.1 refactors Shizuku authorization to a single 'Enable Optimization' switch, while v1.10.1 fixes a crash when calling Shizuku on Samsung OneUi.", "source_chunk_ids": ["gkd_kit__gkd__release__v1_11_0_beta_1", "gkd_kit__gkd__release__v1_10_1"], "answer_support": [{"memory_node_id": "gkd_kit__gkd__release__v1_11_0_beta_1", "answer_text": "Shizuku authorization is refactored to a single 'Enable Optimization' switch"}, {"memory_node_id": "gkd_kit__gkd__release__v1_10_1", "answer_text": "fix for a crash when calling Shizuku on Samsung OneUi"}]}
{"prototype_id": "gkd_kit__gkd_release_window", "repo": "gkd-kit/gkd", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the gkd-kit/gkd release window, order the following release-content states from earliest to latest: (1) a release that adds an automated work mode and swipe operations, (2) a release that introduces a consent dialog for usage declaration and accessibility explanation, (3) a release that fixes a crash when calling Shizuku on Samsung OneUi, (4) a release that optimizes the app list by adding pull-to-refresh and hiding interface-less apps.", "options": [{"option_id": "A", "text": "3 -> 2 -> 4 -> 1"}, {"option_id": "B", "text": "2 -> 3 -> 1 -> 4"}, {"option_id": "C", "text": "3 -> 4 -> 2 -> 1"}, {"option_id": "D", "text": "2 -> 4 -> 3 -> 1"}], "correct_option_id": "A", "expected_answer": "3 -> 2 -> 4 -> 1", "source_chunk_ids": ["gkd_kit__gkd__release__v1_10_1", "gkd_kit__gkd__release__v1_10_2_beta_2", "gkd_kit__gkd__release__v1_11_0_beta_1", "gkd_kit__gkd__release__v1_12_0_beta_1"], "answer_support": [{"memory_node_id": "gkd_kit__gkd__release__v1_10_1", "answer_text": "fix for a crash when calling Shizuku on Samsung OneUi"}, {"memory_node_id": "gkd_kit__gkd__release__v1_10_2_beta_2", "answer_text": "consent dialog for usage declaration and accessibility explanation"}, {"memory_node_id": "gkd_kit__gkd__release__v1_11_0_beta_1", "answer_text": "app list is restructured: ... pull-to-refresh is supported ... interface-less apps are hidden"}, {"memory_node_id": "gkd_kit__gkd__release__v1_12_0_beta_1", "answer_text": "automated work mode, swipe operations"}]}
{"prototype_id": "glanceapp__glance_release_window", "repo": "glanceapp/glance", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the glanceapp/glance releases, which release introduces a search widget with custom bangs and a clock widget with optional timezones?", "options": [{"option_id": "A", "text": "v0.5.0-beta.1"}, {"option_id": "B", "text": "v0.5.0"}, {"option_id": "C", "text": "v0.6.0-beta.1"}, {"option_id": "D", "text": "v0.6.0"}], "correct_option_id": "B", "expected_answer": "v0.5.0", "source_chunk_ids": ["glanceapp__glance__release__v0_5_0"], "answer_support": [{"memory_node_id": "glanceapp__glance__release__v0_5_0", "answer_text": "new widgets are introduced: a search widget with custom bangs and search engine support, a clock widget with optional timezones"}]}
{"prototype_id": "glanceapp__glance_release_window", "repo": "glanceapp/glance", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the glanceapp/glance releases, how does the DNS stats widget change from v0.6.0 to v0.7.5?", "options": [{"option_id": "A", "text": "v0.6.0 introduces the DNS stats widget supporting AdGuard Home and Pi-hole, while v0.7.5 adds support for Pi-hole version 6 via a new pihole-v6 service option."}, {"option_id": "B", "text": "v0.6.0 removes the DNS stats widget, and v0.7.5 reintroduces it with Pi-hole v6 support."}, {"option_id": "C", "text": "Both releases only fix graphical bugs in the DNS stats widget without adding new features."}, {"option_id": "D", "text": "v0.6.0 adds Pi-hole v6 support, while v0.7.5 adds AdGuard Home support."}], "correct_option_id": "A", "expected_answer": "v0.6.0 introduces the DNS stats widget supporting AdGuard Home and Pi-hole, while v0.7.5 adds support for Pi-hole version 6 via a new pihole-v6 service option.", "source_chunk_ids": ["glanceapp__glance__release__v0_6_0", "glanceapp__glance__release__v0_7_5"], "answer_support": [{"memory_node_id": "glanceapp__glance__release__v0_6_0", "answer_text": "a DNS stats widget supporting AdGuard Home and Pi-hole is added"}, {"memory_node_id": "glanceapp__glance__release__v0_7_5", "answer_text": "support for Pi-hole version 6 is added via a new pihole-v6 service option in the DNS stats widget"}]}
{"prototype_id": "glanceapp__glance_release_window", "repo": "glanceapp/glance", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the glanceapp/glance release window, order the following release-content states from earliest to latest: (1) a release that adds a group widget allowing multiple widgets to be grouped into one via tabs, (2) a release that introduces a search widget with custom bangs and a clock widget with optional timezones, (3) a release that adds a to-do widget and authentication.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3"}, {"option_id": "B", "text": "1 -> 2 -> 3"}, {"option_id": "C", "text": "3 -> 1 -> 2"}, {"option_id": "D", "text": "2 -> 3 -> 1"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3", "source_chunk_ids": ["glanceapp__glance__release__v0_5_0", "glanceapp__glance__release__v0_6_0_beta_2", "glanceapp__glance__release__v0_8_0"], "answer_support": [{"memory_node_id": "glanceapp__glance__release__v0_5_0", "answer_text": "new widgets are introduced: a search widget with custom bangs and search engine support, a clock widget with optional timezones"}, {"memory_node_id": "glanceapp__glance__release__v0_6_0_beta_2", "answer_text": "a group widget is added that allows grouping multiple widgets into one via tabs"}, {"memory_node_id": "glanceapp__glance__release__v0_8_0", "answer_text": "major features include authentication, a theme picker, a to-do widget"}]}
{"prototype_id": "goauthentik__authentik_release_window", "repo": "goauthentik/authentik", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the goauthentik/authentik releases, how does the security patch content in version/2025.8.6 differ from that in version/2025.12.6?", "options": [{"option_id": "A", "text": "2025.8.6 patches CVE-2026-25922, CVE-2026-25748, and CVE-2026-25227, while 2025.12.6 patches GHSA-wr38-7xg8-fqxr, GHSA-xp7f-xjjx-gwm8, and GHSA-c3m2-jqmq-pvp3."}, {"option_id": "B", "text": "Both releases patch the same set of CVEs."}, {"option_id": "C", "text": "2025.8.6 patches GHSA-wr38-7xg8-fqxr, while 2025.12.6 patches CVE-2026-25922."}, {"option_id": "D", "text": "Neither release includes any security patches."}], "correct_option_id": "A", "expected_answer": "2025.8.6 patches CVE-2026-25922, CVE-2026-25748, and CVE-2026-25227, while 2025.12.6 patches GHSA-wr38-7xg8-fqxr, GHSA-xp7f-xjjx-gwm8, and GHSA-c3m2-jqmq-pvp3.", "source_chunk_ids": ["goauthentik__authentik__release__version_2025_8_6", "goauthentik__authentik__release__version_2025_12_6"], "answer_support": [{"memory_node_id": "goauthentik__authentik__release__version_2025_8_6", "answer_text": "security patches for CVE-2026-25922, CVE-2026-25748, and CVE-2026-25227"}, {"memory_node_id": "goauthentik__authentik__release__version_2025_12_6", "answer_text": "security patches for GHSA-wr38-7xg8-fqxr, GHSA-xp7f-xjjx-gwm8, and GHSA-c3m2-jqmq-pvp3"}]}
{"prototype_id": "godotengine__godot_release_window", "repo": "godotengine/godot", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the godotengine/godot releases, which release introduces a new NavigationServer with obstacle avoidance, a Time singleton, and asynchronous shader compilation?", "options": [{"option_id": "A", "text": "Godot 3.5-stable"}, {"option_id": "B", "text": "Godot 4.0-stable"}, {"option_id": "C", "text": "Godot 3.6-stable"}, {"option_id": "D", "text": "Godot 4.1-stable"}], "correct_option_id": "A", "expected_answer": "Godot 3.5-stable", "source_chunk_ids": ["godotengine__godot__release__3_5_stable"], "answer_support": [{"memory_node_id": "godotengine__godot__release__3_5_stable", "answer_text": "new NavigationServer with obstacle avoidance; Time singleton; asynchronous shader compilation and caching"}]}
{"prototype_id": "godotengine__godot_release_window", "repo": "godotengine/godot", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the godotengine/godot releases, how does the change described in Godot 4.0-stable differ from the change described in Godot 4.1-stable?", "options": [{"option_id": "A", "text": "4.0-stable is a massive overhaul of the entire engine with 12,000 merged pull requests, while 4.1-stable is a feature release that improves performance and reliability and introduces a 4-month release cycle."}, {"option_id": "B", "text": "4.0-stable introduces a 4-month release cycle, while 4.1-stable is a maintenance release fixing bugs."}, {"option_id": "C", "text": "Both releases are maintenance releases that only fix bugs without adding new features."}, {"option_id": "D", "text": "4.0-stable adds a NavigationServer, while 4.1-stable adds asynchronous shader compilation."}], "correct_option_id": "A", "expected_answer": "4.0-stable is a massive overhaul of the entire engine with 12,000 merged pull requests, while 4.1-stable is a feature release that improves performance and reliability and introduces a 4-month release cycle.", "source_chunk_ids": ["godotengine__godot__release__4_0_stable", "godotengine__godot__release__4_1_stable"], "answer_support": [{"memory_node_id": "godotengine__godot__release__4_0_stable", "answer_text": "4 years of development. 12,000 merged pull requests. 7,000 fixed issues. 1,500 individual contributors ... all parts of the engine have been modernized, refactored, overhauled, rewritten, redesigned."}, {"memory_node_id": "godotengine__godot__release__4_1_stable", "answer_text": "feature release improving upon Godot 4.0 in all aspects, making it more performant, reliable and feature-packed. It inaugurates the 4-month release cycle"}]}
{"prototype_id": "godotengine__godot_release_window", "repo": "godotengine/godot", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the godotengine/godot release window, order the following release-content states from earliest to latest: (1) a release that is a major milestone with a new NavigationServer and asynchronous shader compilation, (2) a release that is the biggest release so far with 12,000 merged pull requests and a complete engine overhaul, (3) a feature release that inaugurates the 4-month release cycle, (4) a maintenance release that fixes an iOS export template issue for Xcode < 15.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["godotengine__godot__release__3_5_stable", "godotengine__godot__release__4_0_stable", "godotengine__godot__release__4_1_stable", "godotengine__godot__release__4_1_2_stable"], "answer_support": [{"memory_node_id": "godotengine__godot__release__3_5_stable", "answer_text": "Godot 3.5 is a major new milestone ... new NavigationServer with obstacle avoidance ... asynchronous shader compilation and caching"}, {"memory_node_id": "godotengine__godot__release__4_0_stable", "answer_text": "The Godot 4.0 release is by all metrics our biggest release so far. ... 12,000 merged pull requests ... all parts of the engine have been modernized, refactored, overhauled, rewritten, redesigned."}, {"memory_node_id": "godotengine__godot__release__4_1_stable", "answer_text": "Godot 4.1 is a feature release ... inaugurates the 4-month release cycle"}, {"memory_node_id": "godotengine__godot__release__4_1_2_stable", "answer_text": "The file Godot_v4.1.2-stable_export_templates.tpz was updated on October 11, 2023 to fix an issue with the iOS export template, preventing from exporting to iOS with Xcode < 15."}]}
{"prototype_id": "gofiber__fiber_release_window", "repo": "gofiber/fiber", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the gofiber/fiber releases, which release introduces a healthcheck middleware with liveness and readiness checks?", "options": [{"option_id": "A", "text": "v2.48.0"}, {"option_id": "B", "text": "v2.52.0"}, {"option_id": "C", "text": "v2.50.0"}, {"option_id": "D", "text": "v2.51.0"}], "correct_option_id": "B", "expected_answer": "v2.52.0", "source_chunk_ids": ["gofiber__fiber__release__v2_52_0"], "answer_support": [{"memory_node_id": "gofiber__fiber__release__v2_52_0", "answer_text": "a new healthcheck middleware adds liveness and readiness checks"}]}
{"prototype_id": "gofiber__fiber_release_window", "repo": "gofiber/fiber", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the gofiber/fiber releases, how does the CSRF middleware change described in v2.50.0 differ from the CSRF middleware change described in v3.0.0-beta.2?", "options": [{"option_id": "A", "text": "v2.50.0 adds single-use tokens, session integration, origin checks, and double submit cookie approach; v3.0.0-beta.2 adds support for trusted origins with subdomain style."}, {"option_id": "B", "text": "v2.50.0 removes CSRF middleware entirely; v3.0.0-beta.2 reintroduces it with trusted origins."}, {"option_id": "C", "text": "Both releases only update CSRF documentation without functional changes."}, {"option_id": "D", "text": "v2.50.0 adds trusted origins; v3.0.0-beta.2 adds single-use tokens."}], "correct_option_id": "A", "expected_answer": "v2.50.0 adds single-use tokens, session integration, origin checks, and double submit cookie approach; v3.0.0-beta.2 adds support for trusted origins with subdomain style.", "source_chunk_ids": ["gofiber__fiber__release__v2_50_0", "gofiber__fiber__release__v3_0_0_beta_2"], "answer_support": [{"memory_node_id": "gofiber__fiber__release__v2_50_0", "answer_text": "Security improvements to CSRF middleware include single-use tokens, session integration, origin checks, and double submit cookie approach"}, {"memory_node_id": "gofiber__fiber__release__v3_0_0_beta_2", "answer_text": "CSRF trusted origins with subdomain style"}]}
{"prototype_id": "gofiber__fiber_release_window", "repo": "gofiber/fiber", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the gofiber/fiber release window, order the following release-content states from earliest to latest: (1) a release that adds a healthcheck middleware with liveness and readiness checks, (2) a release that introduces a cookie parser and session Reset/Delete methods, (3) a release that adds support for parameters in content negotiation and application/problem+json.", "options": [{"option_id": "A", "text": "2 -> 3 -> 1"}, {"option_id": "B", "text": "1 -> 2 -> 3"}, {"option_id": "C", "text": "3 -> 1 -> 2"}, {"option_id": "D", "text": "2 -> 1 -> 3"}], "correct_option_id": "A", "expected_answer": "2 -> 3 -> 1", "source_chunk_ids": ["gofiber__fiber__release__v2_50_0", "gofiber__fiber__release__v2_51_0", "gofiber__fiber__release__v2_52_0"], "answer_support": [{"memory_node_id": "gofiber__fiber__release__v2_50_0", "answer_text": "New features add a cookie parser, session Reset and Store Delete methods"}, {"memory_node_id": "gofiber__fiber__release__v2_51_0", "answer_text": "new features add support for parameters in content negotiation and application/problem+json"}, {"memory_node_id": "gofiber__fiber__release__v2_52_0", "answer_text": "a new healthcheck middleware adds liveness and readiness checks"}]}
{"prototype_id": "gogs__gogs_release_window", "repo": "gogs/gogs", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the gogs/gogs releases, how does the security fix in v0.12.4 differ from the security fix in v0.12.5?", "options": [{"option_id": "A", "text": "v0.12.4 fixes potential SSRF attack by CRLF injection via repository migration, while v0.12.5 fixes potential SSRF in repository migration and improper PAM authorization handling."}, {"option_id": "B", "text": "v0.12.4 fixes remote command execution in file uploading, while v0.12.5 fixes stored XSS in issues."}, {"option_id": "C", "text": "v0.12.4 adds X-Frame-Options header, while v0.12.5 adds LOCAL_NETWORK_ALLOWLIST."}, {"option_id": "D", "text": "v0.12.4 fixes smart links for issues, while v0.12.5 fixes invalid character in Access-Control-Allow-Credentials."}], "correct_option_id": "A", "expected_answer": "v0.12.4 fixes potential SSRF attack by CRLF injection via repository migration, while v0.12.5 fixes potential SSRF in repository migration and improper PAM authorization handling.", "source_chunk_ids": ["gogs__gogs__release__v0_12_4", "gogs__gogs__release__v0_12_5"], "answer_support": [{"memory_node_id": "gogs__gogs__release__v0_12_4", "answer_text": "Security: Potential SSRF attack by CRLF injection via repository migration."}, {"memory_node_id": "gogs__gogs__release__v0_12_5", "answer_text": "Security: Potential SSRF in repository migration. Security: Improper PAM authorization handling."}]}
{"prototype_id": "gogs__gogs_release_window", "repo": "gogs/gogs", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the gogs/gogs release window, order the following release-content states from earliest to latest: (1) a release that adds support for comparing tags in addition to branches, (2) a release that adds support for personal access token in the password field, (3) a release that fixes stored XSS for issue assignees, (4) a release that fixes cross-repository LFS object overwrite.", "options": [{"option_id": "A", "text": "3 -> 2 -> 1 -> 4"}, {"option_id": "B", "text": "2 -> 3 -> 1 -> 4"}, {"option_id": "C", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "D", "text": "1 -> 2 -> 3 -> 4"}], "correct_option_id": "A", "expected_answer": "3 -> 2 -> 1 -> 4", "source_chunk_ids": ["gogs__gogs__release__v0_12_11", "gogs__gogs__release__v0_13_0", "gogs__gogs__release__v0_14_1", "gogs__gogs__release__v0_14_2"], "answer_support": [{"memory_node_id": "gogs__gogs__release__v0_12_11", "answer_text": "Security: Stored XSS for issue assignees."}, {"memory_node_id": "gogs__gogs__release__v0_13_0", "answer_text": "Support using personal access token in the password field."}, {"memory_node_id": "gogs__gogs__release__v0_14_1", "answer_text": "Support comparing tags in addition to branches."}, {"memory_node_id": "gogs__gogs__release__v0_14_2", "answer_text": "Security: Cross-repository LFS object overwrite via missing content hash verification."}]}
{"prototype_id": "gohugoio__hugo_release_window", "repo": "gohugoio/hugo", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the gohugoio/hugo releases, which release introduces partial decorators and adds reflect.IsPage, IsSite, IsResource, and IsImageResource utility functions?", "options": [{"option_id": "A", "text": "v0.153.0"}, {"option_id": "B", "text": "v0.154.0"}, {"option_id": "C", "text": "v0.155.0"}, {"option_id": "D", "text": "v0.156.0"}], "correct_option_id": "B", "expected_answer": "v0.154.0", "source_chunk_ids": ["gohugoio__hugo__release__v0_154_0"], "answer_support": [{"memory_node_id": "gohugoio__hugo__release__v0_154_0", "answer_text": "introduces partial decorators ... adds reflect.IsPage, IsSite, IsResource, and IsImageResource utility functions"}]}
{"prototype_id": "gohugoio__hugo_release_window", "repo": "gohugoio/hugo", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the gohugoio/hugo releases, how does the WebP memory limit change from v0.153.1 to v0.154.0?", "options": [{"option_id": "A", "text": "v0.153.1 increases the WebP memory limit to 256 MiB, while v0.154.0 further increases it to 384 MiB."}, {"option_id": "B", "text": "v0.153.1 sets the WebP memory limit to 128 MiB, while v0.154.0 removes the limit entirely."}, {"option_id": "C", "text": "v0.153.1 introduces the WebP memory limit, and v0.154.0 decreases it to 256 MiB."}, {"option_id": "D", "text": "Both releases keep the WebP memory limit at 256 MiB."}], "correct_option_id": "A", "expected_answer": "v0.153.1 increases the WebP memory limit to 256 MiB, while v0.154.0 further increases it to 384 MiB.", "source_chunk_ids": ["gohugoio__hugo__release__v0_153_1", "gohugoio__hugo__release__v0_154_0"], "answer_support": [{"memory_node_id": "gohugoio__hugo__release__v0_153_1", "answer_text": "increases the WebP memory limit to 256 MiB"}, {"memory_node_id": "gohugoio__hugo__release__v0_154_0", "answer_text": "increases WebP memory limit to 384 MiB"}]}
{"prototype_id": "gohugoio__hugo_release_window", "repo": "gohugoio/hugo", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the gohugoio/hugo release window, order the following release-content states from earliest to latest: (1) a release that adds AVIF image support and disallows text/html content files by default, (2) a release that introduces a multidimensional content model and overhauls WebP image support, (3) a release that adds css.Build and deprecates language configuration options, (4) a release that adds nested vars support in css.Build and slice-based permalinks config.", "options": [{"option_id": "A", "text": "2 -> 3 -> 4 -> 1"}, {"option_id": "B", "text": "3 -> 2 -> 1 -> 4"}, {"option_id": "C", "text": "2 -> 4 -> 3 -> 1"}, {"option_id": "D", "text": "1 -> 2 -> 3 -> 4"}], "correct_option_id": "A", "expected_answer": "2 -> 3 -> 4 -> 1", "source_chunk_ids": ["gohugoio__hugo__release__v0_153_0", "gohugoio__hugo__release__v0_158_0", "gohugoio__hugo__release__v0_161_0", "gohugoio__hugo__release__v0_162_0"], "answer_support": [{"memory_node_id": "gohugoio__hugo__release__v0_153_0", "answer_text": "introduces a multidimensional content model ... overhauls WebP image support"}, {"memory_node_id": "gohugoio__hugo__release__v0_158_0", "answer_text": "adds css.Build ... deprecates language configuration options"}, {"memory_node_id": "gohugoio__hugo__release__v0_161_0", "answer_text": "adds nested vars support in css.Build ... slice-based permalinks config"}, {"memory_node_id": "gohugoio__hugo__release__v0_162_0", "answer_text": "adds AVIF image support ... disallows text/html content files by default"}]}
{"prototype_id": "google_ai_edge__mediapipe_release_window", "repo": "google-ai-edge/mediapipe", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the google-ai-edge/mediapipe releases, which release introduces the Interactive Segmenter MediaPipe Task and adds the EDGETPU_NNAPI delegate option in the tasks API?", "options": [{"option_id": "A", "text": "v0.9.2.1"}, {"option_id": "B", "text": "v0.9.3.0"}, {"option_id": "C", "text": "v0.10.0"}, {"option_id": "D", "text": "v0.10.1"}], "correct_option_id": "B", "expected_answer": "v0.9.3.0", "source_chunk_ids": ["google_ai_edge__mediapipe__release__v0_9_3_0"], "answer_support": [{"memory_node_id": "google_ai_edge__mediapipe__release__v0_9_3_0", "answer_text": "Add Interactive Segmenter MediaPipe Task ... Add EDGETPU_NNAPI delegate option in MediaPipe tasks API"}]}
{"prototype_id": "google_ai_edge__mediapipe_release_window", "repo": "google-ai-edge/mediapipe", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the google-ai-edge/mediapipe releases, how does the LLM-related change described in v0.10.10 differ from the LLM-related change described in v0.10.11?", "options": [{"option_id": "A", "text": "v0.10.10 introduces the LLM Task Runner with TextGenerator Java API migrated to C Wrapper, while v0.10.11 adds LlmInference stats logging for Android and iOS LlmInference with asynchronous predict and generate functions."}, {"option_id": "B", "text": "v0.10.10 removes the LLM Inference Engine, while v0.10.11 adds vision modality to the LLM API."}, {"option_id": "C", "text": "Both releases only update WASM files without any LLM-related changes."}, {"option_id": "D", "text": "v0.10.10 adds audio modality to LLM, while v0.10.11 adds prompt templates for session in C API."}], "correct_option_id": "A", "expected_answer": "v0.10.10 introduces the LLM Task Runner with TextGenerator Java API migrated to C Wrapper, while v0.10.11 adds LlmInference stats logging for Android and iOS LlmInference with asynchronous predict and generate functions.", "source_chunk_ids": ["google_ai_edge__mediapipe__release__v0_10_10", "google_ai_edge__mediapipe__release__v0_10_11"], "answer_support": [{"memory_node_id": "google_ai_edge__mediapipe__release__v0_10_10", "answer_text": "LLM Task Runner with TextGenerator Java API migrated to C Wrapper"}, {"memory_node_id": "google_ai_edge__mediapipe__release__v0_10_11", "answer_text": "Add LlmInference stats logging for Android ... iOS LlmInference with LlmTaskRunner and asynchronous predict and generate functions"}]}
{"prototype_id": "google_gemini__gemini_cli_release_window", "repo": "google-gemini/gemini-cli", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the google-gemini/gemini-cli releases, which release introduces real-time voice mode with cloud and local backends?", "options": [{"option_id": "A", "text": "v0.41.0"}, {"option_id": "B", "text": "v0.42.0"}, {"option_id": "C", "text": "v0.43.0"}, {"option_id": "D", "text": "v0.44.0"}], "correct_option_id": "A", "expected_answer": "v0.41.0", "source_chunk_ids": ["google_gemini__gemini_cli__release__v0_41_0"], "answer_support": [{"memory_node_id": "google_gemini__gemini_cli__release__v0_41_0", "answer_text": "real-time voice mode with cloud and local backends"}]}
{"prototype_id": "google_gemini__gemini_cli_release_window", "repo": "google-gemini/gemini-cli", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the google-gemini/gemini-cli releases, how does the change in v0.42.0-nightly.20260506.g80d269054 regarding redirection in YOLO and AUTO_EDIT modes differ from the change in v0.44.0-nightly.20260514.g77078b3e8 regarding shell redirections in AUTO_EDIT mode?", "options": [{"option_id": "A", "text": "v0.42.0-nightly.20260506.g80d269054 allows redirection in YOLO and AUTO_EDIT modes without sandboxing, while v0.44.0-nightly.20260514.g77078b3e8 auto-approves shell redirections in AUTO_EDIT mode."}, {"option_id": "B", "text": "Both releases remove redirection support entirely."}, {"option_id": "C", "text": "v0.42.0-nightly.20260506.g80d269054 disables redirection, while v0.44.0-nightly.20260514.g77078b3e8 enables it only in sandboxed environments."}, {"option_id": "D", "text": "v0.42.0-nightly.20260506.g80d269054 introduces redirection for the first time, and v0.44.0-nightly.20260514.g77078b3e8 reverts that change."}], "correct_option_id": "A", "expected_answer": "v0.42.0-nightly.20260506.g80d269054 allows redirection in YOLO and AUTO_EDIT modes without sandboxing, while v0.44.0-nightly.20260514.g77078b3e8 auto-approves shell redirections in AUTO_EDIT mode.", "source_chunk_ids": ["google_gemini__gemini_cli__release__v0_42_0_nightly_20260506_g80d269054", "google_gemini__gemini_cli__release__v0_44_0_nightly_20260514_g77078b3e8"], "answer_support": [{"memory_node_id": "google_gemini__gemini_cli__release__v0_42_0_nightly_20260506_g80d269054", "answer_text": "allowing redirection in YOLO and AUTO_EDIT modes without sandboxing"}, {"memory_node_id": "google_gemini__gemini_cli__release__v0_44_0_nightly_20260514_g77078b3e8", "answer_text": "auto-approving shell redirections in AUTO_EDIT mode"}]}
{"prototype_id": "google__guava_release_window", "repo": "google/guava", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the google/guava releases, which release adds the method ImmutableMap.Builder.buildKeepingLast()?", "options": [{"option_id": "A", "text": "31.0"}, {"option_id": "B", "text": "31.1"}, {"option_id": "C", "text": "32.0.0"}, {"option_id": "D", "text": "33.0.0"}], "correct_option_id": "B", "expected_answer": "31.1", "source_chunk_ids": ["google__guava__release__v31_1"], "answer_support": [{"memory_node_id": "google__guava__release__v31_1", "answer_text": "collect: Added a new method ImmutableMap.Builder.buildKeepingLast()"}]}
{"prototype_id": "google__guava_release_window", "repo": "google/guava", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the google/guava releases, how does the change to Files.createTempDir in release 32.0.0 differ from the change in release 30.0?", "options": [{"option_id": "A", "text": "30.0 deprecated Files.createTempDir due to CVE-2020-8908, while 32.0.0 reimplemented it to further address the CVE but introduced a Windows-specific exception."}, {"option_id": "B", "text": "30.0 removed Files.createTempDir entirely, while 32.0.0 restored it with a new implementation."}, {"option_id": "C", "text": "Both releases only updated the method's documentation without functional changes."}, {"option_id": "D", "text": "30.0 added Files.createTempDir, and 32.0.0 deprecated it."}], "correct_option_id": "A", "expected_answer": "30.0 deprecated Files.createTempDir due to CVE-2020-8908, while 32.0.0 reimplemented it to further address the CVE but introduced a Windows-specific exception.", "source_chunk_ids": ["google__guava__release__v30_0", "google__guava__release__v32_0_0"], "answer_support": [{"memory_node_id": "google__guava__release__v30_0", "answer_text": "io: Deprecated Files.createTempDir(). (CVE-2020-8908)"}, {"memory_node_id": "google__guava__release__v32_0_0", "answer_text": "Reimplemented Files.createTempDir and FileBackedOutputStream to further address CVE-2020-8908 ... The new implementations ... throw an exception under Windows."}]}
{"prototype_id": "google__zx_release_window", "repo": "google/zx", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the google/zx releases, which release introduces delayed piping that allows filling dependent streams at any time during the origin process lifecycle without losing data?", "options": [{"option_id": "A", "text": "8.1.9"}, {"option_id": "B", "text": "8.2.0"}, {"option_id": "C", "text": "8.2.3"}, {"option_id": "D", "text": "8.3.0"}], "correct_option_id": "B", "expected_answer": "8.2.0", "source_chunk_ids": ["google__zx__release__8_2_0"], "answer_support": [{"memory_node_id": "google__zx__release__8_2_0", "answer_text": "introduces delayed piping that allows filling dependent streams at any time during the origin process lifecycle without losing data"}]}
{"prototype_id": "google__zx_release_window", "repo": "google/zx", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the google/zx releases, how does the pipe-related change in release 8.2.0 differ from the pipe-related change in release 8.8.0?", "options": [{"option_id": "A", "text": "8.2.0 introduces delayed piping and promisified streams, while 8.8.0 introduces unpipe(), many-to-one piping, and piping from rejected processes."}, {"option_id": "B", "text": "8.2.0 removes piping support, while 8.8.0 restores it."}, {"option_id": "C", "text": "Both releases only fix bugs in existing pipe functionality without adding new features."}, {"option_id": "D", "text": "8.2.0 adds stream picking, while 8.8.0 adds direct piping to file shortcut."}], "correct_option_id": "A", "expected_answer": "8.2.0 introduces delayed piping and promisified streams, while 8.8.0 introduces unpipe(), many-to-one piping, and piping from rejected processes.", "source_chunk_ids": ["google__zx__release__8_2_0", "google__zx__release__8_8_0"], "answer_support": [{"memory_node_id": "google__zx__release__8_2_0", "answer_text": "introduces delayed piping ... and promisified streams"}, {"memory_node_id": "google__zx__release__8_8_0", "answer_text": "introduces unpipe() ... many-to-one piping ... piping from rejected processes"}]}
{"prototype_id": "google__zx_release_window", "repo": "google/zx", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the google/zx release window, order the following release-content states from earliest to latest: (1) a release that introduces full-featured .env support via a tiny dotenv-inspired parser and serializer, (2) a release that introduces zx@lite, a ~7x smaller version with only core functions, (3) a release that introduces unpipe() to selectively stop piping, (4) a release that fixes potential cmd injection via kill() method for Windows platform.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["google__zx__release__8_3_1", "google__zx__release__8_5_0", "google__zx__release__8_8_0", "google__zx__release__8_8_2"], "answer_support": [{"memory_node_id": "google__zx__release__8_3_1", "answer_text": "introduces full-featured .env support via a tiny dotenv-inspired parser and serializer"}, {"memory_node_id": "google__zx__release__8_5_0", "answer_text": "introduces zx@lite, a ~7x smaller version with only core functions"}, {"memory_node_id": "google__zx__release__8_8_0", "answer_text": "introduces unpipe() to selectively stop piping"}, {"memory_node_id": "google__zx__release__8_8_2", "answer_text": "fixes potential cmd injection via kill() method for Windows platform"}]}
{"prototype_id": "gorhill__uBlock_release_window", "repo": "gorhill/uBlock", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the gorhill/uBlock releases, how does the change related to the urlskip= filter option in release 1.61.0 differ from the change related to the urlskip= filter option in release 1.60.0?", "options": [{"option_id": "A", "text": "1.60.0 introduces the urlskip= option, while 1.61.0 adds the -blocked directive and regex extraction transformation step to urlskip=."}, {"option_id": "B", "text": "1.60.0 removes the urlskip= option, while 1.61.0 reintroduces it with additional directives."}, {"option_id": "C", "text": "Both releases only fix bugs in the urlskip= option without adding new features."}, {"option_id": "D", "text": "1.60.0 adds the -blocked directive to urlskip=, while 1.61.0 introduces the urlskip= option for the first time."}], "correct_option_id": "A", "expected_answer": "1.60.0 introduces the urlskip= option, while 1.61.0 adds the -blocked directive and regex extraction transformation step to urlskip=.", "source_chunk_ids": ["gorhill__uBlock__release__1_60_0", "gorhill__uBlock__release__1_61_0"], "answer_support": [{"memory_node_id": "gorhill__uBlock__release__1_60_0", "answer_text": "introduces new static network filter option urlskip="}, {"memory_node_id": "gorhill__uBlock__release__1_61_0", "answer_text": "adds -blocked directive to urlskip= option, adds regex extraction transformation step to urlskip= option"}]}
{"prototype_id": "grafana__grafana_release_window", "repo": "grafana/grafana", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the grafana/grafana releases, how does the security fix content in release 12.4.2 differ from the security fix content in release 12.3.6?", "options": [{"option_id": "A", "text": "12.4.2 fixes CVE-2026-27876, CVE-2026-27877, CVE-2026-28375, CVE-2026-27879, CVE-2026-27880, and CVE-2026-33375, while 12.3.6 fixes only CVE-2026-27876, CVE-2026-27877, CVE-2026-28375, CVE-2026-27879, and CVE-2026-27880."}, {"option_id": "B", "text": "12.4.2 fixes only CVE-2026-33375, while 12.3.6 fixes CVE-2026-27876, CVE-2026-27877, CVE-2026-28375, CVE-2026-27879, and CVE-2026-27880."}, {"option_id": "C", "text": "Both releases fix exactly the same set of CVEs."}, {"option_id": "D", "text": "12.4.2 fixes CVE-2026-27876 and CVE-2026-27877, while 12.3.6 fixes CVE-2026-28375 and CVE-2026-27879."}], "correct_option_id": "A", "expected_answer": "12.4.2 fixes CVE-2026-27876, CVE-2026-27877, CVE-2026-28375, CVE-2026-27879, CVE-2026-27880, and CVE-2026-33375, while 12.3.6 fixes only CVE-2026-27876, CVE-2026-27877, CVE-2026-28375, CVE-2026-27879, and CVE-2026-27880.", "source_chunk_ids": ["grafana__grafana__release__v12_4_2", "grafana__grafana__release__v12_3_6"], "answer_support": [{"memory_node_id": "grafana__grafana__release__v12_4_2", "answer_text": "security fixes for CVE-2026-27876, CVE-2026-27877, CVE-2026-28375, CVE-2026-27879, CVE-2026-27880, and CVE-2026-33375"}, {"memory_node_id": "grafana__grafana__release__v12_3_6", "answer_text": "bug fixes for security vulnerabilities CVE-2026-27876, CVE-2026-27877, CVE-2026-28375, CVE-2026-27879, and CVE-2026-27880"}]}
{"prototype_id": "grafana__pyroscope_release_window", "repo": "grafana/pyroscope", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the grafana/pyroscope releases, which release introduces OTLP HTTP/json and HTTP/protobuf ingestion?", "options": [{"option_id": "A", "text": "v1.15.0"}, {"option_id": "B", "text": "v1.16.0"}, {"option_id": "C", "text": "v1.17.0"}, {"option_id": "D", "text": "v1.18.0"}], "correct_option_id": "B", "expected_answer": "v1.16.0", "source_chunk_ids": ["grafana__pyroscope__release__v1_16_0"], "answer_support": [{"memory_node_id": "grafana__pyroscope__release__v1_16_0", "answer_text": "Add OTLP HTTP/json and HTTP/protobuf ingestion"}]}
{"prototype_id": "grafana__pyroscope_release_window", "repo": "grafana/pyroscope", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the grafana/pyroscope releases, how does the source code integration change described in v1.18.0 differ from the change described in v1.19.0?", "options": [{"option_id": "A", "text": "v1.18.0 adds Python support, while v1.19.0 adds Javascript and Typescript support."}, {"option_id": "B", "text": "v1.18.0 adds Java support, while v1.19.0 adds Python support."}, {"option_id": "C", "text": "v1.18.0 adds Javascript support, while v1.19.0 adds Python support."}, {"option_id": "D", "text": "v1.18.0 adds Python support, while v1.19.0 adds Java support."}], "correct_option_id": "A", "expected_answer": "v1.18.0 adds Python support, while v1.19.0 adds Javascript and Typescript support.", "source_chunk_ids": ["grafana__pyroscope__release__v1_18_0", "grafana__pyroscope__release__v1_19_0"], "answer_support": [{"memory_node_id": "grafana__pyroscope__release__v1_18_0", "answer_text": "The source code integration now supports Python"}, {"memory_node_id": "grafana__pyroscope__release__v1_19_0", "answer_text": "Add support for Javascript and Typescript source code integration"}]}
{"prototype_id": "grpc__grpc_release_window", "repo": "grpc/grpc", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the grpc/grpc releases, which release introduces a SetDefaultEventEngine API and drops Python 3.8 support?", "options": [{"option_id": "A", "text": "v1.71.0"}, {"option_id": "B", "text": "v1.72.0"}, {"option_id": "C", "text": "v1.73.0"}, {"option_id": "D", "text": "v1.74.0"}], "correct_option_id": "A", "expected_answer": "v1.71.0", "source_chunk_ids": ["grpc__grpc__release__v1_71_0"], "answer_support": [{"memory_node_id": "grpc__grpc__release__v1_71_0", "answer_text": "adding a SetDefaultEventEngine API ... Python drops support for Python 3.8"}]}
{"prototype_id": "grpc__grpc_release_window", "repo": "grpc/grpc", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the grpc/grpc releases, how does the Python Cython pinning change described in v1.72.1 differ from the Python Cython pinning described in v1.73.0?", "options": [{"option_id": "A", "text": "v1.72.1 pins Cython to 3.1.1 as a backport to address inconsistent versions and a memory leak, while v1.73.0 pins Cython to 3.1.1 as a direct change in the stable release."}, {"option_id": "B", "text": "v1.72.1 pins Cython to 3.1.0, while v1.73.0 pins Cython to 3.1.1."}, {"option_id": "C", "text": "v1.72.1 does not mention Cython, while v1.73.0 pins Cython to 3.1.1."}, {"option_id": "D", "text": "Both releases pin Cython to 3.1.0."}], "correct_option_id": "A", "expected_answer": "v1.72.1 pins Cython to 3.1.1 as a backport to address inconsistent versions and a memory leak, while v1.73.0 pins Cython to 3.1.1 as a direct change in the stable release.", "source_chunk_ids": ["grpc__grpc__release__v1_72_1", "grpc__grpc__release__v1_73_0"], "answer_support": [{"memory_node_id": "grpc__grpc__release__v1_72_1", "answer_text": "pinning Cython to 3.1.1 in Python to address inconsistent Cython versions and a memory leak in AsyncIO APIs"}, {"memory_node_id": "grpc__grpc__release__v1_73_0", "answer_text": "Python pins Cython to 3.1.1"}]}
{"prototype_id": "grpc__grpc_release_window", "repo": "grpc/grpc", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the grpc/grpc release window, order the following release-content states from earliest to latest: (1) a release that drops Python 3.8 support and adds musl-linux binary wheels on arm64, (2) a release that updates Protobuf to v31.0 and enables EventEngine experiments by default on all platforms, (3) a release that implements fork support in Posix Event Engine and drops Ruby 3.0 support, (4) a release that migrates to pyproject.toml build system and fixes a race condition causing asyncio.run() to hang forever during shutdown.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "3 -> 2 -> 1 -> 4"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["grpc__grpc__release__v1_71_0", "grpc__grpc__release__v1_73_0", "grpc__grpc__release__v1_74_0", "grpc__grpc__release__v1_78_0"], "answer_support": [{"memory_node_id": "grpc__grpc__release__v1_71_0", "answer_text": "Python drops support for Python 3.8 and adds musl-linux binary wheels on arm64"}, {"memory_node_id": "grpc__grpc__release__v1_73_0", "answer_text": "updating Protobuf to v31.0 ... enabling EventEngine client, listener, and dns experiments by default on all platforms"}, {"memory_node_id": "grpc__grpc__release__v1_74_0", "answer_text": "implementing fork support in Posix Event Engine ... drops Ruby 3.0 support"}, {"memory_node_id": "grpc__grpc__release__v1_78_0", "answer_text": "migrates to pyproject.toml build system ... fixes a race condition causing asyncio.run() to hang forever during shutdown"}]}
{"prototype_id": "gsd_build__get_shit_done_release_window", "repo": "gsd-build/get-shit-done", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the gsd-build/get-shit-done releases, which release introduces the /gsd-spike and /gsd-sketch commands for rapid feasibility spiking and UI design sketching?", "options": [{"option_id": "A", "text": "v1.36.0"}, {"option_id": "B", "text": "v1.37.0"}, {"option_id": "C", "text": "v1.38.0"}, {"option_id": "D", "text": "v1.39.0"}], "correct_option_id": "B", "expected_answer": "v1.37.0", "source_chunk_ids": ["gsd_build__get_shit_done__release__v1_37_0"], "answer_support": [{"memory_node_id": "gsd_build__get_shit_done__release__v1_37_0", "answer_text": "adds /gsd-spike and /gsd-sketch commands for rapid feasibility spiking and UI design sketching"}]}
{"prototype_id": "gsd_build__get_shit_done_release_window", "repo": "gsd-build/get-shit-done", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the gsd-build/get-shit-done release window, order the following release-content states from earliest to latest: (1) a release that adds /gsd-ultraplan-phase [BETA] and /gsd-ingest-docs, (2) a release that adds a package legitimacy gate against slopsquatting and an installer migration framework, (3) a release that adds /gsd-spike and /gsd-sketch commands, (4) a release that adds a --minimal install profile and /gsd-edit-phase command.", "options": [{"option_id": "A", "text": "3 -> 1 -> 4 -> 2"}, {"option_id": "B", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "C", "text": "4 -> 2 -> 3 -> 1"}, {"option_id": "D", "text": "2 -> 4 -> 1 -> 3"}], "correct_option_id": "A", "expected_answer": "3 -> 1 -> 4 -> 2", "source_chunk_ids": ["gsd_build__get_shit_done__release__v1_37_0", "gsd_build__get_shit_done__release__v1_38_0", "gsd_build__get_shit_done__release__v1_39_0", "gsd_build__get_shit_done__release__v1_42_0"], "answer_support": [{"memory_node_id": "gsd_build__get_shit_done__release__v1_37_0", "answer_text": "adds /gsd-spike and /gsd-sketch commands"}, {"memory_node_id": "gsd_build__get_shit_done__release__v1_38_0", "answer_text": "adds /gsd-ultraplan-phase [BETA] and /gsd-ingest-docs"}, {"memory_node_id": "gsd_build__get_shit_done__release__v1_39_0", "answer_text": "adds a --minimal install profile and /gsd-edit-phase command"}, {"memory_node_id": "gsd_build__get_shit_done__release__v1_42_0", "answer_text": "adds a package legitimacy gate against slopsquatting and an installer migration framework"}]}
{"prototype_id": "hakimel__reveal_js_release_window", "repo": "hakimel/reveal.js", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the hakimel/reveal.js releases, which release introduces the scroll view feature?", "options": [{"option_id": "A", "text": "4.5.0"}, {"option_id": "B", "text": "5.0.0"}, {"option_id": "C", "text": "5.1.0"}, {"option_id": "D", "text": "6.0.0"}], "correct_option_id": "B", "expected_answer": "5.0.0", "source_chunk_ids": ["hakimel__reveal_js__release__5_0_0"], "answer_support": [{"memory_node_id": "hakimel__reveal_js__release__5_0_0", "answer_text": "introduces scroll view as a groundbreaking new feature"}]}
{"prototype_id": "hakimel__reveal_js_release_window", "repo": "hakimel/reveal.js", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the hakimel/reveal.js releases, how does the new feature introduced in 5.2.0 differ from the new feature introduced in 6.0.0?", "options": [{"option_id": "A", "text": "5.2.0 introduces the Lightbox feature for image/video overlays, while 6.0.0 introduces an official React wrapper package @revealjs/react."}, {"option_id": "B", "text": "5.2.0 introduces scroll view, while 6.0.0 introduces auto-animate."}, {"option_id": "C", "text": "Both releases introduce the same feature: jump-to-slide."}, {"option_id": "D", "text": "5.2.0 introduces the React wrapper, while 6.0.0 introduces the Lightbox."}], "correct_option_id": "A", "expected_answer": "5.2.0 introduces the Lightbox feature for image/video overlays, while 6.0.0 introduces an official React wrapper package @revealjs/react.", "source_chunk_ids": ["hakimel__reveal_js__release__5_2_0", "hakimel__reveal_js__release__6_0_0"], "answer_support": [{"memory_node_id": "hakimel__reveal_js__release__5_2_0", "answer_text": "introduces the Lightbox feature for image/video overlays"}, {"memory_node_id": "hakimel__reveal_js__release__6_0_0", "answer_text": "introduces a new official React wrapper package @revealjs/react"}]}
{"prototype_id": "hakimel__reveal_js_release_window", "repo": "hakimel/reveal.js", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the hakimel/reveal.js release window, order the following release-content states from earliest to latest: (1) a release that adds the ability to destroy/uninitialize a presentation, (2) a release that introduces the scroll view feature, (3) a release that introduces the Lightbox feature, (4) a release that introduces an official React wrapper package.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["hakimel__reveal_js__release__4_3_0", "hakimel__reveal_js__release__5_0_0", "hakimel__reveal_js__release__5_2_0", "hakimel__reveal_js__release__6_0_0"], "answer_support": [{"memory_node_id": "hakimel__reveal_js__release__4_3_0", "answer_text": "adds the ability to destroy/uninitialize a presentation"}, {"memory_node_id": "hakimel__reveal_js__release__5_0_0", "answer_text": "introduces scroll view as a groundbreaking new feature"}, {"memory_node_id": "hakimel__reveal_js__release__5_2_0", "answer_text": "introduces the Lightbox feature for image/video overlays"}, {"memory_node_id": "hakimel__reveal_js__release__6_0_0", "answer_text": "introduces a new official React wrapper package @revealjs/react"}]}
{"prototype_id": "halo_dev__halo_release_window", "repo": "halo-dev/halo", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the halo-dev/halo releases, which release introduces a gallery (image collection) function for the editor and support for setting protected usernames during registration?", "options": [{"option_id": "A", "text": "v2.21.10"}, {"option_id": "B", "text": "v2.22.0-alpha.1"}, {"option_id": "C", "text": "v2.22.0"}, {"option_id": "D", "text": "v2.23.0-beta.1"}], "correct_option_id": "B", "expected_answer": "v2.22.0-alpha.1", "source_chunk_ids": ["halo_dev__halo__release__v2_22_0_alpha_1"], "answer_support": [{"memory_node_id": "halo_dev__halo__release__v2_22_0_alpha_1", "answer_text": "introduces new features including a gallery (image collection) function for the editor, support for setting protected usernames during registration"}]}
{"prototype_id": "halo_dev__halo_release_window", "repo": "halo-dev/halo", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the halo-dev/halo releases, how does the thumbnail-related change in v2.22.0 differ from the thumbnail-related change in v2.22.5?", "options": [{"option_id": "A", "text": "v2.22.0 refactors image thumbnail functionality to generate on demand instead of storing records, while v2.22.5 fixes an issue where plugins not adapted to thumbnails caused images not to display."}, {"option_id": "B", "text": "v2.22.0 removes thumbnail generation entirely, while v2.22.5 adds thumbnail generation for videos."}, {"option_id": "C", "text": "Both releases only update the thumbnail storage path without functional changes."}, {"option_id": "D", "text": "v2.22.0 introduces thumbnail generation for the first time, while v2.22.5 disables thumbnail generation by default."}], "correct_option_id": "A", "expected_answer": "v2.22.0 refactors image thumbnail functionality to generate on demand instead of storing records, while v2.22.5 fixes an issue where plugins not adapted to thumbnails caused images not to display.", "source_chunk_ids": ["halo_dev__halo__release__v2_22_0", "halo_dev__halo__release__v2_22_5"], "answer_support": [{"memory_node_id": "halo_dev__halo__release__v2_22_0", "answer_text": "refactoring image thumbnail functionality to generate on demand instead of storing records"}, {"memory_node_id": "halo_dev__halo__release__v2_22_5", "answer_text": "fixes an issue where plugins not adapted to thumbnails caused images not to display"}]}
{"prototype_id": "halo_dev__halo_release_window", "repo": "halo-dev/halo", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the halo-dev/halo release window, order the following release-content states from earliest to latest: (1) a release that upgrades Spring Boot to 3.5.7 and Tiptap to 3.x, (2) a release that upgrades to Spring Boot 4 and PF4J to 3.15.0, (3) a release that upgrades Spring Boot to 4.0.4, (4) a release that upgrades Spring Boot to 4.0.5.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["halo_dev__halo__release__v2_22_0_alpha_1", "halo_dev__halo__release__v2_23_0_beta_1", "halo_dev__halo__release__v2_23_2", "halo_dev__halo__release__v2_24_0"], "answer_support": [{"memory_node_id": "halo_dev__halo__release__v2_22_0_alpha_1", "answer_text": "upgrading Spring Boot to 3.5.7 and Tiptap to 3.x"}, {"memory_node_id": "halo_dev__halo__release__v2_23_0_beta_1", "answer_text": "upgrading to Spring Boot 4 and upgrading PF4J to 3.15.0"}, {"memory_node_id": "halo_dev__halo__release__v2_23_2", "answer_text": "upgrade Spring Boot to 4.0.4"}, {"memory_node_id": "halo_dev__halo__release__v2_24_0", "answer_text": "upgrading Spring Boot to 4.0.5"}]}
{"prototype_id": "hexojs__hexo_release_window", "repo": "hexojs/hexo", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the hexojs/hexo releases, which release introduces the `full_url_for` helper and switches from minimatch to micromatch?", "options": [{"option_id": "A", "text": "4.0.0"}, {"option_id": "B", "text": "4.1.0"}, {"option_id": "C", "text": "4.2.0"}, {"option_id": "D", "text": "5.0.0"}], "correct_option_id": "A", "expected_answer": "4.0.0", "source_chunk_ids": ["hexojs__hexo__release__4_0_0"], "answer_support": [{"memory_node_id": "hexojs__hexo__release__4_0_0", "answer_text": "a full_url_for helper, and switching from minimatch to micromatch"}]}
{"prototype_id": "hexojs__hexo_release_window", "repo": "hexojs/hexo", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the hexojs/hexo release window, order the following release-content states from earliest to latest: (1) a release that drops Node 6 support and adds a full_url_for helper, (2) a release that drops Node 10 and escapes HTML by default in list_tag, (3) a release that drops Node 16 and Node 18 and adds a permalink variable timestamp.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["hexojs__hexo__release__4_0_0", "hexojs__hexo__release__6_0_0", "hexojs__hexo__release__v8_0_0"], "answer_support": [{"memory_node_id": "hexojs__hexo__release__4_0_0", "answer_text": "drop Node 6 ... full_url_for helper"}, {"memory_node_id": "hexojs__hexo__release__6_0_0", "answer_text": "Drop Node 10 ... Escape HTML by default in list_tag"}, {"memory_node_id": "hexojs__hexo__release__v8_0_0", "answer_text": "drop Node.js 16 ... drop Node.js 18 ... add permalink variable timestamp"}]}
{"prototype_id": "Hmbown__CodeWhale_release_window", "repo": "Hmbown/CodeWhale", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the Hmbown/CodeWhale releases, which release introduces a Windows NSIS installer (CodeWhaleSetup.exe) as a new installation method?", "options": [{"option_id": "A", "text": "v0.8.46"}, {"option_id": "B", "text": "v0.8.48"}, {"option_id": "C", "text": "v0.8.49"}, {"option_id": "D", "text": "v0.8.50"}], "correct_option_id": "D", "expected_answer": "v0.8.50", "source_chunk_ids": ["Hmbown__CodeWhale__release__v0_8_50"], "answer_support": [{"memory_node_id": "Hmbown__CodeWhale__release__v0_8_50", "answer_text": "manual download via platform archives including a new Windows NSIS installer (CodeWhaleSetup.exe)"}]}
{"prototype_id": "Hmbown__CodeWhale_release_window", "repo": "Hmbown/CodeWhale", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the Hmbown/CodeWhale release window, order the following release-content states from earliest to latest: (1) a release that adds a Windows NSIS installer, (2) a release that introduces a Linux RISC-V target in manual download, (3) a release that first renames the project to CodeWhale and updates installation methods accordingly.", "options": [{"option_id": "A", "text": "3 -> 2 -> 1"}, {"option_id": "B", "text": "2 -> 3 -> 1"}, {"option_id": "C", "text": "1 -> 2 -> 3"}, {"option_id": "D", "text": "3 -> 1 -> 2"}], "correct_option_id": "A", "expected_answer": "3 -> 2 -> 1", "source_chunk_ids": ["Hmbown__CodeWhale__release__v0_8_41", "Hmbown__CodeWhale__release__v0_8_48", "Hmbown__CodeWhale__release__v0_8_50"], "answer_support": [{"memory_node_id": "Hmbown__CodeWhale__release__v0_8_41", "answer_text": "the project renames to CodeWhale"}, {"memory_node_id": "Hmbown__CodeWhale__release__v0_8_48", "answer_text": "manual download via platform archives including a new Linux RISC-V target"}, {"memory_node_id": "Hmbown__CodeWhale__release__v0_8_50", "answer_text": "manual download via platform archives including a new Windows NSIS installer (CodeWhaleSetup.exe)"}]}
{"prototype_id": "home_assistant__core_release_window", "repo": "home-assistant/core", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the home-assistant/core releases, which release adds a trigger for water_heater.operation_mode_changed and improves action naming consistency for cloud, script, and valve?", "options": [{"option_id": "A", "text": "2026.4.0b0"}, {"option_id": "B", "text": "2026.4.0b1"}, {"option_id": "C", "text": "2026.4.0b2"}, {"option_id": "D", "text": "2026.4.0b3"}], "correct_option_id": "B", "expected_answer": "2026.4.0b1", "source_chunk_ids": ["home_assistant__core__release__2026_4_0b1"], "answer_support": [{"memory_node_id": "home_assistant__core__release__2026_4_0b1", "answer_text": "adding a trigger for water_heater.operation_mode_changed, using NumericThresholdSelector in numeric conditions, and improving action naming consistency for cloud, script, valve, humidifier, automation, counter, image, device tracker, water heater, group, logger, dashboard, weather, and conversation."}]}
{"prototype_id": "home_assistant__core_release_window", "repo": "home-assistant/core", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the home-assistant/core releases, how does the handling of number entities in triggers and conditions differ between release 2026.4.0b3 and release 2026.4.0b4?", "options": [{"option_id": "A", "text": "2026.4.0b3 removes number entity support from battery, humidity, illuminance, moisture, and power triggers and conditions, while 2026.4.0b4 adds weather support to humidity conditions and adds select conditions."}, {"option_id": "B", "text": "2026.4.0b3 adds number entity support to all triggers, while 2026.4.0b4 removes it entirely."}, {"option_id": "C", "text": "Both releases add number entity support to battery triggers."}, {"option_id": "D", "text": "2026.4.0b3 restores number entity support, while 2026.4.0b4 removes it again."}], "correct_option_id": "A", "expected_answer": "2026.4.0b3 removes number entity support from battery, humidity, illuminance, moisture, and power triggers and conditions, while 2026.4.0b4 adds weather support to humidity conditions and adds select conditions.", "source_chunk_ids": ["home_assistant__core__release__2026_4_0b3", "home_assistant__core__release__2026_4_0b4"], "answer_support": [{"memory_node_id": "home_assistant__core__release__2026_4_0b3", "answer_text": "removes number entity support from battery, humidity, illuminance, moisture, and power triggers and conditions"}, {"memory_node_id": "home_assistant__core__release__2026_4_0b4", "answer_text": "adds weather support to humidity conditions, adds select conditions"}]}
{"prototype_id": "home_assistant__core_release_window", "repo": "home-assistant/core", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the home-assistant/core release window, order the following release-content states from earliest to latest: (1) a release that adds battery triggers and Google Drive backup upload progress, (2) a release that adds trigger water_heater.operation_mode_changed and improves action naming consistency, (3) a release that adds weather support to humidity conditions and adds select conditions, (4) a release that adds new OAuth exceptions to Neato and handles Oauth2 ImplementationUnavailableError in multiple integrations.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "B", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "C", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "D", "text": "1 -> 3 -> 2 -> 4"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3 -> 4", "source_chunk_ids": ["home_assistant__core__release__2026_4_0b1", "home_assistant__core__release__2026_4_0b2", "home_assistant__core__release__2026_4_0b4", "home_assistant__core__release__2026_4_0b5"], "answer_support": [{"memory_node_id": "home_assistant__core__release__2026_4_0b1", "answer_text": "adding a trigger for water_heater.operation_mode_changed, using NumericThresholdSelector in numeric conditions, and improving action naming consistency"}, {"memory_node_id": "home_assistant__core__release__2026_4_0b2", "answer_text": "adds a trigger for humidifier.mode_changed, adds battery triggers, adds Google Drive backup upload progress"}, {"memory_node_id": "home_assistant__core__release__2026_4_0b4", "answer_text": "adds weather support to humidity conditions, adds select conditions"}, {"memory_node_id": "home_assistant__core__release__2026_4_0b5", "answer_text": "adds new OAuth exceptions to Neato, handles Oauth2 ImplementationUnavailableError in husqvarna_automower, corrects Musiccast sound mode name, handles Oauth2 ImplementationUnavailableError in gentex_homelink, geocaching, google_assistant_sdk, google_mail, google_sheets, iotty, monzo, microbees, lyric, and google_tasks"}]}
{"prototype_id": "Homebrew__brew_release_window", "repo": "Homebrew/brew", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the Homebrew/brew releases, which release adds the `brew --taps` command?", "options": [{"option_id": "A", "text": "5.0.2"}, {"option_id": "B", "text": "5.0.3"}, {"option_id": "C", "text": "5.0.4"}, {"option_id": "D", "text": "5.0.5"}], "correct_option_id": "A", "expected_answer": "5.0.2", "source_chunk_ids": ["Homebrew__brew__release__5_0_2"], "answer_support": [{"memory_node_id": "Homebrew__brew__release__5_0_2", "answer_text": "adds `brew --taps` command"}]}
{"prototype_id": "hoppscotch__hoppscotch_release_window", "repo": "hoppscotch/hoppscotch", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the hoppscotch/hoppscotch releases, which release introduces collection variables and OpenTelemetry integration?", "options": [{"option_id": "A", "text": "2025.8.0"}, {"option_id": "B", "text": "2025.9.0"}, {"option_id": "C", "text": "2025.10.0"}, {"option_id": "D", "text": "2025.7.0"}], "correct_option_id": "A", "expected_answer": "2025.8.0", "source_chunk_ids": ["hoppscotch__hoppscotch__release__2025_8_0"], "answer_support": [{"memory_node_id": "hoppscotch__hoppscotch__release__2025_8_0", "answer_text": "introduces collection variables, OpenTelemetry integration for connecting Hoppscotch to your own telemetry pipeline"}]}
{"prototype_id": "hoppscotch__hoppscotch_release_window", "repo": "hoppscotch/hoppscotch", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the hoppscotch/hoppscotch releases, how does the scripting-related change described in 2025.5.0 differ from the scripting-related change described in 2025.7.0?", "options": [{"option_id": "A", "text": "2025.5.0 introduces an experimental scripting sandbox with an in-app console, while 2025.7.0 introduces scripting editors powered by Monaco as part of the experimental scripting sandbox."}, {"option_id": "B", "text": "2025.5.0 removes scripting support, while 2025.7.0 adds it back."}, {"option_id": "C", "text": "Both releases only update the scripting sandbox with minor bug fixes."}, {"option_id": "D", "text": "2025.5.0 introduces the hopp namespace, while 2025.7.0 introduces Chai-powered assertions."}], "correct_option_id": "A", "expected_answer": "2025.5.0 introduces an experimental scripting sandbox with an in-app console, while 2025.7.0 introduces scripting editors powered by Monaco as part of the experimental scripting sandbox.", "source_chunk_ids": ["hoppscotch__hoppscotch__release__2025_5_0", "hoppscotch__hoppscotch__release__2025_7_0"], "answer_support": [{"memory_node_id": "hoppscotch__hoppscotch__release__2025_5_0", "answer_text": "adds support for ... an experimental scripting sandbox comprising an in-app console"}, {"memory_node_id": "hoppscotch__hoppscotch__release__2025_7_0", "answer_text": "introduces ... scripting editors powered by Monaco as part of the experimental scripting sandbox"}]}
{"prototype_id": "hoppscotch__hoppscotch_release_window", "repo": "hoppscotch/hoppscotch", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the hoppscotch/hoppscotch release window, order the following release-content states from earliest to latest: (1) a release that introduces mock servers for simulating API responses, (2) a release that introduces API Documentation for sharing specifications, (3) a release that introduces API documentation versioning, (4) a release that introduces collection-level pre-request and test scripts.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["hoppscotch__hoppscotch__release__2025_10_0", "hoppscotch__hoppscotch__release__2025_11_0", "hoppscotch__hoppscotch__release__2026_2_0", "hoppscotch__hoppscotch__release__2026_4_0"], "answer_support": [{"memory_node_id": "hoppscotch__hoppscotch__release__2025_10_0", "answer_text": "introduces mock servers for simulating API responses"}, {"memory_node_id": "hoppscotch__hoppscotch__release__2025_11_0", "answer_text": "introduces API Documentation for sharing specifications"}, {"memory_node_id": "hoppscotch__hoppscotch__release__2026_2_0", "answer_text": "introduces API documentation versioning"}, {"memory_node_id": "hoppscotch__hoppscotch__release__2026_4_0", "answer_text": "introduces collection-level pre-request and test scripts"}]}
{"prototype_id": "httpie__cli_release_window", "repo": "httpie/cli", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the httpie/cli releases, which release adds support for nested JSON syntax and a plugin manager interface?", "options": [{"option_id": "A", "text": "HTTPie 2.6.0"}, {"option_id": "B", "text": "HTTPie 3.0.0"}, {"option_id": "C", "text": "HTTPie 3.1.0"}, {"option_id": "D", "text": "HTTPie 3.2.0"}], "correct_option_id": "B", "expected_answer": "HTTPie 3.0.0", "source_chunk_ids": ["httpie__cli__release__3_0_0"], "answer_support": [{"memory_node_id": "httpie__cli__release__3_0_0", "answer_text": "added support for nested JSON syntax, added httpie plugins interface for plugin management"}]}
{"prototype_id": "httpie__cli_release_window", "repo": "httpie/cli", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the httpie/cli releases, how does the SSL/TLS-related change in HTTPie 0.9.4 differ from the SSL-related change in 3.2.3?", "options": [{"option_id": "A", "text": "0.9.4 adds --ssl=<PROTOCOL> to specify the desired SSL/TLS protocol version, while 3.2.3 fixes SSL connections by pinning the requests version to 2.31.0."}, {"option_id": "B", "text": "0.9.4 removes SSL support, while 3.2.3 adds TLS 1.3 support."}, {"option_id": "C", "text": "Both releases only update the default --style option."}, {"option_id": "D", "text": "0.9.4 adds --ciphers, while 3.2.3 adds --cert-key-pass."}], "correct_option_id": "A", "expected_answer": "0.9.4 adds --ssl=<PROTOCOL> to specify the desired SSL/TLS protocol version, while 3.2.3 fixes SSL connections by pinning the requests version to 2.31.0.", "source_chunk_ids": ["httpie__cli__release__0_9_4", "httpie__cli__release__3_2_3"], "answer_support": [{"memory_node_id": "httpie__cli__release__0_9_4", "answer_text": "Added --ssl=<PROTOCOL> to specify the desired SSL/TLS protocol version"}, {"memory_node_id": "httpie__cli__release__3_2_3", "answer_text": "Fix SSL connections by pinning the requests version to 2.31.0"}]}
{"prototype_id": "httpie__cli_release_window", "repo": "httpie/cli", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the httpie/cli release window, order the following release-content states from earliest to latest: (1) a release that adds support for nested JSON syntax and a plugin manager, (2) a release that adds --raw to allow specifying the raw request body without extra processing, (3) a release that adds support for streamed uploads and multipart upload streaming, (4) a release that adds --offline to allow building an HTTP request and printing it but not actually sending it over the network.", "options": [{"option_id": "A", "text": "4 -> 3 -> 2 -> 1"}, {"option_id": "B", "text": "3 -> 4 -> 2 -> 1"}, {"option_id": "C", "text": "2 -> 3 -> 4 -> 1"}, {"option_id": "D", "text": "4 -> 2 -> 3 -> 1"}], "correct_option_id": "A", "expected_answer": "4 -> 3 -> 2 -> 1", "source_chunk_ids": ["httpie__cli__release__2_0_0", "httpie__cli__release__2_3_0", "httpie__cli__release__2_5_0", "httpie__cli__release__3_0_0"], "answer_support": [{"memory_node_id": "httpie__cli__release__2_0_0", "answer_text": "Added --offline to allow building an HTTP request and printing it but not actually sending it over the network."}, {"memory_node_id": "httpie__cli__release__2_3_0", "answer_text": "Added support for streamed uploads, multipart upload streaming"}, {"memory_node_id": "httpie__cli__release__2_5_0", "answer_text": "Added --raw to allow specifying the raw request body without extra processing"}, {"memory_node_id": "httpie__cli__release__3_0_0", "answer_text": "Added support for nested JSON syntax, added httpie plugins interface for plugin management"}]}
{"prototype_id": "huggingface__transformers_release_window", "repo": "huggingface/transformers", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the huggingface/transformers releases, which release introduces the Vault-Gemma model as a preview with differential privacy training?", "options": [{"option_id": "A", "text": "v4.57.0"}, {"option_id": "B", "text": "v4.56.1-Vault-Gemma-preview"}, {"option_id": "C", "text": "v5.0.0rc0"}, {"option_id": "D", "text": "v5.1.0"}], "correct_option_id": "B", "expected_answer": "v4.56.1-Vault-Gemma-preview", "source_chunk_ids": ["huggingface__transformers__release__v4_56_1_vault_gemma_preview"], "answer_support": [{"memory_node_id": "huggingface__transformers__release__v4_56_1_vault_gemma_preview", "answer_text": "A new model is added to transformers: Vault-Gemma ... trained from scratch with sequence-level differential privacy (DP)"}]}
{"prototype_id": "huggingface__transformers_release_window", "repo": "huggingface/transformers", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the huggingface/transformers releases, how does the model addition in v5.1.0 differ from the model addition in v5.2.0?", "options": [{"option_id": "A", "text": "v5.1.0 adds EXAONE-MoE, while v5.2.0 adds GLM-5."}, {"option_id": "B", "text": "v5.1.0 adds Qwen3.5, while v5.2.0 adds EXAONE-MoE."}, {"option_id": "C", "text": "Both releases add the same set of models."}, {"option_id": "D", "text": "v5.1.0 adds VoxtralRealtime, while v5.2.0 adds PP-DocLayoutV3."}], "correct_option_id": "A", "expected_answer": "v5.1.0 adds EXAONE-MoE, while v5.2.0 adds GLM-5.", "source_chunk_ids": ["huggingface__transformers__release__v5_1_0", "huggingface__transformers__release__v5_2_0"], "answer_support": [{"memory_node_id": "huggingface__transformers__release__v5_1_0", "answer_text": "New Model additions ### EXAONE-MoE"}, {"memory_node_id": "huggingface__transformers__release__v5_2_0", "answer_text": "New Model additions ### GLM-5 - GlmMoeDsa"}]}
{"prototype_id": "huggingface__transformers_release_window", "repo": "huggingface/transformers", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the huggingface/transformers release window, order the following release-content states from earliest to latest: (1) a release that adds the Vault-Gemma model as a preview, (2) a release that introduces the dynamic weight loading API as a release candidate, (3) a release that adds the DeepSeek-V4 model.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["huggingface__transformers__release__v4_56_1_vault_gemma_preview", "huggingface__transformers__release__v5_0_0rc0", "huggingface__transformers__release__v5_8_0"], "answer_support": [{"memory_node_id": "huggingface__transformers__release__v4_56_1_vault_gemma_preview", "answer_text": "A new model is added to transformers: Vault-Gemma"}, {"memory_node_id": "huggingface__transformers__release__v5_0_0rc0", "answer_text": "We introduce a new weight loading API in transformers"}, {"memory_node_id": "huggingface__transformers__release__v5_8_0", "answer_text": "DeepSeek-V4 is the next-generation MoE language model"}]}
{"prototype_id": "hyprwm__Hyprland_release_window", "repo": "hyprwm/Hyprland", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the hyprwm/Hyprland releases, which release introduces the `toggleswallow` dispatcher?", "options": [{"option_id": "A", "text": "v0.47.0"}, {"option_id": "B", "text": "v0.48.0"}, {"option_id": "C", "text": "v0.49.0"}, {"option_id": "D", "text": "v0.50.0"}], "correct_option_id": "B", "expected_answer": "v0.48.0", "source_chunk_ids": ["hyprwm__Hyprland__release__v0_48_0"], "answer_support": [{"memory_node_id": "hyprwm__Hyprland__release__v0_48_0", "answer_text": "keybinds: Added `toggleswallow` dispatcher (#5548)"}]}
{"prototype_id": "hyprwm__Hyprland_release_window", "repo": "hyprwm/Hyprland", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the hyprwm/Hyprland releases, how does the change to `master:always_center_master` in v0.47.0 differ from the change to `master:center_master_slaves_on_right` in v0.49.0?", "options": [{"option_id": "A", "text": "v0.47.0 replaces `master:always_center_master` with `master:slave_count_for_center_master`, while v0.49.0 changes `master:center_master_slaves_on_right` to `master:center_master_fallback` providing more options than just right."}, {"option_id": "B", "text": "v0.47.0 removes `master:always_center_master` entirely, while v0.49.0 adds `master:center_master_slaves_on_right` as a new feature."}, {"option_id": "C", "text": "Both releases introduce the same master layout change but under different version numbers."}, {"option_id": "D", "text": "v0.47.0 deprecates `master:center_master_slaves_on_right`, and v0.49.0 removes `master:always_center_master`."}], "correct_option_id": "A", "expected_answer": "v0.47.0 replaces `master:always_center_master` with `master:slave_count_for_center_master`, while v0.49.0 changes `master:center_master_slaves_on_right` to `master:center_master_fallback` providing more options than just right.", "source_chunk_ids": ["hyprwm__Hyprland__release__v0_47_0", "hyprwm__Hyprland__release__v0_49_0"], "answer_support": [{"memory_node_id": "hyprwm__Hyprland__release__v0_47_0", "answer_text": "Breaking changes: `master:always_center_master` has been replaced with a more flexible `master:slave_count_for_center_master`"}, {"memory_node_id": "hyprwm__Hyprland__release__v0_49_0", "answer_text": "Breaking changes: `master:center_master_slaves_on_right` has been changed to `master:center_master_fallback` providing more options than just right."}]}
{"prototype_id": "hyprwm__Hyprland_release_window", "repo": "hyprwm/Hyprland", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the hyprwm/Hyprland release window, order the following release-content states from earliest to latest: (1) a release that adds the `toggleswallow` dispatcher, (2) a release that introduces the `sendkeystate` dispatcher, (3) a release that adds the `forceidle` dispatcher.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["hyprwm__Hyprland__release__v0_48_0", "hyprwm__Hyprland__release__v0_49_0", "hyprwm__Hyprland__release__v0_52_0"], "answer_support": [{"memory_node_id": "hyprwm__Hyprland__release__v0_48_0", "answer_text": "keybinds: Added `toggleswallow` dispatcher (#5548)"}, {"memory_node_id": "hyprwm__Hyprland__release__v0_49_0", "answer_text": "keybinds: add sendkeystate dispatcher (#9599)"}, {"memory_node_id": "hyprwm__Hyprland__release__v0_52_0", "answer_text": "dispatchers: add forceidle (#11922)"}]}
{"prototype_id": "iamgio__quarkdown_release_window", "repo": "iamgio/quarkdown", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the iamgio/quarkdown releases, which release introduces a bibliography feature?", "options": [{"option_id": "A", "text": "v1.4.0"}, {"option_id": "B", "text": "v1.5.0"}, {"option_id": "C", "text": "v1.6.0"}, {"option_id": "D", "text": "v1.7.0"}], "correct_option_id": "B", "expected_answer": "v1.5.0", "source_chunk_ids": ["iamgio__quarkdown__release__v1_5_0"], "answer_support": [{"memory_node_id": "iamgio__quarkdown__release__v1_5_0", "answer_text": "a bibliography feature is introduced"}]}
{"prototype_id": "iamgio__quarkdown_release_window", "repo": "iamgio/quarkdown", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the iamgio/quarkdown release window, order the following release-content states from earliest to latest: (1) a release that adds a bibliography feature, (2) a release that introduces CSL bibliography styles and multi-key citations, (3) a release that adds a permission system and line continuation in function calls.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["iamgio__quarkdown__release__v1_5_0", "iamgio__quarkdown__release__v1_15_0", "iamgio__quarkdown__release__v2_0_0"], "answer_support": [{"memory_node_id": "iamgio__quarkdown__release__v1_5_0", "answer_text": "a bibliography feature is introduced"}, {"memory_node_id": "iamgio__quarkdown__release__v1_15_0", "answer_text": "CSL bibliography styles are introduced (breaking change), multi-key citations are supported"}, {"memory_node_id": "iamgio__quarkdown__release__v2_0_0", "answer_text": "a permission system is introduced, line continuation in function calls is supported"}]}
{"prototype_id": "ianstormtaylor__slate_release_window", "repo": "ianstormtaylor/slate", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the ianstormtaylor/slate releases, which release adds the splitDecorationsByChild function to split an array of decorated ranges by child index?", "options": [{"option_id": "A", "text": "slate-dom@0.116.0"}, {"option_id": "B", "text": "slate-react@0.116.0"}, {"option_id": "C", "text": "slate@0.116.0"}, {"option_id": "D", "text": "slate-dom@0.117.4"}], "correct_option_id": "A", "expected_answer": "slate-dom@0.116.0", "source_chunk_ids": ["ianstormtaylor__slate__release__slate_dom_0_116_0"], "answer_support": [{"memory_node_id": "ianstormtaylor__slate__release__slate_dom_0_116_0", "answer_text": "adds splitDecorationsByChild to split an array of decorated ranges by child index"}]}
{"prototype_id": "ianstormtaylor__slate_release_window", "repo": "ianstormtaylor/slate", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the ianstormtaylor/slate releases, how does the performance-related change in slate@0.116.0 differ from the performance-related change in slate-react@0.116.0?", "options": [{"option_id": "A", "text": "slate@0.116.0 replaces Immer with pure JS for operations and transforms, while slate-react@0.116.0 introduces an experimental chunking optimization and a subscribable pattern to reduce re-renders."}, {"option_id": "B", "text": "slate@0.116.0 adds splitDecorationsByChild, while slate-react@0.116.0 removes Immer."}, {"option_id": "C", "text": "Both releases only update peer dependencies without performance changes."}, {"option_id": "D", "text": "slate@0.116.0 deprecates useSlateWithV, while slate-react@0.116.0 adds useElement hooks."}], "correct_option_id": "A", "expected_answer": "slate@0.116.0 replaces Immer with pure JS for operations and transforms, while slate-react@0.116.0 introduces an experimental chunking optimization and a subscribable pattern to reduce re-renders.", "source_chunk_ids": ["ianstormtaylor__slate__release__slate_0_116_0", "ianstormtaylor__slate__release__slate_react_0_116_0"], "answer_support": [{"memory_node_id": "ianstormtaylor__slate__release__slate_0_116_0", "answer_text": "PERF: Use pure JS instead of Immer for applying operations and transforming points and ranges"}, {"memory_node_id": "ianstormtaylor__slate__release__slate_react_0_116_0", "answer_text": "Implement experimental chunking optimization ... PERF: Use subscribable pattern for useSlate, useSelected and decorations to reduce re-renders"}]}
{"prototype_id": "iina__iina_release_window", "repo": "iina/iina", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the iina/iina releases, how does the HDR support described in IINA 1.3.0 differ from the HDR-related changes described in IINA 1.3.1?", "options": [{"option_id": "A", "text": "1.3.0 adds HDR support for M1 Pro/Max MacBooks, while 1.3.1 adds an option to control whether HDR support is enabled by default and fixes HDR sometimes not working and HDR video becoming dark in full screen in macOS Ventura."}, {"option_id": "B", "text": "1.3.0 removes HDR support entirely, while 1.3.1 reintroduces it with tone mapping settings."}, {"option_id": "C", "text": "Both releases only update FFmpeg without any HDR-specific changes."}, {"option_id": "D", "text": "1.3.0 adds HDR support for all Macs, while 1.3.1 adds HDR support for M1 Pro/Max MacBooks."}], "correct_option_id": "A", "expected_answer": "1.3.0 adds HDR support for M1 Pro/Max MacBooks, while 1.3.1 adds an option to control whether HDR support is enabled by default and fixes HDR sometimes not working and HDR video becoming dark in full screen in macOS Ventura.", "source_chunk_ids": ["iina__iina__release__v1_3_0", "iina__iina__release__v1_3_1"], "answer_support": [{"memory_node_id": "iina__iina__release__v1_3_0", "answer_text": "Added HDR support for M1 Pro/Max Macbook 14/16"}, {"memory_node_id": "iina__iina__release__v1_3_1", "answer_text": "You can now control whether HDR support is enabled by default in the preferences ... Fixed HDR sometimes not working ... Fixed HDR video becoming dark in full screen in macOS Ventura"}]}
{"prototype_id": "immich_app__immich_release_window", "repo": "immich-app/immich", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the immich-app/immich releases, which release introduces Optical Character Recognition (OCR) and a mutable Docker tag for v2 versions?", "options": [{"option_id": "A", "text": "v2.0.0"}, {"option_id": "B", "text": "v2.2.0"}, {"option_id": "C", "text": "v2.3.0"}, {"option_id": "D", "text": "v2.5.0"}], "correct_option_id": "B", "expected_answer": "v2.2.0", "source_chunk_ids": ["immich_app__immich__release__v2_2_0"], "answer_support": [{"memory_node_id": "immich_app__immich__release__v2_2_0", "answer_text": "introduces a mutable Docker tag for v2 versions, Optical Character Recognition (OCR)"}]}
{"prototype_id": "immich_app__immich_release_window", "repo": "immich-app/immich", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the immich-app/immich release window, order the following release-content states from earliest to latest: (1) a release that adds a command palette and shows the owner's name in shared albums, (2) a release that introduces Free Up Space and non-destructive editing, (3) a release that adds a map side panel on web and native HTTP clients on mobile.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["immich_app__immich__release__v2_4_0", "immich_app__immich__release__v2_5_0", "immich_app__immich__release__v2_6_0"], "answer_support": [{"memory_node_id": "immich_app__immich__release__v2_4_0", "answer_text": "command palette ... show the owner's name in the shared album"}, {"memory_node_id": "immich_app__immich__release__v2_5_0", "answer_text": "Free Up Space ... Non-destructive editing"}, {"memory_node_id": "immich_app__immich__release__v2_6_0", "answer_text": "Map side panel (web) ... Native HTTP clients (mobile)"}]}
{"prototype_id": "influxdata__influxdb_release_window", "repo": "influxdata/influxdb", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the influxdata/influxdb releases, which release introduces optional token hashing and provides a recommended two-step upgrade process?", "options": [{"option_id": "A", "text": "v2.7.12"}, {"option_id": "B", "text": "v2.8.0"}, {"option_id": "C", "text": "v2.9.0"}, {"option_id": "D", "text": "v3.0.0"}], "correct_option_id": "B", "expected_answer": "v2.8.0", "source_chunk_ids": ["influxdata__influxdb__release__v2_8_0"], "answer_support": [{"memory_node_id": "influxdata__influxdb__release__v2_8_0", "answer_text": "Features include adding optional token hashing... The release notes provide detailed guidance on upgrading and enabling token hashing, including a recommended two-step process"}]}
{"prototype_id": "influxdata__influxdb_release_window", "repo": "influxdata/influxdb", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the influxdata/influxdb releases, how does the token-related change in v2.8.0 differ from the token-related change in v3.0.3?", "options": [{"option_id": "A", "text": "v2.8.0 introduces optional token hashing, while v3.0.3 prevents operator tokens from being deleted."}, {"option_id": "B", "text": "v2.8.0 prevents operator tokens from being deleted, while v3.0.3 introduces optional token hashing."}, {"option_id": "C", "text": "Both releases introduce token hashing."}, {"option_id": "D", "text": "Both releases prevent operator tokens from being deleted."}], "correct_option_id": "A", "expected_answer": "v2.8.0 introduces optional token hashing, while v3.0.3 prevents operator tokens from being deleted.", "source_chunk_ids": ["influxdata__influxdb__release__v2_8_0", "influxdata__influxdb__release__v3_0_3"], "answer_support": [{"memory_node_id": "influxdata__influxdb__release__v2_8_0", "answer_text": "Features include adding optional token hashing"}, {"memory_node_id": "influxdata__influxdb__release__v3_0_3", "answer_text": "Operator tokens can no longer be deleted."}]}
{"prototype_id": "influxdata__influxdb_release_window", "repo": "influxdata/influxdb", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the influxdata/influxdb release window, order the following release-content states from earliest to latest: (1) a release that adds optional token hashing, (2) a release that enables token hashing by default, (3) a release that fixes level 3 compactions stop occurring.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["influxdata__influxdb__release__v2_8_0", "influxdata__influxdb__release__v2_9_0", "influxdata__influxdb__release__v2_9_1"], "answer_support": [{"memory_node_id": "influxdata__influxdb__release__v2_8_0", "answer_text": "Features include adding optional token hashing"}, {"memory_node_id": "influxdata__influxdb__release__v2_9_0", "answer_text": "Features include ... enabling token hashing by default"}, {"memory_node_id": "influxdata__influxdb__release__v2_9_1", "answer_text": "Bug fixes for level 3 compactions stop occurring"}]}
{"prototype_id": "ionic_team__ionic_framework_release_window", "repo": "ionic-team/ionic-framework", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the ionic-team/ionic-framework releases, which release adds CSS utility classes for display and flex, updates ionicons to v8, and introduces ionReorderStart, ionReorderMove, and ionReorderEnd events?", "options": [{"option_id": "A", "text": "v8.6.7"}, {"option_id": "B", "text": "v8.7.0"}, {"option_id": "C", "text": "v8.7.1"}, {"option_id": "D", "text": "v8.8.0"}], "correct_option_id": "B", "expected_answer": "v8.7.0", "source_chunk_ids": ["ionic_team__ionic_framework__release__v8_7_0"], "answer_support": [{"memory_node_id": "ionic_team__ionic_framework__release__v8_7_0", "answer_text": "new features include CSS utility classes for display and flex, an update to ionicons v8, and ionReorderStart, ionReorderMove, ionReorderEnd events for reorder-group"}]}
{"prototype_id": "ionic_team__ionic_framework_release_window", "repo": "ionic-team/ionic-framework", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the ionic-team/ionic-framework releases, how does the change to @stencil/core in v8.6.7 differ from the change to @stencil/core in v8.7.1?", "options": [{"option_id": "A", "text": "v8.6.7 downgrades @stencil/core to 4.33.1 due to a Reorder regression, while v8.7.1 upgrades it to 4.36.2."}, {"option_id": "B", "text": "v8.6.7 upgrades @stencil/core to 4.36.2, while v8.7.1 downgrades it to 4.33.1."}, {"option_id": "C", "text": "Both releases upgrade @stencil/core to 4.36.2."}, {"option_id": "D", "text": "v8.6.7 removes @stencil/core, while v8.7.1 adds it back."}], "correct_option_id": "A", "expected_answer": "v8.6.7 downgrades @stencil/core to 4.33.1 due to a Reorder regression, while v8.7.1 upgrades it to 4.36.2.", "source_chunk_ids": ["ionic_team__ionic_framework__release__v8_6_7", "ionic_team__ionic_framework__release__v8_7_1"], "answer_support": [{"memory_node_id": "ionic_team__ionic_framework__release__v8_6_7", "answer_text": "the @stencil/core dependency is downgraded to version 4.33.1 due to an uncaught regression in Reorder"}, {"memory_node_id": "ionic_team__ionic_framework__release__v8_7_1", "answer_text": "the @stencil/core dependency is upgraded again to version 4.36.2"}]}
{"prototype_id": "ionic_team__ionic_framework_release_window", "repo": "ionic-team/ionic-framework", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the ionic-team/ionic-framework release window, order the following release-content states from earliest to latest: (1) a release that adds a children fallback in reorder-group for framework compatibility, (2) a release that adds CSS utility classes for display and flex, (3) a release that adds drag events for sheet and card modals, (4) a release that prevents scroll assist from firing duplicate click events in input.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "B", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "C", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "D", "text": "1 -> 2 -> 3 -> 4"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3 -> 4", "source_chunk_ids": ["ionic_team__ionic_framework__release__v8_7_0", "ionic_team__ionic_framework__release__v8_7_2", "ionic_team__ionic_framework__release__v8_8_0", "ionic_team__ionic_framework__release__v8_8_7"], "answer_support": [{"memory_node_id": "ionic_team__ionic_framework__release__v8_7_0", "answer_text": "new features include CSS utility classes for display and flex"}, {"memory_node_id": "ionic_team__ionic_framework__release__v8_7_2", "answer_text": "adding a children fallback in reorder-group for framework compatibility"}, {"memory_node_id": "ionic_team__ionic_framework__release__v8_8_0", "answer_text": "drag events for sheet and card modals"}, {"memory_node_id": "ionic_team__ionic_framework__release__v8_8_7", "answer_text": "prevent scroll assist from firing duplicate click events in input"}]}
{"prototype_id": "jeecgboot__JeecgBoot_release_window", "repo": "jeecgboot/JeecgBoot", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the jeecgboot/JeecgBoot releases, which release introduces a full suite of AI large model features including AI model management, AI applications, knowledge base, and AI process orchestration?", "options": [{"option_id": "A", "text": "v3.7.3"}, {"option_id": "B", "text": "v3.8.0"}, {"option_id": "C", "text": "v3.9.0"}, {"option_id": "D", "text": "v3.9.1"}], "correct_option_id": "B", "expected_answer": "v3.8.0", "source_chunk_ids": ["jeecgboot__JeecgBoot__release__v3_8_0"], "answer_support": [{"memory_node_id": "jeecgboot__JeecgBoot__release__v3_8_0", "answer_text": "introduces a full suite of AI large model features including AI model management, AI applications, knowledge base, AI process orchestration, and AI chat assistant"}]}
{"prototype_id": "jeecgboot__JeecgBoot_release_window", "repo": "jeecgboot/JeecgBoot", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the jeecgboot/JeecgBoot releases, how does the AI integration described in v3.6.3 differ from the AI platform introduced in v3.8.0?", "options": [{"option_id": "A", "text": "v3.6.3 integrates ChatGPT for an AI assistant chat feature, while v3.8.0 introduces a full suite of AI large model features including model management, applications, knowledge base, and process orchestration."}, {"option_id": "B", "text": "v3.6.3 removes all AI features, while v3.8.0 adds them back."}, {"option_id": "C", "text": "Both releases only upgrade frontend dependencies without AI changes."}, {"option_id": "D", "text": "v3.6.3 introduces AI process orchestration, while v3.8.0 focuses on dashboard templates."}], "correct_option_id": "A", "expected_answer": "v3.6.3 integrates ChatGPT for an AI assistant chat feature, while v3.8.0 introduces a full suite of AI large model features including model management, applications, knowledge base, and process orchestration.", "source_chunk_ids": ["jeecgboot__JeecgBoot__release__v3_6_3", "jeecgboot__JeecgBoot__release__v3_8_0"], "answer_support": [{"memory_node_id": "jeecgboot__JeecgBoot__release__v3_6_3", "answer_text": "integrates with ChatGPT, introducing an AI assistant chat feature"}, {"memory_node_id": "jeecgboot__JeecgBoot__release__v3_8_0", "answer_text": "introduces a full suite of AI large model features including AI model management, AI applications, knowledge base, AI process orchestration, and AI chat assistant"}]}
{"prototype_id": "jeecgboot__JeecgBoot_release_window", "repo": "jeecgboot/JeecgBoot", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the jeecgboot/JeecgBoot release window, order the following release-content states from earliest to latest: (1) a release that upgrades ant-design-vue to 4.0.8 and adds flyway automatic database upgrade, (2) a release that introduces a full suite of AI large model features including AI model management and knowledge base, (3) a release that upgrades langchain4j to 1.3.0 and adds MCP and plugin support, (4) a release that evolves the low-code platform to v2.0 with Skills integration and natural language-driven development.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["jeecgboot__JeecgBoot__release__v3_6_2", "jeecgboot__JeecgBoot__release__v3_8_0", "jeecgboot__JeecgBoot__release__v3_9_0", "jeecgboot__JeecgBoot__release__v3_9_2"], "answer_support": [{"memory_node_id": "jeecgboot__JeecgBoot__release__v3_6_2", "answer_text": "upgrades ant-design-vue to 4.0.8, adds flyway automatic database upgrade mechanism"}, {"memory_node_id": "jeecgboot__JeecgBoot__release__v3_8_0", "answer_text": "introduces a full suite of AI large model features including AI model management, AI applications, knowledge base"}, {"memory_node_id": "jeecgboot__JeecgBoot__release__v3_9_0", "answer_text": "langchain4j is upgraded to 1.3.0, AI features are enhanced with MCP and plugin support"}, {"memory_node_id": "jeecgboot__JeecgBoot__release__v3_9_2", "answer_text": "low-code platform evolves to v2.0 with Skills integration, enabling natural language-driven development"}]}
{"prototype_id": "jekyll__jekyll_release_window", "repo": "jekyll/jekyll", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the jekyll/jekyll releases, which release adds the :post_convert hook to modify HTML content before layout?", "options": [{"option_id": "A", "text": "v4.1.0"}, {"option_id": "B", "text": "v4.2.0"}, {"option_id": "C", "text": "v4.3.0"}, {"option_id": "D", "text": "v4.4.0"}], "correct_option_id": "B", "expected_answer": "v4.2.0", "source_chunk_ids": ["jekyll__jekyll__release__v4_2_0"], "answer_support": [{"memory_node_id": "jekyll__jekyll__release__v4_2_0", "answer_text": "adding :post_convert hook to modify HTML content before layout"}]}
{"prototype_id": "jesseduffield__lazydocker_release_window", "repo": "jesseduffield/lazydocker", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the jesseduffield/lazydocker releases, which release introduces a networks view and allows configuring the number of logs to tail?", "options": [{"option_id": "A", "text": "v0.19.0"}, {"option_id": "B", "text": "v0.20.0"}, {"option_id": "C", "text": "v0.21.0"}, {"option_id": "D", "text": "v0.23.0"}], "correct_option_id": "C", "expected_answer": "v0.21.0", "source_chunk_ids": ["jesseduffield__lazydocker__release__v0_21_0"], "answer_support": [{"memory_node_id": "jesseduffield__lazydocker__release__v0_21_0", "answer_text": "add a networks view, allow configuring the number of logs to tail"}]}
{"prototype_id": "jesseduffield__lazydocker_release_window", "repo": "jesseduffield/lazydocker", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the jesseduffield/lazydocker releases, how does the CPU usage improvement described in v0.17.1 differ from the CPU-related change in v0.8?", "options": [{"option_id": "A", "text": "v0.17.1 reduces CPU usage by using Docker's event stream to avoid polling, while v0.8 reduces CPU usage caused by tickers."}, {"option_id": "B", "text": "v0.17.1 removes all tickers, while v0.8 adds more tickers for better monitoring."}, {"option_id": "C", "text": "Both releases achieve CPU reduction by removing the Docker binary dependency."}, {"option_id": "D", "text": "v0.17.1 focuses on memory optimization, while v0.8 focuses on disk I/O reduction."}], "correct_option_id": "A", "expected_answer": "v0.17.1 reduces CPU usage by using Docker's event stream to avoid polling, while v0.8 reduces CPU usage caused by tickers.", "source_chunk_ids": ["jesseduffield__lazydocker__release__v0_17_1", "jesseduffield__lazydocker__release__v0_8"], "answer_support": [{"memory_node_id": "jesseduffield__lazydocker__release__v0_17_1", "answer_text": "CPU usage is now under control ... using Docker's event stream to avoid polling for changes"}, {"memory_node_id": "jesseduffield__lazydocker__release__v0_8", "answer_text": "reduce cpu usage caused by tickers"}]}
{"prototype_id": "jesseduffield__lazydocker_release_window", "repo": "jesseduffield/lazydocker", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the jesseduffield/lazydocker release window, order the following release-content states from earliest to latest: (1) a release that adds a health check to the container list and corrects Dutch typos, (2) a release that adds a networks view and allows configuring the number of logs to tail, (3) a release that properly supports remote Docker daemon over SSH and uses 'docker compose' by default, (4) a release that fixes a panic by validating Names slice length and upgrades Go to 1.23.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["jesseduffield__lazydocker__release__v0_10", "jesseduffield__lazydocker__release__v0_21_0", "jesseduffield__lazydocker__release__v0_24_1", "jesseduffield__lazydocker__release__v0_24_3"], "answer_support": [{"memory_node_id": "jesseduffield__lazydocker__release__v0_10", "answer_text": "add a health check to the container list ... Corrected some typos dutch"}, {"memory_node_id": "jesseduffield__lazydocker__release__v0_21_0", "answer_text": "Add networks view ... Allow configuring number of logs to tail"}, {"memory_node_id": "jesseduffield__lazydocker__release__v0_24_1", "answer_text": "fix: Properly support remote docker daemon over ssh ... Use 'docker compose' by default"}, {"memory_node_id": "jesseduffield__lazydocker__release__v0_24_3", "answer_text": "Fix panic: validate Names slice length ... Upgrade Go version from 1.21 to 1.23"}]}
{"prototype_id": "jesseduffield__lazygit_release_window", "repo": "jesseduffield/lazygit", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the jesseduffield/lazygit releases, which release introduces per-repo config files with automatic reloading and the ability to view diff across a range of commits?", "options": [{"option_id": "A", "text": "v0.44.0"}, {"option_id": "B", "text": "v0.45.0"}, {"option_id": "C", "text": "v0.46.0"}, {"option_id": "D", "text": "v0.47.2"}], "correct_option_id": "A", "expected_answer": "v0.44.0", "source_chunk_ids": ["jesseduffield__lazygit__release__v0_44_0"], "answer_support": [{"memory_node_id": "jesseduffield__lazygit__release__v0_44_0", "answer_text": "enhancements include per-repo config files with automatic reloading, viewing diff across a range of commits"}]}
{"prototype_id": "jesseduffield__lazygit_release_window", "repo": "jesseduffield/lazygit", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the jesseduffield/lazygit releases, how does the change to the default selection mode in staging described in v0.54.0 differ from the hunk selection improvement described in v0.53.0?", "options": [{"option_id": "A", "text": "v0.53.0 improves hunk selection mode in staging view and adds a user config to use it by default, while v0.54.0 changes the default to hunk mode and also changes branch sort order defaults."}, {"option_id": "B", "text": "v0.53.0 removes hunk mode entirely, while v0.54.0 reintroduces it as the only option."}, {"option_id": "C", "text": "Both releases only fix crashes in the staging view without changing selection behavior."}, {"option_id": "D", "text": "v0.53.0 makes hunk mode mandatory, while v0.54.0 makes line mode mandatory."}], "correct_option_id": "A", "expected_answer": "v0.53.0 improves hunk selection mode in staging view and adds a user config to use it by default, while v0.54.0 changes the default to hunk mode and also changes branch sort order defaults.", "source_chunk_ids": ["jesseduffield__lazygit__release__v0_53_0", "jesseduffield__lazygit__release__v0_54_0"], "answer_support": [{"memory_node_id": "jesseduffield__lazygit__release__v0_53_0", "answer_text": "improving hunk selection mode in the staging view, and adding a user config to use hunk mode by default when entering the staging view"}, {"memory_node_id": "jesseduffield__lazygit__release__v0_54_0", "answer_text": "changing the default selection mode in staging and custom patch building views to hunk mode"}]}
{"prototype_id": "jesseduffield__lazygit_release_window", "repo": "jesseduffield/lazygit", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the jesseduffield/lazygit release window, order the following release-content states from earliest to latest: (1) a release that adds custom commands submenus, (2) a release that introduces per-repo config files with automatic reloading, (3) a release that adds support for GitHub pull requests shown as icons next to branches, (4) a release that revamps the keybinding mechanism to support richer keybindings.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "B", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "C", "text": "2 -> 3 -> 1 -> 4"}, {"option_id": "D", "text": "3 -> 2 -> 4 -> 1"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3 -> 4", "source_chunk_ids": ["jesseduffield__lazygit__release__v0_44_0", "jesseduffield__lazygit__release__v0_48_0", "jesseduffield__lazygit__release__v0_61_0", "jesseduffield__lazygit__release__v0_62_0"], "answer_support": [{"memory_node_id": "jesseduffield__lazygit__release__v0_44_0", "answer_text": "per-repo config files with automatic reloading"}, {"memory_node_id": "jesseduffield__lazygit__release__v0_48_0", "answer_text": "custom commands submenus"}, {"memory_node_id": "jesseduffield__lazygit__release__v0_61_0", "answer_text": "support for GitHub pull requests, shown as GitHub icons next to branches"}, {"memory_node_id": "jesseduffield__lazygit__release__v0_62_0", "answer_text": "keybinding revamp allowing richer keybindings"}]}
{"prototype_id": "jestjs__jest_release_window", "repo": "jestjs/jest", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the jestjs/jest releases, which release adds support for Sapling in jest-changed-files and introduces a feature to randomize test order via CLI flag or config?", "options": [{"option_id": "A", "text": "v29.4.3"}, {"option_id": "B", "text": "v29.5.0"}, {"option_id": "C", "text": "v29.6.0"}, {"option_id": "D", "text": "v29.7.0"}], "correct_option_id": "B", "expected_answer": "v29.5.0", "source_chunk_ids": ["jestjs__jest__release__v29_5_0"], "answer_support": [{"memory_node_id": "jestjs__jest__release__v29_5_0", "answer_text": "adds support for Sapling in jest-changed-files, introduces a feature to randomize test order via CLI flag or config"}]}
{"prototype_id": "jestjs__jest_release_window", "repo": "jestjs/jest", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the jestjs/jest release window, order the following release-content states from earliest to latest: (1) a release that adds support for snapshot matchers in concurrent tests, (2) a release that adds a retryImmediately option to jest.retryTimes, (3) a release that adds an option excludeJestPreset to allow opting out of babel-preset-jest in babel-jest, (4) a release that announces the release of Jest 30 with renamed globalsCleanupMode to globalsCleanup.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["jestjs__jest__release__v29_6_0", "jestjs__jest__release__v30_0_0_alpha_4", "jestjs__jest__release__v30_0_0_alpha_6", "jestjs__jest__release__v30_0_0"], "answer_support": [{"memory_node_id": "jestjs__jest__release__v29_6_0", "answer_text": "Add support for snapshot matchers in concurrent tests"}, {"memory_node_id": "jestjs__jest__release__v30_0_0_alpha_4", "answer_text": "Add a retryImmediately option to jest.retryTimes"}, {"memory_node_id": "jestjs__jest__release__v30_0_0_alpha_6", "answer_text": "Add option excludeJestPreset to allow opting out of babel-preset-jest in babel-jest"}, {"memory_node_id": "jestjs__jest__release__v30_0_0", "answer_text": "announces the release of Jest 30 ... Renamed globalsCleanupMode to globalsCleanup"}]}
{"prototype_id": "JetBrains__kotlin_release_window", "repo": "JetBrains/kotlin", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the JetBrains/kotlin releases, how does the Compose compiler change in Kotlin 2.4.0-RC2 differ from the Compose compiler change in Kotlin 2.3.20-RC?", "options": [{"option_id": "A", "text": "2.4.0-RC2 changes the default stability of non-final classes to Unknown, while 2.3.20-RC caches stability inference results during session."}, {"option_id": "B", "text": "Both releases fix the same issue with lambda memoization in local classes."}, {"option_id": "C", "text": "2.4.0-RC2 adds groups to inline functions, while 2.3.20-RC removes groups from inline functions."}, {"option_id": "D", "text": "2.4.0-RC2 fixes a codegen crash in inline functions, while 2.3.20-RC fixes a platform declaration clash on iOS."}], "correct_option_id": "A", "expected_answer": "2.4.0-RC2 changes the default stability of non-final classes to Unknown, while 2.3.20-RC caches stability inference results during session.", "source_chunk_ids": ["JetBrains__kotlin__release__v2_4_0_rc2", "JetBrains__kotlin__release__v2_3_20_rc"], "answer_support": [{"memory_node_id": "JetBrains__kotlin__release__v2_4_0_rc2", "answer_text": "Compose compiler: Made the default stability of non-final classes Unknown instead of Stable"}, {"memory_node_id": "JetBrains__kotlin__release__v2_3_20_rc", "answer_text": "Compose compiler: Cache stability inference results during session"}]}
{"prototype_id": "jgraph__drawio_desktop_release_window", "repo": "jgraph/drawio-desktop", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the jgraph/drawio-desktop releases, which release replaces the Windows non-installer with a zip of the exe?", "options": [{"option_id": "A", "text": "26.0.15"}, {"option_id": "B", "text": "27.0.9"}, {"option_id": "C", "text": "28.0.4"}, {"option_id": "D", "text": "29.0.3"}], "correct_option_id": "B", "expected_answer": "27.0.9", "source_chunk_ids": ["jgraph__drawio_desktop__release__v27_0_9"], "answer_support": [{"memory_node_id": "jgraph__drawio_desktop__release__v27_0_9", "answer_text": "replaces the Windows non-installer with a zip of the exe (issue #2039)"}]}
{"prototype_id": "jgraph__drawio_desktop_release_window", "repo": "jgraph/drawio-desktop", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the jgraph/drawio-desktop releases, how does the Electron version used in release 26.0.15 differ from the Electron version used in release 28.2.8?", "options": [{"option_id": "A", "text": "26.0.15 uses Electron 34.2.0, while 28.2.8 uses Electron 38.4.0."}, {"option_id": "B", "text": "26.0.15 uses Electron 32.2.5, while 28.2.8 uses Electron 35.1.2."}, {"option_id": "C", "text": "Both releases use Electron 37.2.1."}, {"option_id": "D", "text": "26.0.15 uses Electron 35.2.1, while 28.2.8 uses Electron 37.7.1."}], "correct_option_id": "A", "expected_answer": "26.0.15 uses Electron 34.2.0, while 28.2.8 uses Electron 38.4.0.", "source_chunk_ids": ["jgraph__drawio_desktop__release__v26_0_15", "jgraph__drawio_desktop__release__v28_2_8"], "answer_support": [{"memory_node_id": "jgraph__drawio_desktop__release__v26_0_15", "answer_text": "uses Electron 34.2.0"}, {"memory_node_id": "jgraph__drawio_desktop__release__v28_2_8", "answer_text": "uses Electron 38.4.0"}]}
{"prototype_id": "jgraph__drawio_desktop_release_window", "repo": "jgraph/drawio-desktop", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the jgraph/drawio-desktop release window, order the following release-content states from earliest to latest: (1) a release that updates to draw.io core 26.0.15 and uses Electron 34.2.0, (2) a release that addresses issues #2058 and #2059 and uses Electron 35.3.0, (3) a release that fixes a PDF title issue and uses Electron 37.2.1, (4) a release that introduces adaptive colours as default for new installs and uses Electron 42.0.1.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "3 -> 1 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["jgraph__drawio_desktop__release__v26_0_15", "jgraph__drawio_desktop__release__v27_0_2", "jgraph__drawio_desktop__release__v28_0_4", "jgraph__drawio_desktop__release__v30_0_0"], "answer_support": [{"memory_node_id": "jgraph__drawio_desktop__release__v26_0_15", "answer_text": "updates to draw.io core 26.0.15 and uses Electron 34.2.0"}, {"memory_node_id": "jgraph__drawio_desktop__release__v27_0_2", "answer_text": "addresses issues #2058 and #2059 and uses Electron 35.3.0"}, {"memory_node_id": "jgraph__drawio_desktop__release__v28_0_4", "answer_text": "fixes a PDF title issue and uses Electron 37.2.1"}, {"memory_node_id": "jgraph__drawio_desktop__release__v30_0_0", "answer_text": "introduces adaptive colours as default for new installs and uses Electron 42.0.1"}]}
{"prototype_id": "juliangarnier__anime_release_window", "repo": "juliangarnier/anime", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the juliangarnier/anime releases, which release introduces a new keyframes system, spring and steps easings, and a new staggering helper?", "options": [{"option_id": "A", "text": "v2.2.0"}, {"option_id": "B", "text": "v3.0.0"}, {"option_id": "C", "text": "v3.1.0"}, {"option_id": "D", "text": "v4.0.0"}], "correct_option_id": "B", "expected_answer": "v3.0.0", "source_chunk_ids": ["juliangarnier__anime__release__v3_0_0"], "answer_support": [{"memory_node_id": "juliangarnier__anime__release__v3_0_0", "answer_text": "new features include spring and steps easings, an endDelay parameter, a new keyframes system, a new staggering helper"}]}
{"prototype_id": "juliangarnier__anime_release_window", "repo": "juliangarnier/anime", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the juliangarnier/anime releases, how does the easing-related change in v3.1.0 differ from the easing-related change in v4.2.0?", "options": [{"option_id": "A", "text": "v3.1.0 adds Bounce easing and refactors easing functions, while v4.2.0 removes linear(), irregular(), steps(), and cubicBezier() from the core and requires separate imports."}, {"option_id": "B", "text": "v3.1.0 removes all easing functions, while v4.2.0 adds spring easing."}, {"option_id": "C", "text": "Both releases only fix easing calculation bugs without adding or removing easings."}, {"option_id": "D", "text": "v3.1.0 introduces the easing functions editor, while v4.2.0 deprecates all easings."}], "correct_option_id": "A", "expected_answer": "v3.1.0 adds Bounce easing and refactors easing functions, while v4.2.0 removes linear(), irregular(), steps(), and cubicBezier() from the core and requires separate imports.", "source_chunk_ids": ["juliangarnier__anime__release__v3_1_0", "juliangarnier__anime__release__v4_2_0"], "answer_support": [{"memory_node_id": "juliangarnier__anime__release__v3_1_0", "answer_text": "easing functions refactoring, and addition of Bounce easing"}, {"memory_node_id": "juliangarnier__anime__release__v4_2_0", "answer_text": "linear(), irregular(), steps() and cubicBezier() have been removed from the core and must be imported separately"}]}
{"prototype_id": "juliangarnier__anime_release_window", "repo": "juliangarnier/anime", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the juliangarnier/anime release window, order the following release-content states from earliest to latest: (1) a release that adds support for RGBA and HSLA color animations, (2) a release that introduces a complete rewrite with a modular ESM-first API and new Timer, Animation, and Timeline components, (3) a release that adds a text.split() method and new Scope methods addOnce() and keepTime(), (4) a release that introduces scrambleText() and a fixed transform render order.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["juliangarnier__anime__release__v2_2_0", "juliangarnier__anime__release__v4_0_0", "juliangarnier__anime__release__v4_1_0", "juliangarnier__anime__release__v4_4_0"], "answer_support": [{"memory_node_id": "juliangarnier__anime__release__v2_2_0", "answer_text": "support for RGBA and HSLA colors animations"}, {"memory_node_id": "juliangarnier__anime__release__v4_0_0", "answer_text": "complete rewrite of Anime.js, introduces a modular, ESM-first API ... Timer ... Animation ... Timeline"}, {"memory_node_id": "juliangarnier__anime__release__v4_1_0", "answer_text": "text.split() method ... scope.addOnce() and scope.keepTime()"}, {"memory_node_id": "juliangarnier__anime__release__v4_4_0", "answer_text": "scrambleText() ... transforms now following a fixed render order"}]}
{"prototype_id": "junegunn__fzf_release_window", "repo": "junegunn/fzf", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the junegunn/fzf releases, which release introduces the --gap[=N] option to display empty lines between items?", "options": [{"option_id": "A", "text": "0.56.0"}, {"option_id": "B", "text": "0.57.0"}, {"option_id": "C", "text": "0.58.0"}, {"option_id": "D", "text": "0.59.0"}], "correct_option_id": "A", "expected_answer": "0.56.0", "source_chunk_ids": ["junegunn__fzf__release__v0_56_0"], "answer_support": [{"memory_node_id": "junegunn__fzf__release__v0_56_0", "answer_text": "introduces the --gap[=N] option to display empty lines between items"}]}
{"prototype_id": "junegunn__fzf_release_window", "repo": "junegunn/fzf", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the junegunn/fzf release window, order the following release-content states from earliest to latest: (1) a release that adds the --ghost option to display ghost text when input is empty, (2) a release that introduces raw mode with --raw and toggle-raw action, (3) a release that adds --freeze-left and --freeze-right options to keep columns always visible, (4) a release that implements word wrapping in the list section with --wrap=word.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["junegunn__fzf__release__v0_61_0", "junegunn__fzf__release__v0_66_0", "junegunn__fzf__release__v0_67_0", "junegunn__fzf__release__v0_68_0"], "answer_support": [{"memory_node_id": "junegunn__fzf__release__v0_61_0", "answer_text": "Added --ghost=TEXT to display a ghost text when the input is empty"}, {"memory_node_id": "junegunn__fzf__release__v0_66_0", "answer_text": "Introducing \"raw\" mode ... You can enable raw mode by default with --raw, but it's often more useful when toggled dynamically with the toggle-raw action."}, {"memory_node_id": "junegunn__fzf__release__v0_67_0", "answer_text": "Added --freeze-left=N option to keep the leftmost N columns always visible. ... Also added --freeze-right=N option"}, {"memory_node_id": "junegunn__fzf__release__v0_68_0", "answer_text": "Implemented word wrapping in the list section ... Added --wrap=word (or --wrap-word) option"}]}
{"prototype_id": "juspay__hyperswitch_release_window", "repo": "juspay/hyperswitch", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the juspay/hyperswitch releases, which release introduces a payment link status page UI and adds automatic retries with step-up 3DS flow?", "options": [{"option_id": "A", "text": "v1.78.0"}, {"option_id": "B", "text": "v1.79.0"}, {"option_id": "C", "text": "v1.80.0"}, {"option_id": "D", "text": "v1.81.0"}], "correct_option_id": "A", "expected_answer": "v1.78.0", "source_chunk_ids": ["juspay__hyperswitch__release__v1_78_0"], "answer_support": [{"memory_node_id": "juspay__hyperswitch__release__v1_78_0", "answer_text": "adds automatic retries and step-up 3DS flow in the router, introduces a payment link status page UI"}]}
{"prototype_id": "juspay__hyperswitch_release_window", "repo": "juspay/hyperswitch", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the juspay/hyperswitch releases, how does the connector-related change in v1.81.0 differ from the connector-related change in v1.84.0?", "options": [{"option_id": "A", "text": "v1.81.0 implements Cards for Bank of America and Card Redirect flows for ProphetPay, while v1.84.0 applies a PSYNC bugfix for Bank of America."}, {"option_id": "B", "text": "v1.81.0 adds a PSYNC bugfix for Bank of America, while v1.84.0 implements Cards for Bank of America."}, {"option_id": "C", "text": "Both releases only update postman collection files without connector changes."}, {"option_id": "D", "text": "v1.81.0 removes Bank of America support, while v1.84.0 adds it back."}], "correct_option_id": "A", "expected_answer": "v1.81.0 implements Cards for Bank of America and Card Redirect flows for ProphetPay, while v1.84.0 applies a PSYNC bugfix for Bank of America.", "source_chunk_ids": ["juspay__hyperswitch__release__v1_81_0", "juspay__hyperswitch__release__v1_84_0"], "answer_support": [{"memory_node_id": "juspay__hyperswitch__release__v1_81_0", "answer_text": "implements Cards for Bank of America connector, implements Card Redirect PaymentMethodType and flows for ProphetPay connector"}, {"memory_node_id": "juspay__hyperswitch__release__v1_84_0", "answer_text": "applies a PSYNC bugfix for the Bank of America connector"}]}
{"prototype_id": "juspay__hyperswitch_release_window", "repo": "juspay/hyperswitch", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the juspay/hyperswitch release window, order the following release-content states from earliest to latest: (1) a release that adds an API to migrate card data from basilisk to rust and spawns webhooks in the background, (2) a release that implements Cards for Bank of America and Card Redirect flows for ProphetPay, (3) a release that adds fallback while adding and retrieving cards from the rust locker and introduces new attempt and intent statuses for multiple partial captures.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["juspay__hyperswitch__release__v1_80_0", "juspay__hyperswitch__release__v1_81_0", "juspay__hyperswitch__release__v1_82_0"], "answer_support": [{"memory_node_id": "juspay__hyperswitch__release__v1_80_0", "answer_text": "adds an API to migrate card data from basilisk to rust, spawns webhooks and async scheduling in the background"}, {"memory_node_id": "juspay__hyperswitch__release__v1_81_0", "answer_text": "implements Cards for Bank of America connector, implements Card Redirect PaymentMethodType and flows for ProphetPay connector"}, {"memory_node_id": "juspay__hyperswitch__release__v1_82_0", "answer_text": "adds fallback while adding and retrieving cards from the rust locker, introduces new attempt and intent statuses to handle multiple partial captures"}]}
{"prototype_id": "keycloak__keycloak_release_window", "repo": "keycloak/keycloak", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the keycloak/keycloak releases, which release introduces Fine-Grained Admin Permissions V2 with centralized management and explicit operation scoping?", "options": [{"option_id": "A", "text": "26.2.0"}, {"option_id": "B", "text": "26.3.0"}, {"option_id": "C", "text": "26.4.0"}, {"option_id": "D", "text": "26.5.0"}], "correct_option_id": "A", "expected_answer": "26.2.0", "source_chunk_ids": ["keycloak__keycloak__release__26_2_0"], "answer_support": [{"memory_node_id": "keycloak__keycloak__release__26_2_0", "answer_text": "introduces Fine-Grained Admin Permissions V2 with centralized management and explicit operation scoping"}]}
{"prototype_id": "keycloak__keycloak_release_window", "repo": "keycloak/keycloak", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the keycloak/keycloak release window, order the following release-content states from earliest to latest: (1) a release that adds filtering of LDAP referrals by default, (2) a release that introduces Fine-Grained Admin Permissions V2, (3) a release that promotes JWT Authorization Grant to supported, (4) a release that delivers account recovery with 2FA recovery codes.", "options": [{"option_id": "A", "text": "2 -> 4 -> 1 -> 3"}, {"option_id": "B", "text": "4 -> 2 -> 3 -> 1"}, {"option_id": "C", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "D", "text": "1 -> 2 -> 3 -> 4"}], "correct_option_id": "A", "expected_answer": "2 -> 4 -> 1 -> 3", "source_chunk_ids": ["keycloak__keycloak__release__26_2_0", "keycloak__keycloak__release__26_3_0", "keycloak__keycloak__release__26_4_6", "keycloak__keycloak__release__26_6_0"], "answer_support": [{"memory_node_id": "keycloak__keycloak__release__26_2_0", "answer_text": "introduces Fine-Grained Admin Permissions V2"}, {"memory_node_id": "keycloak__keycloak__release__26_3_0", "answer_text": "delivers account recovery with 2FA recovery codes"}, {"memory_node_id": "keycloak__keycloak__release__26_4_6", "answer_text": "adds filtering of LDAP referrals by default"}, {"memory_node_id": "keycloak__keycloak__release__26_6_0", "answer_text": "promotes JWT Authorization Grant to supported"}]}
{"prototype_id": "koala73__worldmonitor_release_window", "repo": "koala73/worldmonitor", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the koala73/worldmonitor releases, which release adds a finance/trading variant with a market-focused dashboard and integrates GCC investments?", "options": [{"option_id": "A", "text": "v2.3.7"}, {"option_id": "B", "text": "v2.3.8"}, {"option_id": "C", "text": "v2.3.9"}, {"option_id": "D", "text": "v2.4.1"}], "correct_option_id": "B", "expected_answer": "v2.3.8", "source_chunk_ids": ["koala73__worldmonitor__release__v2_3_8"], "answer_support": [{"memory_node_id": "koala73__worldmonitor__release__v2_3_8", "answer_text": "adds a finance/trading variant with a market-focused dashboard, integrates GCC investments into the finance variant"}]}
{"prototype_id": "koala73__worldmonitor_release_window", "repo": "koala73/worldmonitor", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the koala73/worldmonitor releases, how does the internationalization effort in v2.3.9 differ from the internationalization effort in v2.5.0?", "options": [{"option_id": "A", "text": "v2.3.9 implements full i18n support for 9 languages and adds a Linux AppImage config, while v2.5.0 adds Turkish as the 14th language and localizes remaining hardcoded English in 6 panel components."}, {"option_id": "B", "text": "v2.3.9 adds Japanese locale only, while v2.5.0 removes all i18n support."}, {"option_id": "C", "text": "Both releases only add Arabic and Chinese Simplified locales."}, {"option_id": "D", "text": "v2.3.9 focuses on RTL detection, while v2.5.0 focuses on adding a Russian locale."}], "correct_option_id": "A", "expected_answer": "v2.3.9 implements full i18n support for 9 languages and adds a Linux AppImage config, while v2.5.0 adds Turkish as the 14th language and localizes remaining hardcoded English in 6 panel components.", "source_chunk_ids": ["koala73__worldmonitor__release__v2_3_9", "koala73__worldmonitor__release__v2_5_0"], "answer_support": [{"memory_node_id": "koala73__worldmonitor__release__v2_3_9", "answer_text": "implements full internationalization support for 9 languages and adds a Linux AppImage config"}, {"memory_node_id": "koala73__worldmonitor__release__v2_5_0", "answer_text": "adds Turkish language support as the 14th language, localizes remaining hardcoded English in 6 panel components"}]}
{"prototype_id": "Kong__insomnia_release_window", "repo": "Kong/insomnia", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the Kong/insomnia releases, which release introduces LLM integrations and preferences together with MCP client support?", "options": [{"option_id": "A", "text": "core@12.0.0-beta.0"}, {"option_id": "B", "text": "core@12.1.0-beta.0"}, {"option_id": "C", "text": "core@11.6.0-beta.0"}, {"option_id": "D", "text": "core@12.2.0-beta.0"}], "correct_option_id": "A", "expected_answer": "core@12.0.0-beta.0", "source_chunk_ids": ["Kong__insomnia__release__core_12_0_0_beta_0"], "answer_support": [{"memory_node_id": "Kong__insomnia__release__core_12_0_0_beta_0", "answer_text": "adds LLM integrations and preferences, supports MCP client"}]}
{"prototype_id": "Kong__insomnia_release_window", "repo": "Kong/insomnia", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the Kong/insomnia release window, order the following release-content states from earliest to latest: (1) a release that adds external vault separation and bundle plugin support, (2) a release that introduces LLM integrations and preferences, (3) a release that adds konnect sync integration, (4) a release that supports Vault Dedicated for Hashicorp.", "options": [{"option_id": "A", "text": "1 -> 4 -> 2 -> 3"}, {"option_id": "B", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "C", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "D", "text": "4 -> 1 -> 2 -> 3"}], "correct_option_id": "A", "expected_answer": "1 -> 4 -> 2 -> 3", "source_chunk_ids": ["Kong__insomnia__release__core_11_5_0_beta_0", "Kong__insomnia__release__core_11_6_1", "Kong__insomnia__release__core_12_0_0_beta_0", "Kong__insomnia__release__core_12_6_0_beta_0"], "answer_support": [{"memory_node_id": "Kong__insomnia__release__core_11_5_0_beta_0", "answer_text": "external vault separation and bundle plugin support"}, {"memory_node_id": "Kong__insomnia__release__core_11_6_1", "answer_text": "supports Vault Dedicated for Hashicorp"}, {"memory_node_id": "Kong__insomnia__release__core_12_0_0_beta_0", "answer_text": "adds LLM integrations and preferences"}, {"memory_node_id": "Kong__insomnia__release__core_12_6_0_beta_0", "answer_text": "adds konnect sync integration"}]}
{"prototype_id": "Kong__kong_release_window", "repo": "Kong/kong", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the Kong/kong releases, which release is described as a patch release to cover CVE-2023-44487?", "options": [{"option_id": "A", "text": "3.4.1"}, {"option_id": "B", "text": "3.4.2"}, {"option_id": "C", "text": "3.5.0"}, {"option_id": "D", "text": "3.6.0"}], "correct_option_id": "B", "expected_answer": "3.4.2", "source_chunk_ids": ["Kong__kong__release__3_4_2"], "answer_support": [{"memory_node_id": "Kong__kong__release__3_4_2", "answer_text": "patch release to cover CVE-2023-44487"}]}
{"prototype_id": "ktorio__ktor_release_window", "repo": "ktorio/ktor", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the ktorio/ktor releases, which release introduces a dependency injection Ktor extension and support for Version Catalog?", "options": [{"option_id": "A", "text": "3.1.0"}, {"option_id": "B", "text": "3.2.0"}, {"option_id": "C", "text": "3.3.0"}, {"option_id": "D", "text": "3.4.0"}], "correct_option_id": "B", "expected_answer": "3.2.0", "source_chunk_ids": ["ktorio__ktor__release__3_2_0"], "answer_support": [{"memory_node_id": "ktorio__ktor__release__3_2_0", "answer_text": "introduces features including a dependency injection Ktor extension, Version Catalog support"}]}
{"prototype_id": "ktorio__ktor_release_window", "repo": "ktorio/ktor", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the ktorio/ktor releases, how does the SSE-related change described in release 3.2.2 differ from the SSE-related change described in release 3.1.0?", "options": [{"option_id": "A", "text": "3.2.2 changes the order of SSE field serialization to put event before data, while 3.1.0 introduces reconnection in ClientSSESession and heartbeat for SSE."}, {"option_id": "B", "text": "3.2.2 adds serialization for SSE, while 3.1.0 removes SSE support."}, {"option_id": "C", "text": "Both releases only fix SSE bugs without adding features."}, {"option_id": "D", "text": "3.2.2 introduces SSE heartbeat, while 3.1.0 changes field serialization order."}], "correct_option_id": "A", "expected_answer": "3.2.2 changes the order of SSE field serialization to put event before data, while 3.1.0 introduces reconnection in ClientSSESession and heartbeat for SSE.", "source_chunk_ids": ["ktorio__ktor__release__3_2_2", "ktorio__ktor__release__3_1_0"], "answer_support": [{"memory_node_id": "ktorio__ktor__release__3_2_2", "answer_text": "changes the order of SSE field serialization to put event before data"}, {"memory_node_id": "ktorio__ktor__release__3_1_0", "answer_text": "introduces features including reconnection in ClientSSESession, heartbeat for SSE"}]}
{"prototype_id": "ktorio__ktor_release_window", "repo": "ktorio/ktor", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the ktorio/ktor release window, order the following release-content states from earliest to latest: (1) a release that fixes a bug where the test client ignored socket timeout, (2) a release that introduces a dependency injection Ktor extension and support for Version Catalog, (3) a release that adds server-side HTTP/2 without TLS (h2c) and upgrades OkHttp to version 5.0.0, (4) a release that introduces OpenAPI specification support for Ktor Client and Server and Zstd support.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["ktorio__ktor__release__2_3_11", "ktorio__ktor__release__3_2_0", "ktorio__ktor__release__3_3_0", "ktorio__ktor__release__3_4_0"], "answer_support": [{"memory_node_id": "ktorio__ktor__release__2_3_11", "answer_text": "fixes a bug where the test client ignored socket timeout"}, {"memory_node_id": "ktorio__ktor__release__3_2_0", "answer_text": "introduces features including a dependency injection Ktor extension, Version Catalog support"}, {"memory_node_id": "ktorio__ktor__release__3_3_0", "answer_text": "introduces features including server-side HTTP/2 without TLS (h2c) ... upgrading OkHttp to version 5.0.0"}, {"memory_node_id": "ktorio__ktor__release__3_4_0", "answer_text": "introduces features including OpenAPI specification support for Ktor Client and Server ... Zstd support"}]}
{"prototype_id": "kubernetes__minikube_release_window", "repo": "kubernetes/minikube", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the kubernetes/minikube releases, which release introduces the --no-kubernetes flag to start minikube without Kubernetes?", "options": [{"option_id": "A", "text": "v1.23.2"}, {"option_id": "B", "text": "v1.24.0"}, {"option_id": "C", "text": "v1.25.0"}, {"option_id": "D", "text": "v1.26.0"}], "correct_option_id": "B", "expected_answer": "v1.24.0", "source_chunk_ids": ["kubernetes__minikube__release__v1_24_0"], "answer_support": [{"memory_node_id": "kubernetes__minikube__release__v1_24_0", "answer_text": "Add --no-kubernetes flag to start minikube without kubernetes"}]}
{"prototype_id": "kubernetes__minikube_release_window", "repo": "kubernetes/minikube", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the kubernetes/minikube release window, order the following release-content states from earliest to latest: (1) a release that adds the headlamp addon, (2) a release that adds the kubeflow addon, (3) a release that adds the volcano addon, (4) a release that adds the kubetail addon.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["kubernetes__minikube__release__v1_26_0", "kubernetes__minikube__release__v1_32_0", "kubernetes__minikube__release__v1_34_0", "kubernetes__minikube__release__v1_37_0"], "answer_support": [{"memory_node_id": "kubernetes__minikube__release__v1_26_0", "answer_text": "Add headlamp addon"}, {"memory_node_id": "kubernetes__minikube__release__v1_32_0", "answer_text": "New kubeflow addon"}, {"memory_node_id": "kubernetes__minikube__release__v1_34_0", "answer_text": "Add new volcano addon"}, {"memory_node_id": "kubernetes__minikube__release__v1_37_0", "answer_text": "new addon: kubetail"}]}
{"prototype_id": "kubeshark__kubeshark_release_window", "repo": "kubeshark/kubeshark", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the kubeshark/kubeshark releases, which release introduces BoringSSL support to inspect Envoy-encrypted traffic in plaintext for Istio mTLS STRICT mode?", "options": [{"option_id": "A", "text": "v52.3.88"}, {"option_id": "B", "text": "v52.3.89"}, {"option_id": "C", "text": "v52.3.90"}, {"option_id": "D", "text": "v52.3.91"}], "correct_option_id": "C", "expected_answer": "v52.3.90", "source_chunk_ids": ["kubeshark__kubeshark__release__v52_3_90"], "answer_support": [{"memory_node_id": "kubeshark__kubeshark__release__v52_3_90", "answer_text": "introduces BoringSSL support to inspect Envoy-encrypted traffic in plaintext for Istio mTLS STRICT mode"}]}
{"prototype_id": "kubeshark__kubeshark_release_window", "repo": "kubeshark/kubeshark", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the kubeshark/kubeshark releases, how does the protocol support added in v52.3.92 differ from the protocol support added in v52.3.95?", "options": [{"option_id": "A", "text": "v52.3.92 adds LDAPv3 protocol support, while v52.3.95 adds RADIUS protocol support."}, {"option_id": "B", "text": "v52.3.92 adds RADIUS protocol support, while v52.3.95 adds LDAPv3 protocol support."}, {"option_id": "C", "text": "Both releases add the same protocol support."}, {"option_id": "D", "text": "v52.3.92 adds Diameter protocol support, while v52.3.95 adds LDAPv3 protocol support."}], "correct_option_id": "A", "expected_answer": "v52.3.92 adds LDAPv3 protocol support, while v52.3.95 adds RADIUS protocol support.", "source_chunk_ids": ["kubeshark__kubeshark__release__v52_3_92", "kubeshark__kubeshark__release__v52_3_95"], "answer_support": [{"memory_node_id": "kubeshark__kubeshark__release__v52_3_92", "answer_text": "adds LDAPv3 protocol support"}, {"memory_node_id": "kubeshark__kubeshark__release__v52_3_95", "answer_text": "adds RADIUS protocol support"}]}
{"prototype_id": "kubeshark__kubeshark_release_window", "repo": "kubeshark/kubeshark", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the kubeshark/kubeshark release window, order the following release-content states from earliest to latest: (1) a release that adds the ability to override image names in values.yaml for private repositories, (2) a release that introduces automatic per-node packet capture technology selection, (3) a release that adds support for taints and tolerations for all images, (4) a release that adds OIDC with DEX integration for SSO.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "C", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["kubeshark__kubeshark__release__v52_3_88", "kubeshark__kubeshark__release__v52_4_0", "kubeshark__kubeshark__release__v52_5_0", "kubeshark__kubeshark__release__v52_6_0"], "answer_support": [{"memory_node_id": "kubeshark__kubeshark__release__v52_3_88", "answer_text": "adds the ability to override image names in values.yaml for private repositories"}, {"memory_node_id": "kubeshark__kubeshark__release__v52_4_0", "answer_text": "implements automatic per-node packet capture technology selection"}, {"memory_node_id": "kubeshark__kubeshark__release__v52_5_0", "answer_text": "adds support for taints and tolerations for all images"}, {"memory_node_id": "kubeshark__kubeshark__release__v52_6_0", "answer_text": "adds OIDC with DEX integration for SSO"}]}
{"prototype_id": "labstack__echo_release_window", "repo": "labstack/echo", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the labstack/echo releases, which release adds support for arbitrary HTTP method types as routes and custom 404 handlers for specific paths?", "options": [{"option_id": "A", "text": "v4.7.2"}, {"option_id": "B", "text": "v4.8.0"}, {"option_id": "C", "text": "v4.9.0"}, {"option_id": "D", "text": "v4.10.0"}], "correct_option_id": "B", "expected_answer": "v4.8.0", "source_chunk_ids": ["labstack__echo__release__v4_8_0"], "answer_support": [{"memory_node_id": "labstack__echo__release__v4_8_0", "answer_text": "support is added for arbitrary HTTP method types as routes and for custom 404 handlers on specific paths"}]}
{"prototype_id": "labstack__echo_release_window", "repo": "labstack/echo", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the labstack/echo releases, how does the CSRF middleware change described in v4.15.0 differ from the CSRF change described in v4.15.1?", "options": [{"option_id": "A", "text": "v4.15.0 adds Sec-Fetch-Site header support and new configuration options, while v4.15.1 adds support for older token-based CSRF protection handlers that want to render token into template."}, {"option_id": "B", "text": "v4.15.0 removes CSRF middleware entirely, while v4.15.1 reintroduces it with token-based protection."}, {"option_id": "C", "text": "Both releases only update CSRF documentation without functional changes."}, {"option_id": "D", "text": "v4.15.0 fixes a CSRF token extraction bug, while v4.15.1 adds support for multipart forms."}], "correct_option_id": "A", "expected_answer": "v4.15.0 adds Sec-Fetch-Site header support and new configuration options, while v4.15.1 adds support for older token-based CSRF protection handlers that want to render token into template.", "source_chunk_ids": ["labstack__echo__release__v4_15_0", "labstack__echo__release__v4_15_1"], "answer_support": [{"memory_node_id": "labstack__echo__release__v4_15_0", "answer_text": "the CSRF middleware now supports the Sec-Fetch-Site header as a modern defense-in-depth approach, with new configuration options TrustedOrigins and AllowSecFetchSiteFunc"}, {"memory_node_id": "labstack__echo__release__v4_15_1", "answer_text": "CSRF now supports older token-based CSRF protection handlers that want to render token into template"}]}
{"prototype_id": "labstack__echo_release_window", "repo": "labstack/echo", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the labstack/echo release window, order the following release-content states from earliest to latest: (1) a release that deprecates the JWT middleware and bumps the minimum Go version to 1.17, (2) a release that removes the JWT middleware from core due to CVE-2024-51744, (3) a release that adds type-safe generic parameter binding functions and deprecates the Timeout middleware, (4) a release that introduces a major breaking change where Context becomes a struct and the logging interface is replaced with log/slog.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["labstack__echo__release__v4_10_0", "labstack__echo__release__v4_13_0", "labstack__echo__release__v4_15_0", "labstack__echo__release__v5_0_0"], "answer_support": [{"memory_node_id": "labstack__echo__release__v4_10_0", "answer_text": "the JWT middleware is deprecated and moved to a separate repository. The minimum Go version is bumped to 1.17."}, {"memory_node_id": "labstack__echo__release__v4_13_0", "answer_text": "the JWT middleware is removed from core due to CVE-2024-51744"}, {"memory_node_id": "labstack__echo__release__v4_15_0", "answer_text": "Type-safe generic parameter binding functions are added ... The Timeout middleware is deprecated"}, {"memory_node_id": "labstack__echo__release__v5_0_0", "answer_text": "Context is now a struct instead of an interface ... the old logging interface is dropped in favor of log/slog"}]}
{"prototype_id": "langchain_ai__langchain_release_window", "repo": "langchain-ai/langchain", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the langchain-ai/langchain releases, which release adds a 'respond' decision to HITL middleware?", "options": [{"option_id": "A", "text": "langchain==1.3.0a1"}, {"option_id": "B", "text": "langchain==1.3.0"}, {"option_id": "C", "text": "langchain==1.3.2"}, {"option_id": "D", "text": "langchain==1.2.18"}], "correct_option_id": "A", "expected_answer": "langchain==1.3.0a1", "source_chunk_ids": ["langchain_ai__langchain__release__langchain_1_3_0a1"], "answer_support": [{"memory_node_id": "langchain_ai__langchain__release__langchain_1_3_0a1", "answer_text": "adds a 'respond' decision to HITL middleware"}]}
{"prototype_id": "langchain_ai__langchain_release_window", "repo": "langchain-ai/langchain", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the langchain-ai/langchain releases, how does the fireworks partner package change from version 1.3.0 to version 1.4.0?", "options": [{"option_id": "A", "text": "1.3.0 adds a service_tier init kwarg, while 1.4.0 migrates to the fireworks-ai 1.x SDK and raises ContextOverflowError on prompt-too-long."}, {"option_id": "B", "text": "1.3.0 strips non-wire keys from ToolMessage, while 1.4.0 requires api_key in FireworksEmbeddings."}, {"option_id": "C", "text": "1.3.0 retries on APIConnectionError, while 1.4.0 strips non-wire keys from all content parts."}, {"option_id": "D", "text": "1.3.0 migrates to the 1.x SDK, while 1.4.0 adds a service_tier init kwarg."}], "correct_option_id": "A", "expected_answer": "1.3.0 adds a service_tier init kwarg, while 1.4.0 migrates to the fireworks-ai 1.x SDK and raises ContextOverflowError on prompt-too-long.", "source_chunk_ids": ["langchain_ai__langchain__release__langchain_fireworks_1_3_0", "langchain_ai__langchain__release__langchain_fireworks_1_4_0"], "answer_support": [{"memory_node_id": "langchain_ai__langchain__release__langchain_fireworks_1_3_0", "answer_text": "adds a 'service_tier' init kwarg on ChatFireworks"}, {"memory_node_id": "langchain_ai__langchain__release__langchain_fireworks_1_4_0", "answer_text": "migrates to the fireworks-ai 1.x SDK and raises ContextOverflowError on prompt-too-long"}]}
{"prototype_id": "langflow_ai__langflow_release_window", "repo": "langflow-ai/langflow", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the langflow-ai/langflow releases, which release adds robust startup retry logic and port conflict resolution?", "options": [{"option_id": "A", "text": "1.6.5"}, {"option_id": "B", "text": "1.6.6"}, {"option_id": "C", "text": "1.6.7"}, {"option_id": "D", "text": "1.6.8"}], "correct_option_id": "B", "expected_answer": "1.6.6", "source_chunk_ids": ["langflow_ai__langflow__release__1_6_6"], "answer_support": [{"memory_node_id": "langflow_ai__langflow__release__1_6_6", "answer_text": "adds robust startup retry logic and port conflict resolution"}]}
{"prototype_id": "langflow_ai__langflow_release_window", "repo": "langflow-ai/langflow", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the langflow-ai/langflow releases, how does the security-related change in v1.9.3 differ from the security-related change in v1.9.4?", "options": [{"option_id": "A", "text": "v1.9.3 adds SSRF protection with DNS rebinding prevention, while v1.9.4 upgrades dependencies for security fixes and addresses CVEs."}, {"option_id": "B", "text": "v1.9.3 removes SSRF protection, while v1.9.4 adds it."}, {"option_id": "C", "text": "Both releases only update documentation without security changes."}, {"option_id": "D", "text": "v1.9.3 fixes model handling for tool calling, while v1.9.4 adds Python 3.14 support."}], "correct_option_id": "A", "expected_answer": "v1.9.3 adds SSRF protection with DNS rebinding prevention, while v1.9.4 upgrades dependencies for security fixes and addresses CVEs.", "source_chunk_ids": ["langflow_ai__langflow__release__v1_9_3", "langflow_ai__langflow__release__v1_9_4"], "answer_support": [{"memory_node_id": "langflow_ai__langflow__release__v1_9_3", "answer_text": "adds SSRF protection with DNS rebinding prevention"}, {"memory_node_id": "langflow_ai__langflow__release__v1_9_4", "answer_text": "upgrades dependencies for security fixes by addressing CVEs"}]}
{"prototype_id": "langflow_ai__langflow_release_window", "repo": "langflow-ai/langflow", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the langflow-ai/langflow release window, order the following release-content states from earliest to latest: (1) a release that adds robust startup retry logic and port conflict resolution, (2) a release that introduces pinning of mcp-composer to a specific version and fixes agent streaming to use partial messages, (3) a release that fixes cross-platform stream reading in subprocess, (4) a release that improves MCP Composer process management and Windows zombie handling.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "B", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "C", "text": "2 -> 3 -> 1 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3 -> 4", "source_chunk_ids": ["langflow_ai__langflow__release__1_6_5", "langflow_ai__langflow__release__1_6_6", "langflow_ai__langflow__release__1_6_7", "langflow_ai__langflow__release__1_6_8"], "answer_support": [{"memory_node_id": "langflow_ai__langflow__release__1_6_5", "answer_text": "introduces pinning of mcp-composer to a specific version and fixes agent streaming to use partial messages"}, {"memory_node_id": "langflow_ai__langflow__release__1_6_6", "answer_text": "adds robust startup retry logic and port conflict resolution"}, {"memory_node_id": "langflow_ai__langflow__release__1_6_7", "answer_text": "fixes cross-platform stream reading in subprocess"}, {"memory_node_id": "langflow_ai__langflow__release__1_6_8", "answer_text": "improves MCP Composer process management and Windows zombie handling"}]}
{"prototype_id": "langfuse__langfuse_release_window", "repo": "langfuse/langfuse", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the langfuse/langfuse releases, which release introduces a secondary OTel ingestion queue and self-service SSO config with DNS-verified domains?", "options": [{"option_id": "A", "text": "v3.173.0"}, {"option_id": "B", "text": "v3.170.0"}, {"option_id": "C", "text": "v3.175.0"}, {"option_id": "D", "text": "v3.168.0"}], "correct_option_id": "A", "expected_answer": "v3.173.0", "source_chunk_ids": ["langfuse__langfuse__release__v3_173_0"], "answer_support": [{"memory_node_id": "langfuse__langfuse__release__v3_173_0", "answer_text": "features showed metadata in experiments overview, added secondary otel ingestion queue, and provided self-service SSO config with DNS-verified domains."}]}
{"prototype_id": "langfuse__langfuse_release_window", "repo": "langfuse/langfuse", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the langfuse/langfuse releases, how does the evaluation-related change in v3.158.0 differ from the evaluation-related change in v3.163.0?", "options": [{"option_id": "A", "text": "v3.158.0 adds eval config blocking, while v3.163.0 adds boolean scores for LLM-as-a-judge."}, {"option_id": "B", "text": "v3.158.0 adds boolean scores for LLM-as-a-judge, while v3.163.0 adds eval config blocking."}, {"option_id": "C", "text": "Both releases only update model prices without evaluation changes."}, {"option_id": "D", "text": "v3.158.0 removes eval config blocking, while v3.163.0 removes boolean scores."}], "correct_option_id": "A", "expected_answer": "v3.158.0 adds eval config blocking, while v3.163.0 adds boolean scores for LLM-as-a-judge.", "source_chunk_ids": ["langfuse__langfuse__release__v3_158_0", "langfuse__langfuse__release__v3_163_0"], "answer_support": [{"memory_node_id": "langfuse__langfuse__release__v3_158_0", "answer_text": "features included eval config blocking"}, {"memory_node_id": "langfuse__langfuse__release__v3_163_0", "answer_text": "adding boolean scores for LLM-as-a-judge"}]}
{"prototype_id": "langfuse__langfuse_release_window", "repo": "langfuse/langfuse", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the langfuse/langfuse release window, order the following release-content states from earliest to latest: (1) a release that adds gpt-5.4 model support, (2) a release that adds gpt-5.4-mini and gpt-5.4-nano model support, (3) a release that adds gpt-5.5 model pricing.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["langfuse__langfuse__release__v3_157_0", "langfuse__langfuse__release__v3_161_0", "langfuse__langfuse__release__v3_171_0"], "answer_support": [{"memory_node_id": "langfuse__langfuse__release__v3_157_0", "answer_text": "added gpt-5.4 model support"}, {"memory_node_id": "langfuse__langfuse__release__v3_161_0", "answer_text": "added support for gpt-5.4-mini and gpt-5.4-nano models"}, {"memory_node_id": "langfuse__langfuse__release__v3_171_0", "answer_text": "added gpt-5.5 model pricing"}]}
{"prototype_id": "langgenius__dify_release_window", "repo": "langgenius/dify", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the langgenius/dify releases, which release introduces the Knowledge Pipeline, a visual node-based orchestration system for document ingestion?", "options": [{"option_id": "A", "text": "v1.8.0"}, {"option_id": "B", "text": "v1.9.0"}, {"option_id": "C", "text": "v1.10.0"}, {"option_id": "D", "text": "v1.11.0"}], "correct_option_id": "B", "expected_answer": "v1.9.0", "source_chunk_ids": ["langgenius__dify__release__1_9_0"], "answer_support": [{"memory_node_id": "langgenius__dify__release__1_9_0", "answer_text": "introduces the Knowledge Pipeline, a visual node-based orchestration system for document ingestion"}]}
{"prototype_id": "langgenius__dify_release_window", "repo": "langgenius/dify", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the langgenius/dify releases, how does the trigger functionality introduced in v1.10.0 differ from the Human-in-the-Loop (HITL) feature introduced in v1.13.0?", "options": [{"option_id": "A", "text": "v1.10.0 triggers are for event-driven workflow start (schedule, SaaS events, webhooks), while v1.13.0 HITL allows pausing workflows for human review and action-based routing."}, {"option_id": "B", "text": "v1.10.0 triggers require human input, while v1.13.0 HITL is fully automated."}, {"option_id": "C", "text": "Both features are identical in functionality."}, {"option_id": "D", "text": "v1.10.0 triggers are only for Chatflow, while v1.13.0 HITL is only for Workflow."}], "correct_option_id": "A", "expected_answer": "v1.10.0 triggers are for event-driven workflow start (schedule, SaaS events, webhooks), while v1.13.0 HITL allows pausing workflows for human review and action-based routing.", "source_chunk_ids": ["langgenius__dify__release__1_10_0", "langgenius__dify__release__1_13_0"], "answer_support": [{"memory_node_id": "langgenius__dify__release__1_10_0", "answer_text": "introduces trigger functionality for event-driven workflows, supporting schedule, SaaS integration events via plugins, and webhook triggers"}, {"memory_node_id": "langgenius__dify__release__1_13_0", "answer_text": "introduces Human-in-the-Loop (HITL) with a Human Input node that allows pausing workflows for human review, editing variables, and action-based routing"}]}
{"prototype_id": "langgenius__dify_release_window", "repo": "langgenius/dify", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the langgenius/dify release window, order the following release-content states from earliest to latest: (1) a release that introduces MCP support, (2) a release that introduces the Multimodal Knowledge Base, (3) a release that introduces the Summary Index, (4) a release that introduces Collaboration.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["langgenius__dify__release__1_6_0", "langgenius__dify__release__1_11_0", "langgenius__dify__release__1_12_0", "langgenius__dify__release__1_14_0"], "answer_support": [{"memory_node_id": "langgenius__dify__release__1_6_0", "answer_text": "introduces support for Anthropic's Model Context Protocol (MCP)"}, {"memory_node_id": "langgenius__dify__release__1_11_0", "answer_text": "introduces a Multimodal Knowledge Base that understands both text and images"}, {"memory_node_id": "langgenius__dify__release__1_12_0", "answer_text": "introduces Summary Index, an AI-powered summarization for document chunks"}, {"memory_node_id": "langgenius__dify__release__1_14_0", "answer_text": "introduces Collaboration allowing workspace members to co-edit workflows"}]}
{"prototype_id": "laravel__framework_release_window", "repo": "laravel/framework", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the laravel/framework releases, how does the queue-related change in v13.11.0 differ from the queue-related change in v13.1.1?", "options": [{"option_id": "A", "text": "v13.11.0 adds a dedicated Cloud Queue, while v13.1.1 breaks queue dependency."}, {"option_id": "B", "text": "v13.11.0 breaks queue dependency, while v13.1.1 adds a dedicated Cloud Queue."}, {"option_id": "C", "text": "Both releases add a dedicated Cloud Queue."}, {"option_id": "D", "text": "Both releases break queue dependency."}], "correct_option_id": "A", "expected_answer": "v13.11.0 adds a dedicated Cloud Queue, while v13.1.1 breaks queue dependency.", "source_chunk_ids": ["laravel__framework__release__v13_11_0", "laravel__framework__release__v13_1_1"], "answer_support": [{"memory_node_id": "laravel__framework__release__v13_11_0", "answer_text": "adds a dedicated Cloud Queue"}, {"memory_node_id": "laravel__framework__release__v13_1_1", "answer_text": "breaks queue dependency"}]}
{"prototype_id": "lencx__ChatGPT_release_window", "repo": "lencx/ChatGPT", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the lencx/ChatGPT releases, which release introduces a pop-up search feature that shows a DALL·E 2 button when selecting content?", "options": [{"option_id": "A", "text": "v0.7.0"}, {"option_id": "B", "text": "v0.8.0"}, {"option_id": "C", "text": "v0.9.0"}, {"option_id": "D", "text": "v0.10.0"}], "correct_option_id": "B", "expected_answer": "v0.8.0", "source_chunk_ids": ["lencx__ChatGPT__release__v0_8_0"], "answer_support": [{"memory_node_id": "lencx__ChatGPT__release__v0_8_0", "answer_text": "pop-up search: selecting ChatGPT content with the mouse shows a DALL·E 2 button that jumps to search"}]}
{"prototype_id": "lencx__ChatGPT_release_window", "repo": "lencx/ChatGPT", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the lencx/ChatGPT releases, how does the export-related change in v0.9.0 differ from the export-related change in v1.1.0?", "options": [{"option_id": "A", "text": "v0.9.0 adds an export markdown button and new Notes/Download menus for managing exports, while v1.1.0 moves the export button to the sidebar to prevent layout conflicts."}, {"option_id": "B", "text": "v0.9.0 disables export sharing links, while v1.1.0 fixes the export button blinking."}, {"option_id": "C", "text": "Both releases only fix the export button not working without adding new export features."}, {"option_id": "D", "text": "v0.9.0 removes the export button entirely, while v1.1.0 restores it."}], "correct_option_id": "A", "expected_answer": "v0.9.0 adds an export markdown button and new Notes/Download menus for managing exports, while v1.1.0 moves the export button to the sidebar to prevent layout conflicts.", "source_chunk_ids": ["lencx__ChatGPT__release__v0_9_0", "lencx__ChatGPT__release__v1_1_0"], "answer_support": [{"memory_node_id": "lencx__ChatGPT__release__v0_9_0", "answer_text": "Features include an export markdown button (issue #175) and new 'Notes' and 'Download' menus in the Control Center for managing exported chat files"}, {"memory_node_id": "lencx__ChatGPT__release__v1_1_0", "answer_text": "Moved the export button to the sidebar to prevent layout conflicts."}]}
{"prototype_id": "lencx__ChatGPT_release_window", "repo": "lencx/ChatGPT", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the lencx/ChatGPT release window, order the following release-content states from earliest to latest: (1) a release that adds customizable global shortcuts and attempts to resolve Linux shared library errors, (2) a release that introduces theme enhancement (Light, Dark, System) and pop-up search, (3) a release that adds text-to-speech and automatic input focus.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["lencx__ChatGPT__release__v0_7_4", "lencx__ChatGPT__release__v0_8_0", "lencx__ChatGPT__release__v0_12_0"], "answer_support": [{"memory_node_id": "lencx__ChatGPT__release__v0_7_4", "answer_text": "attempts to resolve Linux errors about loading shared libraries (issue #111) and adds customizable global shortcuts"}, {"memory_node_id": "lencx__ChatGPT__release__v0_8_0", "answer_text": "theme enhancement (Light, Dark, System) (issue #52) ... pop-up search"}, {"memory_node_id": "lencx__ChatGPT__release__v0_12_0", "answer_text": "adds a refresh button, text-to-speech ... and automatic focus on the input field"}]}
{"prototype_id": "lensapp__lens_release_window", "repo": "lensapp/lens", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the lensapp/lens releases, which release introduces the feature 'Lens Applications View'?", "options": [{"option_id": "A", "text": "v2023.8.31525-latest"}, {"option_id": "B", "text": "v2023.9.190000-latest"}, {"option_id": "C", "text": "v2023.12.281947-latest"}, {"option_id": "D", "text": "v2024.1.300751-latest"}], "correct_option_id": "B", "expected_answer": "v2023.9.190000-latest", "source_chunk_ids": ["lensapp__lens__release__v2023_9_190000_latest"], "answer_support": [{"memory_node_id": "lensapp__lens__release__v2023_9_190000_latest", "answer_text": "Lens Applications View"}]}
{"prototype_id": "lensapp__lens_release_window", "repo": "lensapp/lens", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the lensapp/lens releases, how does the feature set in v2023.8.31525-latest differ from the feature set in v2023.12.281947-latest?", "options": [{"option_id": "A", "text": "v2023.8.31525-latest introduces tables with resizable columns and log aggregation, while v2023.12.281947-latest introduces a pinnable search bar and Metrics 2.0 with zoom and custom time range."}, {"option_id": "B", "text": "v2023.8.31525-latest introduces Metrics 2.0, while v2023.12.281947-latest introduces tables with resizable columns."}, {"option_id": "C", "text": "Both releases introduce the same features: resizable columns and log aggregation."}, {"option_id": "D", "text": "v2023.8.31525-latest introduces shareable links, while v2023.12.281947-latest introduces Electron v25.3.0."}], "correct_option_id": "A", "expected_answer": "v2023.8.31525-latest introduces tables with resizable columns and log aggregation, while v2023.12.281947-latest introduces a pinnable search bar and Metrics 2.0 with zoom and custom time range.", "source_chunk_ids": ["lensapp__lens__release__v2023_8_31525_latest", "lensapp__lens__release__v2023_12_281947_latest"], "answer_support": [{"memory_node_id": "lensapp__lens__release__v2023_8_31525_latest", "answer_text": "Tables with resizable columns. Added the ability to resize columns in tables. Log aggregation. Added the ability to aggregate all pod logs and container logs for deployments into a single stream."}, {"memory_node_id": "lensapp__lens__release__v2023_12_281947_latest", "answer_text": "The table search has been replaced by a search bar that can be pinned so it stays open. Metrics 2.0. The events are displayed in the Metrics chart. Prometheus is updated in Lens Metrics. Users can now zoom with your mouse and see a custom selected time range option."}]}
{"prototype_id": "liriliri__eruda_release_window", "repo": "liriliri/eruda", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the liriliri/eruda releases, which release introduces drag-to-resize functionality and replaces the browser prompt with a luna modal?", "options": [{"option_id": "A", "text": "v2.6.2"}, {"option_id": "B", "text": "v2.7.0"}, {"option_id": "C", "text": "v2.8.0"}, {"option_id": "D", "text": "v2.9.0"}], "correct_option_id": "B", "expected_answer": "v2.7.0", "source_chunk_ids": ["liriliri__eruda__release__v2_7_0"], "answer_support": [{"memory_node_id": "liriliri__eruda__release__v2_7_0", "answer_text": "introduce drag-to-resize functionality, updated icons, and replacement of the browser prompt with a luna modal"}]}
{"prototype_id": "liriliri__eruda_release_window", "repo": "liriliri/eruda", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the liriliri/eruda releases, how does the network plugin change described in v2.8.0 differ from the network plugin change described in v2.11.0?", "options": [{"option_id": "A", "text": "v2.8.0 adds copy as curl and JSON recognition, while v2.11.0 adds a filter."}, {"option_id": "B", "text": "v2.8.0 removes the network plugin, while v2.11.0 reintroduces it with a filter."}, {"option_id": "C", "text": "Both releases only update the network plugin's data grid styling."}, {"option_id": "D", "text": "v2.8.0 adds a filter, while v2.11.0 adds copy as curl."}], "correct_option_id": "A", "expected_answer": "v2.8.0 adds copy as curl and JSON recognition, while v2.11.0 adds a filter.", "source_chunk_ids": ["liriliri__eruda__release__v2_8_0", "liriliri__eruda__release__v2_11_0"], "answer_support": [{"memory_node_id": "liriliri__eruda__release__v2_8_0", "answer_text": "add copy as curl in network (#220), recognize JSON in network (#201)"}, {"memory_node_id": "liriliri__eruda__release__v2_11_0", "answer_text": "add a filter to the network plugin"}]}
{"prototype_id": "liriliri__eruda_release_window", "repo": "liriliri/eruda", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the liriliri/eruda release window, order the following release-content states from earliest to latest: (1) a release that adds an AMOLED theme and system preference theme support, (2) a release that adds a Vue devtools plugin, (3) a release that supports shadow DOM and fixes quirks mode table rendering, (4) a release that fixes a WebSocket message base64 encoding issue.", "options": [{"option_id": "A", "text": "1 -> 4 -> 2 -> 3"}, {"option_id": "B", "text": "4 -> 1 -> 2 -> 3"}, {"option_id": "C", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "D", "text": "2 -> 1 -> 4 -> 3"}], "correct_option_id": "A", "expected_answer": "1 -> 4 -> 2 -> 3", "source_chunk_ids": ["liriliri__eruda__release__v3_1_0", "liriliri__eruda__release__v3_2_3", "liriliri__eruda__release__v3_3_0", "liriliri__eruda__release__v3_4_0"], "answer_support": [{"memory_node_id": "liriliri__eruda__release__v3_1_0", "answer_text": "add an AMOLED theme (#414), support system preference theme configuration"}, {"memory_node_id": "liriliri__eruda__release__v3_2_3", "answer_text": "fix a WebSocket message base64 encoding issue (#447)"}, {"memory_node_id": "liriliri__eruda__release__v3_3_0", "answer_text": "add a Vue devtools plugin"}, {"memory_node_id": "liriliri__eruda__release__v3_4_0", "answer_text": "support shadow DOM (#158) and fix quirks mode table rendering (#459)"}]}
{"prototype_id": "LizardByte__Sunshine_release_window", "repo": "LizardByte/Sunshine", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the LizardByte/Sunshine releases, which release adds initial support for macOS?", "options": [{"option_id": "A", "text": "v0.11.1"}, {"option_id": "B", "text": "v0.12.0"}, {"option_id": "C", "text": "v0.13.0"}, {"option_id": "D", "text": "v0.14.0"}], "correct_option_id": "C", "expected_answer": "v0.13.0", "source_chunk_ids": ["LizardByte__Sunshine__release__v0_13_0"], "answer_support": [{"memory_node_id": "LizardByte__Sunshine__release__v0_13_0", "answer_text": "adds initial support for macOS"}]}
{"prototype_id": "LizardByte__Sunshine_release_window", "repo": "LizardByte/Sunshine", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the LizardByte/Sunshine releases, how does the security-related change in v0.17.0 differ from the security-related change in v0.18.0?", "options": [{"option_id": "A", "text": "v0.17.0 fixes a Windows service security flaw where games ran as SYSTEM, while v0.18.0 contains critical security fixes and encourages users to change their Sunshine password."}, {"option_id": "B", "text": "v0.17.0 adds HDR support, while v0.18.0 adds Intel QuickSync support."}, {"option_id": "C", "text": "Both releases only update dependencies without security changes."}, {"option_id": "D", "text": "v0.17.0 removes automatic desktop entry, while v0.18.0 adds a cover finder."}], "correct_option_id": "A", "expected_answer": "v0.17.0 fixes a Windows service security flaw where games ran as SYSTEM, while v0.18.0 contains critical security fixes and encourages users to change their Sunshine password.", "source_chunk_ids": ["LizardByte__Sunshine__release__v0_17_0", "LizardByte__Sunshine__release__v0_18_0"], "answer_support": [{"memory_node_id": "LizardByte__Sunshine__release__v0_17_0", "answer_text": "addresses a security flaw on Windows where the binary was in a user-writable location and games ran as SYSTEM; now games run under the user account without elevated privileges"}, {"memory_node_id": "LizardByte__Sunshine__release__v0_18_0", "answer_text": "contains critical security fixes and encourages users to change their Sunshine password"}]}
{"prototype_id": "LizardByte__Sunshine_release_window", "repo": "LizardByte/Sunshine", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the LizardByte/Sunshine release window, order the following release-content states from earliest to latest: (1) a release that adds a Flatpak package for Linux, (2) a release that adds AV1 encoding, (3) a release that adds YUV 4:4:4 encoding support for Intel and NVIDIA GPUs on Windows, (4) a release that adds Vulkan encoding on Linux.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["LizardByte__Sunshine__release__v0_14_1", "LizardByte__Sunshine__release__v0_21_0", "LizardByte__Sunshine__release__v2025_118_151840", "LizardByte__Sunshine__release__v2026_516_143833"], "answer_support": [{"memory_node_id": "LizardByte__Sunshine__release__v0_14_1", "answer_text": "adds a Flatpak package for Linux"}, {"memory_node_id": "LizardByte__Sunshine__release__v0_21_0", "answer_text": "adds AV1 encoding"}, {"memory_node_id": "LizardByte__Sunshine__release__v2025_118_151840", "answer_text": "YUV 4:4:4 encoding support for Intel and NVIDIA GPUs on Windows"}, {"memory_node_id": "LizardByte__Sunshine__release__v2026_516_143833", "answer_text": "Vulkan encoding on Linux"}]}
{"prototype_id": "lizongying__my_tv_release_window", "repo": "lizongying/my-tv", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the lizongying/my-tv releases, which release adds an exit button in the settings and fixes the back button not exiting?", "options": [{"option_id": "A", "text": "v1.7.5"}, {"option_id": "B", "text": "v1.8.0"}, {"option_id": "C", "text": "v1.8.2"}, {"option_id": "D", "text": "v1.8.4"}], "correct_option_id": "B", "expected_answer": "v1.8.0", "source_chunk_ids": ["lizongying__my_tv__release__v1_8_0"], "answer_support": [{"memory_node_id": "lizongying__my_tv__release__v1_8_0", "answer_text": "the issue where the back button cannot exit is fixed, an exit button is added in the settings"}]}
{"prototype_id": "lizongying__my_tv_release_window", "repo": "lizongying/my-tv", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the lizongying/my-tv releases, how does the channel list interaction change from v1.7.3 to v1.7.8?", "options": [{"option_id": "A", "text": "v1.7.3 uses left button for program list and right button for menu, while v1.7.8 uses left button for channel list and right button for settings menu, and adds hiding on empty area click."}, {"option_id": "B", "text": "v1.7.3 removes the channel list entirely, while v1.7.8 reintroduces it with grid style."}, {"option_id": "C", "text": "Both versions use the same remote control mappings but v1.7.8 adds time display."}, {"option_id": "D", "text": "v1.7.3 adds program guides, while v1.7.8 removes them."}], "correct_option_id": "A", "expected_answer": "v1.7.3 uses left button for program list and right button for menu, while v1.7.8 uses left button for channel list and right button for settings menu, and adds hiding on empty area click.", "source_chunk_ids": ["lizongying__my_tv__release__v1_7_3", "lizongying__my_tv__release__v1_7_8"], "answer_support": [{"memory_node_id": "lizongying__my_tv__release__v1_7_3", "answer_text": "pressing the left button on the remote control enters the program list, and pressing the right button enters the menu"}, {"memory_node_id": "lizongying__my_tv__release__v1_7_8", "answer_text": "pressing the left button on the remote control opens the channel list, pressing the right button opens the settings menu, and clicking on an empty area in the channel list hides it"}]}
{"prototype_id": "louislam__uptime_kuma_release_window", "repo": "louislam/uptime-kuma", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the louislam/uptime-kuma releases, which release introduces a manual (static/fixed) monitor and a proxy clone functionality?", "options": [{"option_id": "A", "text": "2.0.0-beta.3"}, {"option_id": "B", "text": "2.0.0-beta.4"}, {"option_id": "C", "text": "2.0.0"}, {"option_id": "D", "text": "2.1.0-beta.0"}], "correct_option_id": "B", "expected_answer": "2.0.0-beta.4", "source_chunk_ids": ["louislam__uptime_kuma__release__2_0_0_beta_4"], "answer_support": [{"memory_node_id": "louislam__uptime_kuma__release__2_0_0_beta_4", "answer_text": "feat: Add a \"manual\" (static/fixed) monitor ... feat: Add proxy clone functionality to settings"}]}
{"prototype_id": "louislam__uptime_kuma_release_window", "repo": "louislam/uptime-kuma", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the louislam/uptime-kuma release window, order the following release-content states from earliest to latest: (1) a release that adds a manual monitor and proxy clone functionality, (2) a release that adds Webpush notifications and drag & drop for groups, (3) a release that adds incidents to RSS and VKTeams bot notification.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["louislam__uptime_kuma__release__2_0_0_beta_4", "louislam__uptime_kuma__release__2_1_0_beta_0", "louislam__uptime_kuma__release__2_4_0"], "answer_support": [{"memory_node_id": "louislam__uptime_kuma__release__2_0_0_beta_4", "answer_text": "feat: Add a \"manual\" (static/fixed) monitor ... feat: Add proxy clone functionality to settings"}, {"memory_node_id": "louislam__uptime_kuma__release__2_1_0_beta_0", "answer_text": "Webpush notifications ... feat: Add Drag & drop for groups"}, {"memory_node_id": "louislam__uptime_kuma__release__2_4_0", "answer_text": "feat: Add incidents to RSS ... feat: Add VKTeams bot notification provider"}]}
{"prototype_id": "mastodon__mastodon_release_window", "repo": "mastodon/mastodon", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the mastodon/mastodon releases, which release includes a fix for 'Cmd/Ctrl+Enter not submitting Alt text modal on some browsers'?", "options": [{"option_id": "A", "text": "v4.5.1"}, {"option_id": "B", "text": "v4.5.2"}, {"option_id": "C", "text": "v4.5.3"}, {"option_id": "D", "text": "v4.5.4"}], "correct_option_id": "A", "expected_answer": "v4.5.1", "source_chunk_ids": ["mastodon__mastodon__release__v4_5_1"], "answer_support": [{"memory_node_id": "mastodon__mastodon__release__v4_5_1", "answer_text": "Fix Cmd/Ctrl + Enter not submitting Alt text modal on some browsers"}]}
{"prototype_id": "mastodon__mastodon_release_window", "repo": "mastodon/mastodon", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the mastodon/mastodon releases, how does the security fix in v4.5.3 differ from the security fix in v4.5.4?", "options": [{"option_id": "A", "text": "v4.5.3 fixes inconsistent error handling leaking information on existence of private posts, while v4.5.4 fixes SSRF protection bypass and missing ownership check in severed relationships controller."}, {"option_id": "B", "text": "v4.5.3 fixes SSRF protection bypass, while v4.5.4 fixes inconsistent error handling leaking information on existence of private posts."}, {"option_id": "C", "text": "Both releases fix the same SSRF protection bypass issue."}, {"option_id": "D", "text": "v4.5.3 fixes missing ownership check in severed relationships controller, while v4.5.4 fixes inconsistent error handling leaking information on existence of private posts."}], "correct_option_id": "A", "expected_answer": "v4.5.3 fixes inconsistent error handling leaking information on existence of private posts, while v4.5.4 fixes SSRF protection bypass and missing ownership check in severed relationships controller.", "source_chunk_ids": ["mastodon__mastodon__release__v4_5_3", "mastodon__mastodon__release__v4_5_4"], "answer_support": [{"memory_node_id": "mastodon__mastodon__release__v4_5_3", "answer_text": "Fix inconsistent error handling leaking information on existence of private posts (GHSA-gwhw-gcjx-72v8)"}, {"memory_node_id": "mastodon__mastodon__release__v4_5_4", "answer_text": "Fix SSRF protection bypass (GHSA-xfrj-c749-jxxq) and Fix missing ownership check in severed relationships controller (GHSA-ww85-x9cp-5v24)"}]}
{"prototype_id": "mastodon__mastodon_release_window", "repo": "mastodon/mastodon", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the mastodon/mastodon release window, order the following release-content states from earliest to latest: (1) a release that adds the --suspended-only option to tootctl emoji purge, (2) a release that fixes 'Cmd/Ctrl+Enter not submitting Alt text modal on some browsers', (3) a release that fixes insufficient checks on quote authorizations and open redirect in legacy path handler, (4) a release that fixes SSRF protection bypass and Linked-Data Signature bypass.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "B", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "C", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "D", "text": "1 -> 2 -> 3 -> 4"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3 -> 4", "source_chunk_ids": ["mastodon__mastodon__release__v4_5_1", "mastodon__mastodon__release__v4_5_7", "mastodon__mastodon__release__v4_5_8", "mastodon__mastodon__release__v4_5_10"], "answer_support": [{"memory_node_id": "mastodon__mastodon__release__v4_5_1", "answer_text": "Fix Cmd/Ctrl + Enter not submitting Alt text modal on some browsers"}, {"memory_node_id": "mastodon__mastodon__release__v4_5_7", "answer_text": "Add --suspended-only option to tootctl emoji purge"}, {"memory_node_id": "mastodon__mastodon__release__v4_5_8", "answer_text": "Fix insufficient checks on quote authorizations (GHSA-q4g8-82c5-9h33) and Fix open redirect in legacy path handler (GHSA-xqw8-4j56-5hj6)"}, {"memory_node_id": "mastodon__mastodon__release__v4_5_10", "answer_text": "Fix SSRF protection bypass (GHSA-crr4-7rm4-8gpw, GHSA-xx55-4rrg-8xg6) and Fix Linked-Data Signature bypass through JSON-LD graph restructuring features (GHSA-53m7-2wrh-q839, GHSA-chgx-jx3p-rf73)"}]}
{"prototype_id": "meilisearch__meilisearch_release_window", "repo": "meilisearch/meilisearch", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the meilisearch/meilisearch releases, which release introduces the `attributeRank` and `wordPosition` ranking rules?", "options": [{"option_id": "A", "text": "v1.36.0"}, {"option_id": "B", "text": "v1.35.0"}, {"option_id": "C", "text": "v1.37.0"}, {"option_id": "D", "text": "v1.34.0"}], "correct_option_id": "A", "expected_answer": "v1.36.0", "source_chunk_ids": ["meilisearch__meilisearch__release__v1_36_0"], "answer_support": [{"memory_node_id": "meilisearch__meilisearch__release__v1_36_0", "answer_text": "Introduce the `attributeRank` and `wordPosition` criteria"}]}
{"prototype_id": "meilisearch__meilisearch_release_window", "repo": "meilisearch/meilisearch", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the meilisearch/meilisearch releases, how does the vector store change in v1.29.0 differ from the vector store change in v1.36.0?", "options": [{"option_id": "A", "text": "v1.29.0 makes the new vector store backend the default for new indexes, while v1.36.0 migrates existing indexes from the old annoy vector store to the new Hannoy one via a dumpless upgrade step."}, {"option_id": "B", "text": "v1.29.0 removes the vector store entirely, while v1.36.0 reintroduces it with a different backend."}, {"option_id": "C", "text": "Both releases only update the vector store to support XLM Roberta models."}, {"option_id": "D", "text": "v1.29.0 migrates all indexes to Hannoy, while v1.36.0 makes the new backend default for new indexes."}], "correct_option_id": "A", "expected_answer": "v1.29.0 makes the new vector store backend the default for new indexes, while v1.36.0 migrates existing indexes from the old annoy vector store to the new Hannoy one via a dumpless upgrade step.", "source_chunk_ids": ["meilisearch__meilisearch__release__v1_29_0", "meilisearch__meilisearch__release__v1_36_0"], "answer_support": [{"memory_node_id": "meilisearch__meilisearch__release__v1_29_0", "answer_text": "Enable the new vector store by default for new indexes"}, {"memory_node_id": "meilisearch__meilisearch__release__v1_36_0", "answer_text": "introducing a new dumpless upgrade step that migrates index uses the old annoy vector store to the new Hannoy one"}]}
{"prototype_id": "meilisearch__meilisearch_release_window", "repo": "meilisearch/meilisearch", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the meilisearch/meilisearch release window, order the following release-content states from earliest to latest: (1) a release that introduces the `useNetwork` field for easy search over a network of machines, (2) a release that adds the ability to modify the number of participants in sharding without starting over, (3) a release that introduces replicated sharding with breaking changes to the network object, (4) a release that adds a fallback system for sharding and replication to avoid unavailable machines.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "B", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "C", "text": "2 -> 3 -> 1 -> 4"}, {"option_id": "D", "text": "3 -> 2 -> 1 -> 4"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3 -> 4", "source_chunk_ids": ["meilisearch__meilisearch__release__v1_30_0", "meilisearch__meilisearch__release__v1_34_0", "meilisearch__meilisearch__release__v1_37_0", "meilisearch__meilisearch__release__v1_42_0"], "answer_support": [{"memory_node_id": "meilisearch__meilisearch__release__v1_30_0", "answer_text": "adds the ability to modify the number of participants in sharding, without having to start over"}, {"memory_node_id": "meilisearch__meilisearch__release__v1_34_0", "answer_text": "`useNetwork` field in `POST /indexes/{:indexUid}/search`"}, {"memory_node_id": "meilisearch__meilisearch__release__v1_37_0", "answer_text": "Replicated sharding ... Breaking changes ... network objects sent to the PATCH /network route must now contain at least one shard object"}, {"memory_node_id": "meilisearch__meilisearch__release__v1_42_0", "answer_text": "Support search fallback on remote unavailability ... fallback system for the sharding and replication enterprise edition feature"}]}
{"prototype_id": "mermaid_js__mermaid_release_window", "repo": "mermaid-js/mermaid", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the mermaid-js/mermaid releases, which release adds support for decimal start and increment values in the autonumber directive for sequence diagrams?", "options": [{"option_id": "A", "text": "mermaid@11.13.0"}, {"option_id": "B", "text": "mermaid@11.14.0"}, {"option_id": "C", "text": "mermaid@11.15.0"}, {"option_id": "D", "text": "mermaid@11.12.0"}], "correct_option_id": "C", "expected_answer": "mermaid@11.15.0", "source_chunk_ids": ["mermaid_js__mermaid__release__mermaid_11_15_0"], "answer_support": [{"memory_node_id": "mermaid_js__mermaid__release__mermaid_11_15_0", "answer_text": "add support for decimal start and increment values in the autonumber directive for sequence diagrams"}]}
{"prototype_id": "microsoft__monaco_editor_release_window", "repo": "microsoft/monaco-editor", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the microsoft/monaco-editor releases, which release implements language selection and adds AMD and Firefox/WebKit to smoke tests?", "options": [{"option_id": "A", "text": "v0.53.0-dev-20250830"}, {"option_id": "B", "text": "v0.54.0"}, {"option_id": "C", "text": "v0.55.0-rc"}, {"option_id": "D", "text": "v0.56.0-dev-20260113"}], "correct_option_id": "A", "expected_answer": "v0.53.0-dev-20250830", "source_chunk_ids": ["microsoft__monaco_editor__release__v0_53_0_dev_20250830"], "answer_support": [{"memory_node_id": "microsoft__monaco_editor__release__v0_53_0_dev_20250830", "answer_text": "implements language selection and adds AMD and Firefox/WebKit to smoke tests"}]}
{"prototype_id": "microsoft__monaco_editor_release_window", "repo": "microsoft/monaco-editor", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the microsoft/monaco-editor releases, how does the change in v0.55.0-dev-20251010.1 differ from the change in v0.55.0-dev-20251014?", "options": [{"option_id": "A", "text": "v0.55.0-dev-20251010.1 introduces the first iteration of the monaco editor LSP client, while v0.55.0-dev-20251014 addresses bug #5010 and updates TypeScript to 5.9.3."}, {"option_id": "B", "text": "v0.55.0-dev-20251010.1 fixes Kotlin number literals, while v0.55.0-dev-20251014 adds missing NLS files."}, {"option_id": "C", "text": "Both releases only bump dependencies without any feature changes."}, {"option_id": "D", "text": "v0.55.0-dev-20251010.1 removes the LSP client, while v0.55.0-dev-20251014 adds it."}], "correct_option_id": "A", "expected_answer": "v0.55.0-dev-20251010.1 introduces the first iteration of the monaco editor LSP client, while v0.55.0-dev-20251014 addresses bug #5010 and updates TypeScript to 5.9.3.", "source_chunk_ids": ["microsoft__monaco_editor__release__v0_55_0_dev_20251010_1", "microsoft__monaco_editor__release__v0_55_0_dev_20251014"], "answer_support": [{"memory_node_id": "microsoft__monaco_editor__release__v0_55_0_dev_20251010_1", "answer_text": "first iteration of the monaco editor LSP client"}, {"memory_node_id": "microsoft__monaco_editor__release__v0_55_0_dev_20251014", "answer_text": "addresses bug #5010 regarding multiple issues with how monaco-editor is published, fixes #5010, updates TypeScript to 5.9.3"}]}
{"prototype_id": "microsoft__monaco_editor_release_window", "repo": "microsoft/monaco-editor", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the microsoft/monaco-editor release window, order the following release-content states from earliest to latest: (1) a release that fixes AMD web worker loading, (2) a release that makes out/languages no longer available, (3) a release that adds .js file extensions for the ESM build, (4) a release that includes the first iteration of the monaco editor LSP client.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["microsoft__monaco_editor__release__v0_53_0_dev_20250829", "microsoft__monaco_editor__release__v0_54_0_dev_20250911", "microsoft__monaco_editor__release__v0_54_0_dev_20250928", "microsoft__monaco_editor__release__v0_55_0_dev_20251010_1"], "answer_support": [{"memory_node_id": "microsoft__monaco_editor__release__v0_53_0_dev_20250829", "answer_text": "fixes AMD web worker loading"}, {"memory_node_id": "microsoft__monaco_editor__release__v0_54_0_dev_20250911", "answer_text": "makes out/languages no longer available"}, {"memory_node_id": "microsoft__monaco_editor__release__v0_54_0_dev_20250928", "answer_text": "adds .js file extensions for the ESM build"}, {"memory_node_id": "microsoft__monaco_editor__release__v0_55_0_dev_20251010_1", "answer_text": "first iteration of the monaco editor LSP client"}]}
{"prototype_id": "microsoft__playwright_release_window", "repo": "microsoft/playwright", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the microsoft/playwright releases, which release introduces the page.screencast API for screencast recordings, action annotations, and visual overlays?", "options": [{"option_id": "A", "text": "v1.57.0"}, {"option_id": "B", "text": "v1.58.0"}, {"option_id": "C", "text": "v1.59.0"}, {"option_id": "D", "text": "v1.60.0"}], "correct_option_id": "C", "expected_answer": "v1.59.0", "source_chunk_ids": ["microsoft__playwright__release__v1_59_0"], "answer_support": [{"memory_node_id": "microsoft__playwright__release__v1_59_0", "answer_text": "new page.screencast API provides screencast recordings, action annotations, visual overlays, real-time frame capture, and agentic video receipts"}]}
{"prototype_id": "microsoft__playwright_release_window", "repo": "microsoft/playwright", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the microsoft/playwright releases, how does the WebSocket-related change in v1.48.0 differ from the WebSocket-related change in v1.48.1?", "options": [{"option_id": "A", "text": "v1.48.0 introduces page.routeWebSocket() and browserContext.routeWebSocket() for intercepting WebSocket connections, while v1.48.1 fixes a bug where WebSocket route did not handle full URLs."}, {"option_id": "B", "text": "v1.48.0 removes WebSocket support, while v1.48.1 adds it back."}, {"option_id": "C", "text": "Both releases only update WebSocket-related documentation without functional changes."}, {"option_id": "D", "text": "v1.48.0 deprecates WebSocket routing, and v1.48.1 removes it entirely."}], "correct_option_id": "A", "expected_answer": "v1.48.0 introduces page.routeWebSocket() and browserContext.routeWebSocket() for intercepting WebSocket connections, while v1.48.1 fixes a bug where WebSocket route did not handle full URLs.", "source_chunk_ids": ["microsoft__playwright__release__v1_48_0", "microsoft__playwright__release__v1_48_1"], "answer_support": [{"memory_node_id": "microsoft__playwright__release__v1_48_0", "answer_text": "new page.routeWebSocket() and browserContext.routeWebSocket() methods allow intercepting, modifying, and mocking WebSocket connections"}, {"memory_node_id": "microsoft__playwright__release__v1_48_1", "answer_text": "a bug fix for WebSocket route not handling full URLs"}]}
{"prototype_id": "microsoft__playwright_release_window", "repo": "microsoft/playwright", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the microsoft/playwright release window, order the following release-content states from earliest to latest: (1) a release that introduces the page.screencast API, (2) a release that introduces Playwright Agents (planner, generator, healer), (3) a release that switches from Chromium to Chrome for Testing builds, (4) a release that introduces WebSocket routing with page.routeWebSocket().", "options": [{"option_id": "A", "text": "4 -> 2 -> 3 -> 1"}, {"option_id": "B", "text": "4 -> 3 -> 2 -> 1"}, {"option_id": "C", "text": "2 -> 4 -> 3 -> 1"}, {"option_id": "D", "text": "1 -> 2 -> 3 -> 4"}], "correct_option_id": "A", "expected_answer": "4 -> 2 -> 3 -> 1", "source_chunk_ids": ["microsoft__playwright__release__v1_48_0", "microsoft__playwright__release__v1_56_0", "microsoft__playwright__release__v1_57_0", "microsoft__playwright__release__v1_59_0"], "answer_support": [{"memory_node_id": "microsoft__playwright__release__v1_48_0", "answer_text": "new page.routeWebSocket() and browserContext.routeWebSocket() methods allow intercepting, modifying, and mocking WebSocket connections"}, {"memory_node_id": "microsoft__playwright__release__v1_56_0", "answer_text": "Playwright Agents are introduced: planner, generator, and healer agents"}, {"memory_node_id": "microsoft__playwright__release__v1_57_0", "answer_text": "Playwright switches from Chromium to Chrome for Testing builds"}, {"memory_node_id": "microsoft__playwright__release__v1_59_0", "answer_text": "new page.screencast API provides screencast recordings, action annotations, visual overlays"}]}
{"prototype_id": "microsoft__terminal_release_window", "repo": "microsoft/terminal", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the microsoft/terminal releases, which release introduces a completely rewritten console hosting implementation with Sixel support and grapheme clusters?", "options": [{"option_id": "A", "text": "Windows Terminal v1.21.10351.0"}, {"option_id": "B", "text": "Windows Terminal v1.22.10352.0"}, {"option_id": "C", "text": "Windows Terminal Preview v1.23.10353.0"}, {"option_id": "D", "text": "Windows Terminal v1.24.10621.0"}], "correct_option_id": "B", "expected_answer": "Windows Terminal v1.22.10352.0", "source_chunk_ids": ["microsoft__terminal__release__v1_22_10352_0"], "answer_support": [{"memory_node_id": "microsoft__terminal__release__v1_22_10352_0", "answer_text": "completely rewritten console hosting implementation with Sixel support and better performance, grapheme clusters for emoji and combining characters"}]}
{"prototype_id": "microsoft__vscode_release_window", "repo": "microsoft/vscode", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the microsoft/vscode releases, which release introduces Agent HQ, background agents, and custom agents for organizations?", "options": [{"option_id": "A", "text": "1.107.0 (November 2025)"}, {"option_id": "B", "text": "1.109.0 (January 2026)"}, {"option_id": "C", "text": "1.110 (February 2026)"}, {"option_id": "D", "text": "1.111.0 (March 2026)"}], "correct_option_id": "A", "expected_answer": "1.107.0 (November 2025)", "source_chunk_ids": ["microsoft__vscode__release__1_107_0"], "answer_support": [{"memory_node_id": "microsoft__vscode__release__1_107_0", "answer_text": "VS Code introduces Agent HQ, background agents, and custom agents for organizations."}]}
{"prototype_id": "microsoft__vscode_release_window", "repo": "microsoft/vscode", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the microsoft/vscode releases, how does the agent-related change described in 1.110 (February 2026) differ from the change described in 1.109.0 (January 2026)?", "options": [{"option_id": "A", "text": "1.110 introduces Agent plugins and Agentic browser tools, while 1.109.0 introduces Agent Session Management and Agent Customization."}, {"option_id": "B", "text": "1.110 introduces Agent HQ, while 1.109.0 introduces background agents."}, {"option_id": "C", "text": "Both releases focus on issue cleanup and recovery fixes."}, {"option_id": "D", "text": "1.110 introduces the first weekly Stable release, while 1.109.0 introduces the integrated browser."}], "correct_option_id": "A", "expected_answer": "1.110 introduces Agent plugins and Agentic browser tools, while 1.109.0 introduces Agent Session Management and Agent Customization.", "source_chunk_ids": ["microsoft__vscode__release__1_110", "microsoft__vscode__release__1_109_0"], "answer_support": [{"memory_node_id": "microsoft__vscode__release__1_110", "answer_text": "Agent plugins (prepackaged bundles of skills, tools, and hooks), Agentic browser tools (agent drives browser to interact with app and verify changes)"}, {"memory_node_id": "microsoft__vscode__release__1_109_0", "answer_text": "Agent Session Management for delegating tasks to local, background, and cloud agents, Agent Customization with orchestrations and Agent Skills"}]}
{"prototype_id": "microsoft__vscode_release_window", "repo": "microsoft/vscode", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the microsoft/vscode release window, order the following release-content states from earliest to latest: (1) a release that introduces Agent HQ and background agents, (2) a release that introduces Agent plugins and Agentic browser tools, (3) a release that is the first weekly Stable release with agent permissions and agent-scoped hooks, (4) a release that fixes GitHub Copilot CLI not working from VS Code.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["microsoft__vscode__release__1_107_0", "microsoft__vscode__release__1_110", "microsoft__vscode__release__1_111_0", "microsoft__vscode__release__1_118_1"], "answer_support": [{"memory_node_id": "microsoft__vscode__release__1_107_0", "answer_text": "VS Code introduces Agent HQ, background agents, and custom agents for organizations."}, {"memory_node_id": "microsoft__vscode__release__1_110", "answer_text": "Agent plugins (prepackaged bundles of skills, tools, and hooks), Agentic browser tools"}, {"memory_node_id": "microsoft__vscode__release__1_111_0", "answer_text": "first of the weekly Stable releases ... agent permissions, agent-scoped hooks"}, {"memory_node_id": "microsoft__vscode__release__1_118_1", "answer_text": "fixes GitHub Copilot CLI not working from VS Code"}]}
{"prototype_id": "microsoft__WSL_release_window", "repo": "microsoft/WSL", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the microsoft/WSL releases, which release removes the experimental useWindowsDnsCache config?", "options": [{"option_id": "A", "text": "2.3.17"}, {"option_id": "B", "text": "2.3.22"}, {"option_id": "C", "text": "2.4.4"}, {"option_id": "D", "text": "2.5.1"}], "correct_option_id": "B", "expected_answer": "2.3.22", "source_chunk_ids": ["microsoft__WSL__release__2_3_22"], "answer_support": [{"memory_node_id": "microsoft__WSL__release__2_3_22", "answer_text": "the experimental useWindowsDnsCache config is removed"}]}
{"prototype_id": "microsoft__WSL_release_window", "repo": "microsoft/WSL", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the microsoft/WSL releases, how does the networking fallback behavior described in release 2.3.25 differ from the networking fallback behavior described in release 2.4.4?", "options": [{"option_id": "A", "text": "2.3.25 falls back to virtioProxy if NAT fails, while 2.4.4 also falls back to virtioProxy if NAT fails but additionally adds socket receive timeouts when starting a new distro."}, {"option_id": "B", "text": "2.3.25 removes bridged networking, while 2.4.4 adds bridged networking."}, {"option_id": "C", "text": "Both releases only update the Windows SDK without networking changes."}, {"option_id": "D", "text": "2.3.25 introduces DNS tunneling, while 2.4.4 disables DNS tunneling."}], "correct_option_id": "A", "expected_answer": "2.3.25 falls back to virtioProxy if NAT fails, while 2.4.4 also falls back to virtioProxy if NAT fails but additionally adds socket receive timeouts when starting a new distro.", "source_chunk_ids": ["microsoft__WSL__release__2_3_25", "microsoft__WSL__release__2_4_4"], "answer_support": [{"memory_node_id": "microsoft__WSL__release__2_3_25", "answer_text": "automatically falls back to virtioProxy networking mode if NAT networking mode fails"}, {"memory_node_id": "microsoft__WSL__release__2_4_4", "answer_text": "Fall back to using virito proxy networking mode if NAT fails ... Socket receive timeouts are added when starting a new distro"}]}
{"prototype_id": "microsoft__WSL_release_window", "repo": "microsoft/WSL", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the microsoft/WSL release window, order the following release-content states from earliest to latest: (1) a release that updates the kernel to 6.6.75 and switches modules to a vhd, (2) a release that updates the kernel to 6.6.87.1-1 and increases the soft file descriptor limit to 1024 * 1024, (3) a release that updates the kernel to 6.6.84.1 and brings back bridged networking mode, (4) a release that updates the kernel to 6.6.87.2 and makes post import distribution checks less strict.", "options": [{"option_id": "A", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "B", "text": "3 -> 1 -> 4 -> 2"}, {"option_id": "C", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "D", "text": "4 -> 2 -> 3 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 3 -> 2 -> 4", "source_chunk_ids": ["microsoft__WSL__release__2_5_1", "microsoft__WSL__release__2_5_6", "microsoft__WSL__release__2_5_7", "microsoft__WSL__release__2_5_9"], "answer_support": [{"memory_node_id": "microsoft__WSL__release__2_5_1", "answer_text": "kernel is updated to 6.6.75 and modules are switched to a vhd"}, {"memory_node_id": "microsoft__WSL__release__2_5_6", "answer_text": "WSL kernel is updated to 6.6.84.1 ... Bridged networking mode is brought back"}, {"memory_node_id": "microsoft__WSL__release__2_5_7", "answer_text": "Linux kernel is updated to 6.6.87.1-1 ... soft file descriptor limit is increased to 1024 * 1024"}, {"memory_node_id": "microsoft__WSL__release__2_5_9", "answer_text": "WSL kernel is updated to 6.6.87.2 ... Post import distribution checks are made less strict"}]}
{"prototype_id": "milvus_io__milvus_release_window", "repo": "milvus-io/milvus", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the milvus-io/milvus releases, which release introduces the Struct in ARRAY data type and enables default JSON shredding?", "options": [{"option_id": "A", "text": "v2.6.3"}, {"option_id": "B", "text": "v2.6.4"}, {"option_id": "C", "text": "v2.6.5"}, {"option_id": "D", "text": "v2.6.6"}], "correct_option_id": "B", "expected_answer": "v2.6.4", "source_chunk_ids": ["milvus_io__milvus__release__v2_6_4"], "answer_support": [{"memory_node_id": "milvus_io__milvus__release__v2_6_4", "answer_text": "introduces Struct in ARRAY data type ... enabled default JSON Shredding"}]}
{"prototype_id": "milvus_io__milvus_release_window", "repo": "milvus-io/milvus", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the milvus-io/milvus releases, how does the security vulnerability addressed in v2.5.21 differ from the one addressed in v2.5.27?", "options": [{"option_id": "A", "text": "v2.5.21 addresses CVE-2025-64513, while v2.5.27 addresses CVE-2026-26190."}, {"option_id": "B", "text": "Both releases address the same CVE-2025-64513."}, {"option_id": "C", "text": "v2.5.21 addresses CVE-2026-26190, while v2.5.27 addresses CVE-2025-64513."}, {"option_id": "D", "text": "Neither release addresses any security vulnerability."}], "correct_option_id": "A", "expected_answer": "v2.5.21 addresses CVE-2025-64513, while v2.5.27 addresses CVE-2026-26190.", "source_chunk_ids": ["milvus_io__milvus__release__v2_5_21", "milvus_io__milvus__release__v2_5_27"], "answer_support": [{"memory_node_id": "milvus_io__milvus__release__v2_5_21", "answer_text": "addresses a critical security vulnerability CVE-2025-64513"}, {"memory_node_id": "milvus_io__milvus__release__v2_5_27", "answer_text": "fixes CVE-2026-26190"}]}
{"prototype_id": "milvus_io__milvus_release_window", "repo": "milvus-io/milvus", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the milvus-io/milvus release window, order the following release-content states from earliest to latest: (1) a release that introduces Geospatial data type and Timestamptz data type, (2) a release that introduces External Collection and Snapshot, (3) a release that introduces search with highlighter and moves query optimization logic to Proxy, (4) a release that introduces Struct in ARRAY data type and enables default JSON shredding.", "options": [{"option_id": "A", "text": "4 -> 1 -> 3 -> 2"}, {"option_id": "B", "text": "1 -> 4 -> 3 -> 2"}, {"option_id": "C", "text": "4 -> 3 -> 1 -> 2"}, {"option_id": "D", "text": "1 -> 3 -> 4 -> 2"}], "correct_option_id": "A", "expected_answer": "4 -> 1 -> 3 -> 2", "source_chunk_ids": ["milvus_io__milvus__release__v2_6_4", "milvus_io__milvus__release__v2_6_6", "milvus_io__milvus__release__v2_6_8", "milvus_io__milvus__release__v3_0_beta"], "answer_support": [{"memory_node_id": "milvus_io__milvus__release__v2_6_4", "answer_text": "introduces Struct in ARRAY data type ... enabled default JSON Shredding"}, {"memory_node_id": "milvus_io__milvus__release__v2_6_6", "answer_text": "introduces Geospatial data type ... Timestamptz data type"}, {"memory_node_id": "milvus_io__milvus__release__v2_6_8", "answer_text": "introduces search with highlighter ... moved query optimization logic to the Proxy"}, {"memory_node_id": "milvus_io__milvus__release__v3_0_beta", "answer_text": "introduces External Collection ... Snapshot"}]}
{"prototype_id": "moby__moby_release_window", "repo": "moby/moby", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the moby/moby releases, how does the networking fix in v29.1.1 differ from the networking fix in v29.1.5?", "options": [{"option_id": "A", "text": "v29.1.1 reverts a PR that broke external DNS resolution on custom bridge networks, while v29.1.5 fixes a regression where established network connections could be disrupted during a container's shutdown grace period."}, {"option_id": "B", "text": "v29.1.1 fixes port mappings in rootless mode, while v29.1.5 fixes DNS config corruption on daemon reload."}, {"option_id": "C", "text": "v29.1.1 fixes --publish-all for Windows containers, while v29.1.5 fixes UDP conntrack entries not being deleted."}, {"option_id": "D", "text": "v29.1.1 fixes container restart when gateway configuration fails, while v29.1.5 fixes encrypted overlay networks not passing traffic."}], "correct_option_id": "A", "expected_answer": "v29.1.1 reverts a PR that broke external DNS resolution on custom bridge networks, while v29.1.5 fixes a regression where established network connections could be disrupted during a container's shutdown grace period.", "source_chunk_ids": ["moby__moby__release__docker_v29_1_1", "moby__moby__release__docker_v29_1_5"], "answer_support": [{"memory_node_id": "moby__moby__release__docker_v29_1_1", "answer_text": "reverts a PR breaking external DNS resolution on all custom bridge networks"}, {"memory_node_id": "moby__moby__release__docker_v29_1_5", "answer_text": "Fixed a regression where established network connections could be disrupted during a container's shutdown grace period"}]}
{"prototype_id": "mochajs__mocha_release_window", "repo": "mochajs/mocha", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the mochajs/mocha releases, which release adds the --fail-hook-affected-tests option to report skipped tests as failed?", "options": [{"option_id": "A", "text": "v12.0.0-beta-4"}, {"option_id": "B", "text": "v12.0.0-beta-5"}, {"option_id": "C", "text": "v12.0.0-beta-6"}, {"option_id": "D", "text": "v12.0.0-beta-7"}], "correct_option_id": "B", "expected_answer": "v12.0.0-beta-5", "source_chunk_ids": ["mochajs__mocha__release__v12_0_0_beta_5"], "answer_support": [{"memory_node_id": "mochajs__mocha__release__v12_0_0_beta_5", "answer_text": "a feature added the --fail-hook-affected-tests option to report skipped tests as failed"}]}
{"prototype_id": "mochajs__mocha_release_window", "repo": "mochajs/mocha", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the mochajs/mocha releases, how does the dependency update in v11.5.0 differ from the dependency update in v11.6.0?", "options": [{"option_id": "A", "text": "v11.5.0 bumps minimatch from ^5.1.6 to ^9.0.5, while v11.6.0 bumps workerpool from ^6.5.1 to ^9.2.0."}, {"option_id": "B", "text": "v11.5.0 bumps workerpool from ^6.5.1 to ^9.2.0, while v11.6.0 bumps minimatch from ^5.1.6 to ^9.0.5."}, {"option_id": "C", "text": "Both releases bump the same dependency, diff, to different versions."}, {"option_id": "D", "text": "v11.5.0 bumps chokidar to v4, while v11.6.0 bumps glob to v13."}], "correct_option_id": "A", "expected_answer": "v11.5.0 bumps minimatch from ^5.1.6 to ^9.0.5, while v11.6.0 bumps workerpool from ^6.5.1 to ^9.2.0.", "source_chunk_ids": ["mochajs__mocha__release__v11_5_0", "mochajs__mocha__release__v11_6_0"], "answer_support": [{"memory_node_id": "mochajs__mocha__release__v11_5_0", "answer_text": "the minimatch dependency was bumped from ^5.1.6 to ^9.0.5"}, {"memory_node_id": "mochajs__mocha__release__v11_6_0", "answer_text": "the workerpool dependency was bumped from ^6.5.1 to ^9.2.0"}]}
{"prototype_id": "mochajs__mocha_release_window", "repo": "mochajs/mocha", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the mochajs/mocha release window, order the following release-content states from earliest to latest: (1) a release that bumps the diff dependency from ^5.2.0 to ^7.0.0, (2) a release that adds a feature to use require to load esm, (3) a release that bumps the minimatch dependency from ^5.1.6 to ^9.0.5, (4) a release that bumps the workerpool dependency from ^6.5.1 to ^9.2.0.", "options": [{"option_id": "A", "text": "1 -> 3 -> 4 -> 2"}, {"option_id": "B", "text": "3 -> 1 -> 4 -> 2"}, {"option_id": "C", "text": "1 -> 4 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 4 -> 1 -> 2"}], "correct_option_id": "A", "expected_answer": "1 -> 3 -> 4 -> 2", "source_chunk_ids": ["mochajs__mocha__release__v11_4_0", "mochajs__mocha__release__v11_5_0", "mochajs__mocha__release__v11_6_0", "mochajs__mocha__release__v11_7_0"], "answer_support": [{"memory_node_id": "mochajs__mocha__release__v11_4_0", "answer_text": "the diff dependency was bumped from ^5.2.0 to ^7.0.0"}, {"memory_node_id": "mochajs__mocha__release__v11_5_0", "answer_text": "the minimatch dependency was bumped from ^5.1.6 to ^9.0.5"}, {"memory_node_id": "mochajs__mocha__release__v11_6_0", "answer_text": "the workerpool dependency was bumped from ^6.5.1 to ^9.2.0"}, {"memory_node_id": "mochajs__mocha__release__v11_7_0", "answer_text": "a feature was added to use require to load esm"}]}
{"prototype_id": "mozilla__pdf_js_release_window", "repo": "mozilla/pdf.js", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the mozilla/pdf.js releases, which release introduces a new JPX decoder based on OpenJPEG that improves JPX image rendering performance and correctness?", "options": [{"option_id": "A", "text": "v4.0.189"}, {"option_id": "B", "text": "v4.2.67"}, {"option_id": "C", "text": "v4.5.136"}, {"option_id": "D", "text": "v5.0.375"}], "correct_option_id": "B", "expected_answer": "v4.2.67", "source_chunk_ids": ["mozilla__pdf_js__release__v4_2_67"], "answer_support": [{"memory_node_id": "mozilla__pdf_js__release__v4_2_67", "answer_text": "includes a new JPX decoder, based on OpenJPEG, which improves JPX image rendering performance and correctness"}]}
{"prototype_id": "mozilla__pdf_js_release_window", "repo": "mozilla/pdf.js", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the mozilla/pdf.js releases, how does the annotation editor improvement described in v4.0.269 differ from the annotation editor improvement described in v4.0.379?", "options": [{"option_id": "A", "text": "v4.0.269 adds a UI for deleting annotations and experimental support for highlight annotations, while v4.0.379 mainly contains improvements and bugfixes for the annotation editor functionality."}, {"option_id": "B", "text": "v4.0.269 introduces a new JPX decoder, while v4.0.379 adds support for ICC profiles."}, {"option_id": "C", "text": "Both releases only update the viewer without annotation editor changes."}, {"option_id": "D", "text": "v4.0.269 removes the annotation editor entirely, while v4.0.379 restores it."}], "correct_option_id": "A", "expected_answer": "v4.0.269 adds a UI for deleting annotations and experimental support for highlight annotations, while v4.0.379 mainly contains improvements and bugfixes for the annotation editor functionality.", "source_chunk_ids": ["mozilla__pdf_js__release__v4_0_269", "mozilla__pdf_js__release__v4_0_379"], "answer_support": [{"memory_node_id": "mozilla__pdf_js__release__v4_0_269", "answer_text": "improvements for the annotation editor, including a UI for deleting annotations and experimental support for highlight annotations"}, {"memory_node_id": "mozilla__pdf_js__release__v4_0_379", "answer_text": "mainly contains improvements and bugfixes for the annotation editor functionality"}]}
{"prototype_id": "mozilla__pdf_js_release_window", "repo": "mozilla/pdf.js", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the mozilla/pdf.js release window, order the following release-content states from earliest to latest: (1) a release that includes a new JPX decoder based on OpenJPEG, (2) a release that announces PDF.js 5.0 with improved JPEG 2000 decoding support and ICC profiles, (3) a release that contains improvements for the annotation editor, font conversion, performance, SMask rendering and the viewer, as well as bugfixes after feedback on the initial PDF.js 5.0 release.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["mozilla__pdf_js__release__v4_2_67", "mozilla__pdf_js__release__v5_0_375", "mozilla__pdf_js__release__v5_1_91"], "answer_support": [{"memory_node_id": "mozilla__pdf_js__release__v4_2_67", "answer_text": "includes a new JPX decoder, based on OpenJPEG"}, {"memory_node_id": "mozilla__pdf_js__release__v5_0_375", "answer_text": "PDF.js 5.0 is a major release ... improved JPEG 2000 decoding support ... support for ICC profiles"}, {"memory_node_id": "mozilla__pdf_js__release__v5_1_91", "answer_text": "improvements for the annotation editor, font conversion, performance, SMask rendering and the viewer, as well as bugfixes and improvements after feedback on the initial PDF.js 5.0 release"}]}
{"prototype_id": "mpv_player__mpv_release_window", "repo": "mpv-player/mpv", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the mpv-player/mpv releases, which release adds the select.lua script and native autoload replacement?", "options": [{"option_id": "A", "text": "v0.38.0"}, {"option_id": "B", "text": "v0.39.0"}, {"option_id": "C", "text": "v0.40.0"}, {"option_id": "D", "text": "v0.41.0"}], "correct_option_id": "B", "expected_answer": "v0.39.0", "source_chunk_ids": ["mpv_player__mpv__release__v0_39_0"], "answer_support": [{"memory_node_id": "mpv_player__mpv__release__v0_39_0", "answer_text": "adds select.lua, native autoload replacement"}]}
{"prototype_id": "mpv_player__mpv_release_window", "repo": "mpv-player/mpv", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the mpv-player/mpv release window, order the following release-content states from earliest to latest: (1) a release that adds javascript scripting support and UWP support, (2) a release that adds the select.lua script and native autoload replacement, (3) a release that makes gpu-next the default and adds context_menu.lua, (4) a release that adds the console.lua interactive REPL and pseudo client side decorations via OSC.", "options": [{"option_id": "A", "text": "1 -> 4 -> 2 -> 3"}, {"option_id": "B", "text": "4 -> 1 -> 2 -> 3"}, {"option_id": "C", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "D", "text": "2 -> 1 -> 3 -> 4"}], "correct_option_id": "A", "expected_answer": "1 -> 4 -> 2 -> 3", "source_chunk_ids": ["mpv_player__mpv__release__v0_26_0", "mpv_player__mpv__release__v0_31_0", "mpv_player__mpv__release__v0_39_0", "mpv_player__mpv__release__v0_41_0"], "answer_support": [{"memory_node_id": "mpv_player__mpv__release__v0_26_0", "answer_text": "add javascript scripting support using MuJS ... Universal Windows Platform (UWP) support"}, {"memory_node_id": "mpv_player__mpv__release__v0_31_0", "answer_text": "added console.lua: interactive REPL for input commands ... implement pseudo client side decorations via OSC"}, {"memory_node_id": "mpv_player__mpv__release__v0_39_0", "answer_text": "A new select.lua script ... A native replacement for autoload.lua has been implemented"}, {"memory_node_id": "mpv_player__mpv__release__v0_41_0", "answer_text": "The libplacebo based gpu-next is now the default ... New context_menu.lua script"}]}
{"prototype_id": "mrdoob__three_js_release_window", "repo": "mrdoob/three.js", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the mrdoob/three.js releases, which release introduces the BatchedMesh addon for batching geometries?", "options": [{"option_id": "A", "text": "r157"}, {"option_id": "B", "text": "r158"}, {"option_id": "C", "text": "r159"}, {"option_id": "D", "text": "r160"}], "correct_option_id": "B", "expected_answer": "r158", "source_chunk_ids": ["mrdoob__three_js__release__r158"], "answer_support": [{"memory_node_id": "mrdoob__three_js__release__r158", "answer_text": "introduces the BatchedMesh addon for batching geometries"}]}
{"prototype_id": "mrdoob__three_js_release_window", "repo": "mrdoob/three.js", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the mrdoob/three.js releases, how does the tone mapping change in r160 differ from the tone mapping change in r162?", "options": [{"option_id": "A", "text": "r160 adds AgX tone mapping, while r162 adds Khronos Neutral Tone Mapping."}, {"option_id": "B", "text": "r160 adds Khronos Neutral Tone Mapping, while r162 adds AgX tone mapping."}, {"option_id": "C", "text": "Both releases add the same tone mapping feature."}, {"option_id": "D", "text": "r160 removes tone mapping, while r162 adds it back."}], "correct_option_id": "A", "expected_answer": "r160 adds AgX tone mapping, while r162 adds Khronos Neutral Tone Mapping.", "source_chunk_ids": ["mrdoob__three_js__release__r160", "mrdoob__three_js__release__r162"], "answer_support": [{"memory_node_id": "mrdoob__three_js__release__r160", "answer_text": "adds AgX tone mapping support to WebGLRenderer"}, {"memory_node_id": "mrdoob__three_js__release__r162", "answer_text": "adds support for Khronos Neutral Tone Mapping in WebGLRenderer"}]}
{"prototype_id": "mrdoob__three_js_release_window", "repo": "mrdoob/three.js", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the mrdoob/three.js release window, order the following release-content states from earliest to latest: (1) a release that moves BatchedMesh to core and adds multi draw support, (2) a release that introduces the BatchedMesh addon for batching geometries, (3) a release that adds getColorAt/setColorAt to BatchedMesh.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3"}, {"option_id": "B", "text": "1 -> 2 -> 3"}, {"option_id": "C", "text": "2 -> 3 -> 1"}, {"option_id": "D", "text": "3 -> 1 -> 2"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3", "source_chunk_ids": ["mrdoob__three_js__release__r158", "mrdoob__three_js__release__r159", "mrdoob__three_js__release__r165"], "answer_support": [{"memory_node_id": "mrdoob__three_js__release__r158", "answer_text": "introduces the BatchedMesh addon for batching geometries"}, {"memory_node_id": "mrdoob__three_js__release__r159", "answer_text": "moves BatchedMesh to core, adds multi draw support"}, {"memory_node_id": "mrdoob__three_js__release__r165", "answer_text": "adds getColorAt/setColorAt to BatchedMesh"}]}
{"prototype_id": "mudler__LocalAI_release_window", "repo": "mudler/LocalAI", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the mudler/LocalAI releases, which release introduces a universal model import feature that auto-detects backends and chat templates from Hugging Face, Ollama, OCI, or local paths?", "options": [{"option_id": "A", "text": "v3.7.0"}, {"option_id": "B", "text": "v3.8.0"}, {"option_id": "C", "text": "v3.9.0"}, {"option_id": "D", "text": "v3.10.0"}], "correct_option_id": "B", "expected_answer": "v3.8.0", "source_chunk_ids": ["mudler__LocalAI__release__v3_8_0"], "answer_support": [{"memory_node_id": "mudler__LocalAI__release__v3_8_0", "answer_text": "universal model import from Hugging Face, Ollama, OCI, or local paths with auto-detection of backends and chat templates"}]}
{"prototype_id": "mudler__LocalAI_release_window", "repo": "mudler/LocalAI", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the mudler/LocalAI releases, how does the agent-related feature introduced in v3.7.0 differ from the agent-related feature introduced in v3.9.0?", "options": [{"option_id": "A", "text": "v3.7.0 introduces Agentic MCP support with WebUI integration, while v3.9.0 introduces an Agent Jobs panel for scheduling and managing background agentic tasks."}, {"option_id": "B", "text": "v3.7.0 introduces an Agent Jobs panel, while v3.9.0 introduces Agentic MCP support."}, {"option_id": "C", "text": "Both releases introduce the same agent feature but with different names."}, {"option_id": "D", "text": "v3.7.0 introduces agent scheduling, while v3.9.0 introduces agent tool use."}], "correct_option_id": "A", "expected_answer": "v3.7.0 introduces Agentic MCP support with WebUI integration, while v3.9.0 introduces an Agent Jobs panel for scheduling and managing background agentic tasks.", "source_chunk_ids": ["mudler__LocalAI__release__v3_7_0", "mudler__LocalAI__release__v3_9_0"], "answer_support": [{"memory_node_id": "mudler__LocalAI__release__v3_7_0", "answer_text": "introduces Agentic MCP support with full WebUI integration"}, {"memory_node_id": "mudler__LocalAI__release__v3_9_0", "answer_text": "introduces an Agent Jobs panel for scheduling and managing background agentic tasks"}]}
{"prototype_id": "mui__material_ui_release_window", "repo": "mui/material-ui", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the mui/material-ui releases, which release introduces the nativeColor feature that eliminates JS color manipulation and unlocks support for all modern color spaces?", "options": [{"option_id": "A", "text": "v7.3.0"}, {"option_id": "B", "text": "v7.2.0"}, {"option_id": "C", "text": "v7.1.0"}, {"option_id": "D", "text": "v7.3.2"}], "correct_option_id": "A", "expected_answer": "v7.3.0", "source_chunk_ids": ["mui__material_ui__release__v7_3_0"], "answer_support": [{"memory_node_id": "mui__material_ui__release__v7_3_0", "answer_text": "the nativeColor feature is shipped, eliminating JS color manipulation and unlocking support for all modern color spaces"}]}
{"prototype_id": "mui__material_ui_release_window", "repo": "mui/material-ui", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the mui/material-ui releases, how does the CSS layers feature differ between v5.18.0 and v7.2.0?", "options": [{"option_id": "A", "text": "v5.18.0 backports CSS layers from v7, while v7.2.0 introduces a modularCssLayers theme option for splitting styles into multiple CSS layers."}, {"option_id": "B", "text": "v5.18.0 introduces CSS layers as a new feature, while v7.2.0 removes CSS layers support."}, {"option_id": "C", "text": "Both releases only update the styled-engine caching without any CSS layers changes."}, {"option_id": "D", "text": "v5.18.0 adds CSS layers to the system package only, while v7.2.0 adds it to the material package only."}], "correct_option_id": "A", "expected_answer": "v5.18.0 backports CSS layers from v7, while v7.2.0 introduces a modularCssLayers theme option for splitting styles into multiple CSS layers.", "source_chunk_ids": ["mui__material_ui__release__v5_18_0", "mui__material_ui__release__v7_2_0"], "answer_support": [{"memory_node_id": "mui__material_ui__release__v5_18_0", "answer_text": "CSS layers are backported from v7 to the system and material-nextjs packages"}, {"memory_node_id": "mui__material_ui__release__v7_2_0", "answer_text": "a modularCssLayers theme option is added for splitting styles into multiple CSS layers"}]}
{"prototype_id": "mui__material_ui_release_window", "repo": "mui/material-ui", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the mui/material-ui release window, order the following release-content states from earliest to latest: (1) a release that adds the Menubar component page to docs, (2) a release that introduces the nativeColor feature, (3) a release that adds support for Tailwind CSS v4, (4) a release that deprecates composed classes in Dialog.", "options": [{"option_id": "A", "text": "4 -> 3 -> 2 -> 1"}, {"option_id": "B", "text": "3 -> 2 -> 1 -> 4"}, {"option_id": "C", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "D", "text": "1 -> 4 -> 3 -> 2"}], "correct_option_id": "A", "expected_answer": "4 -> 3 -> 2 -> 1", "source_chunk_ids": ["mui__material_ui__release__v7_0_2", "mui__material_ui__release__v7_1_0", "mui__material_ui__release__v7_3_0", "mui__material_ui__release__v7_3_10"], "answer_support": [{"memory_node_id": "mui__material_ui__release__v7_0_2", "answer_text": "The Dialog component deprecates composed classes"}, {"memory_node_id": "mui__material_ui__release__v7_1_0", "answer_text": "Material UI now works with Tailwind CSS v4"}, {"memory_node_id": "mui__material_ui__release__v7_3_0", "answer_text": "the nativeColor feature is shipped"}, {"memory_node_id": "mui__material_ui__release__v7_3_10", "answer_text": "the Menubar component page is added to docs"}]}
{"prototype_id": "n8n_io__n8n_release_window", "repo": "n8n-io/n8n", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the n8n-io/n8n releases, how does the handling of scheduled polls differ between n8n@2.21.6 and n8n@2.21.7?", "options": [{"option_id": "A", "text": "2.21.6 acquires expression isolate for scheduled polls, while 2.21.7 additionally reports scheduled-poll isolate acquisition failures via __emitError."}, {"option_id": "B", "text": "2.21.6 reports scheduled-poll isolate acquisition failures via __emitError, while 2.21.7 removes that reporting."}, {"option_id": "C", "text": "Both releases only validate non-empty prompts in AI vendor nodes without any scheduled poll changes."}, {"option_id": "D", "text": "2.21.6 removes expression isolate acquisition, while 2.21.7 adds it back."}], "correct_option_id": "A", "expected_answer": "2.21.6 acquires expression isolate for scheduled polls, while 2.21.7 additionally reports scheduled-poll isolate acquisition failures via __emitError.", "source_chunk_ids": ["n8n_io__n8n__release__n8n_2_21_6", "n8n_io__n8n__release__n8n_2_21_7"], "answer_support": [{"memory_node_id": "n8n_io__n8n__release__n8n_2_21_6", "answer_text": "acquires expression isolate for scheduled polls"}, {"memory_node_id": "n8n_io__n8n__release__n8n_2_21_7", "answer_text": "acquires expression isolate for scheduled polls ... reports scheduled-poll isolate acquisition failures via __emitError"}]}
{"prototype_id": "n8n_io__n8n_release_window", "repo": "n8n-io/n8n", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the n8n-io/n8n release window, order the following release-content states from earliest to latest: (1) a release that limits Insights compaction runs and fixes a langsmith security issue, (2) a release that requires admin push when migrating legacy environments to projects folder, (3) a release that fixes 16 security issues in vm2, ws, protobufjs and more, and upgrades urllib3.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["n8n_io__n8n__release__n8n_1_123_45", "n8n_io__n8n__release__n8n_1_123_46", "n8n_io__n8n__release__n8n_1_123_47"], "answer_support": [{"memory_node_id": "n8n_io__n8n__release__n8n_1_123_45", "answer_text": "limits Insights compaction runs and fixes a security issue in langsmith"}, {"memory_node_id": "n8n_io__n8n__release__n8n_1_123_46", "answer_text": "requires admin push when migrating legacy environments to projects folder"}, {"memory_node_id": "n8n_io__n8n__release__n8n_1_123_47", "answer_text": "fixes 16 security issues in vm2, ws, protobufjs and 4 more, and fixes a security issue in urllib3"}]}
{"prototype_id": "nektos__act_release_window", "repo": "nektos/act", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the nektos/act releases, which release introduces a cli option to set concurrent jobs count and adds models permission level for AI inference responses?", "options": [{"option_id": "A", "text": "v0.2.76"}, {"option_id": "B", "text": "v0.2.78"}, {"option_id": "C", "text": "v0.2.79"}, {"option_id": "D", "text": "v0.2.80"}], "correct_option_id": "B", "expected_answer": "v0.2.78", "source_chunk_ids": ["nektos__act__release__v0_2_78"], "answer_support": [{"memory_node_id": "nektos__act__release__v0_2_78", "answer_text": "new features add a cli option to set concurrent jobs count and add models permission level for AI inference responses"}]}
{"prototype_id": "nektos__act_release_window", "repo": "nektos/act", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the nektos/act releases, how does the artifact-related change in v0.2.63 differ from the artifact-related change in v0.2.67?", "options": [{"option_id": "A", "text": "v0.2.63 introduces an Actions Artifacts v4 backend, while v0.2.67 fixes artifact v4 upload above 8MB."}, {"option_id": "B", "text": "v0.2.63 fixes artifact v4 upload above 8MB, while v0.2.67 introduces an Actions Artifacts v4 backend."}, {"option_id": "C", "text": "Both releases only update artifact-related dependencies without functional changes."}, {"option_id": "D", "text": "v0.2.63 removes artifact support, while v0.2.67 adds it back."}], "correct_option_id": "A", "expected_answer": "v0.2.63 introduces an Actions Artifacts v4 backend, while v0.2.67 fixes artifact v4 upload above 8MB.", "source_chunk_ids": ["nektos__act__release__v0_2_63", "nektos__act__release__v0_2_67"], "answer_support": [{"memory_node_id": "nektos__act__release__v0_2_63", "answer_text": "Actions Artifacts v4 backend"}, {"memory_node_id": "nektos__act__release__v0_2_67", "answer_text": "fix: artifact v4 upload above 8MB"}]}
{"prototype_id": "neovim__neovim_release_window", "repo": "neovim/neovim", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the neovim/neovim releases, which release introduces support for Lua function and description in keymap, API and Lua autocmds, and nvim_buf_get_text?", "options": [{"option_id": "A", "text": "v0.6.1"}, {"option_id": "B", "text": "v0.7.0"}, {"option_id": "C", "text": "v0.8.0"}, {"option_id": "D", "text": "v0.9.0"}], "correct_option_id": "B", "expected_answer": "v0.7.0", "source_chunk_ids": ["neovim__neovim__release__v0_7_0"], "answer_support": [{"memory_node_id": "neovim__neovim__release__v0_7_0", "answer_text": "support for Lua function and description in keymap, API and Lua autocmds, and nvim_buf_get_text"}]}
{"prototype_id": "neovim__neovim_release_window", "repo": "neovim/neovim", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the neovim/neovim releases, how does the treesitter-related change in v0.8.0 differ from the treesitter-related change in v0.9.0?", "options": [{"option_id": "A", "text": "v0.8.0 uses @foo.bar style highlight groups and does not merge queries by default, while v0.9.0 removes g:ts_highlight_lua and deprecates top level indexes to modules."}, {"option_id": "B", "text": "v0.8.0 removes treesitter support entirely, while v0.9.0 adds it back."}, {"option_id": "C", "text": "Both releases only update treesitter parsers without any breaking changes."}, {"option_id": "D", "text": "v0.8.0 introduces treesitter spelling, while v0.9.0 removes treesitter spelling."}], "correct_option_id": "A", "expected_answer": "v0.8.0 uses @foo.bar style highlight groups and does not merge queries by default, while v0.9.0 removes g:ts_highlight_lua and deprecates top level indexes to modules.", "source_chunk_ids": ["neovim__neovim__release__v0_8_0", "neovim__neovim__release__v0_9_0"], "answer_support": [{"memory_node_id": "neovim__neovim__release__v0_8_0", "answer_text": "treesitter: Use @foo.bar style highlight groups; treesitter: Do not merge queries by default"}, {"memory_node_id": "neovim__neovim__release__v0_9_0", "answer_text": "treesitter: Remove g:ts_highlight_lua; treesitter: Deprecate top level indexes to modules"}]}
{"prototype_id": "nestjs__nest_release_window", "repo": "nestjs/nest", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the nestjs/nest releases, which release adds support for topic exchange in RabbitMQ?", "options": [{"option_id": "A", "text": "v11.0.21"}, {"option_id": "B", "text": "v11.1.0"}, {"option_id": "C", "text": "v11.1.1"}, {"option_id": "D", "text": "v11.1.2"}], "correct_option_id": "B", "expected_answer": "v11.1.0", "source_chunk_ids": ["nestjs__nest__release__v11_1_0"], "answer_support": [{"memory_node_id": "nestjs__nest__release__v11_1_0", "answer_text": "adds support for topic exchange in RabbitMQ"}]}
{"prototype_id": "nestjs__nest_release_window", "repo": "nestjs/nest", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the nestjs/nest releases, how does the multer dependency change differ between v10.4.18 and v11.1.5?", "options": [{"option_id": "A", "text": "v10.4.18 bumps multer from 1.4.5-lts.2 to 2.0.0, while v11.1.5 bumps multer from 2.0.1 to 2.0.2."}, {"option_id": "B", "text": "v10.4.18 bumps multer from 2.0.0 to 2.0.1, while v11.1.5 bumps multer from 2.0.1 to 2.0.2."}, {"option_id": "C", "text": "Both releases bump multer from 1.4.5-lts.2 to 2.0.0."}, {"option_id": "D", "text": "v10.4.18 bumps multer from 2.0.1 to 2.0.2, while v11.1.5 bumps multer from 1.4.5-lts.2 to 2.0.0."}], "correct_option_id": "A", "expected_answer": "v10.4.18 bumps multer from 1.4.5-lts.2 to 2.0.0, while v11.1.5 bumps multer from 2.0.1 to 2.0.2.", "source_chunk_ids": ["nestjs__nest__release__v10_4_18", "nestjs__nest__release__v11_1_5"], "answer_support": [{"memory_node_id": "nestjs__nest__release__v10_4_18", "answer_text": "multer is bumped from 1.4.5-lts.2 to 2.0.0"}, {"memory_node_id": "nestjs__nest__release__v11_1_5", "answer_text": "multer is bumped from 2.0.1 to 2.0.2"}]}
{"prototype_id": "nestjs__nest_release_window", "repo": "nestjs/nest", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the nestjs/nest release window, order the following release-content states from earliest to latest: (1) a release that adds fallbackToMimetype support in FileTypeValidator, (2) a release that adds support for topic exchange in RabbitMQ, (3) a release that adds specific transport id to microservices and restores getHeader/appendHeader methods, (4) a release that fixes a regression in loading file-type under Windows OS.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 2 -> 1 -> 3"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["nestjs__nest__release__v11_0_21", "nestjs__nest__release__v11_1_0", "nestjs__nest__release__v11_1_1", "nestjs__nest__release__v11_1_12"], "answer_support": [{"memory_node_id": "nestjs__nest__release__v11_0_21", "answer_text": "adds fallbackToMimetype support in FileTypeValidator"}, {"memory_node_id": "nestjs__nest__release__v11_1_0", "answer_text": "adds support for topic exchange in RabbitMQ"}, {"memory_node_id": "nestjs__nest__release__v11_1_1", "answer_text": "adds specific transport id to microservices and restores getHeader and appendHeader methods"}, {"memory_node_id": "nestjs__nest__release__v11_1_12", "answer_text": "fixes a regression in loading file-type under Windows OS"}]}
{"prototype_id": "netdata__netdata_release_window", "repo": "netdata/netdata", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the netdata/netdata releases, which release introduces a generic SQL collector (alpha) for monitoring any SQL database with custom queries?", "options": [{"option_id": "A", "text": "v2.8.0"}, {"option_id": "B", "text": "v2.9.0"}, {"option_id": "C", "text": "v2.10.0"}, {"option_id": "D", "text": "v2.7.0"}], "correct_option_id": "A", "expected_answer": "v2.8.0", "source_chunk_ids": ["netdata__netdata__release__v2_8_0"], "answer_support": [{"memory_node_id": "netdata__netdata__release__v2_8_0", "answer_text": "generic SQL collector (alpha) for monitoring any SQL database with custom queries"}]}
{"prototype_id": "netdata__netdata_release_window", "repo": "netdata/netdata", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the netdata/netdata releases, how does the SNMP-related change described in v2.3.0 differ from the SNMP-related change described in v2.6.0?", "options": [{"option_id": "A", "text": "v2.3.0 introduces SNMP service discovery for automatic detection and monitoring of SNMP-enabled devices, while v2.6.0 introduces SNMP profile-based collection with 100+ device profiles (alpha) and auto-detection for specific vendors like Cisco, Palo Alto, and F5."}, {"option_id": "B", "text": "v2.3.0 removes SNMP support entirely, while v2.6.0 adds it back."}, {"option_id": "C", "text": "Both releases only fix SNMP collector bugs without introducing new features."}, {"option_id": "D", "text": "v2.3.0 adds SNMP profile-based collection, while v2.6.0 adds SNMP service discovery."}], "correct_option_id": "A", "expected_answer": "v2.3.0 introduces SNMP service discovery for automatic detection and monitoring of SNMP-enabled devices, while v2.6.0 introduces SNMP profile-based collection with 100+ device profiles (alpha) and auto-detection for specific vendors like Cisco, Palo Alto, and F5.", "source_chunk_ids": ["netdata__netdata__release__v2_3_0", "netdata__netdata__release__v2_6_0"], "answer_support": [{"memory_node_id": "netdata__netdata__release__v2_3_0", "answer_text": "SNMP service discovery for automatic detection and monitoring of SNMP-enabled devices"}, {"memory_node_id": "netdata__netdata__release__v2_6_0", "answer_text": "SNMP profile-based collection with 100+ device profiles (alpha) and auto-detection for Cisco, Palo Alto, F5, and more"}]}
{"prototype_id": "netdata__netdata_release_window", "repo": "netdata/netdata", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the netdata/netdata release window, order the following release-content states from earliest to latest: (1) a release that introduces AI-powered monitoring intelligence with MCP server support and natural language questions in AI Insights, (2) a release that introduces Netdata AI for automated troubleshooting, on-demand analysis, and scheduled infrastructure reports, (3) a release that introduces secrets management with 4 resolver types and 4 backends including AWS Secrets Manager and HashiCorp Vault.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["netdata__netdata__release__v2_6_0", "netdata__netdata__release__v2_7_0", "netdata__netdata__release__v2_10_0"], "answer_support": [{"memory_node_id": "netdata__netdata__release__v2_6_0", "answer_text": "AI-powered monitoring intelligence with MCP server support enabling AI assistants to query infrastructure, natural language questions in AI Insights"}, {"memory_node_id": "netdata__netdata__release__v2_7_0", "answer_text": "Netdata AI for automated troubleshooting, on-demand analysis, and scheduled infrastructure reports"}, {"memory_node_id": "netdata__netdata__release__v2_10_0", "answer_text": "secrets management with 4 resolver types and 4 backends (AWS Secrets Manager, Azure Key Vault, GCP Secret Manager, HashiCorp Vault)"}]}
{"prototype_id": "nicolargo__glances_release_window", "repo": "nicolargo/glances", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the nicolargo/glances releases, which release introduces the Browser feature that allows accessing all Glances servers in a single web page?", "options": [{"option_id": "A", "text": "v4.0.2"}, {"option_id": "B", "text": "v4.3.0"}, {"option_id": "C", "text": "v4.4.0"}, {"option_id": "D", "text": "v4.5.0"}], "correct_option_id": "B", "expected_answer": "v4.3.0", "source_chunk_ids": ["nicolargo__glances__release__v4_3_0"], "answer_support": [{"memory_node_id": "nicolargo__glances__release__v4_3_0", "answer_text": "introduces the Browser feature for accessing all Glances servers in a single web page"}]}
{"prototype_id": "nicolargo__glances_release_window", "repo": "nicolargo/glances", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the nicolargo/glances releases, how does the GPU-related change in v4.0.2 differ from the GPU-related change in v4.5.1?", "options": [{"option_id": "A", "text": "v4.0.2 adds AMD GPU support via /sys/class/drm, while v4.5.1 fixes Snap GPU plugin permissions for AMD and NVIDIA."}, {"option_id": "B", "text": "v4.0.2 removes GPU support, while v4.5.1 adds Intel GPU support."}, {"option_id": "C", "text": "Both releases only update GPU plugin documentation without functional changes."}, {"option_id": "D", "text": "v4.0.2 adds NVIDIA GPU support, while v4.5.1 adds AMD GPU support."}], "correct_option_id": "A", "expected_answer": "v4.0.2 adds AMD GPU support via /sys/class/drm, while v4.5.1 fixes Snap GPU plugin permissions for AMD and NVIDIA.", "source_chunk_ids": ["nicolargo__glances__release__v4_0_2", "nicolargo__glances__release__v4_5_1"], "answer_support": [{"memory_node_id": "nicolargo__glances__release__v4_0_2", "answer_text": "adds AMD GPU support through /sys/class/drm"}, {"memory_node_id": "nicolargo__glances__release__v4_5_1", "answer_text": "fixes Snap GPU plugin permissions for AMD and NVIDIA"}]}
{"prototype_id": "nicolargo__glances_release_window", "repo": "nicolargo/glances", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the nicolargo/glances release window, order the following release-content states from earliest to latest: (1) a release that migrates the WebUI from AngularJS to Angular/React/Vue, (2) a release that introduces export of individual process stats and AMD GPU support, (3) a release that adds ZFS monitoring and API token authentication.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["nicolargo__glances__release__v3_3_0", "nicolargo__glances__release__v4_0_2", "nicolargo__glances__release__v4_5_0"], "answer_support": [{"memory_node_id": "nicolargo__glances__release__v3_3_0", "answer_text": "migrates the WebUI from AngularJS to Angular/React/Vue"}, {"memory_node_id": "nicolargo__glances__release__v4_0_2", "answer_text": "introduces export of individual process stats and AMD GPU support"}, {"memory_node_id": "nicolargo__glances__release__v4_5_0", "answer_text": "adds ZFS monitoring and API token authentication"}]}
{"prototype_id": "nlohmann__json_release_window", "repo": "nlohmann/json", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the nlohmann/json releases, which release introduces the SAX interface and support for parsing from wide string types?", "options": [{"option_id": "A", "text": "v3.0.0"}, {"option_id": "B", "text": "v3.2.0"}, {"option_id": "C", "text": "v3.1.0"}, {"option_id": "D", "text": "v3.3.0"}], "correct_option_id": "B", "expected_answer": "v3.2.0", "source_chunk_ids": ["nlohmann__json__release__v3_2_0"], "answer_support": [{"memory_node_id": "nlohmann__json__release__v3_2_0", "answer_text": "introduces a SAX interface for parsing, supports parsing from wide string types"}]}
{"prototype_id": "nlohmann__json_release_window", "repo": "nlohmann/json", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the nlohmann/json releases, how does the binary format support added in v3.8.0 differ from the binary format support added in v3.11.0?", "options": [{"option_id": "A", "text": "v3.8.0 adds binary values for CBOR, BSON, and MessagePack, while v3.11.0 adds BJData format support."}, {"option_id": "B", "text": "v3.8.0 adds UBJSON support, while v3.11.0 adds BSON support."}, {"option_id": "C", "text": "Both releases add the same binary format support."}, {"option_id": "D", "text": "v3.8.0 adds BJData support, while v3.11.0 adds binary values for CBOR."}], "correct_option_id": "A", "expected_answer": "v3.8.0 adds binary values for CBOR, BSON, and MessagePack, while v3.11.0 adds BJData format support.", "source_chunk_ids": ["nlohmann__json__release__v3_8_0", "nlohmann__json__release__v3_11_0"], "answer_support": [{"memory_node_id": "nlohmann__json__release__v3_8_0", "answer_text": "adds support for binary values in CBOR, BSON, and MessagePack"}, {"memory_node_id": "nlohmann__json__release__v3_11_0", "answer_text": "BJData format support"}]}
{"prototype_id": "nlohmann__json_release_window", "repo": "nlohmann/json", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the nlohmann/json release window, order the following release-content states from earliest to latest: (1) a release that adds support for UBJSON format and JSON Merge Patch, (2) a release that introduces extended diagnostics with JSON Pointer in exception messages, (3) a release that adds diagnostic byte positions via JSON_DIAGNOSTIC_POSITIONS, (4) a release that adds optional comment support in JSON parsing and introduces nlohmann::ordered_json.", "options": [{"option_id": "A", "text": "1 -> 4 -> 2 -> 3"}, {"option_id": "B", "text": "4 -> 1 -> 2 -> 3"}, {"option_id": "C", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "D", "text": "2 -> 1 -> 4 -> 3"}], "correct_option_id": "A", "expected_answer": "1 -> 4 -> 2 -> 3", "source_chunk_ids": ["nlohmann__json__release__v3_1_0", "nlohmann__json__release__v3_9_0", "nlohmann__json__release__v3_10_0", "nlohmann__json__release__v3_12_0"], "answer_support": [{"memory_node_id": "nlohmann__json__release__v3_1_0", "answer_text": "adds support for UBJSON format and JSON Merge Patch"}, {"memory_node_id": "nlohmann__json__release__v3_9_0", "answer_text": "adds optional comment support in JSON parsing and introduces nlohmann::ordered_json"}, {"memory_node_id": "nlohmann__json__release__v3_10_0", "answer_text": "introduces extended diagnostics with JSON Pointer in exception messages"}, {"memory_node_id": "nlohmann__json__release__v3_12_0", "answer_text": "adds diagnostic byte positions via JSON_DIAGNOSTIC_POSITIONS"}]}
{"prototype_id": "nodejs__node_release_window", "repo": "nodejs/node", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the nodejs/node releases, how does the security fix for CVE-2026-21717 differ between v20.20.2 and v22.22.2?", "options": [{"option_id": "A", "text": "v20.20.2 fixes array index hash collision, while v22.22.2 tests array index hash collision."}, {"option_id": "B", "text": "v20.20.2 tests array index hash collision, while v22.22.2 fixes array index hash collision."}, {"option_id": "C", "text": "Both releases only update root certificates without addressing CVE-2026-21717."}, {"option_id": "D", "text": "v20.20.2 adds permission check to realpath.native, while v22.22.2 uses null prototype for headersDistinct."}], "correct_option_id": "A", "expected_answer": "v20.20.2 fixes array index hash collision, while v22.22.2 tests array index hash collision.", "source_chunk_ids": ["nodejs__node__release__v20_20_2", "nodejs__node__release__v22_22_2"], "answer_support": [{"memory_node_id": "nodejs__node__release__v20_20_2", "answer_text": "CVE-2026-21717 fixes array index hash collision"}, {"memory_node_id": "nodejs__node__release__v22_22_2", "answer_text": "CVE-2026-21717 tests array index hash collision"}]}
{"prototype_id": "nolimits4web__swiper_release_window", "repo": "nolimits4web/swiper", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the nolimits4web/swiper releases, which release introduces the a11y module prop scrollOnFocus and element support for using slots as swiper wrappers?", "options": [{"option_id": "A", "text": "v11.1.4"}, {"option_id": "B", "text": "v11.1.5"}, {"option_id": "C", "text": "v11.1.6"}, {"option_id": "D", "text": "v11.1.7"}], "correct_option_id": "C", "expected_answer": "v11.1.6", "source_chunk_ids": ["nolimits4web__swiper__release__v11_1_6"], "answer_support": [{"memory_node_id": "nolimits4web__swiper__release__v11_1_6", "answer_text": "new features: an a11y module prop scrollOnFocus, and element support for using slots as swiper wrappers"}]}
{"prototype_id": "nolimits4web__swiper_release_window", "repo": "nolimits4web/swiper", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the nolimits4web/swiper releases, how does the navigation-related change in v12.0.0 differ from the navigation-related change in v12.0.2?", "options": [{"option_id": "A", "text": "v12.0.0 moves to SVG icons for navigation, while v12.0.2 adds an addIcons parameter to add SVG icons to nav buttons."}, {"option_id": "B", "text": "v12.0.0 removes navigation buttons entirely, while v12.0.2 restores them with CSS styles."}, {"option_id": "C", "text": "Both releases only fix navigation button click events without adding new features."}, {"option_id": "D", "text": "v12.0.0 introduces navigation button slots, while v12.0.2 deprecates SVG icons."}], "correct_option_id": "A", "expected_answer": "v12.0.0 moves to SVG icons for navigation, while v12.0.2 adds an addIcons parameter to add SVG icons to nav buttons.", "source_chunk_ids": ["nolimits4web__swiper__release__v12_0_0", "nolimits4web__swiper__release__v12_0_2"], "answer_support": [{"memory_node_id": "nolimits4web__swiper__release__v12_0_0", "answer_text": "move to SVG icons for navigation"}, {"memory_node_id": "nolimits4web__swiper__release__v12_0_2", "answer_text": "new addIcons parameter to add SVG icons to nav buttons"}]}
{"prototype_id": "nomic_ai__gpt4all_release_window", "repo": "nomic-ai/gpt4all", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the nomic-ai/gpt4all releases, which release introduces a complete UI overhaul and switches LocalDocs to use nomic-embed-text-v1.5 with exact KNN search via usearch?", "options": [{"option_id": "A", "text": "v2.8.0"}, {"option_id": "B", "text": "v3.0.0"}, {"option_id": "C", "text": "v3.1.0"}, {"option_id": "D", "text": "v3.5.0"}], "correct_option_id": "B", "expected_answer": "v3.0.0", "source_chunk_ids": ["nomic_ai__gpt4all__release__v3_0_0"], "answer_support": [{"memory_node_id": "nomic_ai__gpt4all__release__v3_0_0", "answer_text": "complete UI overhaul ... LocalDocs is improved by using nomic-embed-text-v1.5 ... doing exact KNN search with usearch"}]}
{"prototype_id": "nomic_ai__gpt4all_release_window", "repo": "nomic-ai/gpt4all", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the nomic-ai/gpt4all release window, order the following release-content states from earliest to latest: (1) a release that adds support for the llama.cpp CUDA backend and InternLM models, (2) a release that introduces a complete UI overhaul and switches LocalDocs to use nomic-embed-text-v1.5 with exact KNN search, (3) a release that adds native DeepSeek-R1-Distill support and completely replaces the chat templating parser.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["nomic_ai__gpt4all__release__v2_8_0", "nomic_ai__gpt4all__release__v3_0_0", "nomic_ai__gpt4all__release__v3_8_0"], "answer_support": [{"memory_node_id": "nomic_ai__gpt4all__release__v2_8_0", "answer_text": "adding support for the llama.cpp CUDA backend ... support for InternLM models"}, {"memory_node_id": "nomic_ai__gpt4all__release__v3_0_0", "answer_text": "complete UI overhaul ... LocalDocs is improved by using nomic-embed-text-v1.5 ... doing exact KNN search with usearch"}, {"memory_node_id": "nomic_ai__gpt4all__release__v3_8_0", "answer_text": "native DeepSeek-R1-Distill support ... chat templating parser is completely replaced"}]}
{"prototype_id": "nushell__nushell_release_window", "repo": "nushell/nushell", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the nushell/nushell releases, which release includes a note that version 0.97.0 was never released and that 0.97.1 is the next major version after 0.96.1?", "options": [{"option_id": "A", "text": "0.96.1"}, {"option_id": "B", "text": "0.97.1"}, {"option_id": "C", "text": "0.98.0"}, {"option_id": "D", "text": "0.99.0"}], "correct_option_id": "B", "expected_answer": "0.97.1", "source_chunk_ids": ["nushell__nushell__release__0_97_1"], "answer_support": [{"memory_node_id": "nushell__nushell__release__0_97_1", "answer_text": "Note that 0.97.0 was never released; this is the next major version after 0.96.1."}]}
{"prototype_id": "nushell__nushell_release_window", "repo": "nushell/nushell", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the nushell/nushell releases, how does the contributor list in release 0.94.2 differ from the contributor list in release 0.94.1?", "options": [{"option_id": "A", "text": "0.94.2 credits only @devyn, while 0.94.1 credits @devyn, @fdncred, @IanManske, and @WindSoilder."}, {"option_id": "B", "text": "0.94.2 credits @devyn and @fdncred, while 0.94.1 credits only @devyn."}, {"option_id": "C", "text": "Both releases credit the same set of contributors."}, {"option_id": "D", "text": "0.94.2 credits @devyn, @fdncred, @IanManske, and @WindSoilder, while 0.94.1 credits only @devyn."}], "correct_option_id": "A", "expected_answer": "0.94.2 credits only @devyn, while 0.94.1 credits @devyn, @fdncred, @IanManske, and @WindSoilder.", "source_chunk_ids": ["nushell__nushell__release__0_94_2", "nushell__nushell__release__0_94_1"], "answer_support": [{"memory_node_id": "nushell__nushell__release__0_94_2", "answer_text": "The release was made possible by PR contributions from @devyn."}, {"memory_node_id": "nushell__nushell__release__0_94_1", "answer_text": "The release was made possible by PR contributions from @devyn, @fdncred, @IanManske, and @WindSoilder."}]}
{"prototype_id": "nuxt__nuxt_release_window", "repo": "nuxt/nuxt", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the nuxt/nuxt releases, which release introduces lazy hydration macros (defineLazyHydrationComponent) for ergonomic hydration control?", "options": [{"option_id": "A", "text": "v4.0.1"}, {"option_id": "B", "text": "v3.18.0"}, {"option_id": "C", "text": "v4.0.2"}, {"option_id": "D", "text": "v3.18.1"}], "correct_option_id": "B", "expected_answer": "v3.18.0", "source_chunk_ids": ["nuxt__nuxt__release__v3_18_0"], "answer_support": [{"memory_node_id": "nuxt__nuxt__release__v3_18_0", "answer_text": "highlights include lazy hydration macros (defineLazyHydrationComponent) for ergonomic hydration control"}]}
{"prototype_id": "nuxt__nuxt_release_window", "repo": "nuxt/nuxt", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the nuxt/nuxt releases, how does the abort control for data fetching described in v4.2.0 differ from the abortController option added in v3.20.0?", "options": [{"option_id": "A", "text": "v4.2.0 introduces AbortController signals directly within useAsyncData, while v3.20.0 adds an abortController option to useAsyncData."}, {"option_id": "B", "text": "v4.2.0 removes abort control, while v3.20.0 adds it."}, {"option_id": "C", "text": "Both releases only update error pages without data fetching changes."}, {"option_id": "D", "text": "v4.2.0 adds abort control to useFetch, while v3.20.0 adds it to useAsyncData."}], "correct_option_id": "A", "expected_answer": "v4.2.0 introduces AbortController signals directly within useAsyncData, while v3.20.0 adds an abortController option to useAsyncData.", "source_chunk_ids": ["nuxt__nuxt__release__v4_2_0", "nuxt__nuxt__release__v3_20_0"], "answer_support": [{"memory_node_id": "nuxt__nuxt__release__v4_2_0", "answer_text": "abort control for data fetching via AbortController signals in useAsyncData"}, {"memory_node_id": "nuxt__nuxt__release__v3_20_0", "answer_text": "adding abortController option to useAsyncData"}]}
{"prototype_id": "nuxt__nuxt_release_window", "repo": "nuxt/nuxt", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the nuxt/nuxt release window, order the following release-content states from earliest to latest: (1) a release that adds route rule layouts via appLayout property, (2) a release that introduces createUseFetch and createUseAsyncData, (3) a release that adds abort control for data fetching via AbortController signals in useAsyncData.", "options": [{"option_id": "A", "text": "3 -> 1 -> 2"}, {"option_id": "B", "text": "1 -> 2 -> 3"}, {"option_id": "C", "text": "2 -> 3 -> 1"}, {"option_id": "D", "text": "1 -> 3 -> 2"}], "correct_option_id": "A", "expected_answer": "3 -> 1 -> 2", "source_chunk_ids": ["nuxt__nuxt__release__v4_2_0", "nuxt__nuxt__release__v4_3_0", "nuxt__nuxt__release__v4_4_0"], "answer_support": [{"memory_node_id": "nuxt__nuxt__release__v4_2_0", "answer_text": "abort control for data fetching via AbortController signals in useAsyncData"}, {"memory_node_id": "nuxt__nuxt__release__v4_3_0", "answer_text": "route rule layouts via appLayout property"}, {"memory_node_id": "nuxt__nuxt__release__v4_4_0", "answer_text": "createUseFetch and createUseAsyncData"}]}
{"prototype_id": "obsproject__obs_studio_release_window", "repo": "obsproject/obs-studio", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the obsproject/obs-studio releases, which release introduces a basic plugin manager and opt-in automatic crash log upload for Windows and macOS?", "options": [{"option_id": "A", "text": "OBS Studio 31.1.0"}, {"option_id": "B", "text": "OBS Studio 32.0.0"}, {"option_id": "C", "text": "OBS Studio 32.1.0"}, {"option_id": "D", "text": "OBS Studio 31.0.0"}], "correct_option_id": "B", "expected_answer": "OBS Studio 32.0.0", "source_chunk_ids": ["obsproject__obs_studio__release__32_0_0"], "answer_support": [{"memory_node_id": "obsproject__obs_studio__release__32_0_0", "answer_text": "Added a basic plugin manager ... Added opt-in automatic crash log upload for Windows and macOS"}]}
{"prototype_id": "obsproject__obs_studio_release_window", "repo": "obsproject/obs-studio", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the obsproject/obs-studio releases, how does the Audio Mixer change described in OBS Studio 32.1.0 differ from the audio-related change described in OBS Studio 31.0.0?", "options": [{"option_id": "A", "text": "32.1.0 overhauls the Audio Mixer with new layouts, pinning, and preview sources, while 31.0.0 splits NVIDIA Audio Effects from Noise Suppression."}, {"option_id": "B", "text": "32.1.0 removes the Audio Mixer entirely, while 31.0.0 adds NVIDIA Background Blur."}, {"option_id": "C", "text": "Both releases only update the CEF version without audio changes."}, {"option_id": "D", "text": "32.1.0 adds VAD to NVIDIA RTX Audio Effects, while 31.0.0 introduces the overhauled Audio Mixer."}], "correct_option_id": "A", "expected_answer": "32.1.0 overhauls the Audio Mixer with new layouts, pinning, and preview sources, while 31.0.0 splits NVIDIA Audio Effects from Noise Suppression.", "source_chunk_ids": ["obsproject__obs_studio__release__32_1_0", "obsproject__obs_studio__release__31_0_0"], "answer_support": [{"memory_node_id": "obsproject__obs_studio__release__32_1_0", "answer_text": "Overhauled the Audio Mixer ... Adjusted the horizontal layout ... Added ability to pin audio sources ... Sources in the preview are now shown while in Studio Mode"}, {"memory_node_id": "obsproject__obs_studio__release__31_0_0", "answer_text": "Split NVIDIA Audio Effects from Noise Suppression"}]}
{"prototype_id": "obsproject__obs_studio_release_window", "repo": "obsproject/obs-studio", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the obsproject/obs-studio release window, order the following release-content states from earliest to latest: (1) a release that adds Windows on Arm support and preview zoom controls, (2) a release that adds a basic plugin manager and Hybrid MOV support, (3) a release that overhauls the Audio Mixer and adds WebRTC Simulcast Support.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["obsproject__obs_studio__release__31_1_0", "obsproject__obs_studio__release__32_0_0", "obsproject__obs_studio__release__32_1_0"], "answer_support": [{"memory_node_id": "obsproject__obs_studio__release__31_1_0", "answer_text": "Added support for Windows on Arm ... Added preview zoom controls"}, {"memory_node_id": "obsproject__obs_studio__release__32_0_0", "answer_text": "Added a basic plugin manager ... Added Hybrid MOV support"}, {"memory_node_id": "obsproject__obs_studio__release__32_1_0", "answer_text": "Overhauled the Audio Mixer ... Added WebRTC Simulcast Support"}]}
{"prototype_id": "ocornut__imgui_release_window", "repo": "ocornut/imgui", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the ocornut/imgui releases, which release introduces the io.ConfigDebugHighlightIdConflicts debug feature to detect duplicate identifiers?", "options": [{"option_id": "A", "text": "v1.91.0"}, {"option_id": "B", "text": "v1.91.2"}, {"option_id": "C", "text": "v1.91.4"}, {"option_id": "D", "text": "v1.91.6"}], "correct_option_id": "B", "expected_answer": "v1.91.2", "source_chunk_ids": ["ocornut__imgui__release__v1_91_2"], "answer_support": [{"memory_node_id": "ocornut__imgui__release__v1_91_2", "answer_text": "adds io.ConfigDebugHighlightIdConflicts debug feature to detect duplicate identifiers"}]}
{"prototype_id": "ocornut__imgui_release_window", "repo": "ocornut/imgui", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the ocornut/imgui release window, order the following release-content states from earliest to latest: (1) a release that adds concave polygon rendering, (2) a release that introduces multi-select and box-select, (3) a release that adds io.ConfigDebugHighlightIdConflicts, (4) a release that enables opt-in error recovery features.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "C", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["ocornut__imgui__release__v1_90_5", "ocornut__imgui__release__v1_91_0", "ocornut__imgui__release__v1_91_2", "ocornut__imgui__release__v1_91_3"], "answer_support": [{"memory_node_id": "ocornut__imgui__release__v1_90_5", "answer_text": "adds concave polygon rendering"}, {"memory_node_id": "ocornut__imgui__release__v1_91_0", "answer_text": "introduces multi-select, box-select"}, {"memory_node_id": "ocornut__imgui__release__v1_91_2", "answer_text": "adds io.ConfigDebugHighlightIdConflicts"}, {"memory_node_id": "ocornut__imgui__release__v1_91_3", "answer_text": "enables opt-in error recovery features"}]}
{"prototype_id": "ollama__ollama_release_window", "repo": "ollama/ollama", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the ollama/ollama releases, which release introduces the Hermes Agent that learns with the user and automatically creates skills?", "options": [{"option_id": "A", "text": "v0.20.6"}, {"option_id": "B", "text": "v0.21.0"}, {"option_id": "C", "text": "v0.21.1"}, {"option_id": "D", "text": "v0.23.0"}], "correct_option_id": "B", "expected_answer": "v0.21.0", "source_chunk_ids": ["ollama__ollama__release__v0_21_0"], "answer_support": [{"memory_node_id": "ollama__ollama__release__v0_21_0", "answer_text": "introduces Hermes Agent, which learns with the user and automatically creates skills"}]}
{"prototype_id": "ollama__ollama_release_window", "repo": "ollama/ollama", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the ollama/ollama releases, how does the Claude Desktop support in v0.23.0 differ from the Claude Desktop handling in v0.23.2?", "options": [{"option_id": "A", "text": "v0.23.0 introduces Claude Desktop support with `ollama launch claude-desktop`, while v0.23.2 removes it because the integration is limited to Anthropic models."}, {"option_id": "B", "text": "v0.23.0 removes Claude Desktop, while v0.23.2 adds it back with web search."}, {"option_id": "C", "text": "Both releases only update the MLX runner without changing Claude Desktop."}, {"option_id": "D", "text": "v0.23.0 adds Claude Desktop for Windows only, while v0.23.2 extends it to macOS."}], "correct_option_id": "A", "expected_answer": "v0.23.0 introduces Claude Desktop support with `ollama launch claude-desktop`, while v0.23.2 removes it because the integration is limited to Anthropic models.", "source_chunk_ids": ["ollama__ollama__release__v0_23_0", "ollama__ollama__release__v0_23_2"], "answer_support": [{"memory_node_id": "ollama__ollama__release__v0_23_0", "answer_text": "Claude Desktop is now supported with `ollama launch claude-desktop`"}, {"memory_node_id": "ollama__ollama__release__v0_23_2", "answer_text": "`ollama launch` no longer includes Claude Desktop due to the third-party integration being limited to Anthropic models"}]}
{"prototype_id": "ollama__ollama_release_window", "repo": "ollama/ollama", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the ollama/ollama release window, order the following release-content states from earliest to latest: (1) a release that adds web search and web fetch plugin for OpenClaw, (2) a release that introduces Gemma 4 models, (3) a release that adds support for the Codex App, (4) a release that makes Ollama a provider in OpenClaw.", "options": [{"option_id": "A", "text": "4 -> 1 -> 2 -> 3"}, {"option_id": "B", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "C", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "D", "text": "4 -> 2 -> 1 -> 3"}], "correct_option_id": "A", "expected_answer": "4 -> 1 -> 2 -> 3", "source_chunk_ids": ["ollama__ollama__release__v0_18_0", "ollama__ollama__release__v0_18_1", "ollama__ollama__release__v0_20_0", "ollama__ollama__release__v0_24_0"], "answer_support": [{"memory_node_id": "ollama__ollama__release__v0_18_0", "answer_text": "Ollama is now a provider in OpenClaw"}, {"memory_node_id": "ollama__ollama__release__v0_18_1", "answer_text": "Ollama ships with web search and web fetch plugin for OpenClaw"}, {"memory_node_id": "ollama__ollama__release__v0_20_0", "answer_text": "introduces Gemma 4 models"}, {"memory_node_id": "ollama__ollama__release__v0_24_0", "answer_text": "includes support for the Codex App"}]}
{"prototype_id": "open_webui__open_webui_release_window", "repo": "open-webui/open-webui", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the open-webui/open-webui releases, which release introduces the official Open WebUI Desktop App for Mac, Windows, and Linux?", "options": [{"option_id": "A", "text": "v0.8.0"}, {"option_id": "B", "text": "v0.9.0"}, {"option_id": "C", "text": "v0.8.11"}, {"option_id": "D", "text": "v0.9.6"}], "correct_option_id": "B", "expected_answer": "v0.9.0", "source_chunk_ids": ["open_webui__open_webui__release__v0_9_0"], "answer_support": [{"memory_node_id": "open_webui__open_webui__release__v0_9_0", "answer_text": "the official Open WebUI Desktop App is released for Mac, Windows, and Linux"}]}
{"prototype_id": "open_webui__open_webui_release_window", "repo": "open-webui/open-webui", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the open-webui/open-webui releases, how does the knowledge base file management change described in v0.6.42 differ from the knowledge base feature described in v0.9.6?", "options": [{"option_id": "A", "text": "v0.6.42 introduces server-side pagination loading 30 files at a time, while v0.9.6 introduces knowledge base folders and a filesystem tool for knowledge bases."}, {"option_id": "B", "text": "v0.6.42 removes knowledge base file management, while v0.9.6 adds server-side pagination."}, {"option_id": "C", "text": "Both releases introduce the same knowledge base sync tool."}, {"option_id": "D", "text": "v0.6.42 adds knowledge base folders, while v0.9.6 adds server-side pagination."}], "correct_option_id": "A", "expected_answer": "v0.6.42 introduces server-side pagination loading 30 files at a time, while v0.9.6 introduces knowledge base folders and a filesystem tool for knowledge bases.", "source_chunk_ids": ["open_webui__open_webui__release__v0_6_42", "open_webui__open_webui__release__v0_9_6"], "answer_support": [{"memory_node_id": "open_webui__open_webui__release__v0_6_42", "answer_text": "knowledge base file management is overhauled with server-side pagination loading 30 files at a time"}, {"memory_node_id": "open_webui__open_webui__release__v0_9_6", "answer_text": "knowledge base folders are added. A filesystem tool for knowledge bases is added."}]}
{"prototype_id": "open_webui__open_webui_release_window", "repo": "open-webui/open-webui", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the open-webui/open-webui release window, order the following release-content states from earliest to latest: (1) a release that adds sign-in rate limiting and group channels, (2) a release that adds native function calling with built-in tools, (3) a release that adds an analytics dashboard and experimental Skills support, (4) a release that adds the official Open WebUI Desktop App.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["open_webui__open_webui__release__v0_6_41", "open_webui__open_webui__release__v0_7_0", "open_webui__open_webui__release__v0_8_0", "open_webui__open_webui__release__v0_9_0"], "answer_support": [{"memory_node_id": "open_webui__open_webui__release__v0_6_41", "answer_text": "sign-in rate limiting is implemented ... Group channels are introduced"}, {"memory_node_id": "open_webui__open_webui__release__v0_7_0", "answer_text": "native function calling with built-in tools is added"}, {"memory_node_id": "open_webui__open_webui__release__v0_8_0", "answer_text": "an analytics dashboard is added ... Experimental support for Skills is added"}, {"memory_node_id": "open_webui__open_webui__release__v0_9_0", "answer_text": "the official Open WebUI Desktop App is released"}]}
{"prototype_id": "opencv__opencv_release_window", "repo": "opencv/opencv", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the opencv/opencv releases, which release introduces a new Windows package with OpenCV DNN accelerated by Inference Engine (DLDT)?", "options": [{"option_id": "A", "text": "OpenCV 4.1.1"}, {"option_id": "B", "text": "OpenCV 4.2.0"}, {"option_id": "C", "text": "OpenCV 4.3.0"}, {"option_id": "D", "text": "OpenCV 4.4.0"}], "correct_option_id": "C", "expected_answer": "OpenCV 4.3.0", "source_chunk_ids": ["opencv__opencv__release__4_3_0"], "answer_support": [{"memory_node_id": "opencv__opencv__release__4_3_0", "answer_text": "introduces a new Windows package with OpenCV DNN accelerated by Inference Engine (DLDT)"}]}
{"prototype_id": "opencv__opencv_release_window", "repo": "opencv/opencv", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the opencv/opencv releases, how does the package availability described in OpenCV 4.9.0 differ from the package availability described in OpenCV 4.8.1?", "options": [{"option_id": "A", "text": "4.9.0 adds Android AAR availability on Maven Central and includes docs package, while 4.8.1 does not mention Maven Central and lacks docs package."}, {"option_id": "B", "text": "4.9.0 removes iOS framework support, while 4.8.1 includes it."}, {"option_id": "C", "text": "Both releases provide identical package sets with no differences."}, {"option_id": "D", "text": "4.9.0 only provides Windows executable, while 4.8.1 provides Android, iOS, and Windows."}], "correct_option_id": "A", "expected_answer": "4.9.0 adds Android AAR availability on Maven Central and includes docs package, while 4.8.1 does not mention Maven Central and lacks docs package.", "source_chunk_ids": ["opencv__opencv__release__4_9_0", "opencv__opencv__release__4_8_1"], "answer_support": [{"memory_node_id": "opencv__opencv__release__4_9_0", "answer_text": "Android package is also available as AAR on Maven Central starting from this version, and lists SHA256 sums for Android SDK, iOS framework, Windows executable, and docs."}, {"memory_node_id": "opencv__opencv__release__4_8_1", "answer_text": "lists SHA256 sums for Android SDK, iOS framework, and Windows executable."}]}
{"prototype_id": "OpenHands__OpenHands_release_window", "repo": "OpenHands/OpenHands", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the OpenHands/OpenHands releases, which release introduces a new UI for landing and conversation pages along with a bring your own key (BYOK) feature in OpenHands Cloud?", "options": [{"option_id": "A", "text": "0.56.0"}, {"option_id": "B", "text": "0.57.0"}, {"option_id": "C", "text": "0.58.0"}, {"option_id": "D", "text": "0.59.0"}], "correct_option_id": "B", "expected_answer": "0.57.0", "source_chunk_ids": ["OpenHands__OpenHands__release__0_57_0"], "answer_support": [{"memory_node_id": "OpenHands__OpenHands__release__0_57_0", "answer_text": "introduces a new UI for landing and conversation pages and a new bring your own key (BYOK) feature in OpenHands Cloud"}]}
{"prototype_id": "OpenHands__OpenHands_release_window", "repo": "OpenHands/OpenHands", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the OpenHands/OpenHands release window, order the following release-content states from earliest to latest: (1) a release that adds support for AGENTS.md files in microagents, (2) a release that adds a task tracking tool and planning mode for long-horizon tasks, (3) a release that adds an LLM risk analyzer, (4) a release that adds MCP support for CLI.", "options": [{"option_id": "A", "text": "4 -> 2 -> 3 -> 1"}, {"option_id": "B", "text": "4 -> 3 -> 2 -> 1"}, {"option_id": "C", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "D", "text": "2 -> 1 -> 4 -> 3"}], "correct_option_id": "A", "expected_answer": "4 -> 2 -> 3 -> 1", "source_chunk_ids": ["OpenHands__OpenHands__release__0_51_0", "OpenHands__OpenHands__release__0_54_0", "OpenHands__OpenHands__release__0_55_0", "OpenHands__OpenHands__release__0_56_0"], "answer_support": [{"memory_node_id": "OpenHands__OpenHands__release__0_51_0", "answer_text": "Add MCP support for CLI"}, {"memory_node_id": "OpenHands__OpenHands__release__0_54_0", "answer_text": "Added task tracking tool and planning mode for long-horizon tasks"}, {"memory_node_id": "OpenHands__OpenHands__release__0_55_0", "answer_text": "Added LLM risk analyzer"}, {"memory_node_id": "OpenHands__OpenHands__release__0_56_0", "answer_text": "Added support for AGENTS.md files in microagents"}]}
{"prototype_id": "openobserve__openobserve_release_window", "repo": "openobserve/openobserve", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the openobserve/openobserve releases, which release introduces the Service Catalog for traces with a topology view and side-panel drill-downs?", "options": [{"option_id": "A", "text": "v0.70.0"}, {"option_id": "B", "text": "v0.80.0"}, {"option_id": "C", "text": "v0.90.0"}, {"option_id": "D", "text": "v0.90.1"}], "correct_option_id": "C", "expected_answer": "v0.90.0", "source_chunk_ids": ["openobserve__openobserve__release__v0_90_0"], "answer_support": [{"memory_node_id": "openobserve__openobserve__release__v0_90_0", "answer_text": "introduces the Service Catalog for traces with topology view and side-panel drill-downs"}]}
{"prototype_id": "openobserve__openobserve_release_window", "repo": "openobserve/openobserve", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the openobserve/openobserve release window, order the following release-content states from earliest to latest: (1) a release that introduces LLM Observability with DAG graph visualization, (2) a release that introduces ML-based Anomaly Detection using Random Cut Forest, (3) a release that introduces the Service Catalog for traces, (4) a patch release that fixes identity and correlate API auth.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["openobserve__openobserve__release__v0_70_0", "openobserve__openobserve__release__v0_80_0", "openobserve__openobserve__release__v0_90_0", "openobserve__openobserve__release__v0_90_2"], "answer_support": [{"memory_node_id": "openobserve__openobserve__release__v0_70_0", "answer_text": "introduces LLM Observability with DAG graph visualization"}, {"memory_node_id": "openobserve__openobserve__release__v0_80_0", "answer_text": "introducing ML-based Anomaly Detection using the Random Cut Forest algorithm"}, {"memory_node_id": "openobserve__openobserve__release__v0_90_0", "answer_text": "introduces the Service Catalog for traces"}, {"memory_node_id": "openobserve__openobserve__release__v0_90_2", "answer_text": "fixes for identity and correlate API auth"}]}
{"prototype_id": "osquery__osquery_release_window", "repo": "osquery/osquery", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the osquery/osquery releases, which release introduces native Apple Silicon (M1) support to the macOS platform?", "options": [{"option_id": "A", "text": "5.0.1"}, {"option_id": "B", "text": "5.2.2"}, {"option_id": "C", "text": "5.3.0"}, {"option_id": "D", "text": "5.4.0"}], "correct_option_id": "B", "expected_answer": "5.2.2", "source_chunk_ids": ["osquery__osquery__release__5_2_2"], "answer_support": [{"memory_node_id": "osquery__osquery__release__5_2_2", "answer_text": "Osquery 5.2.2 brings native Apple Silicon (M1) support to the macOS platform."}]}
{"prototype_id": "osquery__osquery_release_window", "repo": "osquery/osquery", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the osquery/osquery releases, how does the security update in release 5.2.3 differ from the feature addition in release 5.9.1?", "options": [{"option_id": "A", "text": "5.2.3 focuses on updating third-party libraries to address CVEs and drops unmaintained tables, while 5.9.1 adds support for Windows on Arm and a new string_batch logger request type."}, {"option_id": "B", "text": "5.2.3 introduces Apple Silicon support, while 5.9.1 removes the shortcut_files table."}, {"option_id": "C", "text": "Both releases only update OpenSSL to the same version."}, {"option_id": "D", "text": "5.2.3 adds the unified_log table, while 5.9.1 deprecates the smart_drive_info table."}], "correct_option_id": "A", "expected_answer": "5.2.3 focuses on updating third-party libraries to address CVEs and drops unmaintained tables, while 5.9.1 adds support for Windows on Arm and a new string_batch logger request type.", "source_chunk_ids": ["osquery__osquery__release__5_2_3", "osquery__osquery__release__5_9_1"], "answer_support": [{"memory_node_id": "osquery__osquery__release__5_2_3", "answer_text": "Osquery 5.2.3 is a security update that focuses on updating some third-party libraries which contained CVEs that could affect osquery. Additionally some other third-party libraries and tables have been dropped, since they were not maintained or considered safe anymore."}, {"memory_node_id": "osquery__osquery__release__5_9_1", "answer_text": "Big shoutout for the Windows Arm port! New Features: Add support for Windows on Arm, logger: Add new string_batch request type to compliment existing string type."}]}
{"prototype_id": "PaddlePaddle__PaddleOCR_release_window", "repo": "PaddlePaddle/PaddleOCR", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the PaddlePaddle/PaddleOCR releases, which release introduces the end-to-end text recognition algorithm PGNet and a multi-language recognition model supporting more than 80 languages?", "options": [{"option_id": "A", "text": "v2.1.0"}, {"option_id": "B", "text": "v2.5.0"}, {"option_id": "C", "text": "v2.7.0"}, {"option_id": "D", "text": "v3.0.0"}], "correct_option_id": "A", "expected_answer": "v2.1.0", "source_chunk_ids": ["PaddlePaddle__PaddleOCR__release__v2_1_0"], "answer_support": [{"memory_node_id": "PaddlePaddle__PaddleOCR__release__v2_1_0", "answer_text": "introduces the end-to-end text recognition algorithm PGNet ... multi-language recognition model supporting more than 80 languages"}]}
{"prototype_id": "PaddlePaddle__PaddleOCR_release_window", "repo": "PaddlePaddle/PaddleOCR", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the PaddlePaddle/PaddleOCR releases, how does the document parsing capability introduced in v2.6.0 differ from the document parsing capability introduced in v3.0.0?", "options": [{"option_id": "A", "text": "v2.6.0 releases PP-Structurev2 with layout recovery and PDF-to-Word conversion, while v3.0.0 releases PP-StructureV3 for high-precision PDF parsing."}, {"option_id": "B", "text": "v2.6.0 introduces PP-OCRv3, while v3.0.0 introduces PP-OCRv5."}, {"option_id": "C", "text": "Both releases focus on multilingual model improvements without document parsing changes."}, {"option_id": "D", "text": "v2.6.0 adds PP-ChatOCR, while v3.0.0 adds PP-DocTranslation."}], "correct_option_id": "A", "expected_answer": "v2.6.0 releases PP-Structurev2 with layout recovery and PDF-to-Word conversion, while v3.0.0 releases PP-StructureV3 for high-precision PDF parsing.", "source_chunk_ids": ["PaddlePaddle__PaddleOCR__release__v2_6_0", "PaddlePaddle__PaddleOCR__release__v3_0_0"], "answer_support": [{"memory_node_id": "PaddlePaddle__PaddleOCR__release__v2_6_0", "answer_text": "Release PP-Structurev2 ... layout recovery and one-line command to convert PDF to Word"}, {"memory_node_id": "PaddlePaddle__PaddleOCR__release__v3_0_0", "answer_text": "release PP-StructureV3 ... high-precision PDF parsing"}]}
{"prototype_id": "PaddlePaddle__PaddleOCR_release_window", "repo": "PaddlePaddle/PaddleOCR", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the PaddlePaddle/PaddleOCR release window, order the following release-content states from earliest to latest: (1) a release that adds model pruning and quantization tools based on PaddleSlim, (2) a release that introduces PP-OCRv4 with mobile and server versions, (3) a release that releases PaddleOCR-VL, a compact vision-language model for document parsing.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["PaddlePaddle__PaddleOCR__release__v2_1_1", "PaddlePaddle__PaddleOCR__release__v2_7_0", "PaddlePaddle__PaddleOCR__release__v3_3_0"], "answer_support": [{"memory_node_id": "PaddlePaddle__PaddleOCR__release__v2_1_1", "answer_text": "Newly release model pruning and model quantization tools based on PaddleSlim"}, {"memory_node_id": "PaddlePaddle__PaddleOCR__release__v2_7_0", "answer_text": "Release PP-OCRv4, support mobile version and server version"}, {"memory_node_id": "PaddlePaddle__PaddleOCR__release__v3_3_0", "answer_text": "Released PaddleOCR-VL ... a compact yet powerful vision-language model (VLM)"}]}
{"prototype_id": "pallets__flask_release_window", "repo": "pallets/flask", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the pallets/flask releases, which release fixes an issue where using other JSON providers such as flask-orjson previously caused loaded session data to have an incorrect format in some cases?", "options": [{"option_id": "A", "text": "Flask 3.0.1"}, {"option_id": "B", "text": "Flask 3.0.2"}, {"option_id": "C", "text": "Flask 3.0.3"}, {"option_id": "D", "text": "Flask 3.1.0"}], "correct_option_id": "A", "expected_answer": "Flask 3.0.1", "source_chunk_ids": ["pallets__flask__release__3_0_1"], "answer_support": [{"memory_node_id": "pallets__flask__release__3_0_1", "answer_text": "fixing an issue where using other JSON providers such as flask-orjson previously caused loaded session data to have an incorrect format in some cases"}]}
{"prototype_id": "pallets__flask_release_window", "repo": "pallets/flask", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the pallets/flask releases, how does the security fix in Flask 2.3.2 differ from the security fix in Flask 3.1.3?", "options": [{"option_id": "A", "text": "2.3.2 addresses CVE-2023-30861, while 3.1.3 addresses GHSA-68rp-wp8r-4726 related to session key access."}, {"option_id": "B", "text": "2.3.2 fixes a JSON provider issue, while 3.1.3 fixes a type hint."}, {"option_id": "C", "text": "Both releases fix the same CVE-2023-30861."}, {"option_id": "D", "text": "2.3.2 adds key rotation support, while 3.1.3 drops Python 3.8 support."}], "correct_option_id": "A", "expected_answer": "2.3.2 addresses CVE-2023-30861, while 3.1.3 addresses GHSA-68rp-wp8r-4726 related to session key access.", "source_chunk_ids": ["pallets__flask__release__2_3_2", "pallets__flask__release__3_1_3"], "answer_support": [{"memory_node_id": "pallets__flask__release__2_3_2", "answer_text": "security fix release ... referencing security advisory GHSA-m2qf-hxjv-5gpq and CVE-2023-30861"}, {"memory_node_id": "pallets__flask__release__3_1_3", "answer_text": "security fix release ... marks the session as accessed for operations that only access the keys but not the values ... referencing GHSA-68rp-wp8r-4726"}]}
{"prototype_id": "pbatard__rufus_release_window", "repo": "pbatard/rufus", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the pbatard/rufus releases, which release adds a new selection dialog for Windows 11 setup customization that includes bypassing the mandatory Microsoft account requirement for Windows 11 22H2?", "options": [{"option_id": "A", "text": "v3.19"}, {"option_id": "B", "text": "v3.20"}, {"option_id": "C", "text": "v3.21"}, {"option_id": "D", "text": "v3.22"}], "correct_option_id": "A", "expected_answer": "v3.19", "source_chunk_ids": ["pbatard__rufus__release__v3_19"], "answer_support": [{"memory_node_id": "pbatard__rufus__release__v3_19", "answer_text": "adds a new selection dialog for Windows 11 setup customization ... also allows bypassing the mandatory requirement for a Microsoft account with Windows 11 22H2"}]}
{"prototype_id": "pbatard__rufus_release_window", "repo": "pbatard/rufus", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the pbatard/rufus releases, how does the Windows 11 in-place upgrade bypass in v4.6 differ from the Windows 11 setup customization dialog introduced in v3.19?", "options": [{"option_id": "A", "text": "v4.6 adds a setup.exe wrapper to bypass Windows 11 24H2 in-place upgrade restrictions, while v3.19 adds a dialog that includes bypassing the Microsoft account requirement for Windows 11 22H2."}, {"option_id": "B", "text": "v4.6 removes the customization dialog entirely, while v3.19 only adds TPM bypass."}, {"option_id": "C", "text": "Both releases add the same setup.exe wrapper for in-place upgrades."}, {"option_id": "D", "text": "v4.6 adds a dialog for Microsoft account bypass, while v3.19 adds a setup.exe wrapper."}], "correct_option_id": "A", "expected_answer": "v4.6 adds a setup.exe wrapper to bypass Windows 11 24H2 in-place upgrade restrictions, while v3.19 adds a dialog that includes bypassing the Microsoft account requirement for Windows 11 22H2.", "source_chunk_ids": ["pbatard__rufus__release__v4_6", "pbatard__rufus__release__v3_19"], "answer_support": [{"memory_node_id": "pbatard__rufus__release__v4_6", "answer_text": "Add a new setup.exe wrapper to bypass Windows 11 24H2 in-place upgrade restrictions"}, {"memory_node_id": "pbatard__rufus__release__v3_19", "answer_text": "adds a new selection dialog for Windows 11 setup customization ... also allows bypassing the mandatory requirement for a Microsoft account with Windows 11 22H2"}]}
{"prototype_id": "pbatard__rufus_release_window", "repo": "pbatard/rufus", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the pbatard/rufus release window, order the following release-content states from earliest to latest: (1) a release that adds a new selection dialog for Windows 11 setup customization including Microsoft account bypass, (2) a release that adds a setup.exe wrapper to bypass Windows 11 24H2 in-place upgrade restrictions, (3) a release that adds Dark Mode support and support for creating Windows CA 2023 compatible media.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["pbatard__rufus__release__v3_19", "pbatard__rufus__release__v4_6", "pbatard__rufus__release__v4_10"], "answer_support": [{"memory_node_id": "pbatard__rufus__release__v3_19", "answer_text": "adds a new selection dialog for Windows 11 setup customization ... also allows bypassing the mandatory requirement for a Microsoft account with Windows 11 22H2"}, {"memory_node_id": "pbatard__rufus__release__v4_6", "answer_text": "Add a new setup.exe wrapper to bypass Windows 11 24H2 in-place upgrade restrictions"}, {"memory_node_id": "pbatard__rufus__release__v4_10", "answer_text": "Add Dark Mode support ... Add support for creating Windows CA 2023 compatible media"}]}
{"prototype_id": "PhilJay__MPAndroidChart_release_window", "repo": "PhilJay/MPAndroidChart", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the PhilJay/MPAndroidChart releases, which release introduces a FillFormatter interface for custom line-filling in LineChart and fixes a crash in XLabels?", "options": [{"option_id": "A", "text": "v1.7.1"}, {"option_id": "B", "text": "v1.7.2"}, {"option_id": "C", "text": "v1.7.3"}, {"option_id": "D", "text": "v1.7.4"}], "correct_option_id": "C", "expected_answer": "v1.7.3", "source_chunk_ids": ["PhilJay__MPAndroidChart__release__v1_7_3"], "answer_support": [{"memory_node_id": "PhilJay__MPAndroidChart__release__v1_7_3", "answer_text": "provides a FillFormatter interface for custom line-filling in LineChart and fixes a crash in XLabels"}]}
{"prototype_id": "PhilJay__MPAndroidChart_release_window", "repo": "PhilJay/MPAndroidChart", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the PhilJay/MPAndroidChart release window, order the following release-content states from earliest to latest: (1) a release that adds a callback for fling gestures and new LegendPositions, (2) a release that introduces a BubbleChart chart type, (3) a release that adds support for stepped LineChart and simplifies setting axis min and max value, (4) a release that eliminates the x-index concept and changes the Entry constructor.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 2 -> 1 -> 3"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["PhilJay__MPAndroidChart__release__v1_7_2", "PhilJay__MPAndroidChart__release__v2_1_0", "PhilJay__MPAndroidChart__release__v2_2_4", "PhilJay__MPAndroidChart__release__v3_0_0_beta"], "answer_support": [{"memory_node_id": "PhilJay__MPAndroidChart__release__v1_7_2", "answer_text": "adds new LegendPositions NONE and RIGHT_OF_CHART_INSIDE, a callback for fling gestures"}, {"memory_node_id": "PhilJay__MPAndroidChart__release__v2_1_0", "answer_text": "introduces a new BubbleChart chart type"}, {"memory_node_id": "PhilJay__MPAndroidChart__release__v2_2_4", "answer_text": "simplifies setting axis min and max value ... adds support for stepped LineChart"}, {"memory_node_id": "PhilJay__MPAndroidChart__release__v3_0_0_beta", "answer_text": "eliminates the x-index concept ... changes the Entry constructor"}]}
{"prototype_id": "php__php_src_release_window", "repo": "php/php-src", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the php/php-src repository, which release introduces a new URI extension and a pipe operator (|>)?", "options": [{"option_id": "A", "text": "PHP 8.5.0"}, {"option_id": "B", "text": "PHP 8.4.11"}, {"option_id": "C", "text": "PHP 8.3.24"}, {"option_id": "D", "text": "PHP 8.5.1"}], "correct_option_id": "A", "expected_answer": "PHP 8.5.0", "source_chunk_ids": ["php__php_src__release__php_8_5_0"], "answer_support": [{"memory_node_id": "php__php_src__release__php_8_5_0", "answer_text": "introduces new features including a new URI extension, a pipe operator (|>)"}]}
{"prototype_id": "phpstan__phpstan_release_window", "repo": "phpstan/phpstan", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the phpstan/phpstan releases, which release introduces the bisect command for finding regression-introducing commits?", "options": [{"option_id": "A", "text": "2.1.47"}, {"option_id": "B", "text": "2.1.46"}, {"option_id": "C", "text": "2.1.48"}, {"option_id": "D", "text": "2.1.45"}], "correct_option_id": "A", "expected_answer": "2.1.47", "source_chunk_ids": ["phpstan__phpstan__release__2_1_47"], "answer_support": [{"memory_node_id": "phpstan__phpstan__release__2_1_47", "answer_text": "major new features add bisect command for finding regression-introducing commits"}]}
{"prototype_id": "phpstan__phpstan_release_window", "repo": "phpstan/phpstan", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the phpstan/phpstan releases, how does the performance improvement approach in release 2.1.34 differ from the approach in release 2.1.38?", "options": [{"option_id": "A", "text": "2.1.34 introduces Fibers for precise analysis and caching of reflection objects, while 2.1.38 reworks phpDoc inheritance and optimizes type operations for an additional 5-10% speedup."}, {"option_id": "B", "text": "2.1.34 focuses on Docker image builds, while 2.1.38 adds the bisect command."}, {"option_id": "C", "text": "Both releases only update function signatures without performance changes."}, {"option_id": "D", "text": "2.1.34 removes Fibers, while 2.1.38 introduces them."}], "correct_option_id": "A", "expected_answer": "2.1.34 introduces Fibers for precise analysis and caching of reflection objects, while 2.1.38 reworks phpDoc inheritance and optimizes type operations for an additional 5-10% speedup.", "source_chunk_ids": ["phpstan__phpstan__release__2_1_34", "phpstan__phpstan__release__2_1_38"], "answer_support": [{"memory_node_id": "phpstan__phpstan__release__2_1_34", "answer_text": "major new features include optimized performance with caching of reflection objects and resolved PHPDocs, yielding 25-40% faster analysis, and utilization of Fibers for more precise analysis"}, {"memory_node_id": "phpstan__phpstan__release__2_1_38", "answer_text": "bringing another 5-10% faster performance... Performance improvements rework phpDoc inheritance, prevent unnecessary work in TemplateTypeHelper, ConstantArrayType, ImpossibleCheckTypeHelper..."}]}
{"prototype_id": "pocketbase__pocketbase_release_window", "repo": "pocketbase/pocketbase", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the pocketbase/pocketbase releases, how does the rate limiter change in v0.36.7 differ from the rate limit feature added in v0.38.0?", "options": [{"option_id": "A", "text": "v0.36.7 updates the rate limiter reset rules to a fixed window strategy, while v0.38.0 adds an option to exclude IPs/CIDR subnets from rate limiting."}, {"option_id": "B", "text": "v0.36.7 removes rate limiting entirely, while v0.38.0 introduces a sliding window strategy."}, {"option_id": "C", "text": "Both releases only update the rate limiter to use a fixed window strategy."}, {"option_id": "D", "text": "v0.36.7 adds a rate limit exclusion option, while v0.38.0 updates the reset rules."}], "correct_option_id": "A", "expected_answer": "v0.36.7 updates the rate limiter reset rules to a fixed window strategy, while v0.38.0 adds an option to exclude IPs/CIDR subnets from rate limiting.", "source_chunk_ids": ["pocketbase__pocketbase__release__v0_36_7", "pocketbase__pocketbase__release__v0_38_0"], "answer_support": [{"memory_node_id": "pocketbase__pocketbase__release__v0_36_7", "answer_text": "Updated the rate limiter reset rules to follow a more traditional fixed window strategy"}, {"memory_node_id": "pocketbase__pocketbase__release__v0_38_0", "answer_text": "Added rate limit option to exclude IPs/CIDR subnets"}]}
{"prototype_id": "PostgREST__postgrest_release_window", "repo": "PostgREST/postgrest", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the PostgREST/postgrest releases, which release fixes a regression that makes ORDER BY with nulls-order not work alongside limits?", "options": [{"option_id": "A", "text": "v13.0.1"}, {"option_id": "B", "text": "v13.0.2"}, {"option_id": "C", "text": "v13.0.3"}, {"option_id": "D", "text": "v13.0.4"}], "correct_option_id": "B", "expected_answer": "v13.0.2", "source_chunk_ids": ["PostgREST__postgrest__release__v13_0_2"], "answer_support": [{"memory_node_id": "PostgREST__postgrest__release__v13_0_2", "answer_text": "fixes a regression that makes ORDER BY with nulls-order not work alongside limits"}]}
{"prototype_id": "PostgREST__postgrest_release_window", "repo": "PostgREST/postgrest", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the PostgREST/postgrest releases, how does the JWT cache change described in v12.2.10 differ from the JWT cache change described in v14.0?", "options": [{"option_id": "A", "text": "v12.2.10 fixes a performance issue where JWT cache purging on every request decreased performance, while v14.0 introduces a bounded JWT cache using the SIEVE algorithm that increases throughput and includes cache metrics."}, {"option_id": "B", "text": "v12.2.10 removes the JWT cache entirely, while v14.0 adds a new JWT cache with no performance impact."}, {"option_id": "C", "text": "Both releases only fix JWT cache expiration handling without any performance improvements."}, {"option_id": "D", "text": "v12.2.10 introduces the SIEVE algorithm, while v14.0 fixes a purging performance issue."}], "correct_option_id": "A", "expected_answer": "v12.2.10 fixes a performance issue where JWT cache purging on every request decreased performance, while v14.0 introduces a bounded JWT cache using the SIEVE algorithm that increases throughput and includes cache metrics.", "source_chunk_ids": ["PostgREST__postgrest__release__v12_2_10", "PostgREST__postgrest__release__v14_0"], "answer_support": [{"memory_node_id": "PostgREST__postgrest__release__v12_2_10", "answer_text": "fixes a performance issue where JWT cache purging on every request decreased performance"}, {"memory_node_id": "PostgREST__postgrest__release__v14_0", "answer_text": "introduces a bounded JWT cache using the SIEVE algorithm, increasing throughput for GET requests by 20% and including JWT cache metrics"}]}
{"prototype_id": "PostgREST__postgrest_release_window", "repo": "PostgREST/postgrest", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the PostgREST/postgrest release window, order the following release-content states from earliest to latest: (1) a release that fixes startup for the arm64 Docker image, (2) a release that introduces spread to-many relationships and automatic tsvector conversion, (3) a release that introduces a bounded JWT cache using the SIEVE algorithm and a ready flag for healthcheck, (4) a release that fixes a race condition in the pool_available metric causing negative values during network instability.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["PostgREST__postgrest__release__v12_2_5", "PostgREST__postgrest__release__v13_0_0", "PostgREST__postgrest__release__v14_0", "PostgREST__postgrest__release__v14_12"], "answer_support": [{"memory_node_id": "PostgREST__postgrest__release__v12_2_5", "answer_text": "fixes startup for the arm64 Docker image"}, {"memory_node_id": "PostgREST__postgrest__release__v13_0_0", "answer_text": "introduces spread to-many relationships and automatic tsvector conversion"}, {"memory_node_id": "PostgREST__postgrest__release__v14_0", "answer_text": "introduces a bounded JWT cache using the SIEVE algorithm and a ready flag for healthcheck"}, {"memory_node_id": "PostgREST__postgrest__release__v14_12", "answer_text": "fixes a race condition in the pool_available metric causing negative values during network instability"}]}
{"prototype_id": "pppscn__SmsForwarder_release_window", "repo": "pppscn/SmsForwarder", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the pppscn/SmsForwarder releases, which release adds a Gotify sending channel and disables code minification to avoid mysterious issues?", "options": [{"option_id": "A", "text": "v2.3.0"}, {"option_id": "B", "text": "v2.4.0"}, {"option_id": "C", "text": "v2.4.1"}, {"option_id": "D", "text": "v2.4.2"}], "correct_option_id": "B", "expected_answer": "v2.4.0", "source_chunk_ids": ["pppscn__SmsForwarder__release__v2_4_0"], "answer_support": [{"memory_node_id": "pppscn__SmsForwarder__release__v2_4_0", "answer_text": "adds a Gotify sending channel ... disables code minification to avoid mysterious issues"}]}
{"prototype_id": "pppscn__SmsForwarder_release_window", "repo": "pppscn/SmsForwarder", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the pppscn/SmsForwarder releases, how does the keep-alive approach in v2.4.3 differ from the keep-alive approach in v3.0.0?", "options": [{"option_id": "A", "text": "v2.4.3 uses silent music and a 1-pixel transparent Activity, while v3.0.0 introduces a comprehensive Cactus system with dual-process foreground service, JobScheduler, onePix, WorkManager, and silent music."}, {"option_id": "B", "text": "v2.4.3 introduces Cactus, while v3.0.0 removes all keep-alive measures."}, {"option_id": "C", "text": "Both releases rely solely on JobScheduler for keep-alive."}, {"option_id": "D", "text": "v2.4.3 uses WorkManager, while v3.0.0 uses only a foreground service."}], "correct_option_id": "A", "expected_answer": "v2.4.3 uses silent music and a 1-pixel transparent Activity, while v3.0.0 introduces a comprehensive Cactus system with dual-process foreground service, JobScheduler, onePix, WorkManager, and silent music.", "source_chunk_ids": ["pppscn__SmsForwarder__release__v2_4_3", "pppscn__SmsForwarder__release__v3_0_0"], "answer_support": [{"memory_node_id": "pppscn__SmsForwarder__release__v2_4_3", "answer_text": "experimentally optimizes keep-alive by playing silent music ... and using a 1-pixel transparent Activity"}, {"memory_node_id": "pppscn__SmsForwarder__release__v3_0_0", "answer_text": "adds Cactus keep-alive measures (dual-process foreground service, JobScheduler, onePix, WorkManager, silent music)"}]}
{"prototype_id": "pppscn__SmsForwarder_release_window", "repo": "pppscn/SmsForwarder", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the pppscn/SmsForwarder release window, order the following release-content states from earliest to latest: (1) a release that adds a Gotify sending channel and disables code minification, (2) a release that adds a Socket sending channel supporting MQTT/TCP/UDP and remote phone location query, (3) a release that adds automatic tasks with trigger conditions including scheduled tasks and location, (4) a release that adds a {{CONTACT_NAME}} tag and persistent reminder for Bark.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["pppscn__SmsForwarder__release__v2_4_0", "pppscn__SmsForwarder__release__v3_2_0", "pppscn__SmsForwarder__release__v3_3_0", "pppscn__SmsForwarder__release__v3_3_3"], "answer_support": [{"memory_node_id": "pppscn__SmsForwarder__release__v2_4_0", "answer_text": "adds a Gotify sending channel ... disables code minification"}, {"memory_node_id": "pppscn__SmsForwarder__release__v3_2_0", "answer_text": "adds a Socket sending channel (supporting MQTT/TCP/UDP protocols) ... adds remote phone location query"}, {"memory_node_id": "pppscn__SmsForwarder__release__v3_3_0", "answer_text": "adds automatic tasks/shortcut commands with trigger conditions: scheduled tasks, arriving/leaving a location"}, {"memory_node_id": "pppscn__SmsForwarder__release__v3_3_3", "answer_text": "adds a {{CONTACT_NAME}} tag ... adds persistent reminder functionality for Bark channel"}]}
{"prototype_id": "prisma__prisma_release_window", "repo": "prisma/prisma", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the prisma/prisma releases, which release introduces a caching layer in Prisma Client to reuse compiled query plans?", "options": [{"option_id": "A", "text": "7.3.0"}, {"option_id": "B", "text": "7.4.0"}, {"option_id": "C", "text": "7.5.0"}, {"option_id": "D", "text": "7.6.0"}], "correct_option_id": "B", "expected_answer": "7.4.0", "source_chunk_ids": ["prisma__prisma__release__7_4_0"], "answer_support": [{"memory_node_id": "prisma__prisma__release__7_4_0", "answer_text": "introduces a caching layer in Prisma Client to reuse compiled query plans"}]}
{"prototype_id": "prisma__prisma_release_window", "repo": "prisma/prisma", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the prisma/prisma releases, how does the approach to Prisma Client generation differ between release 6.16.0 and release 7.0.0?", "options": [{"option_id": "A", "text": "6.16.0 makes the Rust-free ORM and ESM-first prisma-client generator Generally Available, while 7.0.0 makes ESM Prisma Client the default and requires an adapter or accelerateUrl when creating PrismaClient."}, {"option_id": "B", "text": "6.16.0 removes the prisma-client generator, while 7.0.0 reintroduces it as the only option."}, {"option_id": "C", "text": "Both releases only update driver adapters without changing client generation."}, {"option_id": "D", "text": "6.16.0 deprecates all generators, while 7.0.0 adds a new Rust-based engine."}], "correct_option_id": "A", "expected_answer": "6.16.0 makes the Rust-free ORM and ESM-first prisma-client generator Generally Available, while 7.0.0 makes ESM Prisma Client the default and requires an adapter or accelerateUrl when creating PrismaClient.", "source_chunk_ids": ["prisma__prisma__release__6_16_0", "prisma__prisma__release__7_0_0"], "answer_support": [{"memory_node_id": "prisma__prisma__release__6_16_0", "answer_text": "makes the Rust-free ORM and driver adapters Generally Available, and the new ESM-first prisma-client generator Generally Available"}, {"memory_node_id": "prisma__prisma__release__7_0_0", "answer_text": "makes ESM Prisma Client the default, requires an adapter or accelerateUrl when creating PrismaClient"}]}
{"prototype_id": "prisma__prisma_release_window", "repo": "prisma/prisma", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the prisma/prisma release window, order the following release-content states from earliest to latest: (1) a release that adds AI safety guardrails for destructive commands, (2) a release that introduces a caching layer in Prisma Client, (3) a release that adds a prisma bootstrap command, (4) a release that makes the Rust-free ORM Generally Available.", "options": [{"option_id": "A", "text": "1 -> 4 -> 2 -> 3"}, {"option_id": "B", "text": "4 -> 1 -> 2 -> 3"}, {"option_id": "C", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "D", "text": "4 -> 2 -> 1 -> 3"}], "correct_option_id": "A", "expected_answer": "1 -> 4 -> 2 -> 3", "source_chunk_ids": ["prisma__prisma__release__6_15_0", "prisma__prisma__release__6_16_0", "prisma__prisma__release__7_4_0", "prisma__prisma__release__7_7_0"], "answer_support": [{"memory_node_id": "prisma__prisma__release__6_15_0", "answer_text": "adds AI safety guardrails for destructive commands"}, {"memory_node_id": "prisma__prisma__release__6_16_0", "answer_text": "makes the Rust-free ORM and driver adapters Generally Available"}, {"memory_node_id": "prisma__prisma__release__7_4_0", "answer_text": "introduces a caching layer in Prisma Client"}, {"memory_node_id": "prisma__prisma__release__7_7_0", "answer_text": "introduces a prisma bootstrap command"}]}
{"prototype_id": "probelabs__goreplay_release_window", "repo": "probelabs/goreplay", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the probelabs/goreplay releases, which release introduces middleware support and changes the file format to human readable?", "options": [{"option_id": "A", "text": "v0.9.8"}, {"option_id": "B", "text": "v0.10.0"}, {"option_id": "C", "text": "v0.10.1"}, {"option_id": "D", "text": "v0.11.0"}], "correct_option_id": "B", "expected_answer": "v0.10.0", "source_chunk_ids": ["probelabs__goreplay__release__0_10_0"], "answer_support": [{"memory_node_id": "probelabs__goreplay__release__0_10_0", "answer_text": "Middleware support! ... Changed file format, now it human readable"}]}
{"prototype_id": "probelabs__goreplay_release_window", "repo": "probelabs/goreplay", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the probelabs/goreplay releases, how does the traffic capture engine change described in v0.11.0 differ from the engine change described in v1.3.0?", "options": [{"option_id": "A", "text": "v0.11.0 switches the default engine to libpcap, while v1.3.0 fully re-constructs the capture engine for scalability and efficiency."}, {"option_id": "B", "text": "v0.11.0 removes libpcap, while v1.3.0 adds libpcap support."}, {"option_id": "C", "text": "Both releases only update Go version without engine changes."}, {"option_id": "D", "text": "v0.11.0 adds Windows support, while v1.3.0 removes Windows support."}], "correct_option_id": "A", "expected_answer": "v0.11.0 switches the default engine to libpcap, while v1.3.0 fully re-constructs the capture engine for scalability and efficiency.", "source_chunk_ids": ["probelabs__goreplay__release__v0_11_0", "probelabs__goreplay__release__v1_3_0"], "answer_support": [{"memory_node_id": "probelabs__goreplay__release__v0_11_0", "answer_text": "Default traffic interception engine now libpcap"}, {"memory_node_id": "probelabs__goreplay__release__v1_3_0", "answer_text": "Traffic capture engine fully re-constructed to be more scalable, efficient and bulletproof"}]}
{"prototype_id": "probelabs__goreplay_release_window", "repo": "probelabs/goreplay", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the probelabs/goreplay release window, order the following release-content states from earliest to latest: (1) a release that adds support for IPv6 and fixes memory leaks, (2) a release that adds official Windows support and deprecates its own HTTP client, (3) a release that adds middleware support and changes file format to human readable.", "options": [{"option_id": "A", "text": "3 -> 1 -> 2"}, {"option_id": "B", "text": "1 -> 2 -> 3"}, {"option_id": "C", "text": "2 -> 1 -> 3"}, {"option_id": "D", "text": "1 -> 3 -> 2"}], "correct_option_id": "A", "expected_answer": "3 -> 1 -> 2", "source_chunk_ids": ["probelabs__goreplay__release__0_10_0", "probelabs__goreplay__release__v0_12_0", "probelabs__goreplay__release__v1_3_0"], "answer_support": [{"memory_node_id": "probelabs__goreplay__release__0_10_0", "answer_text": "Middleware support! ... Changed file format, now it human readable"}, {"memory_node_id": "probelabs__goreplay__release__v0_12_0", "answer_text": "Support for IPv6 ... Fixed memory leaks"}, {"memory_node_id": "probelabs__goreplay__release__v1_3_0", "answer_text": "Added official Windows support ... Deprecated own HTTP client in favour of native Go HTTP library"}]}
{"prototype_id": "protocolbuffers__protobuf_release_window", "repo": "protocolbuffers/protobuf", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the protocolbuffers/protobuf releases, which release adds support for an import option for protoc and patches `rules_ruby` to apply `neverlink = True` to the `jars` rule?", "options": [{"option_id": "A", "text": "v31.0-rc1"}, {"option_id": "B", "text": "v31.0-rc2"}, {"option_id": "C", "text": "v31.0"}, {"option_id": "D", "text": "v31.1"}], "correct_option_id": "B", "expected_answer": "v31.0-rc2", "source_chunk_ids": ["protocolbuffers__protobuf__release__v31_0_rc2"], "answer_support": [{"memory_node_id": "protocolbuffers__protobuf__release__v31_0_rc2", "answer_text": "adds support for an import option for protoc, and patches `rules_ruby` to apply `neverlink = True` to the `jars` rule"}]}
{"prototype_id": "protocolbuffers__protobuf_release_window", "repo": "protocolbuffers/protobuf", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the protocolbuffers/protobuf releases, how does the handling of the pre-22 poison pill differ between v25.8 and v25.9?", "options": [{"option_id": "A", "text": "v25.8 changes the pre-22 poison pill to only log once per affected message type, while v25.9 switches the pre22 warning to use CopyOnWriteArraySet."}, {"option_id": "B", "text": "v25.8 removes the pre-22 poison pill entirely, while v25.9 reintroduces it with a stronger enforcement."}, {"option_id": "C", "text": "v25.8 weakens the poison pill to a warning by default, while v25.9 changes it to only log once per affected message type."}, {"option_id": "D", "text": "v25.8 switches the pre22 warning to use CopyOnWriteArraySet, while v25.9 changes it to only log once per affected message type."}], "correct_option_id": "A", "expected_answer": "v25.8 changes the pre-22 poison pill to only log once per affected message type, while v25.9 switches the pre22 warning to use CopyOnWriteArraySet.", "source_chunk_ids": ["protocolbuffers__protobuf__release__v25_8", "protocolbuffers__protobuf__release__v25_9"], "answer_support": [{"memory_node_id": "protocolbuffers__protobuf__release__v25_8", "answer_text": "changes the pre-22 poison pill to only log once per affected message type"}, {"memory_node_id": "protocolbuffers__protobuf__release__v25_9", "answer_text": "switches the pre22 warning to use CopyOnWriteArraySet"}]}
{"prototype_id": "protocolbuffers__protobuf_release_window", "repo": "protocolbuffers/protobuf", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the protocolbuffers/protobuf release window, order the following release-content states from earliest to latest: (1) a release that adds EDITION_UNSTABLE for new edition development and fixes a bug with custom features outside of the `pb` package, (2) a release that adds edition unstable for development work and adds conformance test for edition unstable, (3) a release that implements the Edition 2026 naming style enforcement feature and drops support for Bazel 7.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["protocolbuffers__protobuf__release__v33_2", "protocolbuffers__protobuf__release__v33_3", "protocolbuffers__protobuf__release__v35_0_rc1"], "answer_support": [{"memory_node_id": "protocolbuffers__protobuf__release__v33_2", "answer_text": "adds EDITION_UNSTABLE for new edition development and fixes a bug with custom features outside of the `pb` package"}, {"memory_node_id": "protocolbuffers__protobuf__release__v33_3", "answer_text": "adds edition unstable for development work and adds conformance test for edition unstable"}, {"memory_node_id": "protocolbuffers__protobuf__release__v35_0_rc1", "answer_text": "implements the Edition 2026 naming style enforcement feature and drops support for Bazel 7"}]}
{"prototype_id": "puppeteer__puppeteer_release_window", "repo": "puppeteer/puppeteer", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the puppeteer/puppeteer releases, which release introduces support for the PUPPETEER_DANGEROUS_NO_SANDBOX environment variable?", "options": [{"option_id": "A", "text": "puppeteer-core v24.40.0"}, {"option_id": "B", "text": "puppeteer v24.40.0"}, {"option_id": "C", "text": "puppeteer-core v24.41.0"}, {"option_id": "D", "text": "puppeteer v24.41.0"}], "correct_option_id": "A", "expected_answer": "puppeteer-core v24.40.0", "source_chunk_ids": ["puppeteer__puppeteer__release__puppeteer_core_v24_40_0"], "answer_support": [{"memory_node_id": "puppeteer__puppeteer__release__puppeteer_core_v24_40_0", "answer_text": "adds support for the PUPPETEER_DANGEROUS_NO_SANDBOX environment variable"}]}
{"prototype_id": "puppeteer__puppeteer_release_window", "repo": "puppeteer/puppeteer", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the puppeteer/puppeteer releases, how does the URL restriction feature differ between puppeteer-core v24.42.0 and puppeteer-core v24.43.0?", "options": [{"option_id": "A", "text": "v24.42.0 implements a URL blocklist, while v24.43.0 implements an allowlist."}, {"option_id": "B", "text": "v24.42.0 implements an allowlist, while v24.43.0 implements a URL blocklist."}, {"option_id": "C", "text": "Both releases implement the same URL blocklist feature."}, {"option_id": "D", "text": "Neither release includes any URL restriction feature."}], "correct_option_id": "A", "expected_answer": "v24.42.0 implements a URL blocklist, while v24.43.0 implements an allowlist.", "source_chunk_ids": ["puppeteer__puppeteer__release__puppeteer_core_v24_42_0", "puppeteer__puppeteer__release__puppeteer_core_v24_43_0"], "answer_support": [{"memory_node_id": "puppeteer__puppeteer__release__puppeteer_core_v24_42_0", "answer_text": "implements URL blocklist to restrict access to unauthorized sites"}, {"memory_node_id": "puppeteer__puppeteer__release__puppeteer_core_v24_43_0", "answer_text": "Implements allowlist"}]}
{"prototype_id": "puppeteer__puppeteer_release_window", "repo": "puppeteer/puppeteer", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the puppeteer/puppeteer release window, order the following release-content states from earliest to latest: (1) a release that adds support for Issues and extension realms API, (2) a release that introduces breaking changes including moving packages to ESM only and bumping minimum Node.js to 22, (3) a release that rolls to Chrome 149.0.7827.2 and replaces cosmiconfig with lilconfig.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["puppeteer__puppeteer__release__puppeteer_core_v24_41_0", "puppeteer__puppeteer__release__puppeteer_v25_0_0", "puppeteer__puppeteer__release__puppeteer_v25_1_0"], "answer_support": [{"memory_node_id": "puppeteer__puppeteer__release__puppeteer_core_v24_41_0", "answer_text": "adds support for Issues, extension realms API"}, {"memory_node_id": "puppeteer__puppeteer__release__puppeteer_v25_0_0", "answer_text": "introduces breaking changes: bumps minimum Node.js to 22, moves packages to ESM only"}, {"memory_node_id": "puppeteer__puppeteer__release__puppeteer_v25_1_0", "answer_text": "rolls to Chrome 149.0.7827.2, replaces cosmiconfig with lilconfig"}]}
{"prototype_id": "pytorch__pytorch_release_window", "repo": "pytorch/pytorch", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the pytorch/pytorch releases, how does the backwards incompatible change in v2.7.0 regarding torch.Tensor.new_tensor() differ from the backwards incompatible change in v2.8.0 regarding custom autograd.Function?", "options": [{"option_id": "A", "text": "v2.7.0 changes new_tensor() to use the given Tensor's device by default, while v2.8.0 adds a missing in-place on view check to custom autograd.Function."}, {"option_id": "B", "text": "v2.7.0 removes support for Triton < 2.2.0, while v2.8.0 removes support for Maxwell and Pascal architectures."}, {"option_id": "C", "text": "v2.7.0 changes the default value for weights_only parameter of torch.load, while v2.8.0 changes the default ThreadPool size."}, {"option_id": "D", "text": "v2.7.0 drops support for CUDA 12.4, while v2.8.0 drops support for Volta GPUs."}], "correct_option_id": "A", "expected_answer": "v2.7.0 changes new_tensor() to use the given Tensor's device by default, while v2.8.0 adds a missing in-place on view check to custom autograd.Function.", "source_chunk_ids": ["pytorch__pytorch__release__v2_7_0", "pytorch__pytorch__release__v2_8_0"], "answer_support": [{"memory_node_id": "pytorch__pytorch__release__v2_7_0", "answer_text": "change torch.Tensor.new_tensor() to be on the given Tensor's device by default"}, {"memory_node_id": "pytorch__pytorch__release__v2_8_0", "answer_text": "added missing in-place on view check to custom autograd.Function"}]}
{"prototype_id": "pytorch__pytorch_release_window", "repo": "pytorch/pytorch", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the pytorch/pytorch release window, order the following release-content states from earliest to latest: (1) a release that introduces torch.compile as the main API and Accelerated Transformers, (2) a release that introduces automatic dynamic shape support in torch.compile and torch.distributed.checkpoint, (3) a release that introduces FlashAttention-v2 integration and AOTInductor, (4) a release that introduces user-defined Triton kernels in torch.compile and Tensor Parallelism in Distributed.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["pytorch__pytorch__release__v2_0_0", "pytorch__pytorch__release__v2_1_0", "pytorch__pytorch__release__v2_2_0", "pytorch__pytorch__release__v2_3_0"], "answer_support": [{"memory_node_id": "pytorch__pytorch__release__v2_0_0", "answer_text": "torch.compile as the main API ... Accelerated Transformers"}, {"memory_node_id": "pytorch__pytorch__release__v2_1_0", "answer_text": "automatic dynamic shape support in torch.compile ... torch.distributed.checkpoint"}, {"memory_node_id": "pytorch__pytorch__release__v2_2_0", "answer_text": "FlashAttention-v2 integration ... AOTInductor"}, {"memory_node_id": "pytorch__pytorch__release__v2_3_0", "answer_text": "user-defined Triton kernels in torch.compile ... Tensor Parallelism in Distributed"}]}
{"prototype_id": "QuivrHQ__quivr_release_window", "repo": "QuivrHQ/quivr", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the QuivrHQ/quivr releases, which release introduces configurable retrieval workflows?", "options": [{"option_id": "A", "text": "v0.0.312"}, {"option_id": "B", "text": "v0.0.316"}, {"option_id": "C", "text": "core-0.0.15"}, {"option_id": "D", "text": "core-0.0.17"}], "correct_option_id": "B", "expected_answer": "v0.0.316", "source_chunk_ids": ["QuivrHQ__quivr__release__v0_0_316"], "answer_support": [{"memory_node_id": "QuivrHQ__quivr__release__v0_0_316", "answer_text": "introducing configurable retrieval workflows"}]}
{"prototype_id": "QuivrHQ__quivr_release_window", "repo": "QuivrHQ/quivr", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the QuivrHQ/quivr releases, how does the Notion integration handling differ between v0.0.317 and v0.0.318?", "options": [{"option_id": "A", "text": "v0.0.317 removes syncNotion from ConnectionCards, while v0.0.318 adds syncNotion back to ConnectionCards."}, {"option_id": "B", "text": "v0.0.317 adds syncNotion to ConnectionCards, while v0.0.318 removes it."}, {"option_id": "C", "text": "Both releases add error handling for Notion rate-limited search."}, {"option_id": "D", "text": "v0.0.317 introduces Notion integration, while v0.0.318 fixes a Notion parsing bug."}], "correct_option_id": "A", "expected_answer": "v0.0.317 removes syncNotion from ConnectionCards, while v0.0.318 adds syncNotion back to ConnectionCards.", "source_chunk_ids": ["QuivrHQ__quivr__release__v0_0_317", "QuivrHQ__quivr__release__v0_0_318"], "answer_support": [{"memory_node_id": "QuivrHQ__quivr__release__v0_0_317", "answer_text": "removes syncNotion from ConnectionCards"}, {"memory_node_id": "QuivrHQ__quivr__release__v0_0_318", "answer_text": "adds syncNotion back to ConnectionCards"}]}
{"prototype_id": "QuivrHQ__quivr_release_window", "repo": "QuivrHQ/quivr", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the QuivrHQ/quivr release window, order the following release-content states from earliest to latest: (1) a release that introduces the first version of the Workflow Management System, (2) a release that adds caching to LLMEndpoint, (3) a release that enables workflows without rewriting step, (4) a release that adds support for o3-mini.", "options": [{"option_id": "A", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "B", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "C", "text": "3 -> 1 -> 2 -> 4"}, {"option_id": "D", "text": "2 -> 1 -> 3 -> 4"}], "correct_option_id": "A", "expected_answer": "1 -> 3 -> 2 -> 4", "source_chunk_ids": ["QuivrHQ__quivr__release__core_0_0_26", "QuivrHQ__quivr__release__core_0_0_29", "QuivrHQ__quivr__release__core_0_0_30", "QuivrHQ__quivr__release__core_0_0_32"], "answer_support": [{"memory_node_id": "QuivrHQ__quivr__release__core_0_0_26", "answer_text": "first version (V0) of the Workflow Management System"}, {"memory_node_id": "QuivrHQ__quivr__release__core_0_0_29", "answer_text": "enabling workflows without rewriting step"}, {"memory_node_id": "QuivrHQ__quivr__release__core_0_0_30", "answer_text": "adding cache to LLMEndpoint"}, {"memory_node_id": "QuivrHQ__quivr__release__core_0_0_32", "answer_text": "o3-mini"}]}
{"prototype_id": "radareorg__radare2_release_window", "repo": "radareorg/radare2", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the radareorg/radare2 releases, which release introduces the native C reimplementation of r2pm and initial thread support with one RCore per thread?", "options": [{"option_id": "A", "text": "5.5.4"}, {"option_id": "B", "text": "5.6.0"}, {"option_id": "C", "text": "5.6.2"}, {"option_id": "D", "text": "5.7.0"}], "correct_option_id": "B", "expected_answer": "5.6.0", "source_chunk_ids": ["radareorg__radare2__release__5_6_0"], "answer_support": [{"memory_node_id": "radareorg__radare2__release__5_6_0", "answer_text": "introduces a native C reimplementation of r2pm, initial thread support with one RCore per thread"}]}
{"prototype_id": "radareorg__radare2_release_window", "repo": "radareorg/radare2", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the radareorg/radare2 releases, how does the analysis speed improvement described in 5.8.4 differ from the analysis speed improvement described in 5.6.0?", "options": [{"option_id": "A", "text": "5.8.4 optimizes RCore.analOp() lowering aa from 1m23 to 1m19 and makes aab faster from 39s to 32s, while 5.6.0 introduces orders of magnitude faster analysis with aafs and sixref."}, {"option_id": "B", "text": "5.8.4 introduces aafs and sixref, while 5.6.0 optimizes RCore.analOp()."}, {"option_id": "C", "text": "Both releases only improve disassembly rendering speed without analysis changes."}, {"option_id": "D", "text": "5.8.4 removes the hexagon from anal, while 5.6.0 adds mermaid graph output."}], "correct_option_id": "A", "expected_answer": "5.8.4 optimizes RCore.analOp() lowering aa from 1m23 to 1m19 and makes aab faster from 39s to 32s, while 5.6.0 introduces orders of magnitude faster analysis with aafs and sixref.", "source_chunk_ids": ["radareorg__radare2__release__5_8_4", "radareorg__radare2__release__5_6_0"], "answer_support": [{"memory_node_id": "radareorg__radare2__release__5_8_4", "answer_text": "optimizes RCore.analOp() lowering aa from 1m23 to 1m19, makes aab faster from 39s to 32s"}, {"memory_node_id": "radareorg__radare2__release__5_6_0", "answer_text": "orders of magnitude faster analysis with aafs and sixref"}]}
{"prototype_id": "Raphire__Win11Debloat_release_window", "repo": "Raphire/Win11Debloat", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the Raphire/Win11Debloat releases, which release adds an option to disable AI features in Paint & Notepad?", "options": [{"option_id": "A", "text": "Release 2025.06.12"}, {"option_id": "B", "text": "Release 2025.08.01"}, {"option_id": "C", "text": "Release 2025.08.16"}, {"option_id": "D", "text": "Release 2025.09.07"}], "correct_option_id": "B", "expected_answer": "Release 2025.08.01", "source_chunk_ids": ["Raphire__Win11Debloat__release__2025_08_01"], "answer_support": [{"memory_node_id": "Raphire__Win11Debloat__release__2025_08_01", "answer_text": "an option to disable AI features in Paint & Notepad is introduced"}]}
{"prototype_id": "Raphire__Win11Debloat_release_window", "repo": "Raphire/Win11Debloat", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the Raphire/Win11Debloat releases, how does the change related to Microsoft Edge in release 2025.08.16 differ from the change in release 2026.02.12?", "options": [{"option_id": "A", "text": "2025.08.16 adds an option to disable telemetry, ads, MSN news feed, and AI in Edge, while 2026.02.12 improves DisableEdgeAds to disable additional clutter like first run experience and Adobe Acrobat ads."}, {"option_id": "B", "text": "2025.08.16 removes Edge entirely, while 2026.02.12 adds an option to disable Edge telemetry."}, {"option_id": "C", "text": "Both releases only update Edge removal logic without adding new options."}, {"option_id": "D", "text": "2025.08.16 disables Edge AI features, while 2026.02.12 disables Edge shopping assistant."}], "correct_option_id": "A", "expected_answer": "2025.08.16 adds an option to disable telemetry, ads, MSN news feed, and AI in Edge, while 2026.02.12 improves DisableEdgeAds to disable additional clutter like first run experience and Adobe Acrobat ads.", "source_chunk_ids": ["Raphire__Win11Debloat__release__2025_08_16", "Raphire__Win11Debloat__release__2026_02_12"], "answer_support": [{"memory_node_id": "Raphire__Win11Debloat__release__2025_08_16", "answer_text": "an option to disable telemetry, ads, MSN news feed, and AI in Microsoft Edge is added"}, {"memory_node_id": "Raphire__Win11Debloat__release__2026_02_12", "answer_text": "The DisableEdgeAds feature is improved to disable additional clutter/ads in Microsoft Edge, including first run experience, default browser prompts, Adobe Acrobat buttons/ads, and spotlight experiences"}]}
{"prototype_id": "react__create_react_app_release_window", "repo": "react/create-react-app", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the react/create-react-app releases, which release introduces support for TypeScript app creation using the --typescript flag?", "options": [{"option_id": "A", "text": "v2.0.4"}, {"option_id": "B", "text": "v2.1.0"}, {"option_id": "C", "text": "v3.0.0"}, {"option_id": "D", "text": "v4.0.0"}], "correct_option_id": "B", "expected_answer": "v2.1.0", "source_chunk_ids": ["react__create_react_app__release__v2_1_0"], "answer_support": [{"memory_node_id": "react__create_react_app__release__v2_1_0", "answer_text": "adds support for TypeScript, including TypeScript app creation via --typescript flag"}]}
{"prototype_id": "react__create_react_app_release_window", "repo": "react/create-react-app", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the react/create-react-app releases, how does the TypeScript speed improvement handling differ between v2.1.5 and v2.1.8?", "options": [{"option_id": "A", "text": "v2.1.5 reverts the TypeScript speed improvements to fix a dependency issue, while v2.1.8 reapplies them in a new major version of react-dev-utils."}, {"option_id": "B", "text": "v2.1.5 introduces TypeScript speed improvements, while v2.1.8 removes them permanently."}, {"option_id": "C", "text": "Both releases only update documentation without changing TypeScript behavior."}, {"option_id": "D", "text": "v2.1.5 adds TypeScript support, while v2.1.8 adds decorator support."}], "correct_option_id": "A", "expected_answer": "v2.1.5 reverts the TypeScript speed improvements to fix a dependency issue, while v2.1.8 reapplies them in a new major version of react-dev-utils.", "source_chunk_ids": ["react__create_react_app__release__v2_1_5", "react__create_react_app__release__v2_1_8"], "answer_support": [{"memory_node_id": "react__create_react_app__release__v2_1_5", "answer_text": "reverts the TypeScript speed improvements to fix a dependency issue in react-dev-utils"}, {"memory_node_id": "react__create_react_app__release__v2_1_8", "answer_text": "reapplies the TypeScript speed improvements in a new major version of react-dev-utils"}]}
{"prototype_id": "react__create_react_app_release_window", "repo": "react/create-react-app", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the react/create-react-app release window, order the following release-content states from earliest to latest: (1) a release that adds support for Tailwind, (2) a release that introduces Fast Refresh, (3) a release that adds support for TypeScript app creation, (4) a release that introduces support for Hooks.", "options": [{"option_id": "A", "text": "3 -> 4 -> 2 -> 1"}, {"option_id": "B", "text": "4 -> 3 -> 2 -> 1"}, {"option_id": "C", "text": "3 -> 2 -> 4 -> 1"}, {"option_id": "D", "text": "2 -> 3 -> 4 -> 1"}], "correct_option_id": "A", "expected_answer": "3 -> 4 -> 2 -> 1", "source_chunk_ids": ["react__create_react_app__release__v2_1_0", "react__create_react_app__release__v3_0_0", "react__create_react_app__release__v4_0_0", "react__create_react_app__release__v5_0_0"], "answer_support": [{"memory_node_id": "react__create_react_app__release__v2_1_0", "answer_text": "adds support for TypeScript, including TypeScript app creation via --typescript flag"}, {"memory_node_id": "react__create_react_app__release__v3_0_0", "answer_text": "introduces support for Hooks"}, {"memory_node_id": "react__create_react_app__release__v4_0_0", "answer_text": "introduces Fast Refresh"}, {"memory_node_id": "react__create_react_app__release__v5_0_0", "answer_text": "adds support for Tailwind"}]}
{"prototype_id": "ReactiveX__RxJava_release_window", "repo": "ReactiveX/RxJava", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the ReactiveX/RxJava releases, which release adds overloads to throttleLatest, throttleFirst, throttleLast, and throttleWithTimeout operators with an onDropped callback?", "options": [{"option_id": "A", "text": "v3.1.6"}, {"option_id": "B", "text": "v3.1.7"}, {"option_id": "C", "text": "v3.1.8"}, {"option_id": "D", "text": "v3.1.9"}], "correct_option_id": "A", "expected_answer": "v3.1.6", "source_chunk_ids": ["ReactiveX__RxJava__release__v3_1_6"], "answer_support": [{"memory_node_id": "ReactiveX__RxJava__release__v3_1_6", "answer_text": "API changes adding overloads to throttleLatest, throttleFirst, throttleLast, and throttleWithTimeout operators with an onDropped callback."}]}
{"prototype_id": "ReactiveX__RxJava_release_window", "repo": "ReactiveX/RxJava", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the ReactiveX/RxJava releases, how does the bugfix in v3.1.8 differ from the bugfix in v3.1.10?", "options": [{"option_id": "A", "text": "v3.1.8 fixes a NullPointerException in ObservableSwitchMap due to cancel race, while v3.1.10 fixes GC nepotism with MpscLinkedQueue's poll logic and a FlowableBlockingIterable.onNext exception loss."}, {"option_id": "B", "text": "v3.1.8 fixes a race condition in Single.timeout, while v3.1.10 fixes a ReplaySubject termination-subscription race."}, {"option_id": "C", "text": "v3.1.8 fixes ScheduledRunnable's interruption logic, while v3.1.10 fixes an empty module version string."}, {"option_id": "D", "text": "Both releases only update documentation without any bugfixes."}], "correct_option_id": "A", "expected_answer": "v3.1.8 fixes a NullPointerException in ObservableSwitchMap due to cancel race, while v3.1.10 fixes GC nepotism with MpscLinkedQueue's poll logic and a FlowableBlockingIterable.onNext exception loss.", "source_chunk_ids": ["ReactiveX__RxJava__release__v3_1_8", "ReactiveX__RxJava__release__v3_1_10"], "answer_support": [{"memory_node_id": "ReactiveX__RxJava__release__v3_1_8", "answer_text": "Fix ObservableSwitchMap NullPointerException due to cancel race."}, {"memory_node_id": "ReactiveX__RxJava__release__v3_1_10", "answer_text": "Fix GC nepotism with MpscLinkedQueue's poll logic. Fix FlowableBlockingIterable.onNext to set the exception before terminating to avoid losing it."}]}
{"prototype_id": "redis__redis_release_window", "repo": "redis/redis", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the redis/redis releases, which release introduces the CLUSTER MIGRATION command for atomic slot migration?", "options": [{"option_id": "A", "text": "8.2.2"}, {"option_id": "B", "text": "8.4-RC1"}, {"option_id": "C", "text": "8.6.0"}, {"option_id": "D", "text": "8.8.0"}], "correct_option_id": "B", "expected_answer": "8.4-RC1", "source_chunk_ids": ["redis__redis__release__8_4_rc1"], "answer_support": [{"memory_node_id": "redis__redis__release__8_4_rc1", "answer_text": "New features compared to 8.2.3 include CLUSTER MIGRATION for atomic slot migration"}]}
{"prototype_id": "redis__redis_release_window", "repo": "redis/redis", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the redis/redis releases, how does the security fix in 8.2.3 differ from the security fix in 8.6.1?", "options": [{"option_id": "A", "text": "8.2.3 fixes CVE-2025-62507 (XACKDEL stack overflow), while 8.6.1 fixes a \\r\\n injection vulnerability in error replies."}, {"option_id": "B", "text": "8.2.3 fixes a HyperLogLog crash, while 8.6.1 fixes a Lua Use-After-Free."}, {"option_id": "C", "text": "Both releases fix the same CVE-2025-49844 Lua script vulnerability."}, {"option_id": "D", "text": "8.2.3 fixes a Bloom filter out-of-bounds access, while 8.6.1 fixes a Cuckoo filter division by zero."}], "correct_option_id": "A", "expected_answer": "8.2.3 fixes CVE-2025-62507 (XACKDEL stack overflow), while 8.6.1 fixes a \\r\\n injection vulnerability in error replies.", "source_chunk_ids": ["redis__redis__release__8_2_3", "redis__redis__release__8_6_1"], "answer_support": [{"memory_node_id": "redis__redis__release__8_2_3", "answer_text": "security fix for CVE-2025-62507, a potential stack overflow and RCE in XACKDEL"}, {"memory_node_id": "redis__redis__release__8_6_1", "answer_text": "security fix addresses a vulnerability where a user can manipulate data read by a connection by injecting \\r\\n sequences into a Redis error reply"}]}
{"prototype_id": "redis__redis_release_window", "repo": "redis/redis", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the redis/redis release window, order the following release-content states from earliest to latest: (1) a release that introduces the HOTKEYS command, (2) a release that introduces the CLUSTER MIGRATION command, (3) a release that introduces the XNACK command, (4) a release that introduces the INCREX command.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "B", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "C", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "D", "text": "1 -> 2 -> 3 -> 4"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3 -> 4", "source_chunk_ids": ["redis__redis__release__8_4_rc1", "redis__redis__release__8_6_rc1", "redis__redis__release__8_8_m02", "redis__redis__release__8_8_rc1"], "answer_support": [{"memory_node_id": "redis__redis__release__8_4_rc1", "answer_text": "New features compared to 8.2.3 include CLUSTER MIGRATION for atomic slot migration"}, {"memory_node_id": "redis__redis__release__8_6_rc1", "answer_text": "New features compared to 8.4.0 include ... hot keys detection and reporting with the HOTKEYS command"}, {"memory_node_id": "redis__redis__release__8_8_m02", "answer_text": "New features compared to 8.6 include ... XNACK command for consumers to explicitly release pending messages"}, {"memory_node_id": "redis__redis__release__8_8_rc1", "answer_text": "New features compared to 8.8-M03 include ... INCREX window counter rate limiter"}]}
{"prototype_id": "refinedev__refine_release_window", "repo": "refinedev/refine", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the refinedev/refine releases, which release adds the option to disable RouteChangeHandler?", "options": [{"option_id": "A", "text": "@refinedev/core@5.0.6"}, {"option_id": "B", "text": "@refinedev/core@5.0.7"}, {"option_id": "C", "text": "@refinedev/core@5.0.8"}, {"option_id": "D", "text": "@refinedev/core@5.0.9"}], "correct_option_id": "B", "expected_answer": "@refinedev/core@5.0.7", "source_chunk_ids": ["refinedev__refine__release__refinedev_core_5_0_7"], "answer_support": [{"memory_node_id": "refinedev__refine__release__refinedev_core_5_0_7", "answer_text": "adds the option to disable RouteChangeHandler via the disableRouteChangeHandler option"}]}
{"prototype_id": "refinedev__refine_release_window", "repo": "refinedev/refine", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the refinedev/refine releases, how does the change in @refinedev/rest@2.1.0 differ from the change in @refinedev/rest@2.1.1?", "options": [{"option_id": "A", "text": "2.1.0 makes getMany optional, while 2.1.1 adds missing transformError to deleteOne and custom methods."}, {"option_id": "B", "text": "2.1.0 adds transformError, while 2.1.1 makes getMany optional."}, {"option_id": "C", "text": "Both releases only update dependencies."}, {"option_id": "D", "text": "2.1.0 disables minification, while 2.1.1 removes authentication."}], "correct_option_id": "A", "expected_answer": "2.1.0 makes getMany optional, while 2.1.1 adds missing transformError to deleteOne and custom methods.", "source_chunk_ids": ["refinedev__refine__release__refinedev_rest_2_1_0", "refinedev__refine__release__refinedev_rest_2_1_1"], "answer_support": [{"memory_node_id": "refinedev__refine__release__refinedev_rest_2_1_0", "answer_text": "makes the getMany method optional in the data provider"}, {"memory_node_id": "refinedev__refine__release__refinedev_rest_2_1_1", "answer_text": "adds missing transformError to deleteOne and custom methods"}]}
{"prototype_id": "refinedev__refine_release_window", "repo": "refinedev/refine", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the refinedev/refine release window, order the following release-content states from earliest to latest: (1) a release that adds case-sensitive eq and ne variants, (2) a release that adds the option to disable RouteChangeHandler, (3) a release that preserves custom getList response fields in useList and useTable.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3"}, {"option_id": "B", "text": "1 -> 2 -> 3"}, {"option_id": "C", "text": "2 -> 3 -> 1"}, {"option_id": "D", "text": "3 -> 1 -> 2"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3", "source_chunk_ids": ["refinedev__refine__release__refinedev_core_5_0_7", "refinedev__refine__release__refinedev_core_5_0_8", "refinedev__refine__release__refinedev_core_5_0_12"], "answer_support": [{"memory_node_id": "refinedev__refine__release__refinedev_core_5_0_7", "answer_text": "adds the option to disable RouteChangeHandler"}, {"memory_node_id": "refinedev__refine__release__refinedev_core_5_0_8", "answer_text": "adds case-sensitive eq and ne variants"}, {"memory_node_id": "refinedev__refine__release__refinedev_core_5_0_12", "answer_text": "preserves custom getList response fields in useList and useTable results"}]}
{"prototype_id": "rtk_ai__rtk_release_window", "repo": "rtk-ai/rtk", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the rtk-ai/rtk releases, which release introduces a TOML filter DSL engine with 14 built-in filters?", "options": [{"option_id": "A", "text": "v0.28.0"}, {"option_id": "B", "text": "v0.29.0"}, {"option_id": "C", "text": "v0.30.0"}, {"option_id": "D", "text": "v0.31.0"}], "correct_option_id": "A", "expected_answer": "v0.28.0", "source_chunk_ids": ["rtk_ai__rtk__release__v0_28_0"], "answer_support": [{"memory_node_id": "rtk_ai__rtk__release__v0_28_0", "answer_text": "TOML Part 1 — filter DSL engine + 14 built-in filters"}]}
{"prototype_id": "rtk_ai__rtk_release_window", "repo": "rtk-ai/rtk", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the rtk-ai/rtk releases, how does the telemetry-related change in v0.28.2 differ from the telemetry-related change in v0.34.1?", "options": [{"option_id": "A", "text": "v0.28.2 adds tokens_saved to the telemetry payload, while v0.34.1 salts the device hash for telemetry and sets 0600 permissions on the salt file."}, {"option_id": "B", "text": "v0.28.2 introduces anonymous telemetry ping, while v0.34.1 removes telemetry entirely."}, {"option_id": "C", "text": "Both releases only fix telemetry documentation without functional changes."}, {"option_id": "D", "text": "v0.28.2 caches the salt in-process, while v0.34.1 adds tokens_saved to the payload."}], "correct_option_id": "A", "expected_answer": "v0.28.2 adds tokens_saved to the telemetry payload, while v0.34.1 salts the device hash for telemetry and sets 0600 permissions on the salt file.", "source_chunk_ids": ["rtk_ai__rtk__release__v0_28_2", "rtk_ai__rtk__release__v0_34_1"], "answer_support": [{"memory_node_id": "rtk_ai__rtk__release__v0_28_2", "answer_text": "add tokens_saved to telemetry payload"}, {"memory_node_id": "rtk_ai__rtk__release__v0_34_1", "answer_text": "salt device hash for telemetry, set 0600 permissions on salt file"}]}
{"prototype_id": "rtk_ai__rtk_release_window", "repo": "rtk-ai/rtk", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the rtk-ai/rtk release window, order the following release-content states from earliest to latest: (1) a release that adds Graphite CLI support, (2) a release that introduces a rewrite engine and OpenCode support, (3) a release that adds a --copilot flag for GitHub Copilot integration in init, (4) a release that adds pi agent support in the hook.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["rtk_ai__rtk__release__v0_28_0", "rtk_ai__rtk__release__v0_29_0", "rtk_ai__rtk__release__v0_34_0", "rtk_ai__rtk__release__v0_42_0"], "answer_support": [{"memory_node_id": "rtk_ai__rtk__release__v0_28_0", "answer_text": "add Graphite CLI support"}, {"memory_node_id": "rtk_ai__rtk__release__v0_29_0", "answer_text": "rewrite engine, OpenCode support"}, {"memory_node_id": "rtk_ai__rtk__release__v0_34_0", "answer_text": "add --copilot flag for GitHub Copilot integration"}, {"memory_node_id": "rtk_ai__rtk__release__v0_42_0", "answer_text": "add pi agent support"}]}
{"prototype_id": "rust_lang__rust_release_window", "repo": "rust-lang/rust", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the rust-lang/rust releases, which release stabilizes async closures and the 2024 Edition?", "options": [{"option_id": "A", "text": "Rust 1.84.0"}, {"option_id": "B", "text": "Rust 1.85.0"}, {"option_id": "C", "text": "Rust 1.86.0"}, {"option_id": "D", "text": "Rust 1.87.0"}], "correct_option_id": "B", "expected_answer": "Rust 1.85.0", "source_chunk_ids": ["rust_lang__rust__release__1_85_0"], "answer_support": [{"memory_node_id": "rust_lang__rust__release__1_85_0", "answer_text": "The 2024 Edition is now stable. ... Stabilize async closures"}]}
{"prototype_id": "rust_lang__rust_release_window", "repo": "rust-lang/rust", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the rust-lang/rust releases, how does the handling of debuginfo differ between Rust 1.77.1 and Rust 1.84.1?", "options": [{"option_id": "A", "text": "1.77.1 reverts stripping debuginfo by default for Windows, while 1.84.1 fixes debuginfo when LLVM's location discriminator value limit is exceeded."}, {"option_id": "B", "text": "1.77.1 adds debuginfo in macros, while 1.84.1 removes debuginfo from PDB files."}, {"option_id": "C", "text": "Both releases only update Cargo dependencies without debuginfo changes."}, {"option_id": "D", "text": "1.77.1 stabilizes -C collapse-macro-debuginfo, while 1.84.1 deprecates -Cdwarf-version."}], "correct_option_id": "A", "expected_answer": "1.77.1 reverts stripping debuginfo by default for Windows, while 1.84.1 fixes debuginfo when LLVM's location discriminator value limit is exceeded.", "source_chunk_ids": ["rust_lang__rust__release__1_77_1", "rust_lang__rust__release__1_84_1"], "answer_support": [{"memory_node_id": "rust_lang__rust__release__1_77_1", "answer_text": "Revert stripping debuginfo by default for Windows"}, {"memory_node_id": "rust_lang__rust__release__1_84_1", "answer_text": "Fix debuginfo when LLVM's location discriminator value limit is exceeded"}]}
{"prototype_id": "rust_lang__rust_release_window", "repo": "rust-lang/rust", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the rust-lang/rust release window, order the following release-content states from earliest to latest: (1) a release that stabilizes C-string literals and THIR unsafeck, (2) a release that stabilizes async fn and return-position impl Trait in traits, (3) a release that stabilizes inline const {} expressions and associated type bounds, (4) a release that stabilizes &raw const and &raw mut operators and unsafe extern blocks.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "B", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "C", "text": "2 -> 3 -> 1 -> 4"}, {"option_id": "D", "text": "3 -> 2 -> 1 -> 4"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3 -> 4", "source_chunk_ids": ["rust_lang__rust__release__1_75_0", "rust_lang__rust__release__1_77_0", "rust_lang__rust__release__1_79_0", "rust_lang__rust__release__1_82_0"], "answer_support": [{"memory_node_id": "rust_lang__rust__release__1_75_0", "answer_text": "stabilizes async fn and return-position impl Trait in traits"}, {"memory_node_id": "rust_lang__rust__release__1_77_0", "answer_text": "stabilizes C-string literals and THIR unsafeck"}, {"memory_node_id": "rust_lang__rust__release__1_79_0", "answer_text": "stabilizes inline const {} expressions ... associated type bounds"}, {"memory_node_id": "rust_lang__rust__release__1_82_0", "answer_text": "stabilizes &raw const and &raw mut operators ... unsafe extern blocks"}]}
{"prototype_id": "rust_lang__rustlings_release_window", "repo": "rust-lang/rustlings", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the rust-lang/rustlings releases, how does the change to the exercise list in Rustlings 4.4.0 differ from the change to the exercise list in Rustlings v6.4.0?", "options": [{"option_id": "A", "text": "4.4.0 makes the list display structured data with filtering options and per-exercise progress, while v6.4.0 makes the list searchable and adds new prompt options c and x."}, {"option_id": "B", "text": "4.4.0 adds a search feature to the list, while v6.4.0 removes the list entirely."}, {"option_id": "C", "text": "Both releases only add a progress indicator to the list without other changes."}, {"option_id": "D", "text": "4.4.0 introduces the list command for the first time, while v6.4.0 adds mouse scrolling to the list."}], "correct_option_id": "A", "expected_answer": "4.4.0 makes the list display structured data with filtering options and per-exercise progress, while v6.4.0 makes the list searchable and adds new prompt options c and x.", "source_chunk_ids": ["rust_lang__rustlings__release__4_4_0", "rust_lang__rustlings__release__v6_4_0"], "answer_support": [{"memory_node_id": "rust_lang__rustlings__release__4_4_0", "answer_text": "rustlings list now displays structured data, and a takes a lot more options to filter that data ... also now shows you progress per-exercise"}, {"memory_node_id": "rust_lang__rustlings__release__v6_4_0", "answer_text": "The list of exercises is now searchable ... New option c in the prompt to manually check all exercises ... New option x in the prompt to reset the file of the current exercise"}]}
{"prototype_id": "rust_lang__rustlings_release_window", "repo": "rust-lang/rustlings", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the rust-lang/rustlings release window, order the following release-content states from earliest to latest: (1) a release that adds a progress indicator and a new rustlings lsp command, (2) a release that adds a new intro section and rust-analyzer support, (3) a release that makes the exercise list searchable and adds a check-all command, (4) a release that upgrades to Rust edition 2024 and raises the minimum supported Rust version to 1.88.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "B", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "C", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "D", "text": "1 -> 2 -> 3 -> 4"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3 -> 4", "source_chunk_ids": ["rust_lang__rustlings__release__4_7_0", "rust_lang__rustlings__release__4_8_0", "rust_lang__rustlings__release__v6_4_0", "rust_lang__rustlings__release__v6_5_0"], "answer_support": [{"memory_node_id": "rust_lang__rustlings__release__4_7_0", "answer_text": "A new intro section prefixing the normal exercises has been added ... rust-analyzer support has been added"}, {"memory_node_id": "rust_lang__rustlings__release__4_8_0", "answer_text": "Adds a progress indicator, a new rustlings lsp command"}, {"memory_node_id": "rust_lang__rustlings__release__v6_4_0", "answer_text": "The list of exercises is now searchable ... New command check-all"}, {"memory_node_id": "rust_lang__rustlings__release__v6_5_0", "answer_text": "Upgrade to Rust edition 2024 ... Raise the minimum supported Rust version to 1.88"}]}
{"prototype_id": "rustdesk__rustdesk_release_window", "repo": "rustdesk/rustdesk", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the rustdesk/rustdesk releases, which release introduces a web client v2 preview and auto record outgoing sessions?", "options": [{"option_id": "A", "text": "1.3.0"}, {"option_id": "B", "text": "1.3.2"}, {"option_id": "C", "text": "1.3.1"}, {"option_id": "D", "text": "1.2.7"}], "correct_option_id": "B", "expected_answer": "1.3.2", "source_chunk_ids": ["rustdesk__rustdesk__release__1_3_2"], "answer_support": [{"memory_node_id": "rustdesk__rustdesk__release__1_3_2", "answer_text": "adds a Web client v2 Preview, auto record outgoing sessions"}]}
{"prototype_id": "rustdesk__rustdesk_release_window", "repo": "rustdesk/rustdesk", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the rustdesk/rustdesk releases, how does the Wayland support described in release 1.2.3 differ from the Wayland support described in release 1.4.3?", "options": [{"option_id": "A", "text": "1.2.3 improves Wayland support for cursor, clipboard, and multi-monitors but depends on Xwayland and works well on GNOME with bad KDE compatibility, while 1.4.3 adds Wayland multi-monitor screen capture functionality."}, {"option_id": "B", "text": "1.2.3 removes Wayland support entirely, while 1.4.3 reintroduces it with full KDE compatibility."}, {"option_id": "C", "text": "Both releases only mention Wayland as an experimental feature with no specific improvements."}, {"option_id": "D", "text": "1.2.3 adds Wayland multi-monitor screen capture, while 1.4.3 improves cursor and clipboard support."}], "correct_option_id": "A", "expected_answer": "1.2.3 improves Wayland support for cursor, clipboard, and multi-monitors but depends on Xwayland and works well on GNOME with bad KDE compatibility, while 1.4.3 adds Wayland multi-monitor screen capture functionality.", "source_chunk_ids": ["rustdesk__rustdesk__release__1_2_3", "rustdesk__rustdesk__release__1_4_3"], "answer_support": [{"memory_node_id": "rustdesk__rustdesk__release__1_2_3", "answer_text": "improve Wayland support, cursor/clipboard/multi-monitors etc, but highly depends on Xwayland, working well on GNOME, bad compatibility on KDE"}, {"memory_node_id": "rustdesk__rustdesk__release__1_4_3", "answer_text": "Wayland multi-monitor screen capture functionality"}]}
{"prototype_id": "rustdesk__rustdesk_release_window", "repo": "rustdesk/rustdesk", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the rustdesk/rustdesk release window, order the following release-content states from earliest to latest: (1) a release that adds a web client (Beta, for Chrome) and Mac background service, (2) a release that adds a web client v2 preview and auto record outgoing sessions, (3) a release that adds a terminal and UDP/IPv6 punch, (4) a release that adds remote printer (Windows to Windows only) and view camera.", "options": [{"option_id": "A", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "B", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "C", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "D", "text": "1 -> 4 -> 2 -> 3"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 4 -> 3", "source_chunk_ids": ["rustdesk__rustdesk__release__1_1_9", "rustdesk__rustdesk__release__1_3_2", "rustdesk__rustdesk__release__1_3_9", "rustdesk__rustdesk__release__1_4_1"], "answer_support": [{"memory_node_id": "rustdesk__rustdesk__release__1_1_9", "answer_text": "Web client (Beta, Chrome please), Mac background service"}, {"memory_node_id": "rustdesk__rustdesk__release__1_3_2", "answer_text": "Web client v2 Preview, auto record outgoing sessions"}, {"memory_node_id": "rustdesk__rustdesk__release__1_3_9", "answer_text": "Remote printer (Windows -> Windows only for now), View camera"}, {"memory_node_id": "rustdesk__rustdesk__release__1_4_1", "answer_text": "Terminal, UDP and IPv6 Punch"}]}
{"prototype_id": "ruvnet__RuView_release_window", "repo": "ruvnet/RuView", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the ruvnet/RuView releases, which release adds a navigation router and three new pages (States, Services, Settings) to the HOMECORE web UI?", "options": [{"option_id": "A", "text": "v0.11.0"}, {"option_id": "B", "text": "v1397"}, {"option_id": "C", "text": "v0.12.0"}, {"option_id": "D", "text": "v1402"}], "correct_option_id": "B", "expected_answer": "v1397", "source_chunk_ids": ["ruvnet__RuView__release__v1397"], "answer_support": [{"memory_node_id": "ruvnet__RuView__release__v1397", "answer_text": "adds a navigation router and three new pages to the HOMECORE web UI: States, Services, and Settings"}]}
{"prototype_id": "ruvnet__RuView_release_window", "repo": "ruvnet/RuView", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the ruvnet/RuView releases, how does the HOMECORE web UI change from v1397 to v0.12.0?", "options": [{"option_id": "A", "text": "v1397 adds a router and three pages, while v0.12.0 makes the UI functional with Dashboard, States, Services, Settings pages and expands the Trust Kill Switch to 9 phases."}, {"option_id": "B", "text": "v1397 removes the UI, and v0.12.0 adds it back."}, {"option_id": "C", "text": "Both releases only update Docker images without UI changes."}, {"option_id": "D", "text": "v1397 adds entity seeding, and v0.12.0 adds service seeding."}], "correct_option_id": "A", "expected_answer": "v1397 adds a router and three pages, while v0.12.0 makes the UI functional with Dashboard, States, Services, Settings pages and expands the Trust Kill Switch to 9 phases.", "source_chunk_ids": ["ruvnet__RuView__release__v1397", "ruvnet__RuView__release__v0_12_0"], "answer_support": [{"memory_node_id": "ruvnet__RuView__release__v1397", "answer_text": "adds a navigation router and three new pages to the HOMECORE web UI: States, Services, and Settings"}, {"memory_node_id": "ruvnet__RuView__release__v0_12_0", "answer_text": "the HOMECORE web UI becomes functional with new Dashboard, States, Services, and Settings pages ... Trust Kill Switch is expanded to a 9-phase verification"}]}
{"prototype_id": "ruvnet__RuView_release_window", "repo": "ruvnet/RuView", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the ruvnet/RuView release window, order the following release-content states from earliest to latest: (1) a release that seeds 13 default services across 6 domains on boot, (2) a release that adds a navigation router and three new pages to the HOMECORE web UI, (3) a release that adds an Add Entity flow with a modal and form.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3"}, {"option_id": "B", "text": "1 -> 2 -> 3"}, {"option_id": "C", "text": "2 -> 3 -> 1"}, {"option_id": "D", "text": "3 -> 1 -> 2"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3", "source_chunk_ids": ["ruvnet__RuView__release__v1397", "ruvnet__RuView__release__v1402", "ruvnet__RuView__release__v1404"], "answer_support": [{"memory_node_id": "ruvnet__RuView__release__v1397", "answer_text": "adds a navigation router and three new pages to the HOMECORE web UI"}, {"memory_node_id": "ruvnet__RuView__release__v1402", "answer_text": "seeds 13 default services across 6 domains on boot"}, {"memory_node_id": "ruvnet__RuView__release__v1404", "answer_text": "gains an Add Entity flow with a modal and form"}]}
{"prototype_id": "seaweedfs__seaweedfs_release_window", "repo": "seaweedfs/seaweedfs", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the seaweedfs/seaweedfs releases, which release introduces the 'weed mini' command for beginners and test/dev environments?", "options": [{"option_id": "A", "text": "4.01"}, {"option_id": "B", "text": "4.04"}, {"option_id": "C", "text": "4.05"}, {"option_id": "D", "text": "4.06"}], "correct_option_id": "B", "expected_answer": "4.04", "source_chunk_ids": ["seaweedfs__seaweedfs__release__4_04"], "answer_support": [{"memory_node_id": "seaweedfs__seaweedfs__release__4_04", "answer_text": "introduces the 'weed mini' command for beginners and test/dev environments"}]}
{"prototype_id": "seaweedfs__seaweedfs_release_window", "repo": "seaweedfs/seaweedfs", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the seaweedfs/seaweedfs releases, how does the architectural change in release 4.01 differ from the new feature introduced in release 4.04?", "options": [{"option_id": "A", "text": "4.01 introduces direct S3 API to volume server access reducing latency, while 4.04 introduces the 'weed mini' command for easy local setup."}, {"option_id": "B", "text": "4.01 adds TUS protocol support, while 4.04 merges IAM server into S3 server."}, {"option_id": "C", "text": "Both releases focus on Helm chart improvements only."}, {"option_id": "D", "text": "4.01 removes the filer component, while 4.04 adds a new NFS server."}], "correct_option_id": "A", "expected_answer": "4.01 introduces direct S3 API to volume server access reducing latency, while 4.04 introduces the 'weed mini' command for easy local setup.", "source_chunk_ids": ["seaweedfs__seaweedfs__release__4_01", "seaweedfs__seaweedfs__release__4_04"], "answer_support": [{"memory_node_id": "seaweedfs__seaweedfs__release__4_01", "answer_text": "major architectural change introduces direct S3 API to volume server access, reducing write latency by 30% and read latency by 5%"}, {"memory_node_id": "seaweedfs__seaweedfs__release__4_04", "answer_text": "introduces the 'weed mini' command for beginners and test/dev environments"}]}
{"prototype_id": "seaweedfs__seaweedfs_release_window", "repo": "seaweedfs/seaweedfs", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the seaweedfs/seaweedfs release window, order the following release-content states from earliest to latest: (1) a release that adds TUS protocol support for resumable uploads and merges IAM server into S3 server, (2) a release that introduces the 'weed mini' command, (3) a release that announces 100% POSIX compliance for FUSE Mount and peer-to-peer chunk sharing, (4) a release that adds S3 Tables support for Iceberg tabular data.", "options": [{"option_id": "A", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "B", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "C", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "D", "text": "1 -> 2 -> 4 -> 3"}], "correct_option_id": "D", "expected_answer": "1 -> 2 -> 4 -> 3", "source_chunk_ids": ["seaweedfs__seaweedfs__release__4_03", "seaweedfs__seaweedfs__release__4_04", "seaweedfs__seaweedfs__release__4_09", "seaweedfs__seaweedfs__release__4_21"], "answer_support": [{"memory_node_id": "seaweedfs__seaweedfs__release__4_03", "answer_text": "adds TUS protocol support for resumable HTTP uploads in the filer and merges the IAM server into the S3 server"}, {"memory_node_id": "seaweedfs__seaweedfs__release__4_04", "answer_text": "introduces the 'weed mini' command"}, {"memory_node_id": "seaweedfs__seaweedfs__release__4_09", "answer_text": "introduction of S3 Tables support for Iceberg tabular data"}, {"memory_node_id": "seaweedfs__seaweedfs__release__4_21", "answer_text": "announces 100% POSIX compliance for FUSE Mount, peer-to-peer file chunk sharing"}]}
{"prototype_id": "SeleniumHQ__selenium_release_window", "repo": "SeleniumHQ/selenium", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the SeleniumHQ/selenium releases, which release includes a commit that adds high-level logging APIs in Java BiDi?", "options": [{"option_id": "A", "text": "Selenium 4.22.0"}, {"option_id": "B", "text": "Selenium 4.23.0"}, {"option_id": "C", "text": "Selenium 4.24.0"}, {"option_id": "D", "text": "Selenium 4.25.0"}], "correct_option_id": "B", "expected_answer": "Selenium 4.23.0", "source_chunk_ids": ["SeleniumHQ__selenium__release__selenium_4_23_0"], "answer_support": [{"memory_node_id": "SeleniumHQ__selenium__release__selenium_4_23_0", "answer_text": "adding high-level logging APIs in Java BiDi"}]}
{"prototype_id": "SeleniumHQ__selenium_release_window", "repo": "SeleniumHQ/selenium", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the SeleniumHQ/selenium releases, how does the BiDi-related change described in Selenium 4.22.0 differ from the BiDi-related change described in Selenium 4.23.0?", "options": [{"option_id": "A", "text": "4.22.0 implements a High Level Logging API with BiDi in Ruby, while 4.23.0 adds high-level logging APIs in Java BiDi."}, {"option_id": "B", "text": "4.22.0 adds high-level logging APIs in Java BiDi, while 4.23.0 implements a High Level Logging API with BiDi in Ruby."}, {"option_id": "C", "text": "Both releases only update CDP versions without BiDi changes."}, {"option_id": "D", "text": "4.22.0 deprecates BiDi, while 4.23.0 removes BiDi support."}], "correct_option_id": "A", "expected_answer": "4.22.0 implements a High Level Logging API with BiDi in Ruby, while 4.23.0 adds high-level logging APIs in Java BiDi.", "source_chunk_ids": ["SeleniumHQ__selenium__release__selenium_4_22_0", "SeleniumHQ__selenium__release__selenium_4_23_0"], "answer_support": [{"memory_node_id": "SeleniumHQ__selenium__release__selenium_4_22_0", "answer_text": "implementing High Level Logging API with BiDi in Ruby"}, {"memory_node_id": "SeleniumHQ__selenium__release__selenium_4_23_0", "answer_text": "adding high-level logging APIs in Java BiDi"}]}
{"prototype_id": "SeleniumHQ__selenium_release_window", "repo": "SeleniumHQ/selenium", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the SeleniumHQ/selenium release window, order the following release-content states from earliest to latest: (1) a release that includes a commit to update CDP to version 122, (2) a release that includes a commit to add high-level logging APIs in Java BiDi, (3) a release that includes a commit to add convenience for enabling BiDi in Java.", "options": [{"option_id": "A", "text": "1 -> 3 -> 2"}, {"option_id": "B", "text": "3 -> 1 -> 2"}, {"option_id": "C", "text": "2 -> 1 -> 3"}, {"option_id": "D", "text": "1 -> 2 -> 3"}], "correct_option_id": "A", "expected_answer": "1 -> 3 -> 2", "source_chunk_ids": ["SeleniumHQ__selenium__release__selenium_4_19_0", "SeleniumHQ__selenium__release__selenium_4_22_0", "SeleniumHQ__selenium__release__selenium_4_23_0"], "answer_support": [{"memory_node_id": "SeleniumHQ__selenium__release__selenium_4_19_0", "answer_text": "updating CDP to version 122"}, {"memory_node_id": "SeleniumHQ__selenium__release__selenium_4_22_0", "answer_text": "adding convenience for enabling BiDi in Java"}, {"memory_node_id": "SeleniumHQ__selenium__release__selenium_4_23_0", "answer_text": "adding high-level logging APIs in Java BiDi"}]}
{"prototype_id": "shadcn_ui__ui_release_window", "repo": "shadcn-ui/ui", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the shadcn-ui/ui releases, which release adds the shadcn apply command?", "options": [{"option_id": "A", "text": "shadcn@4.0.0"}, {"option_id": "B", "text": "shadcn@4.2.0"}, {"option_id": "C", "text": "shadcn@4.3.0"}, {"option_id": "D", "text": "shadcn@4.4.0"}], "correct_option_id": "B", "expected_answer": "shadcn@4.2.0", "source_chunk_ids": ["shadcn_ui__ui__release__shadcn_4_2_0"], "answer_support": [{"memory_node_id": "shadcn_ui__ui__release__shadcn_4_2_0", "answer_text": "adds the shadcn apply command"}]}
{"prototype_id": "shadcn_ui__ui_release_window", "repo": "shadcn-ui/ui", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the shadcn-ui/ui releases, how does the change in shadcn@4.0.0 regarding base colors differ from the change in shadcn@4.1.2 regarding styles?", "options": [{"option_id": "A", "text": "shadcn@4.0.0 adds new base colors mauve, olive, mist and taupe, while shadcn@4.1.2 adds style luma."}, {"option_id": "B", "text": "shadcn@4.0.0 removes base colors, while shadcn@4.1.2 adds style sera."}, {"option_id": "C", "text": "Both releases add the same set of base colors."}, {"option_id": "D", "text": "shadcn@4.0.0 adds style luma, while shadcn@4.1.2 adds base colors."}], "correct_option_id": "A", "expected_answer": "shadcn@4.0.0 adds new base colors mauve, olive, mist and taupe, while shadcn@4.1.2 adds style luma.", "source_chunk_ids": ["shadcn_ui__ui__release__shadcn_4_0_0", "shadcn_ui__ui__release__shadcn_4_1_2"], "answer_support": [{"memory_node_id": "shadcn_ui__ui__release__shadcn_4_0_0", "answer_text": "add new base colors: mauve, olive, mist and taupe"}, {"memory_node_id": "shadcn_ui__ui__release__shadcn_4_1_2", "answer_text": "add style luma"}]}
{"prototype_id": "shadcn_ui__ui_release_window", "repo": "shadcn-ui/ui", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the shadcn-ui/ui release window, order the following release-content states from earliest to latest: (1) a release that adds support for translucent menu, (2) a release that adds the shadcn apply command, (3) a release that adds npx shadcn eject, (4) a release that adds support for GitHub registries.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["shadcn_ui__ui__release__shadcn_4_0_3", "shadcn_ui__ui__release__shadcn_4_2_0", "shadcn_ui__ui__release__shadcn_4_9_0", "shadcn_ui__ui__release__shadcn_4_10_0"], "answer_support": [{"memory_node_id": "shadcn_ui__ui__release__shadcn_4_0_3", "answer_text": "adds support for translucent menu"}, {"memory_node_id": "shadcn_ui__ui__release__shadcn_4_2_0", "answer_text": "adds the shadcn apply command"}, {"memory_node_id": "shadcn_ui__ui__release__shadcn_4_9_0", "answer_text": "adds npx shadcn eject"}, {"memory_node_id": "shadcn_ui__ui__release__shadcn_4_10_0", "answer_text": "adds support for GitHub registries"}]}
{"prototype_id": "shadowsocks__shadowsocks_android_release_window", "repo": "shadowsocks/shadowsocks-android", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the shadowsocks/shadowsocks-android releases, which release adds subscription support for mobile and IPv6 support for ACL rules?", "options": [{"option_id": "A", "text": "v5.0.0"}, {"option_id": "B", "text": "v5.1.0"}, {"option_id": "C", "text": "v5.0.1"}, {"option_id": "D", "text": "v5.2.3"}], "correct_option_id": "A", "expected_answer": "v5.0.0", "source_chunk_ids": ["shadowsocks__shadowsocks_android__release__v5_0_0"], "answer_support": [{"memory_node_id": "shadowsocks__shadowsocks_android__release__v5_0_0", "answer_text": "adds subscription support for mobile, IPv6 support for ACL rules"}]}
{"prototype_id": "shadowsocks__shadowsocks_android_release_window", "repo": "shadowsocks/shadowsocks-android", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the shadowsocks/shadowsocks-android releases, how does the cipher-related change in v5.1.9 differ from the cipher-related change in v5.2.3?", "options": [{"option_id": "A", "text": "v5.1.9 removes obsolete ciphers, while v5.2.3 adds back the xchacha20-ietf-poly1305 cipher."}, {"option_id": "B", "text": "v5.1.9 adds the xchacha20-ietf-poly1305 cipher, while v5.2.3 removes obsolete ciphers."}, {"option_id": "C", "text": "Both releases only update the plugin library without cipher changes."}, {"option_id": "D", "text": "v5.1.9 deprecates the 'plain' method, while v5.2.3 introduces AEAD-2022."}], "correct_option_id": "A", "expected_answer": "v5.1.9 removes obsolete ciphers, while v5.2.3 adds back the xchacha20-ietf-poly1305 cipher.", "source_chunk_ids": ["shadowsocks__shadowsocks_android__release__v5_1_9", "shadowsocks__shadowsocks_android__release__v5_2_3"], "answer_support": [{"memory_node_id": "shadowsocks__shadowsocks_android__release__v5_1_9", "answer_text": "obsolete ciphers are removed"}, {"memory_node_id": "shadowsocks__shadowsocks_android__release__v5_2_3", "answer_text": "xchacha20-ietf-poly1305 cipher is added back"}]}
{"prototype_id": "shadowsocks__shadowsocks_android_release_window", "repo": "shadowsocks/shadowsocks-android", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the shadowsocks/shadowsocks-android release window, order the following release-content states from earliest to latest: (1) a release that adds support for Android 11 and updates the QR code scanner to use machine learning, (2) a release that adds support for Android 12, (3) a release that adds support for Android 13, (4) a release that applies multiple fixes for Android 14.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["shadowsocks__shadowsocks_android__release__v5_1_2", "shadowsocks__shadowsocks_android__release__v5_2_6", "shadowsocks__shadowsocks_android__release__v5_3_1_preview", "shadowsocks__shadowsocks_android__release__v5_3_4"], "answer_support": [{"memory_node_id": "shadowsocks__shadowsocks_android__release__v5_1_2", "answer_text": "support for Android 11 is added, the built-in QR code scanner is updated to use machine learning technology"}, {"memory_node_id": "shadowsocks__shadowsocks_android__release__v5_2_6", "answer_text": "Support Android 12"}, {"memory_node_id": "shadowsocks__shadowsocks_android__release__v5_3_1_preview", "answer_text": "Android 13 support"}, {"memory_node_id": "shadowsocks__shadowsocks_android__release__v5_3_4", "answer_text": "Multiple fixes for Android 14"}]}
{"prototype_id": "sharkdp__bat_release_window", "repo": "sharkdp/bat", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the sharkdp/bat releases, which release introduces the --diff option to show only lines surrounding Git changes?", "options": [{"option_id": "A", "text": "v0.14.0"}, {"option_id": "B", "text": "v0.15.0"}, {"option_id": "C", "text": "v0.16.0"}, {"option_id": "D", "text": "v0.17.0"}], "correct_option_id": "B", "expected_answer": "v0.15.0", "source_chunk_ids": ["sharkdp__bat__release__v0_15_0"], "answer_support": [{"memory_node_id": "sharkdp__bat__release__v0_15_0", "answer_text": "This release adds a new --diff/-d option that can be used to only show lines surrounding Git changes"}]}
{"prototype_id": "sharkdp__bat_release_window", "repo": "sharkdp/bat", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the sharkdp/bat releases, how does the paging-related change in v0.26.0 differ from the paging-related change in v0.26.1?", "options": [{"option_id": "A", "text": "v0.26.0 adds paging to --list-themes, while v0.26.1 adds paging to -h and --help."}, {"option_id": "B", "text": "v0.26.0 adds a built-in pager, while v0.26.1 removes paging from --list-themes."}, {"option_id": "C", "text": "Both releases add paging to --list-themes."}, {"option_id": "D", "text": "v0.26.0 adds paging to --help, while v0.26.1 adds paging to --list-themes."}], "correct_option_id": "A", "expected_answer": "v0.26.0 adds paging to --list-themes, while v0.26.1 adds paging to -h and --help.", "source_chunk_ids": ["sharkdp__bat__release__v0_26_0", "sharkdp__bat__release__v0_26_1"], "answer_support": [{"memory_node_id": "sharkdp__bat__release__v0_26_0", "answer_text": "Add paging to --list-themes"}, {"memory_node_id": "sharkdp__bat__release__v0_26_1", "answer_text": "Add paging to '-h' and '--help'"}]}
{"prototype_id": "sharkdp__bat_release_window", "repo": "sharkdp/bat", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the sharkdp/bat release window, order the following release-content states from earliest to latest: (1) a release that adds the --highlight-line option, (2) a release that makes environment variables override config file settings, (3) a release that adds the --squeeze-blank option, (4) a release that adds a built-in 'minus' pager.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["sharkdp__bat__release__v0_10_0", "sharkdp__bat__release__v0_23_0", "sharkdp__bat__release__v0_25_0", "sharkdp__bat__release__v0_26_0"], "answer_support": [{"memory_node_id": "sharkdp__bat__release__v0_10_0", "answer_text": "Added new --highlight-line <N> option"}, {"memory_node_id": "sharkdp__bat__release__v0_23_0", "answer_text": "Breaking change: Environment variables can now override config file settings"}, {"memory_node_id": "sharkdp__bat__release__v0_25_0", "answer_text": "bat --squeeze-blank/bat -s will now squeeze consecutive empty lines"}, {"memory_node_id": "sharkdp__bat__release__v0_26_0", "answer_text": "Add built-in 'minus' pager"}]}
{"prototype_id": "sharkdp__fd_release_window", "repo": "sharkdp/fd", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the sharkdp/fd releases, which release introduces the --exec-batch option for batch command execution?", "options": [{"option_id": "A", "text": "v7.2.0"}, {"option_id": "B", "text": "v7.3.0"}, {"option_id": "C", "text": "v7.4.0"}, {"option_id": "D", "text": "v8.0.0"}], "correct_option_id": "B", "expected_answer": "v7.3.0", "source_chunk_ids": ["sharkdp__fd__release__v7_3_0"], "answer_support": [{"memory_node_id": "sharkdp__fd__release__v7_3_0", "answer_text": "introduces --exec-batch / -X for batch command execution"}]}
{"prototype_id": "sharkdp__fd_release_window", "repo": "sharkdp/fd", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the sharkdp/fd releases, how does the handling of .gitignore differ between v7.1.0 and v9.0.0?", "options": [{"option_id": "A", "text": "v7.1.0 respects .gitignore only inside Git repositories, while v9.0.0 ignores .git/ by default when using --hidden."}, {"option_id": "B", "text": "v7.1.0 ignores .gitignore entirely, while v9.0.0 always respects it."}, {"option_id": "C", "text": "Both releases treat .gitignore identically."}, {"option_id": "D", "text": "v7.1.0 adds .fdignore support, while v9.0.0 removes .gitignore support."}], "correct_option_id": "A", "expected_answer": "v7.1.0 respects .gitignore only inside Git repositories, while v9.0.0 ignores .git/ by default when using --hidden.", "source_chunk_ids": ["sharkdp__fd__release__v7_1_0", "sharkdp__fd__release__v9_0_0"], "answer_support": [{"memory_node_id": "sharkdp__fd__release__v7_1_0", "answer_text": "changes .gitignore to only be respected inside Git repositories"}, {"memory_node_id": "sharkdp__fd__release__v9_0_0", "answer_text": "ignores .git/ by default when using --hidden"}]}
{"prototype_id": "sharkdp__fd_release_window", "repo": "sharkdp/fd", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the sharkdp/fd release window, order the following release-content states from earliest to latest: (1) a release that adds --list-details and --max-results, (2) a release that adds --owner filter and global ignore file, (3) a release that adds --hyperlink option, (4) a release that adds --ignore-contain option.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "2 -> 3 -> 1 -> 4"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["sharkdp__fd__release__v8_0_0", "sharkdp__fd__release__v8_1_0", "sharkdp__fd__release__v10_2_0", "sharkdp__fd__release__v10_4_0"], "answer_support": [{"memory_node_id": "sharkdp__fd__release__v8_0_0", "answer_text": "adds --list-details / -l to show metadata, --max-results to limit results"}, {"memory_node_id": "sharkdp__fd__release__v8_1_0", "answer_text": "adds --owner filter to filter by user/group, support for a global ignore file"}, {"memory_node_id": "sharkdp__fd__release__v10_2_0", "answer_text": "adds --hyperlink option for OSC 8 hyperlinks"}, {"memory_node_id": "sharkdp__fd__release__v10_4_0", "answer_text": "adds --ignore-contain option to ignore directories containing a named entry"}]}
{"prototype_id": "SigNoz__signoz_release_window", "repo": "SigNoz/signoz", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the SigNoz/signoz releases, which release introduces a feature for adding Docker support for APM data sources in onboarding?", "options": [{"option_id": "A", "text": "v0.109.3"}, {"option_id": "B", "text": "v0.110.1"}, {"option_id": "C", "text": "v0.111.0"}, {"option_id": "D", "text": "v0.112.0"}], "correct_option_id": "C", "expected_answer": "v0.111.0", "source_chunk_ids": ["SigNoz__signoz__release__v0_111_0"], "answer_support": [{"memory_node_id": "SigNoz__signoz__release__v0_111_0", "answer_text": "feat(onboarding): add Docker support for apm data sources"}]}
{"prototype_id": "SigNoz__signoz_release_window", "repo": "SigNoz/signoz", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the SigNoz/signoz releases, how does the sidebar enhancement feature differ between v0.109.3 and v0.110.0?", "options": [{"option_id": "A", "text": "v0.109.3 adds sidebar enhancement, while v0.110.0 reverts it."}, {"option_id": "B", "text": "v0.109.3 removes sidebar enhancement, while v0.110.0 adds it."}, {"option_id": "C", "text": "Both releases add sidebar enhancement."}, {"option_id": "D", "text": "Neither release mentions sidebar enhancement."}], "correct_option_id": "A", "expected_answer": "v0.109.3 adds sidebar enhancement, while v0.110.0 reverts it.", "source_chunk_ids": ["SigNoz__signoz__release__v0_109_3", "SigNoz__signoz__release__v0_110_0"], "answer_support": [{"memory_node_id": "SigNoz__signoz__release__v0_109_3", "answer_text": "feat: sidebar enhancement"}, {"memory_node_id": "SigNoz__signoz__release__v0_110_0", "answer_text": "Revert \"feat: sidebar enhancement\""}]}
{"prototype_id": "SigNoz__signoz_release_window", "repo": "SigNoz/signoz", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the SigNoz/signoz release window, order the following release-content states from earliest to latest: (1) a release that adds a feature for removing the search input and adding a view data sources button in the integrations header, (2) a release that adds a feature for passing region to docs, (3) a release that adds a feature for Docker support for APM data sources in onboarding.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["SigNoz__signoz__release__v0_109_3", "SigNoz__signoz__release__v0_110_1", "SigNoz__signoz__release__v0_111_0"], "answer_support": [{"memory_node_id": "SigNoz__signoz__release__v0_109_3", "answer_text": "feat: remove search input and add view data sources button in integrations header"}, {"memory_node_id": "SigNoz__signoz__release__v0_110_1", "answer_text": "feat: pass region to docs"}, {"memory_node_id": "SigNoz__signoz__release__v0_111_0", "answer_text": "feat(onboarding): add Docker support for apm data sources"}]}
{"prototype_id": "Skyvern_AI__skyvern_release_window", "repo": "Skyvern-AI/skyvern", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the Skyvern-AI/skyvern releases, which release introduces a general text captcha solution and browser sessions v2 backend?", "options": [{"option_id": "A", "text": "v1.0.8"}, {"option_id": "B", "text": "v1.0.9"}, {"option_id": "C", "text": "v1.0.10"}, {"option_id": "D", "text": "v1.0.11"}], "correct_option_id": "C", "expected_answer": "v1.0.10", "source_chunk_ids": ["Skyvern_AI__skyvern__release__v1_0_10"], "answer_support": [{"memory_node_id": "Skyvern_AI__skyvern__release__v1_0_10", "answer_text": "added a general text captcha solution, implemented browser sessions v2 backend"}]}
{"prototype_id": "Skyvern_AI__skyvern_release_window", "repo": "Skyvern-AI/skyvern", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the Skyvern-AI/skyvern releases, how does the Workflow Copilot change described in v1.0.9 differ from the Workflow Copilot change described in v1.0.10?", "options": [{"option_id": "A", "text": "v1.0.9 enables streaming in /chat-post for Workflow Copilot, while v1.0.10 introduces LLM-based YAML autocorrection for Workflow Copilot."}, {"option_id": "B", "text": "v1.0.9 adds Workflow Copilot knowledge base update, while v1.0.10 removes Workflow Copilot entirely."}, {"option_id": "C", "text": "Both releases only update API specifications without any Copilot changes."}, {"option_id": "D", "text": "v1.0.9 adds a general text captcha solution, while v1.0.10 adds browser sessions v2 backend."}], "correct_option_id": "A", "expected_answer": "v1.0.9 enables streaming in /chat-post for Workflow Copilot, while v1.0.10 introduces LLM-based YAML autocorrection for Workflow Copilot.", "source_chunk_ids": ["Skyvern_AI__skyvern__release__v1_0_9", "Skyvern_AI__skyvern__release__v1_0_10"], "answer_support": [{"memory_node_id": "Skyvern_AI__skyvern__release__v1_0_9", "answer_text": "enabled streaming in /chat-post for Workflow Copilot"}, {"memory_node_id": "Skyvern_AI__skyvern__release__v1_0_10", "answer_text": "introduced LLM-based YAML autocorrection for Workflow Copilot"}]}
{"prototype_id": "Skyvern_AI__skyvern_release_window", "repo": "Skyvern-AI/skyvern", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the Skyvern-AI/skyvern release window, order the following release-content states from earliest to latest: (1) a release that adds a general text captcha solution and browser sessions v2 backend, (2) a release that adds a Skyvern skill package, CLI commands, and setup commands, (3) a release that adds browser profile testing and login-free workflow support on backend, (4) a release that adds gated admin impersonation controls for MCP API-key auth.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["Skyvern_AI__skyvern__release__v1_0_10", "Skyvern_AI__skyvern__release__v1_0_17", "Skyvern_AI__skyvern__release__v1_0_18", "Skyvern_AI__skyvern__release__v1_0_19"], "answer_support": [{"memory_node_id": "Skyvern_AI__skyvern__release__v1_0_10", "answer_text": "added a general text captcha solution, implemented browser sessions v2 backend"}, {"memory_node_id": "Skyvern_AI__skyvern__release__v1_0_17", "answer_text": "added a Skyvern skill package, CLI commands, and setup commands"}, {"memory_node_id": "Skyvern_AI__skyvern__release__v1_0_18", "answer_text": "adding browser profile testing and login-free workflow support on backend"}, {"memory_node_id": "Skyvern_AI__skyvern__release__v1_0_19", "answer_text": "adding gated admin impersonation controls for MCP API-key auth"}]}
{"prototype_id": "songquanpeng__one_api_release_window", "repo": "songquanpeng/one-api", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the songquanpeng/one-api releases, which release introduces support for the /v1/edits endpoint and model mapping?", "options": [{"option_id": "A", "text": "v0.4.7"}, {"option_id": "B", "text": "v0.4.8"}, {"option_id": "C", "text": "v0.4.9"}, {"option_id": "D", "text": "v0.5.0"}], "correct_option_id": "B", "expected_answer": "v0.4.8", "source_chunk_ids": ["songquanpeng__one_api__release__v0_4_8"], "answer_support": [{"memory_node_id": "songquanpeng__one_api__release__v0_4_8", "answer_text": "adds support for the /v1/edits endpoint, model mapping to redirect user request models"}]}
{"prototype_id": "songquanpeng__one_api_release_window", "repo": "songquanpeng/one-api", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the songquanpeng/one-api releases, how does the caching-related change in v0.4.6 differ from the caching-related change in v0.4.8?", "options": [{"option_id": "A", "text": "v0.4.6 introduces caching to reduce latency in multi-node deployments, while v0.4.8 fixes an over-quota usage problem when caching is enabled."}, {"option_id": "B", "text": "v0.4.6 removes caching entirely, while v0.4.8 adds caching for the first time."}, {"option_id": "C", "text": "Both releases only update UI styles without any caching changes."}, {"option_id": "D", "text": "v0.4.6 fixes a caching bug, while v0.4.8 introduces caching for database queries."}], "correct_option_id": "A", "expected_answer": "v0.4.6 introduces caching to reduce latency in multi-node deployments, while v0.4.8 fixes an over-quota usage problem when caching is enabled.", "source_chunk_ids": ["songquanpeng__one_api__release__v0_4_6", "songquanpeng__one_api__release__v0_4_8"], "answer_support": [{"memory_node_id": "songquanpeng__one_api__release__v0_4_6", "answer_text": "adds caching to avoid database requests before response return, reducing latency in multi-node deployments"}, {"memory_node_id": "songquanpeng__one_api__release__v0_4_8", "answer_text": "fixes an over-quota usage problem when caching is enabled"}]}
{"prototype_id": "songquanpeng__one_api_release_window", "repo": "songquanpeng/one-api", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the songquanpeng/one-api release window, order the following release-content states from earliest to latest: (1) a release that adds support for the /v1/edits endpoint and model mapping, (2) a release that introduces caching to reduce latency in multi-node deployments, (3) a release that adds support for newly released OpenAI models and allows channels to be assigned to multiple groups.", "options": [{"option_id": "A", "text": "3 -> 2 -> 1"}, {"option_id": "B", "text": "2 -> 3 -> 1"}, {"option_id": "C", "text": "1 -> 2 -> 3"}, {"option_id": "D", "text": "3 -> 1 -> 2"}], "correct_option_id": "A", "expected_answer": "3 -> 2 -> 1", "source_chunk_ids": ["songquanpeng__one_api__release__v0_4_3", "songquanpeng__one_api__release__v0_4_6", "songquanpeng__one_api__release__v0_4_8"], "answer_support": [{"memory_node_id": "songquanpeng__one_api__release__v0_4_3", "answer_text": "adds support for newly released OpenAI models, allows channels to be assigned to multiple groups"}, {"memory_node_id": "songquanpeng__one_api__release__v0_4_6", "answer_text": "adds caching to avoid database requests before response return, reducing latency in multi-node deployments"}, {"memory_node_id": "songquanpeng__one_api__release__v0_4_8", "answer_text": "adds support for the /v1/edits endpoint, model mapping"}]}
{"prototype_id": "spring_projects__spring_framework_release_window", "repo": "spring-projects/spring-framework", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the spring-projects/spring-framework releases, which release introduces minimal retry functionality as a core framework feature and adds support for application/*+x-protobuf media type?", "options": [{"option_id": "A", "text": "v7.0.0-M5"}, {"option_id": "B", "text": "v7.0.0-M6"}, {"option_id": "C", "text": "v7.0.0-M7"}, {"option_id": "D", "text": "v7.0.0-M8"}], "correct_option_id": "B", "expected_answer": "v7.0.0-M6", "source_chunk_ids": ["spring_projects__spring_framework__release__v7_0_0_m6"], "answer_support": [{"memory_node_id": "spring_projects__spring_framework__release__v7_0_0_m6", "answer_text": "introduces minimal retry functionality as a core framework feature ... adds support for application/*+x-protobuf media type"}]}
{"prototype_id": "spring_projects__spring_framework_release_window", "repo": "spring-projects/spring-framework", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the spring-projects/spring-framework releases, how does the retry-related change described in v7.0.0-M7 differ from the retry-related change described in v7.0.0-M9?", "options": [{"option_id": "A", "text": "v7.0.0-M7 removes maxDuration/maxElapsedTime support from RetryPolicy and redesigns RetryPolicy to directly incorporate BackOff, while v7.0.0-M9 introduces onRetryPolicyInterruption() callback in RetryListener and exposes retry attempts in RetryException."}, {"option_id": "B", "text": "v7.0.0-M7 introduces @Retryable annotation, while v7.0.0-M9 removes all retry support."}, {"option_id": "C", "text": "Both releases only update Micrometer dependency versions without retry changes."}, {"option_id": "D", "text": "v7.0.0-M7 deprecates RetryPolicy, while v7.0.0-M9 reintroduces maxDuration support."}], "correct_option_id": "A", "expected_answer": "v7.0.0-M7 removes maxDuration/maxElapsedTime support from RetryPolicy and redesigns RetryPolicy to directly incorporate BackOff, while v7.0.0-M9 introduces onRetryPolicyInterruption() callback in RetryListener and exposes retry attempts in RetryException.", "source_chunk_ids": ["spring_projects__spring_framework__release__v7_0_0_m7", "spring_projects__spring_framework__release__v7_0_0_m9"], "answer_support": [{"memory_node_id": "spring_projects__spring_framework__release__v7_0_0_m7", "answer_text": "removes maxDuration/maxElapsedTime support from RetryPolicy ... redesigns RetryPolicy to directly incorporate BackOff"}, {"memory_node_id": "spring_projects__spring_framework__release__v7_0_0_m9", "answer_text": "introduces onRetryPolicyInterruption() callback in RetryListener ... exposes retry attempts in RetryException"}]}
{"prototype_id": "spring_projects__spring_framework_release_window", "repo": "spring-projects/spring-framework", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the spring-projects/spring-framework release window, order the following release-content states from earliest to latest: (1) a release that deprecates JUnit 4 support in the Spring TestContext Framework and adds defaultApiVersion to RestClient and WebClient builders, (2) a release that introduces @ConcurrencyLimit annotation based on ConcurrencyThrottleInterceptor and deprecates DaoSupport classes, (3) a release that introduces @Proxyable annotation for bean-specific proxy type and adds RestTestClient, (4) a release that renames maxAttempts to maxRetries in @Retryable and RetryPolicy and adds AssertJ support for WebTestClient.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["spring_projects__spring_framework__release__v7_0_0_m5", "spring_projects__spring_framework__release__v7_0_0_m7", "spring_projects__spring_framework__release__v7_0_0_m8", "spring_projects__spring_framework__release__v7_0_0"], "answer_support": [{"memory_node_id": "spring_projects__spring_framework__release__v7_0_0_m5", "answer_text": "deprecates JUnit 4 support in the Spring TestContext Framework ... adds defaultApiVersion to RestClient and WebClient builders"}, {"memory_node_id": "spring_projects__spring_framework__release__v7_0_0_m7", "answer_text": "introduces @ConcurrencyLimit annotation based on ConcurrencyThrottleInterceptor ... deprecates DaoSupport classes"}, {"memory_node_id": "spring_projects__spring_framework__release__v7_0_0_m8", "answer_text": "introduces @Proxyable annotation for bean-specific proxy type ... adds RestTestClient"}, {"memory_node_id": "spring_projects__spring_framework__release__v7_0_0", "answer_text": "renames maxAttempts to maxRetries in @Retryable and RetryPolicy ... adds AssertJ support for WebTestClient"}]}
{"prototype_id": "starship__starship_release_window", "repo": "starship/starship", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the starship/starship releases, which release introduces a user-defined color palette along with left and right transience support for fish?", "options": [{"option_id": "A", "text": "v1.10.3"}, {"option_id": "B", "text": "v1.11.0"}, {"option_id": "C", "text": "v1.12.0"}, {"option_id": "D", "text": "v1.13.0"}], "correct_option_id": "B", "expected_answer": "v1.11.0", "source_chunk_ids": ["starship__starship__release__v1_11_0"], "answer_support": [{"memory_node_id": "starship__starship__release__v1_11_0", "answer_text": "new features include a user-defined color palette, left and right transience support for fish"}]}
{"prototype_id": "starship__starship_release_window", "repo": "starship/starship", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the starship/starship releases, how does the git_commit module change from v1.10.3 to v1.12.0?", "options": [{"option_id": "A", "text": "v1.10.3 uses exact match for tags by default, while v1.12.0 adds support for showing lightweight tags."}, {"option_id": "B", "text": "v1.10.3 removes tag support, while v1.12.0 adds exact match for tags."}, {"option_id": "C", "text": "Both releases only fix git_commit test failures without functional changes."}, {"option_id": "D", "text": "v1.10.3 adds lightweight tag support, while v1.12.0 disables multithreading in git_commit."}], "correct_option_id": "A", "expected_answer": "v1.10.3 uses exact match for tags by default, while v1.12.0 adds support for showing lightweight tags.", "source_chunk_ids": ["starship__starship__release__v1_10_3", "starship__starship__release__v1_12_0"], "answer_support": [{"memory_node_id": "starship__starship__release__v1_10_3", "answer_text": "the git_commit module is improved to use exact match for tags by default"}, {"memory_node_id": "starship__starship__release__v1_12_0", "answer_text": "lightweight tag support in git_commit"}]}
{"prototype_id": "starship__starship_release_window", "repo": "starship/starship", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the starship/starship release window, order the following release-content states from earliest to latest: (1) a release that adds a user-defined color palette and fish transience, (2) a release that introduces a Solidity module and AWS SSO automatic authentication refresh, (3) a release that adds a network namespace module and pixi support, (4) a release that adds a Maven module and a statusline subcommand for Claude Code integration.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["starship__starship__release__v1_11_0", "starship__starship__release__v1_15_0", "starship__starship__release__v1_23_0", "starship__starship__release__v1_25_0"], "answer_support": [{"memory_node_id": "starship__starship__release__v1_11_0", "answer_text": "new features include a user-defined color palette, left and right transience support for fish"}, {"memory_node_id": "starship__starship__release__v1_15_0", "answer_text": "a Solidity module is added, along with ... AWS SSO automatic authentication refresh"}, {"memory_node_id": "starship__starship__release__v1_23_0", "answer_text": "a network namespace module is added, pixi support is introduced"}, {"memory_node_id": "starship__starship__release__v1_25_0", "answer_text": "a Maven module is added, a statusline subcommand for Claude Code integration is introduced"}]}
{"prototype_id": "Stirling_Tools__Stirling_PDF_release_window", "repo": "Stirling-Tools/Stirling-PDF", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the Stirling-Tools/Stirling-PDF releases, which release introduces a Telegram bot integration and MSG support?", "options": [{"option_id": "A", "text": "v2.3.0"}, {"option_id": "B", "text": "v2.2.0"}, {"option_id": "C", "text": "v2.4.0"}, {"option_id": "D", "text": "v2.5.0"}], "correct_option_id": "A", "expected_answer": "v2.3.0", "source_chunk_ids": ["Stirling_Tools__Stirling_PDF__release__v2_3_0"], "answer_support": [{"memory_node_id": "Stirling_Tools__Stirling_PDF__release__v2_3_0", "answer_text": "New features include a Telegram bot (in Connections menu or settings.yml), PDF to EPUB and AZW3 conversion, and MSG support."}]}
{"prototype_id": "Stirling_Tools__Stirling_PDF_release_window", "repo": "Stirling-Tools/Stirling-PDF", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the Stirling-Tools/Stirling-PDF releases, how does the redaction feature in v2.5.0 differ from the redaction feature in v2.2.0?", "options": [{"option_id": "A", "text": "v2.2.0 introduces full manual redaction, while v2.5.0 adds colour selection and improved UI for manual redaction."}, {"option_id": "B", "text": "v2.2.0 adds redaction API, while v2.5.0 removes redaction entirely."}, {"option_id": "C", "text": "Both releases only fix redaction bugs without adding new features."}, {"option_id": "D", "text": "v2.2.0 adds automatic redaction, while v2.5.0 adds manual redaction."}], "correct_option_id": "A", "expected_answer": "v2.2.0 introduces full manual redaction, while v2.5.0 adds colour selection and improved UI for manual redaction.", "source_chunk_ids": ["Stirling_Tools__Stirling_PDF__release__v2_2_0", "Stirling_Tools__Stirling_PDF__release__v2_5_0"], "answer_support": [{"memory_node_id": "Stirling_Tools__Stirling_PDF__release__v2_2_0", "answer_text": "full manual redaction"}, {"memory_node_id": "Stirling_Tools__Stirling_PDF__release__v2_5_0", "answer_text": "huge manual redaction changes with colour selection and improved UI"}]}
{"prototype_id": "Stirling_Tools__Stirling_PDF_release_window", "repo": "Stirling-Tools/Stirling-PDF", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the Stirling-Tools/Stirling-PDF release window, order the following release-content states from earliest to latest: (1) a release that adds SVG to PDF conversion and tessdata language management for OCR, (2) a release that introduces a new UI layout with files on the left and tools on the right, (3) a release that adds a PDF read aloud feature and fixes Mac printing on desktop, (4) a release that adds server-side file sharing and group signing as alpha features.", "options": [{"option_id": "A", "text": "1 -> 3 -> 4 -> 2"}, {"option_id": "B", "text": "1 -> 4 -> 3 -> 2"}, {"option_id": "C", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "D", "text": "3 -> 1 -> 2 -> 4"}], "correct_option_id": "A", "expected_answer": "1 -> 3 -> 4 -> 2", "source_chunk_ids": ["Stirling_Tools__Stirling_PDF__release__v2_3_1", "Stirling_Tools__Stirling_PDF__release__v2_7_3", "Stirling_Tools__Stirling_PDF__release__v2_9_0", "Stirling_Tools__Stirling_PDF__release__v2_11_0"], "answer_support": [{"memory_node_id": "Stirling_Tools__Stirling_PDF__release__v2_3_1", "answer_text": "SVG to PDF conversion ... tessdata language management for OCR"}, {"memory_node_id": "Stirling_Tools__Stirling_PDF__release__v2_7_3", "answer_text": "PDF read aloud feature ... Mac printing finally working on desktop"}, {"memory_node_id": "Stirling_Tools__Stirling_PDF__release__v2_9_0", "answer_text": "server-side file sharing and group signing ... alpha features"}, {"memory_node_id": "Stirling_Tools__Stirling_PDF__release__v2_11_0", "answer_text": "new UI ... files on the left and tools on the right"}]}
{"prototype_id": "storybookjs__storybook_release_window", "repo": "storybookjs/storybook", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the storybookjs/storybook releases, which release introduces the Agentic Setup workflow?", "options": [{"option_id": "A", "text": "v10.4.0-alpha.12"}, {"option_id": "B", "text": "v10.4.0"}, {"option_id": "C", "text": "v10.4.0-alpha.17"}, {"option_id": "D", "text": "v10.4.0-alpha.18"}], "correct_option_id": "A", "expected_answer": "v10.4.0-alpha.12", "source_chunk_ids": ["storybookjs__storybook__release__v10_4_0_alpha_12"], "answer_support": [{"memory_node_id": "storybookjs__storybook__release__v10_4_0_alpha_12", "answer_text": "CLI introduces Agentic Setup workflow."}]}
{"prototype_id": "storybookjs__storybook_release_window", "repo": "storybookjs/storybook", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the storybookjs/storybook releases, how does the change detection feature differ between v10.4.0-alpha.5 and v10.4.0-alpha.8?", "options": [{"option_id": "A", "text": "v10.4.0-alpha.5 adds a changeDetection feature flag, while v10.4.0-alpha.8 implements Git change detection and adds dual-slot status icons for change detection and test results."}, {"option_id": "B", "text": "v10.4.0-alpha.5 implements Git change detection, while v10.4.0-alpha.8 adds a changeDetection feature flag."}, {"option_id": "C", "text": "Both releases only add URL-based tag filter state without change detection."}, {"option_id": "D", "text": "v10.4.0-alpha.5 removes change detection, while v10.4.0-alpha.8 reintroduces it."}], "correct_option_id": "A", "expected_answer": "v10.4.0-alpha.5 adds a changeDetection feature flag, while v10.4.0-alpha.8 implements Git change detection and adds dual-slot status icons for change detection and test results.", "source_chunk_ids": ["storybookjs__storybook__release__v10_4_0_alpha_5", "storybookjs__storybook__release__v10_4_0_alpha_8"], "answer_support": [{"memory_node_id": "storybookjs__storybook__release__v10_4_0_alpha_5", "answer_text": "Core: Add changeDetection feature flag"}, {"memory_node_id": "storybookjs__storybook__release__v10_4_0_alpha_8", "answer_text": "Core: Implement Git change detection ... Sidebar: Add dual-slot status icons for change detection and test results"}]}
{"prototype_id": "storybookjs__storybook_release_window", "repo": "storybookjs/storybook", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the storybookjs/storybook release window, order the following release-content states from earliest to latest: (1) a release that adds a changeDetection feature flag, (2) a release that implements Git change detection and adds dual-slot status icons for change detection and test results, (3) a release that introduces the Agentic Setup workflow.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["storybookjs__storybook__release__v10_4_0_alpha_5", "storybookjs__storybook__release__v10_4_0_alpha_8", "storybookjs__storybook__release__v10_4_0_alpha_12"], "answer_support": [{"memory_node_id": "storybookjs__storybook__release__v10_4_0_alpha_5", "answer_text": "Core: Add changeDetection feature flag"}, {"memory_node_id": "storybookjs__storybook__release__v10_4_0_alpha_8", "answer_text": "Core: Implement Git change detection ... Sidebar: Add dual-slot status icons for change detection and test results"}, {"memory_node_id": "storybookjs__storybook__release__v10_4_0_alpha_12", "answer_text": "CLI: Introduce Agentic Setup workflow"}]}
{"prototype_id": "strapi__strapi_release_window", "repo": "strapi/strapi", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the strapi/strapi releases, which release adds a clear button to boolean toggle and refresh/logout actions to default permissions?", "options": [{"option_id": "A", "text": "v5.31.3"}, {"option_id": "B", "text": "v5.32.0"}, {"option_id": "C", "text": "v5.33.0"}, {"option_id": "D", "text": "v5.34.0"}], "correct_option_id": "B", "expected_answer": "v5.32.0", "source_chunk_ids": ["strapi__strapi__release__v5_32_0"], "answer_support": [{"memory_node_id": "strapi__strapi__release__v5_32_0", "answer_text": "new features add a clear button to boolean toggle and refresh/logout actions to default permissions"}]}
{"prototype_id": "streamlit__streamlit_release_window", "repo": "streamlit/streamlit", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the streamlit/streamlit releases, which release introduces the `st.badge` element and the `streamlit init` command?", "options": [{"option_id": "A", "text": "1.42.0"}, {"option_id": "B", "text": "1.43.0"}, {"option_id": "C", "text": "1.44.0"}, {"option_id": "D", "text": "1.45.0"}], "correct_option_id": "C", "expected_answer": "1.44.0", "source_chunk_ids": ["streamlit__streamlit__release__1_44_0"], "answer_support": [{"memory_node_id": "streamlit__streamlit__release__1_44_0", "answer_text": "Add st.badge and Markdown badges ... Add streamlit init command"}]}
{"prototype_id": "streamlit__streamlit_release_window", "repo": "streamlit/streamlit", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the streamlit/streamlit releases, how does the theming enhancement in 1.43.0 differ from the theming enhancement in 1.44.0?", "options": [{"option_id": "A", "text": "1.43.0 introduces theme.roundness, theme.borderColor, theme.linkColor, custom fonts, and theme.baseFontSize, while 1.44.0 adds showSidebarSeparator, headingFont, theme.sidebar, and theme.codeBackgroundColor."}, {"option_id": "B", "text": "1.43.0 adds theme.codeBackgroundColor, while 1.44.0 adds theme.roundness."}, {"option_id": "C", "text": "Both releases only add theme.baseFontSize."}, {"option_id": "D", "text": "1.43.0 adds headingFont, while 1.44.0 adds theme.linkColor."}], "correct_option_id": "A", "expected_answer": "1.43.0 introduces theme.roundness, theme.borderColor, theme.linkColor, custom fonts, and theme.baseFontSize, while 1.44.0 adds showSidebarSeparator, headingFont, theme.sidebar, and theme.codeBackgroundColor.", "source_chunk_ids": ["streamlit__streamlit__release__1_43_0", "streamlit__streamlit__release__1_44_0"], "answer_support": [{"memory_node_id": "streamlit__streamlit__release__1_43_0", "answer_text": "theme.roundness theming option, theme.borderColor and theme.showBorderAroundInputs config options, theme.linkColor theming config option, theming options to configure custom fonts, theme.baseFontSize theming config option"}, {"memory_node_id": "streamlit__streamlit__release__1_44_0", "answer_text": "adding theming config showSidebarSeparator, adding custom theming headingFont option, supporting theme.sidebar custom theme, and adding theme.codeBackgroundColor theming config option"}]}
{"prototype_id": "streamlit__streamlit_release_window", "repo": "streamlit/streamlit", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the streamlit/streamlit release window, order the following release-content states from earliest to latest: (1) a release that adds `st.badge` and `streamlit init`, (2) a release that adds `st.chat_input` with file uploader and `theme.roundness`, (3) a release that adds `st.pagination` and `st.skills` CLI, (4) a release that adds `st.menu_button` and `st.iframe`.", "options": [{"option_id": "A", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "B", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "C", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "D", "text": "1 -> 2 -> 4 -> 3"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 4 -> 3", "source_chunk_ids": ["streamlit__streamlit__release__1_43_0", "streamlit__streamlit__release__1_44_0", "streamlit__streamlit__release__1_56_0", "streamlit__streamlit__release__1_58_0"], "answer_support": [{"memory_node_id": "streamlit__streamlit__release__1_43_0", "answer_text": "st.chat_input with file uploader ... theme.roundness"}, {"memory_node_id": "streamlit__streamlit__release__1_44_0", "answer_text": "Add st.badge ... Add streamlit init command"}, {"memory_node_id": "streamlit__streamlit__release__1_56_0", "answer_text": "Add st.menu_button widget ... Add st.iframe command"}, {"memory_node_id": "streamlit__streamlit__release__1_58_0", "answer_text": "Add st.pagination widget ... Add streamlit skills CLI command"}]}
{"prototype_id": "sveltejs__svelte_release_window", "repo": "sveltejs/svelte", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the sveltejs/svelte releases, which release introduces support for TrustedHTML in {@html} expressions?", "options": [{"option_id": "A", "text": "svelte@5.53.0"}, {"option_id": "B", "text": "svelte@5.52.0"}, {"option_id": "C", "text": "svelte@5.54.0"}, {"option_id": "D", "text": "svelte@5.55.0"}], "correct_option_id": "B", "expected_answer": "svelte@5.52.0", "source_chunk_ids": ["sveltejs__svelte__release__svelte_5_52_0"], "answer_support": [{"memory_node_id": "sveltejs__svelte__release__svelte_5_52_0", "answer_text": "adds support for TrustedHTML in {@html} expressions"}]}
{"prototype_id": "sveltejs__svelte_release_window", "repo": "sveltejs/svelte", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the sveltejs/svelte releases, how does the feature addition in svelte@5.53.0 differ from the feature addition in svelte@5.56.0?", "options": [{"option_id": "A", "text": "5.53.0 allows comments in tags and error boundaries on the server, while 5.56.0 allows declarations in the template."}, {"option_id": "B", "text": "5.53.0 adds TrustedHTML support, while 5.56.0 exports motion options."}, {"option_id": "C", "text": "Both releases only fix hydration mismatches."}, {"option_id": "D", "text": "5.53.0 allows functions for compiler options, while 5.56.0 allows comments in tags."}], "correct_option_id": "A", "expected_answer": "5.53.0 allows comments in tags and error boundaries on the server, while 5.56.0 allows declarations in the template.", "source_chunk_ids": ["sveltejs__svelte__release__svelte_5_53_0", "sveltejs__svelte__release__svelte_5_56_0"], "answer_support": [{"memory_node_id": "sveltejs__svelte__release__svelte_5_53_0", "answer_text": "allow comments in tags and allow error boundaries to work on the server"}, {"memory_node_id": "sveltejs__svelte__release__svelte_5_56_0", "answer_text": "allows declarations in the template"}]}
{"prototype_id": "sveltejs__svelte_release_window", "repo": "sveltejs/svelte", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the sveltejs/svelte release window, order the following release-content states from earliest to latest: (1) a release that adds support for TrustedHTML in {@html} expressions, (2) a release that allows declarations in the template, (3) a release that exports TweenOptions, SpringOptions, SpringUpdateOptions and Updater from svelte/motion.", "options": [{"option_id": "A", "text": "1 -> 3 -> 2"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "3 -> 2 -> 1"}, {"option_id": "D", "text": "1 -> 2 -> 3"}], "correct_option_id": "A", "expected_answer": "1 -> 3 -> 2", "source_chunk_ids": ["sveltejs__svelte__release__svelte_5_52_0", "sveltejs__svelte__release__svelte_5_55_0", "sveltejs__svelte__release__svelte_5_56_0"], "answer_support": [{"memory_node_id": "sveltejs__svelte__release__svelte_5_52_0", "answer_text": "adds support for TrustedHTML in {@html} expressions"}, {"memory_node_id": "sveltejs__svelte__release__svelte_5_55_0", "answer_text": "exports TweenOptions, SpringOptions, SpringUpdateOptions and Updater from svelte/motion"}, {"memory_node_id": "sveltejs__svelte__release__svelte_5_56_0", "answer_text": "allows declarations in the template"}]}
{"prototype_id": "sxyazi__yazi_release_window", "repo": "sxyazi/yazi", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the sxyazi/yazi releases, which release introduces the spotter concept for file metadata popups and support for transparent image previews across all backends?", "options": [{"option_id": "A", "text": "v0.3.0"}, {"option_id": "B", "text": "v0.4.0"}, {"option_id": "C", "text": "v0.4.1"}, {"option_id": "D", "text": "v25.2.7"}], "correct_option_id": "B", "expected_answer": "v0.4.0", "source_chunk_ids": ["sxyazi__yazi__release__v0_4_0"], "answer_support": [{"memory_node_id": "sxyazi__yazi__release__v0_4_0", "answer_text": "introduces the spotter concept for file metadata popups, support for transparent image previews across all backends"}]}
{"prototype_id": "sxyazi__yazi_release_window", "repo": "sxyazi/yazi", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the sxyazi/yazi releases, how does the image preview enhancement in v0.3.3 differ from the image preview enhancement in v25.5.28?", "options": [{"option_id": "A", "text": "v0.3.3 adds Windows Terminal image preview support via Sixel, while v25.5.28 makes Sixel image preview 9x faster by replacing the quantization algorithm."}, {"option_id": "B", "text": "v0.3.3 introduces transparent image previews, while v25.5.28 adds support for previewing images over SSH."}, {"option_id": "C", "text": "Both releases add the same image preview feature for Kitty graphics protocol."}, {"option_id": "D", "text": "v0.3.3 removes image preview support, while v25.5.28 restores it."}], "correct_option_id": "A", "expected_answer": "v0.3.3 adds Windows Terminal image preview support via Sixel, while v25.5.28 makes Sixel image preview 9x faster by replacing the quantization algorithm.", "source_chunk_ids": ["sxyazi__yazi__release__v0_3_3", "sxyazi__yazi__release__v25_5_28"], "answer_support": [{"memory_node_id": "sxyazi__yazi__release__v0_3_3", "answer_text": "adds Windows Terminal image preview support via Sixel"}, {"memory_node_id": "sxyazi__yazi__release__v25_5_28", "answer_text": "Sixel image preview is made 9x faster by replacing the quantization algorithm"}]}
{"prototype_id": "sxyazi__yazi_release_window", "repo": "sxyazi/yazi", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the sxyazi/yazi release window, order the following release-content states from earliest to latest: (1) a release that introduces a Data Distribution Service (DDS) for communication between multiple Yazi instances, (2) a release that adds mouse support with click, scroll, touch, move, and drag APIs, (3) a release that introduces the spotter concept and transparent image previews, (4) a release that redesigns tabs into an independent tab bar component.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["sxyazi__yazi__release__v0_2_5", "sxyazi__yazi__release__v0_3_0", "sxyazi__yazi__release__v0_4_0", "sxyazi__yazi__release__v25_5_28"], "answer_support": [{"memory_node_id": "sxyazi__yazi__release__v0_2_5", "answer_text": "introduces a Data Distribution Service (DDS) for communication and state synchronization between multiple Yazi instances"}, {"memory_node_id": "sxyazi__yazi__release__v0_3_0", "answer_text": "adds mouse support with new click, scroll, touch, move, and drag APIs for components"}, {"memory_node_id": "sxyazi__yazi__release__v0_4_0", "answer_text": "introduces the spotter concept for file metadata popups, support for transparent image previews"}, {"memory_node_id": "sxyazi__yazi__release__v25_5_28", "answer_text": "Tabs are redesigned into an independent tab bar component"}]}
{"prototype_id": "syncthing__syncthing_release_window", "repo": "syncthing/syncthing", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the syncthing/syncthing releases, how does the database maintenance change described in v2.0.5 differ from the change described in v2.0.14-rc.1?", "options": [{"option_id": "A", "text": "v2.0.5 vacuums the database only when a migration script was run, while v2.0.14-rc.1 allows periodic database maintenance to be disabled entirely."}, {"option_id": "B", "text": "v2.0.5 removes temp_store = MEMORY pragmas, while v2.0.14-rc.1 adds build attestation."}, {"option_id": "C", "text": "Both releases only update dependencies without database changes."}, {"option_id": "D", "text": "v2.0.5 switches to SQLite, while v2.0.14-rc.1 reverts to LevelDB."}], "correct_option_id": "A", "expected_answer": "v2.0.5 vacuums the database only when a migration script was run, while v2.0.14-rc.1 allows periodic database maintenance to be disabled entirely.", "source_chunk_ids": ["syncthing__syncthing__release__v2_0_5", "syncthing__syncthing__release__v2_0_14_rc_1"], "answer_support": [{"memory_node_id": "syncthing__syncthing__release__v2_0_5", "answer_text": "fix(db): only vacuum database on startup when a migration script was actually run"}, {"memory_node_id": "syncthing__syncthing__release__v2_0_14_rc_1", "answer_text": "chore(sqlite): allow periodic database maintenance to be disabled"}]}
{"prototype_id": "TabbyML__tabby_release_window", "repo": "TabbyML/tabby", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the TabbyML/tabby releases, which release introduces the 'Convert to Page' feature that transforms Answer Engine messages into persistent, shareable Pages?", "options": [{"option_id": "A", "text": "v0.27.0"}, {"option_id": "B", "text": "v0.28.0"}, {"option_id": "C", "text": "v0.29.0"}, {"option_id": "D", "text": "v0.30.0"}], "correct_option_id": "B", "expected_answer": "v0.28.0", "source_chunk_ids": ["TabbyML__tabby__release__v0_28_0"], "answer_support": [{"memory_node_id": "TabbyML__tabby__release__v0_28_0", "answer_text": "the 'Convert to Page' feature is introduced, transforming Answer Engine messages into persistent, shareable Pages"}]}
{"prototype_id": "TabbyML__tabby_release_window", "repo": "TabbyML/tabby", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the TabbyML/tabby releases, how does the Answer Engine context selection mechanism change from v0.17.0 to v0.23.0?", "options": [{"option_id": "A", "text": "v0.17.0 uses '@' for Developer Docs/Web search and '#' for Repository Context, while v0.23.0 adds repository selection and removes '#' mentions."}, {"option_id": "B", "text": "v0.17.0 removes all context selection, while v0.23.0 introduces '@' mentions."}, {"option_id": "C", "text": "Both releases use the same context selection mechanism with no changes."}, {"option_id": "D", "text": "v0.17.0 uses '#' for Developer Docs and '@' for Repository Context, while v0.23.0 removes all mentions."}], "correct_option_id": "A", "expected_answer": "v0.17.0 uses '@' for Developer Docs/Web search and '#' for Repository Context, while v0.23.0 adds repository selection and removes '#' mentions.", "source_chunk_ids": ["TabbyML__tabby__release__v0_17_0", "TabbyML__tabby__release__v0_23_0"], "answer_support": [{"memory_node_id": "TabbyML__tabby__release__v0_17_0", "answer_text": "Developer Docs/Web search is triggered by '@', and Repository Context is selected using '#'"}, {"memory_node_id": "TabbyML__tabby__release__v0_23_0", "answer_text": "Add repository selection and remove '#' mentions in the Answer Engine"}]}
{"prototype_id": "TabbyML__tabby_release_window", "repo": "TabbyML/tabby", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the TabbyML/tabby release window, order the following release-content states from earliest to latest: (1) a release that adds LDAP Authentication Integration, (2) a release that introduces User Groups Access Control, (3) a release that adds custom branding with name and logo for Enterprise License, (4) a release that adds generic OAuth support.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "B", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "C", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "D", "text": "1 -> 2 -> 3 -> 4"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3 -> 4", "source_chunk_ids": ["TabbyML__tabby__release__v0_18_0", "TabbyML__tabby__release__v0_24_0", "TabbyML__tabby__release__v0_31_0", "TabbyML__tabby__release__v0_32_0"], "answer_support": [{"memory_node_id": "TabbyML__tabby__release__v0_18_0", "answer_text": "User Groups Access Control is introduced"}, {"memory_node_id": "TabbyML__tabby__release__v0_24_0", "answer_text": "LDAP Authentication Integration is implemented"}, {"memory_node_id": "TabbyML__tabby__release__v0_31_0", "answer_text": "custom branding with name and logo is supported, available exclusively with an Enterprise License"}, {"memory_node_id": "TabbyML__tabby__release__v0_32_0", "answer_text": "generic OAuth support is introduced"}]}
{"prototype_id": "tailwindlabs__tailwindcss_release_window", "repo": "tailwindlabs/tailwindcss", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the tailwindlabs/tailwindcss releases, which release adds support for literal values in --value('…') and --modifier('…')?", "options": [{"option_id": "A", "text": "v4.0.15"}, {"option_id": "B", "text": "v4.0.16"}, {"option_id": "C", "text": "v4.0.17"}, {"option_id": "D", "text": "v4.1.0"}], "correct_option_id": "B", "expected_answer": "v4.0.16", "source_chunk_ids": ["tailwindlabs__tailwindcss__release__v4_0_16"], "answer_support": [{"memory_node_id": "tailwindlabs__tailwindcss__release__v4_0_16", "answer_text": "Add support for literal values in --value('…') and --modifier('…')"}]}
{"prototype_id": "tailwindlabs__tailwindcss_release_window", "repo": "tailwindlabs/tailwindcss", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the tailwindlabs/tailwindcss releases, how does the fix for class extraction followed by '(' differ between v4.0.15 and v4.0.16?", "options": [{"option_id": "A", "text": "v4.0.15 fixes it in Slim, while v4.0.16 fixes it in Pug."}, {"option_id": "B", "text": "v4.0.15 fixes it in Pug, while v4.0.16 fixes it in Slim."}, {"option_id": "C", "text": "Both releases fix it in the same template language."}, {"option_id": "D", "text": "v4.0.15 fixes it in Vue, while v4.0.16 fixes it in Ruby."}], "correct_option_id": "A", "expected_answer": "v4.0.15 fixes it in Slim, while v4.0.16 fixes it in Pug.", "source_chunk_ids": ["tailwindlabs__tailwindcss__release__v4_0_15", "tailwindlabs__tailwindcss__release__v4_0_16"], "answer_support": [{"memory_node_id": "tailwindlabs__tailwindcss__release__v4_0_15", "answer_text": "Fix class extraction followed by '(' in Slim"}, {"memory_node_id": "tailwindlabs__tailwindcss__release__v4_0_16", "answer_text": "Fix class extraction followed by '(' in Pug"}]}
{"prototype_id": "tailwindlabs__tailwindcss_release_window", "repo": "tailwindlabs/tailwindcss", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the tailwindlabs/tailwindcss release window, order the following release-content states from earliest to latest: (1) a release that adds support for Vite 7, (2) a release that adds support for Vite 8, (3) a release that adds the @tailwindcss/webpack package.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "1 -> 3 -> 2"}, {"option_id": "C", "text": "2 -> 1 -> 3"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "B", "expected_answer": "1 -> 3 -> 2", "source_chunk_ids": ["tailwindlabs__tailwindcss__release__v4_1_11", "tailwindlabs__tailwindcss__release__v4_2_0", "tailwindlabs__tailwindcss__release__v4_2_2"], "answer_support": [{"memory_node_id": "tailwindlabs__tailwindcss__release__v4_1_11", "answer_text": "Add support for Vite 7 to @tailwindcss/vite"}, {"memory_node_id": "tailwindlabs__tailwindcss__release__v4_2_0", "answer_text": "Add @tailwindcss/webpack package"}, {"memory_node_id": "tailwindlabs__tailwindcss__release__v4_2_2", "answer_text": "Support Vite 8 in @tailwindcss/vite"}]}
{"prototype_id": "taosdata__TDengine_release_window", "repo": "taosdata/TDengine", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the taosdata/TDengine releases, which release introduces the Count Window for stream processing and a new license mechanism?", "options": [{"option_id": "A", "text": "3.2.2.0"}, {"option_id": "B", "text": "3.2.3.0"}, {"option_id": "C", "text": "3.3.0.0"}, {"option_id": "D", "text": "3.3.2.0"}], "correct_option_id": "B", "expected_answer": "3.2.3.0", "source_chunk_ids": ["taosdata__TDengine__release__ver_3_2_3_0"], "answer_support": [{"memory_node_id": "taosdata__TDengine__release__ver_3_2_3_0", "answer_text": "Count Window for stream processing ... New License Mechanism"}]}
{"prototype_id": "taosdata__TDengine_release_window", "repo": "taosdata/TDengine", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the taosdata/TDengine releases, how does the stream processing capability described in release 3.2.2.0 differ from the stream processing capability described in release 3.3.7.0?", "options": [{"option_id": "A", "text": "3.2.2.0 introduces Event Window for stream processing, while 3.3.7.0 delivers a new version of stream computing with BLOB data type and data subscription MQTT protocol."}, {"option_id": "B", "text": "3.2.2.0 removes stream processing entirely, while 3.3.7.0 adds Count Window."}, {"option_id": "C", "text": "Both releases only provide bug fixes for stream processing without new features."}, {"option_id": "D", "text": "3.2.2.0 introduces Count Window, while 3.3.7.0 introduces Event Window."}], "correct_option_id": "A", "expected_answer": "3.2.2.0 introduces Event Window for stream processing, while 3.3.7.0 delivers a new version of stream computing with BLOB data type and data subscription MQTT protocol.", "source_chunk_ids": ["taosdata__TDengine__release__ver_3_2_2_0", "taosdata__TDengine__release__ver_3_3_7_0"], "answer_support": [{"memory_node_id": "taosdata__TDengine__release__ver_3_2_2_0", "answer_text": "Stream processing supports Event Window"}, {"memory_node_id": "taosdata__TDengine__release__ver_3_3_7_0", "answer_text": "new version of stream computing ... supports BLOB data type ... data subscription supports the MQTT protocol"}]}
{"prototype_id": "taosdata__TDengine_release_window", "repo": "taosdata/TDengine", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the taosdata/TDengine release window, order the following release-content states from earliest to latest: (1) a release that introduces View and optimized query for BI tool integration, (2) a release that introduces full functional Join including ASOF JOIN and WINDOW JOIN, (3) a release that introduces Decimal data type and virtual tables, (4) a release that introduces MCP server for TDengine TSDB and external window query.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "3 -> 1 -> 2 -> 4"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["taosdata__TDengine__release__ver_3_2_1_0", "taosdata__TDengine__release__ver_3_3_0_0", "taosdata__TDengine__release__ver_3_3_6_0", "taosdata__TDengine__release__ver_3_4_1_0"], "answer_support": [{"memory_node_id": "taosdata__TDengine__release__ver_3_2_1_0", "answer_text": "View ... Optimized query for BI tool integration"}, {"memory_node_id": "taosdata__TDengine__release__ver_3_3_0_0", "answer_text": "Full functional Join: including LEFT JOIN, RIGHT JOIN, FULL JOIN, SEMI JOIN, ANTI-SEMI JOIN ... ASOF JOIN and WINDOW JOIN"}, {"memory_node_id": "taosdata__TDengine__release__ver_3_3_6_0", "answer_text": "supports Decimal data type ... supports virtual table"}, {"memory_node_id": "taosdata__TDengine__release__ver_3_4_1_0", "answer_text": "mcp server for TDengine TSDB ... support external window query"}]}
{"prototype_id": "tauri_apps__tauri_release_window", "repo": "tauri-apps/tauri", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the tauri-apps/tauri releases, which release adds uninstaller icon and header image support for NSIS installer, and also adds support for minimumWebview2Version option for MSI installer?", "options": [{"option_id": "A", "text": "@tauri-apps/cli v2.11.0"}, {"option_id": "B", "text": "tauri v2.11.0"}, {"option_id": "C", "text": "tauri-cli v2.11.0"}, {"option_id": "D", "text": "@tauri-apps/cli v2.11.1"}], "correct_option_id": "A", "expected_answer": "@tauri-apps/cli v2.11.0", "source_chunk_ids": ["tauri_apps__tauri__release__tauri_apps_cli_v2_11_0"], "answer_support": [{"memory_node_id": "tauri_apps__tauri__release__tauri_apps_cli_v2_11_0", "answer_text": "new features include uninstaller icon and header image support for NSIS installer, and support for minimumWebview2Version option for MSI installer"}]}
{"prototype_id": "tauri_apps__tauri_release_window", "repo": "tauri-apps/tauri", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the tauri-apps/tauri releases, how does the content of @tauri-apps/cli v2.11.0 differ from @tauri-apps/cli v2.11.1?", "options": [{"option_id": "A", "text": "v2.11.0 includes new features like NSIS uninstaller icon support and MSI minimumWebview2Version option, while v2.11.1 only upgrades dependencies to tauri-cli@2.11.1."}, {"option_id": "B", "text": "v2.11.0 only upgrades dependencies, while v2.11.1 adds NSIS uninstaller icon support."}, {"option_id": "C", "text": "Both releases have identical content, only the version number changed."}, {"option_id": "D", "text": "v2.11.0 fixes iOS build failures, while v2.11.1 adds Vietnamese translations."}], "correct_option_id": "A", "expected_answer": "v2.11.0 includes new features like NSIS uninstaller icon support and MSI minimumWebview2Version option, while v2.11.1 only upgrades dependencies to tauri-cli@2.11.1.", "source_chunk_ids": ["tauri_apps__tauri__release__tauri_apps_cli_v2_11_0", "tauri_apps__tauri__release__tauri_apps_cli_v2_11_1"], "answer_support": [{"memory_node_id": "tauri_apps__tauri__release__tauri_apps_cli_v2_11_0", "answer_text": "new features include uninstaller icon and header image support for NSIS installer, and support for minimumWebview2Version option for MSI installer"}, {"memory_node_id": "tauri_apps__tauri__release__tauri_apps_cli_v2_11_1", "answer_text": "only mentions that dependencies were upgraded to tauri-cli@2.11.1"}]}
{"prototype_id": "tauri_apps__tauri_release_window", "repo": "tauri-apps/tauri", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the tauri-apps/tauri release window, order the following release-content states from earliest to latest: (1) a release that adds uninstaller icon and header image support for NSIS installer, (2) a release that only upgrades dependencies to tauri-cli@2.11.1, (3) a release that only upgrades dependencies to tauri-cli@2.11.2.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["tauri_apps__tauri__release__tauri_apps_cli_v2_11_0", "tauri_apps__tauri__release__tauri_apps_cli_v2_11_1", "tauri_apps__tauri__release__tauri_apps_cli_v2_11_2"], "answer_support": [{"memory_node_id": "tauri_apps__tauri__release__tauri_apps_cli_v2_11_0", "answer_text": "new features include uninstaller icon and header image support for NSIS installer"}, {"memory_node_id": "tauri_apps__tauri__release__tauri_apps_cli_v2_11_1", "answer_text": "only mentions that dependencies were upgraded to tauri-cli@2.11.1"}, {"memory_node_id": "tauri_apps__tauri__release__tauri_apps_cli_v2_11_2", "answer_text": "only mentions that dependencies were upgraded to tauri-cli@2.11.2"}]}
{"prototype_id": "TeamNewPipe__NewPipe_release_window", "repo": "TeamNewPipe/NewPipe", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the TeamNewPipe/NewPipe releases, which release introduces a new card view mode with full width thumbnails and adds long press action on hashtags and web links in descriptions?", "options": [{"option_id": "A", "text": "v0.24.0"}, {"option_id": "B", "text": "v0.25.0"}, {"option_id": "C", "text": "v0.26.0"}, {"option_id": "D", "text": "v0.27.0"}], "correct_option_id": "B", "expected_answer": "v0.25.0", "source_chunk_ids": ["TeamNewPipe__NewPipe__release__v0_25_0"], "answer_support": [{"memory_node_id": "TeamNewPipe__NewPipe__release__v0_25_0", "answer_text": "new card view mode with full width thumbnails and long press action on hashtags and web links in descriptions"}]}
{"prototype_id": "TeamNewPipe__NewPipe_release_window", "repo": "TeamNewPipe/NewPipe", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the TeamNewPipe/NewPipe releases, how does the YouTube-related fix in v0.27.5 differ from the YouTube-related fix in v0.27.6?", "options": [{"option_id": "A", "text": "v0.27.5 fixes the 'IOS player response is not valid' error preventing video details from loading, while v0.27.6 additionally fixes HTTP 403 errors during playback and missing 720p streams."}, {"option_id": "B", "text": "v0.27.5 adds support for poTokens, while v0.27.6 removes poToken support."}, {"option_id": "C", "text": "Both releases only update the user agent without fixing any YouTube issues."}, {"option_id": "D", "text": "v0.27.5 fixes age-restricted videos, while v0.27.6 fixes comment extraction."}], "correct_option_id": "A", "expected_answer": "v0.27.5 fixes the 'IOS player response is not valid' error preventing video details from loading, while v0.27.6 additionally fixes HTTP 403 errors during playback and missing 720p streams.", "source_chunk_ids": ["TeamNewPipe__NewPipe__release__v0_27_5", "TeamNewPipe__NewPipe__release__v0_27_6"], "answer_support": [{"memory_node_id": "TeamNewPipe__NewPipe__release__v0_27_5", "answer_text": "fixes YouTube videos not loading due to extractor error 'IOS player response is not valid'"}, {"memory_node_id": "TeamNewPipe__NewPipe__release__v0_27_6", "answer_text": "fixes various YouTube issues: 'IOS player response is not valid' which prevented any video from loading, HTTP 403 errors while playing videos (usually at minute 1:09), missing video streams at 720p 24-30FPS"}]}
{"prototype_id": "TeamNewPipe__NewPipe_release_window", "repo": "TeamNewPipe/NewPipe", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the TeamNewPipe/NewPipe release window, order the following release-content states from earliest to latest: (1) a release that adds support for comment replies and an option to reset settings, (2) a release that adds a monochrome icon and long-click on stream segment to share timestamped URLs, (3) a release that adds support for Android Auto and feed groups as main screen tabs.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3"}, {"option_id": "B", "text": "1 -> 2 -> 3"}, {"option_id": "C", "text": "3 -> 1 -> 2"}, {"option_id": "D", "text": "2 -> 3 -> 1"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3", "source_chunk_ids": ["TeamNewPipe__NewPipe__release__v0_24_1", "TeamNewPipe__NewPipe__release__v0_27_0", "TeamNewPipe__NewPipe__release__v0_28_0"], "answer_support": [{"memory_node_id": "TeamNewPipe__NewPipe__release__v0_24_1", "answer_text": "add a monochrome icon and long-click on stream segment to share timestamped URLs"}, {"memory_node_id": "TeamNewPipe__NewPipe__release__v0_27_0", "answer_text": "add support for comment replies and add option to reset settings"}, {"memory_node_id": "TeamNewPipe__NewPipe__release__v0_28_0", "answer_text": "add support for Android Auto and add feed groups as main screen tabs"}]}
{"prototype_id": "telegramdesktop__tdesktop_release_window", "repo": "telegramdesktop/tdesktop", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the telegramdesktop/tdesktop releases, which release introduces AI Summaries for posts in channels?", "options": [{"option_id": "A", "text": "v6.3.10"}, {"option_id": "B", "text": "v6.4.0"}, {"option_id": "C", "text": "v6.5.0"}, {"option_id": "D", "text": "v6.6.0"}], "correct_option_id": "B", "expected_answer": "v6.4.0", "source_chunk_ids": ["telegramdesktop__tdesktop__release__v6_4_0"], "answer_support": [{"memory_node_id": "telegramdesktop__tdesktop__release__v6_4_0", "answer_text": "introduce AI Summaries for posts in channels"}]}
{"prototype_id": "telegramdesktop__tdesktop_release_window", "repo": "telegramdesktop/tdesktop", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the telegramdesktop/tdesktop releases, how does the drawing tools feature described in v6.6.3 differ from the drawing tools feature described in v6.7.0?", "options": [{"option_id": "A", "text": "v6.6.3 introduces drawing tools in the image editor, while v6.7.0 adds an AI Text Editor for messages."}, {"option_id": "B", "text": "v6.6.3 introduces drawing tools in the image editor, while v6.7.0 also includes drawing tools but adds Enhanced Polls."}, {"option_id": "C", "text": "v6.6.3 introduces drawing tools in the image editor, while v6.7.0 removes drawing tools."}, {"option_id": "D", "text": "v6.6.3 introduces drawing tools in the image editor, while v6.7.0 introduces drawing tools in the media viewer."}], "correct_option_id": "B", "expected_answer": "v6.6.3 introduces drawing tools in the image editor, while v6.7.0 also includes drawing tools but adds Enhanced Polls.", "source_chunk_ids": ["telegramdesktop__tdesktop__release__v6_6_3", "telegramdesktop__tdesktop__release__v6_7_0"], "answer_support": [{"memory_node_id": "telegramdesktop__tdesktop__release__v6_6_3", "answer_text": "introduce drawing tools in image editor (brush, marker, eraser, arrow)"}, {"memory_node_id": "telegramdesktop__tdesktop__release__v6_7_0", "answer_text": "introduce ... drawing tools in the image editor (brush, marker, eraser, arrow) ... Enhanced Polls with media, locations and suggested options"}]}
{"prototype_id": "tensorflow__tensorflow_release_window", "repo": "tensorflow/tensorflow", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the tensorflow/tensorflow releases, which release introduces the optional pip installation method for Linux that installs necessary Nvidia CUDA libraries through pip using 'pip install tensorflow[and-cuda]'?", "options": [{"option_id": "A", "text": "v2.14.0-rc0"}, {"option_id": "B", "text": "v2.14.0-rc1"}, {"option_id": "C", "text": "v2.14.0"}, {"option_id": "D", "text": "v2.15.0"}], "correct_option_id": "B", "expected_answer": "v2.14.0-rc1", "source_chunk_ids": ["tensorflow__tensorflow__release__v2_14_0_rc1"], "answer_support": [{"memory_node_id": "tensorflow__tensorflow__release__v2_14_0_rc1", "answer_text": "A new major feature is the optional pip installation method for Linux that installs necessary Nvidia CUDA libraries through pip using 'pip install tensorflow[and-cuda]'."}]}
{"prototype_id": "tensorflow__tensorflow_release_window", "repo": "tensorflow/tensorflow", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the tensorflow/tensorflow releases, how does the breaking change related to Python version support in v2.14.0 differ from the breaking change in v2.21.0?", "options": [{"option_id": "A", "text": "v2.14.0 removes Python 3.8 support, while v2.21.0 removes Python 3.9 support."}, {"option_id": "B", "text": "v2.14.0 removes Python 3.9 support, while v2.21.0 removes Python 3.8 support."}, {"option_id": "C", "text": "Both releases remove Python 3.8 support."}, {"option_id": "D", "text": "v2.14.0 adds Python 3.12 support, while v2.21.0 removes Python 3.9 support."}], "correct_option_id": "A", "expected_answer": "v2.14.0 removes Python 3.8 support, while v2.21.0 removes Python 3.9 support.", "source_chunk_ids": ["tensorflow__tensorflow__release__v2_14_0", "tensorflow__tensorflow__release__v2_21_0"], "answer_support": [{"memory_node_id": "tensorflow__tensorflow__release__v2_14_0", "answer_text": "removal of Python 3.8 support"}, {"memory_node_id": "tensorflow__tensorflow__release__v2_21_0", "answer_text": "removal of Python 3.9 support"}]}
{"prototype_id": "termux__termux_app_release_window", "repo": "termux/termux-app", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the termux/termux-app releases, which release adds a context menu action \"Autofill password\"?", "options": [{"option_id": "A", "text": "v0.102"}, {"option_id": "B", "text": "v0.103"}, {"option_id": "C", "text": "v0.104"}, {"option_id": "D", "text": "v0.105"}], "correct_option_id": "A", "expected_answer": "v0.102", "source_chunk_ids": ["termux__termux_app__release__v0_102"], "answer_support": [{"memory_node_id": "termux__termux_app__release__v0_102", "answer_text": "Add context menu action \"Autofill password\"."}]}
{"prototype_id": "termux__termux_app_release_window", "repo": "termux/termux-app", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the termux/termux-app releases, how does the handling of the DECRQM sequence in v0.100 differ from the handling in v0.101?", "options": [{"option_id": "A", "text": "v0.100 fixes the DECRQM sequence but has broken bootstrap archives, while v0.101 is a resubmission with the same DECRQM fix and fixed bootstrap archives."}, {"option_id": "B", "text": "v0.100 introduces the DECRQM sequence, while v0.101 removes it."}, {"option_id": "C", "text": "v0.100 does not mention DECRQM, while v0.101 adds it."}, {"option_id": "D", "text": "Both releases have identical DECRQM handling and identical bootstrap archives."}], "correct_option_id": "A", "expected_answer": "v0.100 fixes the DECRQM sequence but has broken bootstrap archives, while v0.101 is a resubmission with the same DECRQM fix and fixed bootstrap archives.", "source_chunk_ids": ["termux__termux_app__release__v0_100", "termux__termux_app__release__v0_101"], "answer_support": [{"memory_node_id": "termux__termux_app__release__v0_100", "answer_text": "fix handling of DECRQM sequence ... bootstrap archives contain broken dpkg"}, {"memory_node_id": "termux__termux_app__release__v0_101", "answer_text": "fix handling of DECRQM sequence ... Resubmission of v0.100 but with fixed bootstrap archives."}]}
{"prototype_id": "termux__termux_app_release_window", "repo": "termux/termux-app", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the termux/termux-app release window, order the following release-content states from earliest to latest: (1) a release that adds a fullscreen option in termux.properties, (2) a release that adds a context menu action \"Autofill password\", (3) a release that exposes dotfiles through SAF.", "options": [{"option_id": "A", "text": "2 -> 3 -> 1"}, {"option_id": "B", "text": "1 -> 2 -> 3"}, {"option_id": "C", "text": "3 -> 2 -> 1"}, {"option_id": "D", "text": "2 -> 1 -> 3"}], "correct_option_id": "A", "expected_answer": "2 -> 3 -> 1", "source_chunk_ids": ["termux__termux_app__release__v0_102", "termux__termux_app__release__v0_104", "termux__termux_app__release__v0_107"], "answer_support": [{"memory_node_id": "termux__termux_app__release__v0_102", "answer_text": "Add context menu action \"Autofill password\"."}, {"memory_node_id": "termux__termux_app__release__v0_104", "answer_text": "Expose dotfiles through SAF."}, {"memory_node_id": "termux__termux_app__release__v0_107", "answer_text": "add option fullscreen to toggle fullscreen mode."}]}
{"prototype_id": "tesseract_ocr__tesseract_release_window", "repo": "tesseract-ocr/tesseract", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the tesseract-ocr/tesseract releases, which release adds a new PAGE XML renderer and extends the API to retrieve the text angle/gradient?", "options": [{"option_id": "A", "text": "5.3.0"}, {"option_id": "B", "text": "5.4.0"}, {"option_id": "C", "text": "5.5.0"}, {"option_id": "D", "text": "5.2.0"}], "correct_option_id": "B", "expected_answer": "5.4.0", "source_chunk_ids": ["tesseract_ocr__tesseract__release__5_4_0"], "answer_support": [{"memory_node_id": "tesseract_ocr__tesseract__release__5_4_0", "answer_text": "an improved PDF renderer, a new PAGE XML renderer, API extension for text angle/gradient"}]}
{"prototype_id": "tesseract_ocr__tesseract_release_window", "repo": "tesseract-ocr/tesseract", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the tesseract-ocr/tesseract releases, how does the change related to OpenMP in release 4.1.0 differ from the change related to OpenCL in release 5.4.0-rc1?", "options": [{"option_id": "A", "text": "4.1.0 disables OpenMP support by default, while 5.4.0-rc1 removes unsupported OpenCL code and related API functions."}, {"option_id": "B", "text": "4.1.0 enables OpenMP by default, while 5.4.0-rc1 adds OpenCL support."}, {"option_id": "C", "text": "Both releases add support for parallel processing using OpenMP and OpenCL respectively."}, {"option_id": "D", "text": "4.1.0 removes OpenMP, while 5.4.0-rc1 deprecates OpenCL but keeps the code."}], "correct_option_id": "A", "expected_answer": "4.1.0 disables OpenMP support by default, while 5.4.0-rc1 removes unsupported OpenCL code and related API functions.", "source_chunk_ids": ["tesseract_ocr__tesseract__release__4_1_0", "tesseract_ocr__tesseract__release__5_4_0_rc1"], "answer_support": [{"memory_node_id": "tesseract_ocr__tesseract__release__4_1_0", "answer_text": "Disable OpenMP support by default"}, {"memory_node_id": "tesseract_ocr__tesseract__release__5_4_0_rc1", "answer_text": "Remove unsupported OpenCL code and related API functions"}]}
{"prototype_id": "tesseract_ocr__tesseract_release_window", "repo": "tesseract-ocr/tesseract", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the tesseract-ocr/tesseract release window, order the following release-content states from earliest to latest: (1) a release that adds new renderers Alto, LSTMBox, and WordStrBox, (2) a release that replaces all remaining STRING by std::string and lots of GenericVector by std::vector, (3) a release that adds initial support for Intel AVX512F and a new parameter 'invert_threshold', (4) a release that removes Tensorflow support and adds RISC-V V support.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["tesseract_ocr__tesseract__release__4_1_0", "tesseract_ocr__tesseract__release__5_0_0_alpha_20210401", "tesseract_ocr__tesseract__release__5_2_0", "tesseract_ocr__tesseract__release__5_5_0"], "answer_support": [{"memory_node_id": "tesseract_ocr__tesseract__release__4_1_0", "answer_text": "Added new renderers Alto, LSTMBox, WordStrBox"}, {"memory_node_id": "tesseract_ocr__tesseract__release__5_0_0_alpha_20210401", "answer_text": "Replaced all remaining STRING by std::string, Replaced lots of GenericVector by std::vector"}, {"memory_node_id": "tesseract_ocr__tesseract__release__5_2_0", "answer_text": "Add initial support for Intel AVX512F, Add new parameter 'invert_threshold'"}, {"memory_node_id": "tesseract_ocr__tesseract__release__5_5_0", "answer_text": "Remove Tensorflow support, Add RISC-V V support"}]}
{"prototype_id": "Textualize__textual_release_window", "repo": "Textualize/textual", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the Textualize/textual releases, which release adds the `pointer` rule to TCSS for customizing mouse pointer appearance over widgets?", "options": [{"option_id": "A", "text": "v7.3.0"}, {"option_id": "B", "text": "v7.4.0"}, {"option_id": "C", "text": "v7.5.0"}, {"option_id": "D", "text": "v8.0.0"}], "correct_option_id": "B", "expected_answer": "v7.4.0", "source_chunk_ids": ["Textualize__textual__release__v7_4_0"], "answer_support": [{"memory_node_id": "Textualize__textual__release__v7_4_0", "answer_text": "Adds a `pointer` rule to TCSS, so you can change how the mouse pointer looks over a given widget."}]}
{"prototype_id": "Textualize__textual_release_window", "repo": "Textualize/textual", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the Textualize/textual releases, how does the performance improvement in v6.12.0 differ from the performance improvement in v7.0.1?", "options": [{"option_id": "A", "text": "v6.12.0 fixes unnecessary style updates when popping screens, while v7.0.1 adds a refresh_styles boolean to ScreenResult to further reduce style updates during screen transitions."}, {"option_id": "B", "text": "v6.12.0 adds Widget.BLANK for rendering optimization, while v7.0.1 removes superfluous style updates when setting display."}, {"option_id": "C", "text": "v6.12.0 reduces GC time, while v7.0.1 fixes a performance issue with large scrollable containers."}, {"option_id": "D", "text": "v6.12.0 speeds up transitions by adding a 50ms delay, while v7.0.1 replaces circular references with weak references."}], "correct_option_id": "A", "expected_answer": "v6.12.0 fixes unnecessary style updates when popping screens, while v7.0.1 adds a refresh_styles boolean to ScreenResult to further reduce style updates during screen transitions.", "source_chunk_ids": ["Textualize__textual__release__v6_12_0", "Textualize__textual__release__v7_0_1"], "answer_support": [{"memory_node_id": "Textualize__textual__release__v6_12_0", "answer_text": "Fixed unnecessary style update when popping screens, which may have caused noticable pauses changing screens (with a lot of widgets)"}, {"memory_node_id": "Textualize__textual__release__v7_0_1", "answer_text": "Added a `refresh_styles` boolean to the `ScreenResult` message which reduces style updates when popping screens"}]}
{"prototype_id": "Textualize__textual_release_window", "repo": "Textualize/textual", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the Textualize/textual release window, order the following release-content states from earliest to latest: (1) a release that adds the `TextSelected` event, (2) a release that adds the `pointer` rule to TCSS, (3) a release that enhances text selection with auto-scrolling and selecting across containers, (4) a release that adds dedicated ansi themes ansi-dark and ansi-light.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 2 -> 1 -> 3"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["Textualize__textual__release__v6_11_0", "Textualize__textual__release__v7_4_0", "Textualize__textual__release__v8_2_0", "Textualize__textual__release__v8_2_5"], "answer_support": [{"memory_node_id": "Textualize__textual__release__v6_11_0", "answer_text": "Added a `TextSelected` event."}, {"memory_node_id": "Textualize__textual__release__v7_4_0", "answer_text": "Added `pointer` rule"}, {"memory_node_id": "Textualize__textual__release__v8_2_0", "answer_text": "Auto-scrolling on select ... Selecting over containers"}, {"memory_node_id": "Textualize__textual__release__v8_2_5", "answer_text": "Two new themes: \"ansi-dark\" and \"ansi-light\""}]}
{"prototype_id": "thedotmack__claude_mem_release_window", "repo": "thedotmack/claude-mem", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the thedotmack/claude-mem releases, which release introduces a one-shot DB cleanup migration that runs once per data directory at worker startup?", "options": [{"option_id": "A", "text": "v12.4.1"}, {"option_id": "B", "text": "v12.4.2"}, {"option_id": "C", "text": "v12.4.3"}, {"option_id": "D", "text": "v12.4.4"}], "correct_option_id": "C", "expected_answer": "v12.4.3", "source_chunk_ids": ["thedotmack__claude_mem__release__v12_4_3"], "answer_support": [{"memory_node_id": "thedotmack__claude_mem__release__v12_4_3", "answer_text": "One-shot DB cleanup migration (CleanupV12_4_3.ts) — runs once per data directory at worker startup"}]}
{"prototype_id": "thedotmack__claude_mem_release_window", "repo": "thedotmack/claude-mem", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the thedotmack/claude-mem releases, how does the observation pipeline change described in v12.5.0 differ from the queue-draining fix described in v12.4.4?", "options": [{"option_id": "A", "text": "v12.5.0 kills the per-message retry counter and simplifies the parser, while v12.4.4 removes the SessionEnd hook to stop draining the observation queue on /clear."}, {"option_id": "B", "text": "v12.5.0 adds a Telegram notifier, while v12.4.4 adds a rate limiter."}, {"option_id": "C", "text": "Both releases only update Chroma watermarks without changing observation handling."}, {"option_id": "D", "text": "v12.5.0 introduces the Server Beta, while v12.4.4 relicenses the project."}], "correct_option_id": "A", "expected_answer": "v12.5.0 kills the per-message retry counter and simplifies the parser, while v12.4.4 removes the SessionEnd hook to stop draining the observation queue on /clear.", "source_chunk_ids": ["thedotmack__claude_mem__release__v12_5_0", "thedotmack__claude_mem__release__v12_4_4"], "answer_support": [{"memory_node_id": "thedotmack__claude_mem__release__v12_5_0", "answer_text": "Observation pipeline cleanup — kill the per-message retry counter. Parser collapsed to binary valid/invalid."}, {"memory_node_id": "thedotmack__claude_mem__release__v12_4_4", "answer_text": "Bug fix: stop draining the observation queue on /clear. Removed SessionEnd hook entirely."}]}
{"prototype_id": "thedotmack__claude_mem_release_window", "repo": "thedotmack/claude-mem", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the thedotmack/claude-mem release window, order the following release-content states from earliest to latest: (1) a release that adds a one-shot DB cleanup migration, (2) a release that introduces the Server Beta runtime and relicenses to Apache-2.0, (3) a release that adds the wowerpoint skill for generating kawaii NotebookLM slide-deck PDFs.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["thedotmack__claude_mem__release__v12_4_3", "thedotmack__claude_mem__release__v13_0_0", "thedotmack__claude_mem__release__v13_2_0"], "answer_support": [{"memory_node_id": "thedotmack__claude_mem__release__v12_4_3", "answer_text": "One-shot DB cleanup migration"}, {"memory_node_id": "thedotmack__claude_mem__release__v13_0_0", "answer_text": "Server Beta runtime ... relicensed from AGPL-3.0 to Apache-2.0"}, {"memory_node_id": "thedotmack__claude_mem__release__v13_2_0", "answer_text": "wowerpoint skill — kawaii NotebookLM slide-deck generator"}]}
{"prototype_id": "tmux__tmux_release_window", "repo": "tmux/tmux", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the tmux/tmux repository, which release note explicitly states that it is a bug fix release of 3.0 and provides an AppImage package?", "options": [{"option_id": "A", "text": "tmux 3.0"}, {"option_id": "B", "text": "tmux 3.0a"}, {"option_id": "C", "text": "tmux 3.1"}, {"option_id": "D", "text": "tmux 3.1a"}], "correct_option_id": "B", "expected_answer": "tmux 3.0a", "source_chunk_ids": ["tmux__tmux__release__3_0a"], "answer_support": [{"memory_node_id": "tmux__tmux__release__3_0a", "answer_text": "This is a bug fix release of 3.0. The release note directs users to the CHANGES file for a list of changes and mentions that tmux-3.0a.tar.gz is the source tarball and tmux-3.0a-x86_64.AppImage is an AppImage package for Linux."}]}
{"prototype_id": "ToolJet__ToolJet_release_window", "repo": "ToolJet/ToolJet", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the ToolJet/ToolJet releases, which release introduces the new AI Module Builder?", "options": [{"option_id": "A", "text": "v3.20.152-lts"}, {"option_id": "B", "text": "v3.20.153-lts"}, {"option_id": "C", "text": "v3.20.154-lts"}, {"option_id": "D", "text": "v3.20.155-lts"}], "correct_option_id": "B", "expected_answer": "v3.20.153-lts", "source_chunk_ids": ["ToolJet__ToolJet__release__v3_20_153_lts"], "answer_support": [{"memory_node_id": "ToolJet__ToolJet__release__v3_20_153_lts", "answer_text": "introduces the new AI Module Builder"}]}
{"prototype_id": "ToolJet__ToolJet_release_window", "repo": "ToolJet/ToolJet", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the ToolJet/ToolJet releases, how does the feature set in v3.20.155-lts differ from that in v3.20.157-lts?", "options": [{"option_id": "A", "text": "v3.20.155-lts introduces OAuth support for Dynamic Forms and a Context Window widget, while v3.20.157-lts adds QuickBooks Online marketplace plugin support and search functionality for gRPC methods."}, {"option_id": "B", "text": "v3.20.155-lts adds AI datasource support for Snowflake, while v3.20.157-lts adds Intercom marketplace plugin."}, {"option_id": "C", "text": "Both releases only contain bug fixes with no new features."}, {"option_id": "D", "text": "v3.20.155-lts removes the Table component, while v3.20.157-lts restores it."}], "correct_option_id": "A", "expected_answer": "v3.20.155-lts introduces OAuth support for Dynamic Forms and a Context Window widget, while v3.20.157-lts adds QuickBooks Online marketplace plugin support and search functionality for gRPC methods.", "source_chunk_ids": ["ToolJet__ToolJet__release__v3_20_155_lts", "ToolJet__ToolJet__release__v3_20_157_lts"], "answer_support": [{"memory_node_id": "ToolJet__ToolJet__release__v3_20_155_lts", "answer_text": "OAuth support for Dynamic Forms, a new Context Window widget"}, {"memory_node_id": "ToolJet__ToolJet__release__v3_20_157_lts", "answer_text": "QuickBooks Online marketplace plugin support and search functionality for gRPC methods and service names"}]}
{"prototype_id": "ToolJet__ToolJet_release_window", "repo": "ToolJet/ToolJet", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the ToolJet/ToolJet release window, order the following release-content states from earliest to latest: (1) a release that adds AI datasource support for MySQL and MSSQL, (2) a release that introduces the new AI Module Builder, (3) a release that adds AI datasource support for Snowflake, (4) a release that adds native support for Gemini AI.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "B", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "C", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "D", "text": "1 -> 3 -> 2 -> 4"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3 -> 4", "source_chunk_ids": ["ToolJet__ToolJet__release__v3_20_153_lts", "ToolJet__ToolJet__release__v3_20_159_lts", "ToolJet__ToolJet__release__v3_20_164_lts", "ToolJet__ToolJet__release__v3_20_167_lts"], "answer_support": [{"memory_node_id": "ToolJet__ToolJet__release__v3_20_153_lts", "answer_text": "introduces the new AI Module Builder"}, {"memory_node_id": "ToolJet__ToolJet__release__v3_20_159_lts", "answer_text": "AI datasource support for MySQL and MSSQL"}, {"memory_node_id": "ToolJet__ToolJet__release__v3_20_164_lts", "answer_text": "AI datasource support for Snowflake"}, {"memory_node_id": "ToolJet__ToolJet__release__v3_20_167_lts", "answer_text": "native support for Gemini AI"}]}
{"prototype_id": "topjohnwu__Magisk_release_window", "repo": "topjohnwu/Magisk", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the topjohnwu/Magisk releases, which release introduces Zygisk API v4 with a refined PLT function hook API?", "options": [{"option_id": "A", "text": "v25.2"}, {"option_id": "B", "text": "v26.0"}, {"option_id": "C", "text": "v27.0"}, {"option_id": "D", "text": "v28.0"}], "correct_option_id": "B", "expected_answer": "v26.0", "source_chunk_ids": ["topjohnwu__Magisk__release__v26_0"], "answer_support": [{"memory_node_id": "topjohnwu__Magisk__release__v26_0", "answer_text": "Zygisk API v4 is now live! It comes with new features and a refined PLT function hook API."}]}
{"prototype_id": "topjohnwu__Magisk_release_window", "repo": "topjohnwu/Magisk", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the topjohnwu/Magisk releases, how does the sepolicy.rule implementation change from v26.0 to v26.1?", "options": [{"option_id": "A", "text": "v26.0 introduces a new pre-init partition detection mechanism, while v26.1 always prefers ext4 partitions over f2fs for pre-init partition selection."}, {"option_id": "B", "text": "v26.0 removes sepolicy.rule support, while v26.1 restores it."}, {"option_id": "C", "text": "Both releases use the same sepolicy.rule implementation without changes."}, {"option_id": "D", "text": "v26.0 requires custom recovery installation, while v26.1 removes that requirement."}], "correct_option_id": "A", "expected_answer": "v26.0 introduces a new pre-init partition detection mechanism, while v26.1 always prefers ext4 partitions over f2fs for pre-init partition selection.", "source_chunk_ids": ["topjohnwu__Magisk__release__v26_0", "topjohnwu__Magisk__release__v26_1"], "answer_support": [{"memory_node_id": "topjohnwu__Magisk__release__v26_0", "answer_text": "a brand new pre-init partition detection mechanism has been designed"}, {"memory_node_id": "topjohnwu__Magisk__release__v26_1", "answer_text": "Always prefer ext4 partitions over f2fs when selecting the pre-init partition"}]}
{"prototype_id": "traefik__traefik_release_window", "repo": "traefik/traefik", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the traefik/traefik releases, how does the handling of the allowCrossNamespace configuration differ between v3.6.14 and v3.6.12?", "options": [{"option_id": "A", "text": "v3.6.14 introduces a breaking change that makes Chain middleware CRDs honor allowCrossNamespace, while v3.6.12 does not mention this change."}, {"option_id": "B", "text": "v3.6.14 removes the allowCrossNamespace option entirely, while v3.6.12 adds it."}, {"option_id": "C", "text": "Both releases treat allowCrossNamespace identically, with no changes."}, {"option_id": "D", "text": "v3.6.12 makes allowCrossNamespace mandatory, while v3.6.14 makes it optional."}], "correct_option_id": "A", "expected_answer": "v3.6.14 introduces a breaking change that makes Chain middleware CRDs honor allowCrossNamespace, while v3.6.12 does not mention this change.", "source_chunk_ids": ["traefik__traefik__release__v3_6_14", "traefik__traefik__release__v3_6_12"], "answer_support": [{"memory_node_id": "traefik__traefik__release__v3_6_14", "answer_text": "a breaking change makes Chain middleware CRDs honor the allowCrossNamespace configuration"}, {"memory_node_id": "traefik__traefik__release__v3_6_12", "answer_text": "no mention of allowCrossNamespace change"}]}
{"prototype_id": "trpc__trpc_release_window", "repo": "trpc/trpc", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the trpc/trpc releases, which release adds server support for lambda response streaming?", "options": [{"option_id": "A", "text": "v11.1.4"}, {"option_id": "B", "text": "v11.2.0"}, {"option_id": "C", "text": "v11.3.0"}, {"option_id": "D", "text": "v11.4.0"}], "correct_option_id": "B", "expected_answer": "v11.2.0", "source_chunk_ids": ["trpc__trpc__release__v11_2_0"], "answer_support": [{"memory_node_id": "trpc__trpc__release__v11_2_0", "answer_text": "adds server support for lambda response streaming"}]}
{"prototype_id": "trpc__trpc_release_window", "repo": "trpc/trpc", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the trpc/trpc releases, how does the client-related change in v11.3.0 differ from the client-related change in v11.4.0?", "options": [{"option_id": "A", "text": "v11.3.0 adds a `localLink` to the client, while v11.4.0 upgrades `localLink` from experimental to `unstable`."}, {"option_id": "B", "text": "v11.3.0 fixes `httpBatchLink` with a custom transformed object, while v11.4.0 adds TypeScript 5.9 support."}, {"option_id": "C", "text": "v11.3.0 bumps tanstack packages, while v11.4.0 swaps rollup with rolldown."}, {"option_id": "D", "text": "v11.3.0 adds lambda response streaming, while v11.4.0 adds 402 HTTP response support."}], "correct_option_id": "A", "expected_answer": "v11.3.0 adds a `localLink` to the client, while v11.4.0 upgrades `localLink` from experimental to `unstable`.", "source_chunk_ids": ["trpc__trpc__release__v11_3_0", "trpc__trpc__release__v11_4_0"], "answer_support": [{"memory_node_id": "trpc__trpc__release__v11_3_0", "answer_text": "adds a `localLink` to the client"}, {"memory_node_id": "trpc__trpc__release__v11_4_0", "answer_text": "upgrade of `localLink` from experimental to `unstable`"}]}
{"prototype_id": "trpc__trpc_release_window", "repo": "trpc/trpc", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the trpc/trpc release window, order the following release-content states from earliest to latest: (1) a release that adds a `localLink` to the client, (2) a release that upgrades `localLink` from experimental to `unstable`, (3) a release that adds an experimental_encoder option for WebSocket connections.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["trpc__trpc__release__v11_3_0", "trpc__trpc__release__v11_4_0", "trpc__trpc__release__v11_9_0"], "answer_support": [{"memory_node_id": "trpc__trpc__release__v11_3_0", "answer_text": "adds a `localLink` to the client"}, {"memory_node_id": "trpc__trpc__release__v11_4_0", "answer_text": "upgrade of `localLink` from experimental to `unstable`"}, {"memory_node_id": "trpc__trpc__release__v11_9_0", "answer_text": "adds an experimental_encoder option for WebSocket connections"}]}
{"prototype_id": "TryGhost__Ghost_release_window", "repo": "TryGhost/Ghost", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the TryGhost/Ghost releases, which release adds a Danger Zone action to reset all authentication?", "options": [{"option_id": "A", "text": "v6.40.0"}, {"option_id": "B", "text": "v6.41.0"}, {"option_id": "C", "text": "v6.42.0"}, {"option_id": "D", "text": "v6.43.0"}], "correct_option_id": "B", "expected_answer": "v6.41.0", "source_chunk_ids": ["TryGhost__Ghost__release__v6_41_0"], "answer_support": [{"memory_node_id": "TryGhost__Ghost__release__v6_41_0", "answer_text": "adds a Danger Zone action to reset all authentication"}]}
{"prototype_id": "TryGhost__Ghost_release_window", "repo": "TryGhost/Ghost", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the TryGhost/Ghost releases, how does the comment-related change in v6.42.0 differ from the comment-related change in v6.39.0?", "options": [{"option_id": "A", "text": "v6.42.0 releases pinned and threaded comments, while v6.39.0 changes comments to be enabled by default."}, {"option_id": "B", "text": "v6.42.0 adds comment dislikes, while v6.39.0 removes comments entirely."}, {"option_id": "C", "text": "Both releases only fix comment thread connector lines."}, {"option_id": "D", "text": "v6.42.0 disables comments, while v6.39.0 adds a built-in theme code editor."}], "correct_option_id": "A", "expected_answer": "v6.42.0 releases pinned and threaded comments, while v6.39.0 changes comments to be enabled by default.", "source_chunk_ids": ["TryGhost__Ghost__release__v6_42_0", "TryGhost__Ghost__release__v6_39_0"], "answer_support": [{"memory_node_id": "TryGhost__Ghost__release__v6_42_0", "answer_text": "releases pinned comments, releases threaded comments"}, {"memory_node_id": "TryGhost__Ghost__release__v6_39_0", "answer_text": "changes comments to be enabled by default"}]}
{"prototype_id": "TryGhost__Ghost_release_window", "repo": "TryGhost/Ghost", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the TryGhost/Ghost release window, order the following release-content states from earliest to latest: (1) a release that adds retention offers, (2) a release that adds gift subscriptions, (3) a release that releases pinned and threaded comments, (4) a release that adds a frontend admin toolbar.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["TryGhost__Ghost__release__v6_22_0", "TryGhost__Ghost__release__v6_40_0", "TryGhost__Ghost__release__v6_42_0", "TryGhost__Ghost__release__v6_43_0"], "answer_support": [{"memory_node_id": "TryGhost__Ghost__release__v6_22_0", "answer_text": "adds retention offers"}, {"memory_node_id": "TryGhost__Ghost__release__v6_40_0", "answer_text": "adds gift subscriptions"}, {"memory_node_id": "TryGhost__Ghost__release__v6_42_0", "answer_text": "releases pinned comments, releases threaded comments"}, {"memory_node_id": "TryGhost__Ghost__release__v6_43_0", "answer_text": "adds a frontend admin toolbar"}]}
{"prototype_id": "tw93__Pake_release_window", "repo": "tw93/Pake", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the tw93/Pake releases, which release introduces a brand-new native menu system with Navigation, View, Edit, Window, and Help menus, along with richer shortcuts?", "options": [{"option_id": "A", "text": "V2.2.0"}, {"option_id": "B", "text": "V3.6.0"}, {"option_id": "C", "text": "V3.10.0"}, {"option_id": "D", "text": "V3.11.0"}], "correct_option_id": "B", "expected_answer": "V3.6.0", "source_chunk_ids": ["tw93__Pake__release__v3_6_0"], "answer_support": [{"memory_node_id": "tw93__Pake__release__v3_6_0", "answer_text": "a brand-new native menu system is introduced with Navigation, View, Edit, Window, and Help menus, along with richer shortcuts"}]}
{"prototype_id": "tw93__Pake_release_window", "repo": "tw93/Pake", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the tw93/Pake releases, how does the multi-window support introduced in V3.10.0 differ from the managed new windows feature added in V3.11.0?", "options": [{"option_id": "A", "text": "V3.10.0 adds a --multi-window flag for multiple windows within a single instance, while V3.11.0 adds --new-window to open popup and OAuth windows as managed webview windows inside the app."}, {"option_id": "B", "text": "V3.10.0 adds --new-window for OAuth flows, while V3.11.0 adds --multi-window for multiple instances."}, {"option_id": "C", "text": "Both releases add the same multi-window feature but with different parameter names."}, {"option_id": "D", "text": "V3.10.0 removes multi-window support, and V3.11.0 reintroduces it with OAuth handling."}], "correct_option_id": "A", "expected_answer": "V3.10.0 adds a --multi-window flag for multiple windows within a single instance, while V3.11.0 adds --new-window to open popup and OAuth windows as managed webview windows inside the app.", "source_chunk_ids": ["tw93__Pake__release__v3_10_0", "tw93__Pake__release__v3_11_0"], "answer_support": [{"memory_node_id": "tw93__Pake__release__v3_10_0", "answer_text": "multi-window support is added with a --multi-window flag, allowing multiple windows within a single app instance"}, {"memory_node_id": "tw93__Pake__release__v3_11_0", "answer_text": "Managed new windows are supported with --new-window to open popup and OAuth windows inside the app"}]}
{"prototype_id": "tw93__Pake_release_window", "repo": "tw93/Pake", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the tw93/Pake release window, order the following release-content states from earliest to latest: (1) a release that adds support for the aarch64 architecture on Linux, (2) a release that switches the underlying framework from Wry to Tauri, (3) a release that updates the underlying Tauri dependency to version 2.0, (4) a release that adds a --multi-window flag for multiple windows within a single instance.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["tw93__Pake__release__v1_0_4_beta", "tw93__Pake__release__v2_0_0", "tw93__Pake__release__v3_0_3", "tw93__Pake__release__v3_10_0"], "answer_support": [{"memory_node_id": "tw93__Pake__release__v1_0_4_beta", "answer_text": "adds support for the aarch64 (arm64) architecture on Linux"}, {"memory_node_id": "tw93__Pake__release__v2_0_0", "answer_text": "switching the underlying framework from Wry to Tauri"}, {"memory_node_id": "tw93__Pake__release__v3_0_3", "answer_text": "the underlying Tauri dependency is updated to version 2.0"}, {"memory_node_id": "tw93__Pake__release__v3_10_0", "answer_text": "multi-window support is added with a --multi-window flag"}]}
{"prototype_id": "typeorm__typeorm_release_window", "repo": "typeorm/typeorm", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the typeorm/typeorm releases, which release adds support for Common Table Expressions?", "options": [{"option_id": "A", "text": "0.3.2"}, {"option_id": "B", "text": "0.3.3"}, {"option_id": "C", "text": "0.3.4"}, {"option_id": "D", "text": "0.3.5"}], "correct_option_id": "B", "expected_answer": "0.3.3", "source_chunk_ids": ["typeorm__typeorm__release__0_3_3"], "answer_support": [{"memory_node_id": "typeorm__typeorm__release__0_3_3", "answer_text": "adds support for Common Table Expressions"}]}
{"prototype_id": "typeorm__typeorm_release_window", "repo": "typeorm/typeorm", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the typeorm/typeorm releases, how does the security-related change in 0.3.14 differ from the security-related change in 0.3.26?", "options": [{"option_id": "A", "text": "0.3.14 drops xml and yml connection option support to address security issues in an underlying dependency, while 0.3.26 sets stringifyObjects: true for MySQL connections to avoid a potential security vulnerability."}, {"option_id": "B", "text": "0.3.14 adds a new driver for Cloud Spanner, while 0.3.26 adds support for Redis 5.x."}, {"option_id": "C", "text": "Both releases only update documentation without any security changes."}, {"option_id": "D", "text": "0.3.14 fixes a prototype pollution issue, while 0.3.26 fixes a circular dependency breaking node.js 20.6."}], "correct_option_id": "A", "expected_answer": "0.3.14 drops xml and yml connection option support to address security issues in an underlying dependency, while 0.3.26 sets stringifyObjects: true for MySQL connections to avoid a potential security vulnerability.", "source_chunk_ids": ["typeorm__typeorm__release__0_3_14", "typeorm__typeorm__release__0_3_26"], "answer_support": [{"memory_node_id": "typeorm__typeorm__release__0_3_14", "answer_text": "drops xml and yml connection option support to address security issues in an underlying dependency"}, {"memory_node_id": "typeorm__typeorm__release__0_3_26", "answer_text": "when using MySQL, TypeORM now connects using stringifyObjects: true to avoid a potential security vulnerability"}]}
{"prototype_id": "typeorm__typeorm_release_window", "repo": "typeorm/typeorm", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the typeorm/typeorm release window, order the following release-content states from earliest to latest: (1) a release that adds a for_key_share lock mode for postgres driver and a new driver for Cloud Spanner, (2) a release that drops xml and yml connection option support and adds QueryBuilder performance optimizations, (3) a release that introduces a breaking change where delete and update methods throw an error when an empty object is supplied as criteria, (4) a release that announces TypeORM v1.0 with breaking changes and an upgrade guide.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["typeorm__typeorm__release__0_3_6", "typeorm__typeorm__release__0_3_14", "typeorm__typeorm__release__0_3_23", "typeorm__typeorm__release__1_0_0"], "answer_support": [{"memory_node_id": "typeorm__typeorm__release__0_3_6", "answer_text": "adds a for_key_share (FOR KEY SHARE) lock mode for the postgres driver and introduces a new driver for Cloud Spanner"}, {"memory_node_id": "typeorm__typeorm__release__0_3_14", "answer_text": "drops xml and yml connection option support to address security issues in an underlying dependency, and adds QueryBuilder performance optimizations"}, {"memory_node_id": "typeorm__typeorm__release__0_3_23", "answer_text": "introduces a breaking change where delete and update methods of EntityManager and Repository APIs throw an error when an empty object is supplied as criteria"}, {"memory_node_id": "typeorm__typeorm__release__1_0_0", "answer_text": "announces TypeORM v1.0 with breaking changes and an upgrade guide"}]}
{"prototype_id": "typicode__json_server_release_window", "repo": "typicode/json-server", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the typicode/json-server releases, which release introduces the feature that autofixes missing id in arrays?", "options": [{"option_id": "A", "text": "v1.0.0-alpha.10"}, {"option_id": "B", "text": "v1.0.0-alpha.12"}, {"option_id": "C", "text": "v1.0.0-alpha.14"}, {"option_id": "D", "text": "v1.0.0-alpha.20"}], "correct_option_id": "B", "expected_answer": "v1.0.0-alpha.12", "source_chunk_ids": ["typicode__json_server__release__v1_0_0_alpha_12"], "answer_support": [{"memory_node_id": "typicode__json_server__release__v1_0_0_alpha_12", "answer_text": "adds a new feature that autofixes missing id in arrays"}]}
{"prototype_id": "typicode__json_server_release_window", "repo": "typicode/json-server", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the typicode/json-server releases, how does the filtering capability change from v1.0.0-beta.2 to v1.0.0-beta.6?", "options": [{"option_id": "A", "text": "v1.0.0-beta.2 allows multiple conditions for filtering, while v1.0.0-beta.6 adds _where filtering, uses a new operator separator, and drops _start, _end, and _limit."}, {"option_id": "B", "text": "v1.0.0-beta.2 introduces _where filtering, while v1.0.0-beta.6 removes all filtering capabilities."}, {"option_id": "C", "text": "Both releases only support single-condition filtering without any changes."}, {"option_id": "D", "text": "v1.0.0-beta.2 drops _start, _end, and _limit, while v1.0.0-beta.6 adds multiple conditions for filtering."}], "correct_option_id": "A", "expected_answer": "v1.0.0-beta.2 allows multiple conditions for filtering, while v1.0.0-beta.6 adds _where filtering, uses a new operator separator, and drops _start, _end, and _limit.", "source_chunk_ids": ["typicode__json_server__release__v1_0_0_beta_2", "typicode__json_server__release__v1_0_0_beta_6"], "answer_support": [{"memory_node_id": "typicode__json_server__release__v1_0_0_beta_2", "answer_text": "allows multiple conditions for filtering"}, {"memory_node_id": "typicode__json_server__release__v1_0_0_beta_6", "answer_text": "adds _where filtering, uses a new operator separator, and drops _start, _end, and _limit"}]}
{"prototype_id": "typicode__json_server_release_window", "repo": "typicode/json-server", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the typicode/json-server release window, order the following release-content states from earliest to latest: (1) a release that adds support for endpoints returning only an object, (2) a release that switches from alpha to beta and fixes boolean filtering, (3) a release that adds JSON Schema support, (4) a release that returns JSON response for 404 errors instead of plain text.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["typicode__json_server__release__v1_0_0_alpha_10", "typicode__json_server__release__v1_0_0_beta_0", "typicode__json_server__release__v1_0_0_beta_5", "typicode__json_server__release__v1_0_0_beta_15"], "answer_support": [{"memory_node_id": "typicode__json_server__release__v1_0_0_alpha_10", "answer_text": "adds support for endpoints that return only an object"}, {"memory_node_id": "typicode__json_server__release__v1_0_0_beta_0", "answer_text": "switches from alpha to beta and fixes boolean filtering"}, {"memory_node_id": "typicode__json_server__release__v1_0_0_beta_5", "answer_text": "adds JSON Schema support"}, {"memory_node_id": "typicode__json_server__release__v1_0_0_beta_15", "answer_text": "returns JSON response for 404 errors instead of plain text"}]}
{"prototype_id": "ultralytics__ultralytics_release_window", "repo": "ultralytics/ultralytics", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the ultralytics/ultralytics releases, which release introduces per-image precision, recall, and F1 tracking during validation?", "options": [{"option_id": "A", "text": "v8.4.39"}, {"option_id": "B", "text": "v8.4.40"}, {"option_id": "C", "text": "v8.4.41"}, {"option_id": "D", "text": "v8.4.42"}], "correct_option_id": "B", "expected_answer": "v8.4.40", "source_chunk_ids": ["ultralytics__ultralytics__release__v8_4_40"], "answer_support": [{"memory_node_id": "ultralytics__ultralytics__release__v8_4_40", "answer_text": "per-image precision, recall, and F1 tracking are introduced during validation"}]}
{"prototype_id": "ultralytics__ultralytics_release_window", "repo": "ultralytics/ultralytics", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the ultralytics/ultralytics releases, how does the training resume fix in v8.4.33 differ from the training resume fix in v8.4.46?", "options": [{"option_id": "A", "text": "v8.4.33 restores loss state for end-to-end models, while v8.4.46 stops resume when training is already finished."}, {"option_id": "B", "text": "v8.4.33 fixes multi-scale training, while v8.4.46 fixes pretrained checkpoint loading."}, {"option_id": "C", "text": "Both releases fix the same issue of NaN recovery during training."}, {"option_id": "D", "text": "v8.4.33 adds multi-dataset tuning, while v8.4.46 adds per-image metrics."}], "correct_option_id": "A", "expected_answer": "v8.4.33 restores loss state for end-to-end models, while v8.4.46 stops resume when training is already finished.", "source_chunk_ids": ["ultralytics__ultralytics__release__v8_4_33", "ultralytics__ultralytics__release__v8_4_46"], "answer_support": [{"memory_node_id": "ultralytics__ultralytics__release__v8_4_33", "answer_text": "restores correct loss state when resuming training for end-to-end models"}, {"memory_node_id": "ultralytics__ultralytics__release__v8_4_46", "answer_text": "fixes resume training to correctly stop when already finished"}]}
{"prototype_id": "ultralytics__ultralytics_release_window", "repo": "ultralytics/ultralytics", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the ultralytics/ultralytics release window, order the following release-content states from earliest to latest: (1) a release that adds multi-dataset hyperparameter tuning, (2) a release that introduces YOLO26 semantic segmentation models, (3) a release that adds ONNX INT8 export, (4) a release that fixes CLI parsing for Solutions Heatmap colormap values.", "options": [{"option_id": "A", "text": "1 -> 4 -> 2 -> 3"}, {"option_id": "B", "text": "4 -> 1 -> 2 -> 3"}, {"option_id": "C", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "D", "text": "2 -> 1 -> 4 -> 3"}], "correct_option_id": "A", "expected_answer": "1 -> 4 -> 2 -> 3", "source_chunk_ids": ["ultralytics__ultralytics__release__v8_4_34", "ultralytics__ultralytics__release__v8_4_47", "ultralytics__ultralytics__release__v8_4_52", "ultralytics__ultralytics__release__v8_4_60"], "answer_support": [{"memory_node_id": "ultralytics__ultralytics__release__v8_4_34", "answer_text": "multi-dataset hyperparameter tuning"}, {"memory_node_id": "ultralytics__ultralytics__release__v8_4_47", "answer_text": "fixes CLI parsing for Solutions Heatmap colormap values"}, {"memory_node_id": "ultralytics__ultralytics__release__v8_4_52", "answer_text": "full YOLO26 semantic segmentation support is added"}, {"memory_node_id": "ultralytics__ultralytics__release__v8_4_60", "answer_text": "ONNX INT8 export is added"}]}
{"prototype_id": "unionlabs__union_release_window", "repo": "unionlabs/union", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the unionlabs/union releases, which release note includes instructions for an asynchronous binary upgrade, advising users to halt the uniond service, replace the binary, and restart the service?", "options": [{"option_id": "A", "text": "uniond-release v1.2.2"}, {"option_id": "B", "text": "uniond-release v1.2.2-s1"}, {"option_id": "C", "text": "uniond-release v1.2.3"}, {"option_id": "D", "text": "uniond-release v1.3.0-rc1"}], "correct_option_id": "B", "expected_answer": "uniond-release v1.2.2-s1", "source_chunk_ids": ["unionlabs__union__release__uniond_v1_2_2_security_1"], "answer_support": [{"memory_node_id": "unionlabs__union__release__uniond_v1_2_2_security_1", "answer_text": "includes instructions for an asynchronous binary upgrade, advising users to halt the uniond service, replace the binary, and restart the service as soon as possible."}]}
{"prototype_id": "Unitech__pm2_release_window", "repo": "Unitech/pm2", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the Unitech/pm2 releases, which release introduces a new local system monitoring feature that displays vital server metrics in pm2 ls?", "options": [{"option_id": "A", "text": "4.5.0"}, {"option_id": "B", "text": "5.0.0"}, {"option_id": "C", "text": "5.1.1"}, {"option_id": "D", "text": "5.2.0"}], "correct_option_id": "B", "expected_answer": "5.0.0", "source_chunk_ids": ["Unitech__pm2__release__5_0_0"], "answer_support": [{"memory_node_id": "Unitech__pm2__release__5_0_0", "answer_text": "introduces a new local system monitoring feature displaying vital server metrics in pm2 ls"}]}
{"prototype_id": "Unitech__pm2_release_window", "repo": "Unitech/pm2", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the Unitech/pm2 release window, order the following release-content states from earliest to latest: (1) a release that bumps @pm2/js-api for an axios CVE, (2) a release that adds Bun support and disables git parsing by default, (3) a release that replaces chalk with ansis, (4) a release that drops npm-shrinkwrap in favor of fixed dependencies versions.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 2 -> 1 -> 3"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["Unitech__pm2__release__4_5_2", "Unitech__pm2__release__v6_0_5", "Unitech__pm2__release__v6_0_6", "Unitech__pm2__release__v6_0_12"], "answer_support": [{"memory_node_id": "Unitech__pm2__release__4_5_2", "answer_text": "bump @pm2/js-api (axios CVE)"}, {"memory_node_id": "Unitech__pm2__release__v6_0_5", "answer_text": "Bun support - Disable git parsing by default"}, {"memory_node_id": "Unitech__pm2__release__v6_0_6", "answer_text": "replace chalk with ansis"}, {"memory_node_id": "Unitech__pm2__release__v6_0_12", "answer_text": "Drop npm-shrinkwrap in favor of fixed dependencies versions"}]}
{"prototype_id": "usebruno__bruno_release_window", "repo": "usebruno/bruno", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the usebruno/bruno releases, which release introduces gRPC Support along with Global Shortcuts for Zoom, Minimize, and Close on Windows?", "options": [{"option_id": "A", "text": "v2.8.0"}, {"option_id": "B", "text": "v2.10.0"}, {"option_id": "C", "text": "v2.11.0"}, {"option_id": "D", "text": "v2.13.0"}], "correct_option_id": "B", "expected_answer": "v2.10.0", "source_chunk_ids": ["usebruno__bruno__release__v2_10_0"], "answer_support": [{"memory_node_id": "usebruno__bruno__release__v2_10_0", "answer_text": "introduces gRPC Support, Global Shortcuts for Zoom, Minimize, and Close on Windows"}]}
{"prototype_id": "usebruno__bruno_release_window", "repo": "usebruno/bruno", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the usebruno/bruno releases, how does the feature set of v2.13.0 differ from that of v2.14.0?", "options": [{"option_id": "A", "text": "v2.13.0 adds WebSocket Support and system monitor, while v2.14.0 adds visual indicator for GQL requests and copy/paste functionality for requests."}, {"option_id": "B", "text": "v2.13.0 adds gRPC Support and v2.14.0 adds WebSocket Support."}, {"option_id": "C", "text": "Both releases only contain bug fixes with no new features."}, {"option_id": "D", "text": "v2.13.0 adds HTTP Streaming and v2.14.0 adds OAuth 1.0 authentication."}], "correct_option_id": "A", "expected_answer": "v2.13.0 adds WebSocket Support and system monitor, while v2.14.0 adds visual indicator for GQL requests and copy/paste functionality for requests.", "source_chunk_ids": ["usebruno__bruno__release__v2_13_0", "usebruno__bruno__release__v2_14_0"], "answer_support": [{"memory_node_id": "usebruno__bruno__release__v2_13_0", "answer_text": "adds WebSocket Support, system monitor"}, {"memory_node_id": "usebruno__bruno__release__v2_14_0", "answer_text": "adds a visual indicator for GQL requests, copy and paste functionality for requests"}]}
{"prototype_id": "usebruno__bruno_release_window", "repo": "usebruno/bruno", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the usebruno/bruno release window, order the following release-content states from earliest to latest: (1) a release that introduces gRPC Support and Global Shortcuts for Zoom, Minimize, and Close on Windows, (2) a release that adds WebSocket Support and system monitor, (3) a release that adds visual indicator for GQL requests and copy/paste functionality for requests, (4) a release that adds HTTP Streaming and user prompt variables.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["usebruno__bruno__release__v2_10_0", "usebruno__bruno__release__v2_13_0", "usebruno__bruno__release__v2_14_0", "usebruno__bruno__release__v2_15_0"], "answer_support": [{"memory_node_id": "usebruno__bruno__release__v2_10_0", "answer_text": "introduces gRPC Support, Global Shortcuts for Zoom, Minimize, and Close on Windows"}, {"memory_node_id": "usebruno__bruno__release__v2_13_0", "answer_text": "adds WebSocket Support, system monitor"}, {"memory_node_id": "usebruno__bruno__release__v2_14_0", "answer_text": "adds visual indicator for GQL requests, copy and paste functionality for requests"}, {"memory_node_id": "usebruno__bruno__release__v2_15_0", "answer_text": "adds HTTP Streaming, user prompt variables"}]}
{"prototype_id": "usememos__memos_release_window", "repo": "usememos/memos", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the usememos/memos releases, which release introduces a calendar view on the Home page and removes the Timeline page?", "options": [{"option_id": "A", "text": "v0.22.3"}, {"option_id": "B", "text": "v0.22.4"}, {"option_id": "C", "text": "v0.22.5"}, {"option_id": "D", "text": "v0.23.0"}], "correct_option_id": "B", "expected_answer": "v0.22.4", "source_chunk_ids": ["usememos__memos__release__v0_22_4"], "answer_support": [{"memory_node_id": "usememos__memos__release__v0_22_4", "answer_text": "adds a calendar view on the Home page for reviewing recent activities, and removes the Timeline page."}]}
{"prototype_id": "usememos__memos_release_window", "repo": "usememos/memos", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the usememos/memos releases, how does the tag-related change in v0.22.0 differ from the tag-related change in v0.22.3?", "options": [{"option_id": "A", "text": "v0.22.0 refactors tags to display related memo counts and improve search, while v0.22.3 introduces displaying tags in a tree structure."}, {"option_id": "B", "text": "v0.22.0 introduces tag tree view, while v0.22.3 adds tag count display."}, {"option_id": "C", "text": "Both releases only add tag filtering for links and codes."}, {"option_id": "D", "text": "v0.22.0 removes tags entirely, while v0.22.3 reintroduces them with blur support."}], "correct_option_id": "A", "expected_answer": "v0.22.0 refactors tags to display related memo counts and improve search, while v0.22.3 introduces displaying tags in a tree structure.", "source_chunk_ids": ["usememos__memos__release__v0_22_0", "usememos__memos__release__v0_22_3"], "answer_support": [{"memory_node_id": "usememos__memos__release__v0_22_0", "answer_text": "refactoring tags to display related memo counts and improve search"}, {"memory_node_id": "usememos__memos__release__v0_22_3", "answer_text": "displaying tags in a tree structure"}]}
{"prototype_id": "usememos__memos_release_window", "repo": "usememos/memos", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the usememos/memos release window, order the following release-content states from earliest to latest: (1) a release that adds a masonry view (beta) and NSFW blur processing, (2) a release that introduces Shortcuts for filtering memos with comparison, set, string, and logical operators, (3) a release that adds infinite scrolling for memos and automatically adds a new table row in the editor when pressing enter.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3"}, {"option_id": "B", "text": "1 -> 2 -> 3"}, {"option_id": "C", "text": "3 -> 1 -> 2"}, {"option_id": "D", "text": "2 -> 3 -> 1"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3", "source_chunk_ids": ["usememos__memos__release__v0_24_0", "usememos__memos__release__v0_24_1", "usememos__memos__release__v0_24_4"], "answer_support": [{"memory_node_id": "usememos__memos__release__v0_24_0", "answer_text": "introduces Shortcuts for filtering memos based on conditions like tags, visibility, and timestamps with comparison, set, string, and logical operators"}, {"memory_node_id": "usememos__memos__release__v0_24_1", "answer_text": "adds a masonry view (beta) and supports blur processing for NSFW content with customizable NSFW tags"}, {"memory_node_id": "usememos__memos__release__v0_24_4", "answer_text": "adds infinite scrolling for memos and automatically adds a new table row in the editor when pressing enter"}]}
{"prototype_id": "utmapp__UTM_release_window", "repo": "utmapp/UTM", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the utmapp/UTM releases, which release introduces the UTM Remote server for macOS and UTM Remote client for iOS and visionOS?", "options": [{"option_id": "A", "text": "v4.4.0"}, {"option_id": "B", "text": "v4.5.0"}, {"option_id": "C", "text": "v4.6.0"}, {"option_id": "D", "text": "v4.7.0"}], "correct_option_id": "B", "expected_answer": "v4.5.0", "source_chunk_ids": ["utmapp__UTM__release__v4_5_0"], "answer_support": [{"memory_node_id": "utmapp__UTM__release__v4_5_0", "answer_text": "introduces UTM Remote server for macOS and UTM Remote client for iOS and visionOS"}]}
{"prototype_id": "utmapp__UTM_release_window", "repo": "utmapp/UTM", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the utmapp/UTM releases, how does the QEMU backend version differ between v4.3.5 and v4.6.0?", "options": [{"option_id": "A", "text": "v4.3.5 uses QEMU 7.2.0, while v4.6.0 uses QEMU 9.1.0."}, {"option_id": "B", "text": "v4.3.5 uses QEMU 8.0.2, while v4.6.0 uses QEMU 9.1.2."}, {"option_id": "C", "text": "Both use QEMU 8.0.2."}, {"option_id": "D", "text": "v4.3.5 uses QEMU 9.1.0, while v4.6.0 uses QEMU 7.2.0."}], "correct_option_id": "A", "expected_answer": "v4.3.5 uses QEMU 7.2.0, while v4.6.0 uses QEMU 9.1.0.", "source_chunk_ids": ["utmapp__UTM__release__v4_3_5", "utmapp__UTM__release__v4_6_0"], "answer_support": [{"memory_node_id": "utmapp__UTM__release__v4_3_5", "answer_text": "Rollback QEMU version to 7.2.0"}, {"memory_node_id": "utmapp__UTM__release__v4_6_0", "answer_text": "Updated to QEMU v9.1.0"}]}
{"prototype_id": "utmapp__UTM_release_window", "repo": "utmapp/UTM", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the utmapp/UTM release window, order the following release-content states from earliest to latest: (1) a release that rolls back QEMU to 7.2.0 due to a critical boot issue, (2) a release that introduces UTM Remote server and client, (3) a release that updates QEMU to v9.1.0 and adds nested virtualization for Linux on macOS 15.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2"}, {"option_id": "D", "text": "3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3", "source_chunk_ids": ["utmapp__UTM__release__v4_3_5", "utmapp__UTM__release__v4_5_0", "utmapp__UTM__release__v4_6_0"], "answer_support": [{"memory_node_id": "utmapp__UTM__release__v4_3_5", "answer_text": "Rollback QEMU version to 7.2.0"}, {"memory_node_id": "utmapp__UTM__release__v4_5_0", "answer_text": "introduces UTM Remote server for macOS and UTM Remote client for iOS and visionOS"}, {"memory_node_id": "utmapp__UTM__release__v4_6_0", "answer_text": "Updated to QEMU v9.1.0 ... nested virtualization for Linux"}]}
{"prototype_id": "v2ray__v2ray_core_release_window", "repo": "v2ray/v2ray-core", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the v2ray/v2ray-core releases, which release adds DNS over HTTPS (DOH) and ExpectIPs in DNS?", "options": [{"option_id": "A", "text": "v4.21.0"}, {"option_id": "B", "text": "v4.22.0"}, {"option_id": "C", "text": "v4.23.0"}, {"option_id": "D", "text": "v4.24.2"}], "correct_option_id": "B", "expected_answer": "v4.22.0", "source_chunk_ids": ["v2ray__v2ray_core__release__v4_22_0"], "answer_support": [{"memory_node_id": "v2ray__v2ray_core__release__v4_22_0", "answer_text": "adds DNS over HTTPS (DOH), ExpectIPs in DNS"}]}
{"prototype_id": "v2ray__v2ray_core_release_window", "repo": "v2ray/v2ray-core", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the v2ray/v2ray-core releases, how does the VMess security fix in v4.23.3 differ from the VMessAEAD experiment introduced in v4.24.2?", "options": [{"option_id": "A", "text": "v4.23.3 issues an emergency fix for a VMess weakness requiring only server update, while v4.24.2 begins a VMessAEAD header format experiment and introduces a taint mechanic for MD5 authentication data."}, {"option_id": "B", "text": "v4.23.3 adds VMessAEAD support, while v4.24.2 removes VMess entirely."}, {"option_id": "C", "text": "Both releases only update TLS cipher suites without VMess changes."}, {"option_id": "D", "text": "v4.23.3 introduces mKCP encryption, while v4.24.2 fixes a Windows ReadV issue."}], "correct_option_id": "A", "expected_answer": "v4.23.3 issues an emergency fix for a VMess weakness requiring only server update, while v4.24.2 begins a VMessAEAD header format experiment and introduces a taint mechanic for MD5 authentication data.", "source_chunk_ids": ["v2ray__v2ray_core__release__v4_23_3", "v2ray__v2ray_core__release__v4_24_2"], "answer_support": [{"memory_node_id": "v2ray__v2ray_core__release__v4_23_3", "answer_text": "Issued an emergency fix for VMess weakness described in v2ray#2523 ... Only servers need to be updated"}, {"memory_node_id": "v2ray__v2ray_core__release__v4_24_2", "answer_text": "VMess's new header format experiment begins. You can now enable VMessAEAD ... taint mechanic for VMess MD5 authentication data is introduced"}]}
{"prototype_id": "v2ray__v2ray_core_release_window", "repo": "v2ray/v2ray-core", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the v2ray/v2ray-core release window, order the following release-content states from earliest to latest: (1) a release that adds VLESS PREVIEW 1.3 and notes VMess AEAD will be used when alterId is 0 in v4.28.0+, (2) a release that issues an emergency fix for a VMess weakness and only requires server update, (3) a release that begins the VMessAEAD header format experiment and adds mKCP encryption, (4) a release that adds VLESS PREVIEW 2.4 and XTLS Direct Mode.", "options": [{"option_id": "A", "text": "2 -> 3 -> 1 -> 4"}, {"option_id": "B", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "C", "text": "3 -> 2 -> 4 -> 1"}, {"option_id": "D", "text": "2 -> 1 -> 3 -> 4"}], "correct_option_id": "A", "expected_answer": "2 -> 3 -> 1 -> 4", "source_chunk_ids": ["v2ray__v2ray_core__release__v4_23_3", "v2ray__v2ray_core__release__v4_24_2", "v2ray__v2ray_core__release__v4_27_0", "v2ray__v2ray_core__release__v4_31_0"], "answer_support": [{"memory_node_id": "v2ray__v2ray_core__release__v4_23_3", "answer_text": "Issued an emergency fix for VMess weakness"}, {"memory_node_id": "v2ray__v2ray_core__release__v4_24_2", "answer_text": "VMess's new header format experiment begins ... mKCP can now be encrypted"}, {"memory_node_id": "v2ray__v2ray_core__release__v4_27_0", "answer_text": "VLESS PREVIEW 1.3 ... VMess AEAD will be used when alterId is 0 in V2Ray v4.28.0+"}, {"memory_node_id": "v2ray__v2ray_core__release__v4_31_0", "answer_text": "VLESS PREVIEW 2.4 ... Add XTLS Direct Mode"}]}
{"prototype_id": "vadimdemedes__ink_release_window", "repo": "vadimdemedes/ink", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the vadimdemedes/ink releases, how does the change in v5.0.0 differ from the change in v6.0.0 regarding Node.js version requirements?", "options": [{"option_id": "A", "text": "v5.0.0 requires Node.js 18, while v6.0.0 requires Node.js 20."}, {"option_id": "B", "text": "v5.0.0 requires Node.js 20, while v6.0.0 requires Node.js 18."}, {"option_id": "C", "text": "Both releases require Node.js 18."}, {"option_id": "D", "text": "Neither release changes Node.js requirements."}], "correct_option_id": "A", "expected_answer": "v5.0.0 requires Node.js 18, while v6.0.0 requires Node.js 20.", "source_chunk_ids": ["vadimdemedes__ink__release__v5_0_0", "vadimdemedes__ink__release__v6_0_0"], "answer_support": [{"memory_node_id": "vadimdemedes__ink__release__v5_0_0", "answer_text": "Require Node.js 18"}, {"memory_node_id": "vadimdemedes__ink__release__v6_0_0", "answer_text": "Require Node.js 20"}]}
{"prototype_id": "vadimdemedes__ink_release_window", "repo": "vadimdemedes/ink", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the vadimdemedes/ink release window, order the following release-content states from earliest to latest: (1) a release that adds screen reader and ARIA support, (2) a release that adds `backgroundColor` support to the `Box` component, (3) a release that fixes screen reader static rendering.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3"}, {"option_id": "B", "text": "1 -> 2 -> 3"}, {"option_id": "C", "text": "2 -> 3 -> 1"}, {"option_id": "D", "text": "3 -> 1 -> 2"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3", "source_chunk_ids": ["vadimdemedes__ink__release__v6_1_0", "vadimdemedes__ink__release__v6_2_0", "vadimdemedes__ink__release__v6_2_2"], "answer_support": [{"memory_node_id": "vadimdemedes__ink__release__v6_1_0", "answer_text": "adds `backgroundColor` support to the `Box` component"}, {"memory_node_id": "vadimdemedes__ink__release__v6_2_0", "answer_text": "adds screen reader and ARIA support"}, {"memory_node_id": "vadimdemedes__ink__release__v6_2_2", "answer_text": "fixes screen reader static rendering"}]}
{"prototype_id": "valkey_io__valkey_release_window", "repo": "valkey-io/valkey", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the valkey-io/valkey releases, which release introduces atomic slot migration and hash field expiration?", "options": [{"option_id": "A", "text": "Valkey 8.1.0"}, {"option_id": "B", "text": "Valkey 9.0.0-rc1"}, {"option_id": "C", "text": "Valkey 9.0.0"}, {"option_id": "D", "text": "Valkey 9.1.0-rc1"}], "correct_option_id": "B", "expected_answer": "Valkey 9.0.0-rc1", "source_chunk_ids": ["valkey_io__valkey__release__9_0_0_rc1"], "answer_support": [{"memory_node_id": "valkey_io__valkey__release__9_0_0_rc1", "answer_text": "This is the first release candidate of Valkey 9.0.0, with performance improvements, atomic slot migrations, hash field expiration, and numbered databases in cluster mode."}]}
{"prototype_id": "vapor__vapor_release_window", "repo": "vapor/vapor", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the vapor/vapor releases, which release introduces a new VaporTesting module for better compatibility with Swift Testing?", "options": [{"option_id": "A", "text": "4.109.0"}, {"option_id": "B", "text": "4.110.0"}, {"option_id": "C", "text": "4.111.0"}, {"option_id": "D", "text": "4.112.0"}], "correct_option_id": "B", "expected_answer": "4.110.0", "source_chunk_ids": ["vapor__vapor__release__4_110_0"], "answer_support": [{"memory_node_id": "vapor__vapor__release__4_110_0", "answer_text": "introduces a new VaporTesting module for better compatibility with Swift Testing"}]}
{"prototype_id": "vapor__vapor_release_window", "repo": "vapor/vapor", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the vapor/vapor releases, how does the change in release 4.112.1 differ from the change in release 4.113.1?", "options": [{"option_id": "A", "text": "4.112.1 configures the global singleton NIOThreadPool as default to reduce threads, while 4.113.1 prevents a stack overflow by replacing NIOLockedValueBox with NIOLock during service initialization."}, {"option_id": "B", "text": "4.112.1 adds Android support, while 4.113.1 fixes Sendable warnings from NIO 2.79.0."}, {"option_id": "C", "text": "Both releases only update documentation without functional changes."}, {"option_id": "D", "text": "4.112.1 deprecates Application.init(), while 4.113.1 adds a Custom validator."}], "correct_option_id": "A", "expected_answer": "4.112.1 configures the global singleton NIOThreadPool as default to reduce threads, while 4.113.1 prevents a stack overflow by replacing NIOLockedValueBox with NIOLock during service initialization.", "source_chunk_ids": ["vapor__vapor__release__4_112_1", "vapor__vapor__release__4_113_1"], "answer_support": [{"memory_node_id": "vapor__vapor__release__4_112_1", "answer_text": "configures the global singleton NIOThreadPool as the default, eliminating an additional thread pool"}, {"memory_node_id": "vapor__vapor__release__4_113_1", "answer_text": "prevents a stack overflow during service initialization by replacing NIOLockedValueBox with NIOLock"}]}
{"prototype_id": "vapor__vapor_release_window", "repo": "vapor/vapor", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the vapor/vapor release window, order the following release-content states from earliest to latest: (1) a release that adds experimental Android support, (2) a release that updates the minimum Swift version to 6.0, (3) a release that exposes peer certificates in request handlers, (4) a release that fixes compatibility with swift-log 1.8.0 and later.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 4 -> 3"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["vapor__vapor__release__4_112_2", "vapor__vapor__release__4_118_0", "vapor__vapor__release__4_119_0", "vapor__vapor__release__4_120_0"], "answer_support": [{"memory_node_id": "vapor__vapor__release__4_112_2", "answer_text": "adds experimental support for building and testing on Android"}, {"memory_node_id": "vapor__vapor__release__4_118_0", "answer_text": "updates the minimum Swift version to 6.0"}, {"memory_node_id": "vapor__vapor__release__4_119_0", "answer_text": "exposes peer certificates in request handlers"}, {"memory_node_id": "vapor__vapor__release__4_120_0", "answer_text": "fixes compatibility with swift-log 1.8.0 and later"}]}
{"prototype_id": "vectordotdev__vector_release_window", "repo": "vectordotdev/vector", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the vectordotdev/vector releases, which release introduces a new websocket source and templating support for the http sink's uri and request.headers config fields?", "options": [{"option_id": "A", "text": "v0.49.0"}, {"option_id": "B", "text": "v0.50.0"}, {"option_id": "C", "text": "v0.51.0"}, {"option_id": "D", "text": "v0.52.0"}], "correct_option_id": "A", "expected_answer": "v0.49.0", "source_chunk_ids": ["vectordotdev__vector__release__v0_49_0"], "answer_support": [{"memory_node_id": "vectordotdev__vector__release__v0_49_0", "answer_text": "Highlights include a new websocket source, templating support for the http sink's uri and request.headers config fields"}]}
{"prototype_id": "vectordotdev__vector_release_window", "repo": "vectordotdev/vector", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the vectordotdev/vector releases, how does the observability API change described in v0.55.0 differ from the internal telemetry improvements described in v0.51.0?", "options": [{"option_id": "A", "text": "v0.55.0 moves the observability API from GraphQL to gRPC, while v0.51.0 fixes negative utilization metrics and buffer counter underflows."}, {"option_id": "B", "text": "v0.55.0 introduces the otlp codec, while v0.51.0 adds the websocket source."}, {"option_id": "C", "text": "Both releases only update the datadog_logs sink compression default."}, {"option_id": "D", "text": "v0.55.0 deprecates the azure_monitor_logs sink, while v0.51.0 removes the GraphQL API."}], "correct_option_id": "A", "expected_answer": "v0.55.0 moves the observability API from GraphQL to gRPC, while v0.51.0 fixes negative utilization metrics and buffer counter underflows.", "source_chunk_ids": ["vectordotdev__vector__release__v0_55_0", "vectordotdev__vector__release__v0_51_0"], "answer_support": [{"memory_node_id": "vectordotdev__vector__release__v0_55_0", "answer_text": "the observability API has moved from GraphQL to gRPC"}, {"memory_node_id": "vectordotdev__vector__release__v0_51_0", "answer_text": "improved internal telemetry fixing negative utilization metrics and buffer counter underflows"}]}
{"prototype_id": "vectordotdev__vector_release_window", "repo": "vectordotdev/vector", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the vectordotdev/vector release window, order the following release-content states from earliest to latest: (1) a release that introduces a new websocket source and templating support for the http sink, (2) a release that introduces the otlp codec for bidirectional conversion between Vector events and OTLP format, (3) a release that introduces a new windows_event_log source and the aws_s3 sink supporting Apache Parquet batch encoding, (4) a release that introduces the trace_to_log transform and new buffer utilization metrics for sources and transforms.", "options": [{"option_id": "A", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "C", "text": "1 -> 4 -> 2 -> 3"}, {"option_id": "D", "text": "4 -> 1 -> 2 -> 3"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 4 -> 3", "source_chunk_ids": ["vectordotdev__vector__release__v0_49_0", "vectordotdev__vector__release__v0_51_0", "vectordotdev__vector__release__v0_52_0", "vectordotdev__vector__release__v0_55_0"], "answer_support": [{"memory_node_id": "vectordotdev__vector__release__v0_49_0", "answer_text": "new websocket source, templating support for the http sink's uri and request.headers config fields"}, {"memory_node_id": "vectordotdev__vector__release__v0_51_0", "answer_text": "otlp codec enabling bidirectional conversion between Vector events and OTLP format"}, {"memory_node_id": "vectordotdev__vector__release__v0_52_0", "answer_text": "trace_to_log transform, new buffer utilization metrics for sources and transforms"}, {"memory_node_id": "vectordotdev__vector__release__v0_55_0", "answer_text": "new windows_event_log source, aws_s3 sink supporting Apache Parquet batch encoding"}]}
{"prototype_id": "ventoy__Ventoy_release_window", "repo": "ventoy/Ventoy", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the ventoy/Ventoy releases, which release adds experimental support for btrfs file system with the limitation that ISO files cannot be compressed?", "options": [{"option_id": "A", "text": "v1.1.08"}, {"option_id": "B", "text": "v1.1.09"}, {"option_id": "C", "text": "v1.1.10"}, {"option_id": "D", "text": "v1.1.11"}], "correct_option_id": "B", "expected_answer": "v1.1.09", "source_chunk_ids": ["ventoy__Ventoy__release__v1_1_09"], "answer_support": [{"memory_node_id": "ventoy__Ventoy__release__v1_1_09", "answer_text": "Experimental support for btrfs file system. ... ISO file can NOT be compressed."}]}
{"prototype_id": "ventoy__Ventoy_release_window", "repo": "ventoy/Ventoy", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the ventoy/Ventoy releases, how does the handling of VTOY_LINUX_REMOUNT differ between v1.0.99 and v1.1.01?", "options": [{"option_id": "A", "text": "v1.0.99 fixes VTOY_LINUX_REMOUNT for openSUSE, while v1.1.01 optimizes the implementation to support all Linux distros and deprecates the option."}, {"option_id": "B", "text": "v1.0.99 removes VTOY_LINUX_REMOUNT entirely, while v1.1.01 reintroduces it for legacy systems."}, {"option_id": "C", "text": "Both releases only update EFI boot files without changing VTOY_LINUX_REMOUNT."}, {"option_id": "D", "text": "v1.0.99 adds VTOY_LINUX_REMOUNT for the first time, while v1.1.01 restricts it to RHEL9/CentOS9."}], "correct_option_id": "A", "expected_answer": "v1.0.99 fixes VTOY_LINUX_REMOUNT for openSUSE, while v1.1.01 optimizes the implementation to support all Linux distros and deprecates the option.", "source_chunk_ids": ["ventoy__Ventoy__release__v1_0_99", "ventoy__Ventoy__release__v1_1_01"], "answer_support": [{"memory_node_id": "ventoy__Ventoy__release__v1_0_99", "answer_text": "Fix the issue that VTOY_LINUX_REMOUNT can not take effect in latest openSUSE."}, {"memory_node_id": "ventoy__Ventoy__release__v1_1_01", "answer_text": "Optimization for VTOY_LINUX_REMOUNT implementation to support all Linux distros. ... VTOY_LINUX_REMOUNT option now is deprecated."}]}
{"prototype_id": "ventoy__Ventoy_release_window", "repo": "ventoy/Ventoy", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the ventoy/Ventoy release window, order the following release-content states from earliest to latest: (1) a release that adds multi-language support for the Ventoy boot menu, (2) a release that fixes the 0x80070001 error when booting and installing Windows 11, (3) a release that adds support for FreeBSD 15.0, (4) a release that adds experimental btrfs support.", "options": [{"option_id": "A", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "B", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "C", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "D", "text": "1 -> 3 -> 2 -> 4"}], "correct_option_id": "B", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["ventoy__Ventoy__release__v1_0_84", "ventoy__Ventoy__release__v1_1_04", "ventoy__Ventoy__release__v1_1_08", "ventoy__Ventoy__release__v1_1_09"], "answer_support": [{"memory_node_id": "ventoy__Ventoy__release__v1_0_84", "answer_text": "Multi-Language supported for Ventoy boot menu."}, {"memory_node_id": "ventoy__Ventoy__release__v1_1_04", "answer_text": "Fix the 0x80070001 error when boot and install Windows 11."}, {"memory_node_id": "ventoy__Ventoy__release__v1_1_08", "answer_text": "Add support for FreeBSD 15.0"}, {"memory_node_id": "ventoy__Ventoy__release__v1_1_09", "answer_text": "Experimental support for btrfs file system."}]}
{"prototype_id": "vercel__next_js_release_window", "repo": "vercel/next.js", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the vercel/next.js releases, which release adds a graph-based CSS chunking algorithm behind experimental.cssChunking: \"graph\"?", "options": [{"option_id": "A", "text": "v16.3.0-canary.23"}, {"option_id": "B", "text": "v16.3.0-canary.24"}, {"option_id": "C", "text": "v16.3.0-canary.25"}, {"option_id": "D", "text": "v16.3.0-canary.26"}], "correct_option_id": "A", "expected_answer": "v16.3.0-canary.23", "source_chunk_ids": ["vercel__next_js__release__v16_3_0_canary_23"], "answer_support": [{"memory_node_id": "vercel__next_js__release__v16_3_0_canary_23", "answer_text": "add a graph-based CSS chunking algorithm behind experimental.cssChunking: graph"}]}
{"prototype_id": "vercel__next_js_release_window", "repo": "vercel/next.js", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the vercel/next.js releases, how does the security fix content in v16.2.6 differ from the security fix content in v15.5.18?", "options": [{"option_id": "A", "text": "v16.2.6 includes security fixes and additional core changes like fixing HTTP access fallbacks and double-encoding of URL pathname parts, while v15.5.18 only contains security fixes without additional core changes."}, {"option_id": "B", "text": "v16.2.6 only contains security fixes, while v15.5.18 includes both security fixes and core changes."}, {"option_id": "C", "text": "Both releases contain identical security fixes and core changes."}, {"option_id": "D", "text": "v16.2.6 contains no security fixes, while v15.5.18 contains all security fixes."}], "correct_option_id": "A", "expected_answer": "v16.2.6 includes security fixes and additional core changes like fixing HTTP access fallbacks and double-encoding of URL pathname parts, while v15.5.18 only contains security fixes without additional core changes.", "source_chunk_ids": ["vercel__next_js__release__v16_2_6", "vercel__next_js__release__v15_5_18"], "answer_support": [{"memory_node_id": "vercel__next_js__release__v16_2_6", "answer_text": "security fixes address multiple high, moderate, and low severity advisories ... Core changes fix HTTP access fallbacks during prerender recovery, fallback route params, invalid HTML responses, setHeader patching, deployment id in cacheHandlers keys, and double-encoding of URL pathname parts"}, {"memory_node_id": "vercel__next_js__release__v15_5_18", "answer_text": "security fixes address high, moderate, and low severity advisories"}]}
{"prototype_id": "VictoriaMetrics__VictoriaMetrics_release_window", "repo": "VictoriaMetrics/VictoriaMetrics", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the VictoriaMetrics/VictoriaMetrics releases, which release adds a 'Queries with most memory to execute' section in vmui Top Queries and context-aware label value autocomplete?", "options": [{"option_id": "A", "text": "v1.136.0"}, {"option_id": "B", "text": "v1.137.0"}, {"option_id": "C", "text": "v1.138.0"}, {"option_id": "D", "text": "v1.139.0"}], "correct_option_id": "A", "expected_answer": "v1.136.0", "source_chunk_ids": ["VictoriaMetrics__VictoriaMetrics__release__v1_136_0"], "answer_support": [{"memory_node_id": "VictoriaMetrics__VictoriaMetrics__release__v1_136_0", "answer_text": "adds a 'Queries with most memory to execute' section in vmui Top Queries and context-aware label value autocomplete in vmui"}]}
{"prototype_id": "vikejs__vike_release_window", "repo": "vikejs/vike", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the vikejs/vike releases, which release introduces the +onData feature?", "options": [{"option_id": "A", "text": "v0.4.229"}, {"option_id": "B", "text": "v0.4.230"}, {"option_id": "C", "text": "v0.4.231"}, {"option_id": "D", "text": "v0.4.232"}], "correct_option_id": "B", "expected_answer": "v0.4.230", "source_chunk_ids": ["vikejs__vike__release__v0_4_230"], "answer_support": [{"memory_node_id": "vikejs__vike__release__v0_4_230", "answer_text": "introduces the +onData feature"}]}
{"prototype_id": "vikejs__vike_release_window", "repo": "vikejs/vike", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the vikejs/vike releases, how does the change to +onCreatePageContext in v0.4.233 differ from the change to +onHookCall in v0.4.253?", "options": [{"option_id": "A", "text": "v0.4.233 makes +onCreatePageContext execute after routing, while v0.4.253 makes +onHookCall server-only by default."}, {"option_id": "B", "text": "v0.4.233 makes +onCreatePageContext execute before routing, while v0.4.253 makes +onHookCall client-only by default."}, {"option_id": "C", "text": "Both releases remove the respective hooks entirely."}, {"option_id": "D", "text": "v0.4.233 adds +onCreatePageContext, while v0.4.253 removes +onHookCall."}], "correct_option_id": "A", "expected_answer": "v0.4.233 makes +onCreatePageContext execute after routing, while v0.4.253 makes +onHookCall server-only by default.", "source_chunk_ids": ["vikejs__vike__release__v0_4_233", "vikejs__vike__release__v0_4_253"], "answer_support": [{"memory_node_id": "vikejs__vike__release__v0_4_233", "answer_text": "+onCreatePageContext is now called after routing"}, {"memory_node_id": "vikejs__vike__release__v0_4_253", "answer_text": "+onHookCall is now server-only by default"}]}
{"prototype_id": "vikejs__vike_release_window", "repo": "vikejs/vike", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the vikejs/vike release window, order the following release-content states from earliest to latest: (1) a release that introduces +headersResponse and pageContext.headersResponse, (2) a release that introduces +onHookCall, (3) a release that introduces built-in +server support via Universal Deploy, (4) a release that introduces +staticReplace.", "options": [{"option_id": "A", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "B", "text": "1 -> 4 -> 2 -> 3"}, {"option_id": "C", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "D", "text": "4 -> 1 -> 2 -> 3"}], "correct_option_id": "B", "expected_answer": "1 -> 4 -> 2 -> 3", "source_chunk_ids": ["vikejs__vike__release__v0_4_236", "vikejs__vike__release__v0_4_250", "vikejs__vike__release__v0_4_251", "vikejs__vike__release__v0_4_257"], "answer_support": [{"memory_node_id": "vikejs__vike__release__v0_4_236", "answer_text": "introduces +headersResponse and pageContext.headersResponse"}, {"memory_node_id": "vikejs__vike__release__v0_4_250", "answer_text": "introduces +staticReplace"}, {"memory_node_id": "vikejs__vike__release__v0_4_251", "answer_text": "introduces +onHookCall"}, {"memory_node_id": "vikejs__vike__release__v0_4_257", "answer_text": "introduces built-in +server support via Universal Deploy"}]}
{"prototype_id": "vuejs__vue_release_window", "repo": "vuejs/vue", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the vuejs/vue releases, which release note explicitly states that it is the final release for Vue 2 and mentions the End of Life date?", "options": [{"option_id": "A", "text": "v2.7.0 \"Naruto\""}, {"option_id": "B", "text": "v2.7.15"}, {"option_id": "C", "text": "v2.7.16 \"Swan Song\""}, {"option_id": "D", "text": "v2.7.16-beta.2"}], "correct_option_id": "C", "expected_answer": "v2.7.16 \"Swan Song\"", "source_chunk_ids": ["vuejs__vue__release__v2_7_16"], "answer_support": [{"memory_node_id": "vuejs__vue__release__v2_7_16", "answer_text": "This is the final release for Vue 2. Vue 2 will reach End of Life on December 31st, 2023."}]}
{"prototype_id": "webpack__webpack_release_window", "repo": "webpack/webpack", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the webpack/webpack releases, which release introduces the VirtualUrlPlugin to support the 'virtual:' scheme?", "options": [{"option_id": "A", "text": "v5.99.6"}, {"option_id": "B", "text": "v5.100.0"}, {"option_id": "C", "text": "v5.101.0"}, {"option_id": "D", "text": "v5.102.0"}], "correct_option_id": "B", "expected_answer": "v5.100.0", "source_chunk_ids": ["webpack__webpack__release__v5_100_0"], "answer_support": [{"memory_node_id": "webpack__webpack__release__v5_100_0", "answer_text": "Added VirtualUrlPlugin to support 'virtual:' scheme"}]}
{"prototype_id": "webpack__webpack_release_window", "repo": "webpack/webpack", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the webpack/webpack releases, how does the CSS modules improvement in v5.106.0 differ from the CSS modules improvement in v5.107.0?", "options": [{"option_id": "A", "text": "v5.106.0 adds exportType: \"style\" for CSS modules, while v5.107.0 supports module concatenation for CSS modules with various export types."}, {"option_id": "B", "text": "v5.106.0 removes CSS modules support, while v5.107.0 reintroduces it."}, {"option_id": "C", "text": "Both releases only fix CSS parsing bugs without adding new features."}, {"option_id": "D", "text": "v5.106.0 adds CSS @import support, while v5.107.0 adds CSS @value support."}], "correct_option_id": "A", "expected_answer": "v5.106.0 adds exportType: \"style\" for CSS modules, while v5.107.0 supports module concatenation for CSS modules with various export types.", "source_chunk_ids": ["webpack__webpack__release__v5_106_0", "webpack__webpack__release__v5_107_0"], "answer_support": [{"memory_node_id": "webpack__webpack__release__v5_106_0", "answer_text": "Add exportType: \"style\" for CSS modules to inject styles into DOM via HTMLStyleElement"}, {"memory_node_id": "webpack__webpack__release__v5_107_0", "answer_text": "Support module concatenation (scope hoisting) for CSS modules with text, css-style-sheet, style, and link export types"}]}
{"prototype_id": "webpack__webpack_release_window", "repo": "webpack/webpack", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the webpack/webpack release window, order the following release-content states from earliest to latest: (1) a release that fixes dead control flow with deep nested if/else, (2) a release that adds support for the 'using' keyword, (3) a release that adds experimental TypeScript support via experiments.typescript: true, (4) a release that fixes a user information bypass vulnerability in the HttpUriPlugin plugin.", "options": [{"option_id": "A", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "B", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "C", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 4 -> 3", "source_chunk_ids": ["webpack__webpack__release__v5_99_3", "webpack__webpack__release__v5_100_0", "webpack__webpack__release__v5_104_1", "webpack__webpack__release__v5_107_0"], "answer_support": [{"memory_node_id": "webpack__webpack__release__v5_99_3", "answer_text": "Fixed dead control flow with deep nested if/else"}, {"memory_node_id": "webpack__webpack__release__v5_100_0", "answer_text": "Added support 'using' keyword"}, {"memory_node_id": "webpack__webpack__release__v5_104_1", "answer_text": "Fixed a user information bypass vulnerability in the HttpUriPlugin plugin"}, {"memory_node_id": "webpack__webpack__release__v5_107_0", "answer_text": "Add experimental TypeScript support via experiments.typescript: true"}]}
{"prototype_id": "WerWolv__ImHex_release_window", "repo": "WerWolv/ImHex", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the WerWolv/ImHex releases, which release introduces a save editor mode and simplified pattern editor using the [[hex::editor_export]] attribute?", "options": [{"option_id": "A", "text": "v1.38.0"}, {"option_id": "B", "text": "v1.37.0"}, {"option_id": "C", "text": "v1.36.0"}, {"option_id": "D", "text": "v1.35.0"}], "correct_option_id": "A", "expected_answer": "v1.38.0", "source_chunk_ids": ["WerWolv__ImHex__release__v1_38_0"], "answer_support": [{"memory_node_id": "WerWolv__ImHex__release__v1_38_0", "answer_text": "It introduces a save editor mode and simplified pattern editor using [[hex::editor_export]]"}]}
{"prototype_id": "WerWolv__ImHex_release_window", "repo": "WerWolv/ImHex", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the WerWolv/ImHex release window, order the following release-content states from earliest to latest: (1) a release that adds a pattern language debugger and export of generated pattern data, (2) a release that adds a command line interface and .NET scripts, (3) a release that adds web and M1 builds along with workspaces and automatic backups, (4) a release that adds a save editor mode and SSH/UDP data sources.", "options": [{"option_id": "A", "text": "1 -> 2 -> 3 -> 4"}, {"option_id": "B", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "C", "text": "1 -> 3 -> 2 -> 4"}, {"option_id": "D", "text": "4 -> 3 -> 2 -> 1"}], "correct_option_id": "A", "expected_answer": "1 -> 2 -> 3 -> 4", "source_chunk_ids": ["WerWolv__ImHex__release__v1_30_0", "WerWolv__ImHex__release__v1_31_0", "WerWolv__ImHex__release__v1_32_0", "WerWolv__ImHex__release__v1_38_0"], "answer_support": [{"memory_node_id": "WerWolv__ImHex__release__v1_30_0", "answer_text": "Added a debugger to debug your pattern code... Added option to export generated pattern data"}, {"memory_node_id": "WerWolv__ImHex__release__v1_31_0", "answer_text": "Added a command line interface to ImHex... Added initial support for .NET scripts"}, {"memory_node_id": "WerWolv__ImHex__release__v1_32_0", "answer_text": "ImHex is now available for the Web!... ImHex now has a native Apple M1 build!... Added Workspaces... Added automatic backups"}, {"memory_node_id": "WerWolv__ImHex__release__v1_38_0", "answer_text": "Added a new Save Editor Mode and Simplified Pattern Editor... Added multiple new Data Sources... A UDP Provider... A SSH Provider"}]}
{"prototype_id": "withastro__astro_release_window", "repo": "withastro/astro", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the withastro/astro releases, which release introduces a new markdown.processor configuration option and a Rust-based Markdown processor called Sätteri?", "options": [{"option_id": "A", "text": "astro@6.3.4"}, {"option_id": "B", "text": "astro@6.4.0"}, {"option_id": "C", "text": "astro@6.3.8"}, {"option_id": "D", "text": "astro@6.4.2"}], "correct_option_id": "B", "expected_answer": "astro@6.4.0", "source_chunk_ids": ["withastro__astro__release__astro_6_4_0"], "answer_support": [{"memory_node_id": "withastro__astro__release__astro_6_4_0", "answer_text": "introduces a new markdown.processor configuration option allowing alternative Markdown processors including the Rust-based Sätteri processor"}]}
{"prototype_id": "withastro__astro_release_window", "repo": "withastro/astro", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the withastro/astro releases, how does the fix for stale content in the dev server differ between astro@6.3.5 and astro@6.3.6?", "options": [{"option_id": "A", "text": "6.3.5 fixes stale content when SSR-only modules change, while 6.3.6 fixes stale content when components are passed as props via getStaticPaths and through barrel files."}, {"option_id": "B", "text": "6.3.5 fixes stale content for dynamically imported components, while 6.3.6 fixes stale content for SSR-only modules."}, {"option_id": "C", "text": "Both releases fix the same stale content issue for SSR-only modules."}, {"option_id": "D", "text": "6.3.5 fixes stale content for barrel files, while 6.3.6 fixes stale content for getStaticPaths."}], "correct_option_id": "A", "expected_answer": "6.3.5 fixes stale content when SSR-only modules change, while 6.3.6 fixes stale content when components are passed as props via getStaticPaths and through barrel files.", "source_chunk_ids": ["withastro__astro__release__astro_6_3_5", "withastro__astro__release__astro_6_3_6"], "answer_support": [{"memory_node_id": "withastro__astro__release__astro_6_3_5", "answer_text": "fixes dev server serving stale content when SSR-only modules change"}, {"memory_node_id": "withastro__astro__release__astro_6_3_6", "answer_text": "fixes HMR serving stale content when components are passed as props via getStaticPaths ... fixes HMR serving stale content for dynamically imported components through barrel files"}]}
{"prototype_id": "withastro__astro_release_window", "repo": "withastro/astro", "question_id": "q3_temporal_version_ordering", "task_type": "temporal_version_ordering", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "In the withastro/astro release window, order the following release-content states from earliest to latest: (1) a release that fixes request body handling in the Node adapter for binary data, (2) a release that adds a fetchFile option to experimental.advancedRouting, (3) a release that introduces the markdown.processor configuration option, (4) a release that fixes a plugins is not iterable crash with pre-6.0 @astrojs/mdx.", "options": [{"option_id": "A", "text": "2 -> 1 -> 3 -> 4"}, {"option_id": "B", "text": "1 -> 2 -> 4 -> 3"}, {"option_id": "C", "text": "2 -> 3 -> 1 -> 4"}, {"option_id": "D", "text": "3 -> 2 -> 1 -> 4"}], "correct_option_id": "A", "expected_answer": "2 -> 1 -> 3 -> 4", "source_chunk_ids": ["withastro__astro__release__astro_6_3_4", "withastro__astro__release__astro_6_3_7", "withastro__astro__release__astro_6_4_0", "withastro__astro__release__astro_6_4_2"], "answer_support": [{"memory_node_id": "withastro__astro__release__astro_6_3_4", "answer_text": "adds a fetchFile option to experimental.advancedRouting"}, {"memory_node_id": "withastro__astro__release__astro_6_3_7", "answer_text": "fixes request body handling in the Node adapter when req.body is a Buffer, Uint8Array, or ArrayBuffer"}, {"memory_node_id": "withastro__astro__release__astro_6_4_0", "answer_text": "introduces a new markdown.processor configuration option"}, {"memory_node_id": "withastro__astro__release__astro_6_4_2", "answer_text": "fixes a plugins is not iterable crash when using a pre-6.0 @astrojs/mdx"}]}
{"prototype_id": "yeasy__docker_practice_release_window", "repo": "yeasy/docker_practice", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the yeasy/docker_practice releases, which release adds the CI/CD tool Drone and the docker secret command?", "options": [{"option_id": "A", "text": "v0.9.0-rc1"}, {"option_id": "B", "text": "v0.9.0-rc2"}, {"option_id": "C", "text": "v0.9.0"}, {"option_id": "D", "text": "v1.1.0"}], "correct_option_id": "B", "expected_answer": "v0.9.0-rc2", "source_chunk_ids": ["yeasy__docker_practice__release__v0_9_rc2"], "answer_support": [{"memory_node_id": "yeasy__docker_practice__release__v0_9_rc2", "answer_text": "增加介绍基于 Docker 的 CI/CD 工具 Drone ... 增加 docker secret 相关内容"}]}
{"prototype_id": "yeasy__docker_practice_release_window", "repo": "yeasy/docker_practice", "question_id": "q2_cross_version_comparison", "task_type": "cross_version_comparison", "difficulty": "high", "answer_format": "multiple_choice", "query_text": "Across the yeasy/docker_practice releases, how does the content change described in v0.5.0 differ from the content change described in v1.1.0?", "options": [{"option_id": "A", "text": "v0.5.0 adds Compose, Machine, Swarm, and Mesos projects, while v1.1.0 adds BuildKit, docker buildx, and docker manifest, and removes older OS support."}, {"option_id": "B", "text": "v0.5.0 removes Docker Swarm content, while v1.1.0 adds Docker Swarm content."}, {"option_id": "C", "text": "Both releases only fix typos and formatting."}, {"option_id": "D", "text": "v0.5.0 introduces Docker CE v17.MM revision, while v1.1.0 introduces Docker CE v19.x revision."}], "correct_option_id": "A", "expected_answer": "v0.5.0 adds Compose, Machine, Swarm, and Mesos projects, while v1.1.0 adds BuildKit, docker buildx, and docker manifest, and removes older OS support.", "source_chunk_ids": ["yeasy__docker_practice__release__v0_5", "yeasy__docker_practice__release__v1_1_0"], "answer_support": [{"memory_node_id": "yeasy__docker_practice__release__v0_5", "answer_text": "添加 Compose 项目 ... 添加 Machine 项目 ... 添加 Swarm 项目 ... 添加 Mesos 项目内容"}, {"memory_node_id": "yeasy__docker_practice__release__v1_1_0", "answer_text": "增加 BuildKit ... 增加 docker buildx 命令使用说明 ... 增加 docker manifest 命令使用说明 ... 移除 Ubuntu 14.04 Debian 8 Debian 7"}]}
{"prototype_id": "yewstack__yew_release_window", "repo": "yewstack/yew", "question_id": "q1_single_state_lookup", "task_type": "single_state_lookup", "difficulty": "low", "answer_format": "multiple_choice", "query_text": "In the yewstack/yew releases, which release introduces Future support allowing a Component to update after a Future completes?", "options": [{"option_id": "A", "text": "0.10.0"}, {"option_id": "B", "text": "0.11.0"}, {"option_id": "C", "text": "0.12.0"}, {"option_id": "D", "text": "0.13.0"}], "correct_option_id": "A", "expected_answer": "0.10.0", "source_chunk_ids": ["yewstack__yew__release__0_10_0"], "answer_support": [{"memory_node_id": "yewstack__yew__release__0_10_0", "answer_text": "introduces Future support allowing a Component to update after a Future completes"}]}