prototype_id stringlengths 23 50 | repo stringlengths 7 34 | question_id stringclasses 3
values | task_type stringclasses 3
values | difficulty stringclasses 2
values | answer_format stringclasses 1
value | query_text stringlengths 70 637 | options listlengths 4 4 | correct_option_id stringclasses 4
values | expected_answer stringlengths 4 263 | source_chunk_ids listlengths 1 4 | answer_support listlengths 1 4 |
|---|---|---|---|---|---|---|---|---|---|---|---|
2dust__v2rayNG_release_window | 2dust/v2rayNG | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the 2dust/v2rayNG releases, which release introduces WebDAV remote backup and a new tabbed main interface for grouping by subscription? | [
{
"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"
}
] | A | 2.0.13 | [
"2dust__v2rayNG__release__2_0_13"
] | [
{
"memory_node_id": "2dust__v2rayNG__release__2_0_13",
"answer_text": "WebDAV remote backup, a new tabbed main interface for grouping by subscription"
}
] |
2dust__v2rayNG_release_window | 2dust/v2rayNG | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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 subscrip... | [
{
"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"
}
] | A | 4 -> 1 -> 2 -> 3 | [
"2dust__v2rayNG__release__2_0_15",
"2dust__v2rayNG__release__2_1_5",
"2dust__v2rayNG__release__2_1_6",
"2dust__v2rayNG__release__2_2_1"
] | [
{
"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 ... |
aaif_goose__goose_release_window | aaif-goose/goose | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the aaif-goose/goose releases, which release introduces slash commands such as /prompts, /prompt, /compact, and /clear? | [
{
"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"
}
] | B | v1.18.0 | [
"aaif_goose__goose__release__v1_18_0"
] | [
{
"memory_node_id": "aaif_goose__goose__release__v1_18_0",
"answer_text": "slash commands are introduced: /prompts, /prompt, /compact, /clear"
}
] |
agno_agi__agno_release_window | agno-agi/agno | q1_single_state_lookup | single_state_lookup | low | multiple_choice | 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? | [
{
"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"
}
] | B | v2.5.0 | [
"agno_agi__agno__release__v2_5_0"
] | [
{
"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"
}
] |
agno_agi__agno_release_window | agno-agi/agno | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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 re... | A | 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. | [
"agno_agi__agno__release__v2_5_2",
"agno_agi__agno__release__v2_6_0"
] | [
{
"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 sessio... |
agno_agi__agno_release_window | agno-agi/agno | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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 a... | [
{
"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"
}
] | A | 1 -> 2 -> 3 -> 4 | [
"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"
] | [
{
"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"
... |
Aider_AI__aider_release_window | Aider-AI/aider | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the Aider-AI/aider releases, which release introduces the Architect/Editor model pair for improved coding? | [
{
"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"
}
] | B | v0.58.0 | [
"Aider_AI__aider__release__v0_58_0"
] | [
{
"memory_node_id": "Aider_AI__aider__release__v0_58_0",
"answer_text": "a pair of Architect/Editor models for improved coding"
}
] |
Aider_AI__aider_release_window | Aider-AI/aider | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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":... | A | 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. | [
"Aider_AI__aider__release__v0_67_0",
"Aider_AI__aider__release__v0_69_0"
] | [
{
"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... |
Aider_AI__aider_release_window | Aider-AI/aider | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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. | [
{
"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"
}
] | A | 3 -> 2 -> 1 | [
"Aider_AI__aider__release__v0_73_0",
"Aider_AI__aider__release__v0_82_0",
"Aider_AI__aider__release__v0_86_0"
] | [
{
"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."
... |
airbnb__lottie_android_release_window | airbnb/lottie-android | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the airbnb/lottie-android releases, which release adds support for gaussian blur effects and drop shadow effects? | [
{
"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"
}
] | B | 4.1.0 | [
"airbnb__lottie_android__release__v4_1_0"
] | [
{
"memory_node_id": "airbnb__lottie_android__release__v4_1_0",
"answer_text": "Added support for gaussian blur effects and drop shadow effects"
}
] |
airbnb__lottie_android_release_window | airbnb/lottie-android | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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_... | A | 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. | [
"airbnb__lottie_android__release__v5_0_1",
"airbnb__lottie_android__release__v6_1_0"
] | [
{
"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... |
airbnb__lottie_android_release_window | airbnb/lottie-android | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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 ad... | [
{
"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"
}
] | A | 1 -> 2 -> 3 | [
"airbnb__lottie_android__release__v4_1_0",
"airbnb__lottie_android__release__v5_2_0",
"airbnb__lottie_android__release__v6_7_0"
] | [
{
"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 () ->... |
ajeetdsouza__zoxide_release_window | ajeetdsouza/zoxide | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the ajeetdsouza/zoxide releases, which release adds support for the Korn shell (ksh)? | [
{
"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"
}
] | A | v0.9.5 | [
"ajeetdsouza__zoxide__release__v0_9_5"
] | [
{
"memory_node_id": "ajeetdsouza__zoxide__release__v0_9_5",
"answer_text": "ksh: added support for the Korn shell."
}
] |
ajeetdsouza__zoxide_release_window | ajeetdsouza/zoxide | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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. | [
{
"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"
}
] | A | 1 -> 2 -> 3 | [
"ajeetdsouza__zoxide__release__v0_4_1",
"ajeetdsouza__zoxide__release__v0_5_0",
"ajeetdsouza__zoxide__release__v0_6_0"
] | [
{
"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_tex... |
alacritty__alacritty_release_window | alacritty/alacritty | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the alacritty/alacritty releases, which release adds support for fractional scaling on Wayland with wp-fractional-scale protocol? | [
{
"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"
}
] | A | v0.12.0 | [
"alacritty__alacritty__release__v0_12_0"
] | [
{
"memory_node_id": "alacritty__alacritty__release__v0_12_0",
"answer_text": "support for fractional scaling on Wayland with wp-fractional-scale protocol"
}
] |
alacritty__alacritty_release_window | alacritty/alacritty | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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 o... | A | v0.13.0 switches from YAML to TOML, while v0.14.0 moves several config options to a new general section. | [
"alacritty__alacritty__release__v0_13_0",
"alacritty__alacritty__release__v0_14_0"
] | [
{
"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 t... |
Alamofire__Alamofire_release_window | Alamofire/Alamofire | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the Alamofire/Alamofire releases, which release adds Combine support with DataResponsePublisher, DownloadResponsePublisher, and DataStreamPublisher? | [
{
"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"
}
] | B | 5.2.0 | [
"Alamofire__Alamofire__release__5_2_0"
] | [
{
"memory_node_id": "Alamofire__Alamofire__release__5_2_0",
"answer_text": "adds Combine support with DataResponsePublisher, DownloadResponsePublisher, and DataStreamPublisher"
}
] |
Alamofire__Alamofire_release_window | Alamofire/Alamofire | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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 conc... | [
{
"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"
}
] | A | 2 -> 1 -> 3 -> 4 | [
"Alamofire__Alamofire__release__5_2_0",
"Alamofire__Alamofire__release__5_7_0",
"Alamofire__Alamofire__release__5_9_0",
"Alamofire__Alamofire__release__5_10_0"
] | [
{
"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"
... |
alibaba__arthas_release_window | alibaba/arthas | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the alibaba/arthas releases, which release adds the jfr command and upgrades asm to 9.3 to support Java 19? | [
{
"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"
}
] | A | arthas-all-3.6.5 | [
"alibaba__arthas__release__arthas_all_3_6_5"
] | [
{
"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"
}
] |
alibaba__arthas_release_window | alibaba/arthas | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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."
},
{
... | A | 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. | [
"alibaba__arthas__release__arthas_all_4_0_2",
"alibaba__arthas__release__arthas_all_4_2_0"
] | [
{
"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... |
AlistGo__alist_release_window | AlistGo/alist | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the AlistGo/alist releases, which release adds FTP server and SFTP server support? | [
{
"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"
}
] | C | v3.41.0 | [
"AlistGo__alist__release__v3_41_0"
] | [
{
"memory_node_id": "AlistGo__alist__release__v3_41_0",
"answer_text": "FTP server and SFTP server support are added."
}
] |
AlistGo__alist_release_window | AlistGo/alist | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | Across the AlistGo/alist releases, how does the offline download feature change from v3.38.0 to v3.42.0? | [
{
"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",
... | A | v3.38.0 adds transmission support to offline_download, while v3.42.0 allows using offline download tools in any storage. | [
"AlistGo__alist__release__v3_38_0",
"AlistGo__alist__release__v3_42_0"
] | [
{
"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"
}
] |
AlistGo__alist_release_window | AlistGo/alist | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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. | [
{
"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"
}
] | A | 1 -> 2 -> 3 -> 4 | [
"AlistGo__alist__release__v3_39_1",
"AlistGo__alist__release__v3_44_0",
"AlistGo__alist__release__v3_54_0",
"AlistGo__alist__release__v3_55_0"
] | [
{
"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... |
angular__angular_release_window | angular/angular | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the angular/angular releases, which release introduces the @Service decorator and updates Testability to use PendingTasks for stability indicator? | [
{
"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"
}
] | A | 22.0.0-next.9 | [
"angular__angular__release__v22_0_0_next_9"
] | [
{
"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"
}
] |
angular__angular_release_window | angular/angular | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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 disal... | B | 20.3.20 disallows event attribute bindings in host bindings unconditionally, while 22.0.0-next.12 also disallows them unconditionally. | [
"angular__angular__release__v20_3_20",
"angular__angular__release__v22_0_0_next_12"
] | [
{
"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... |
anomalyco__opencode_release_window | anomalyco/opencode | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the anomalyco/opencode releases, which release introduces the Scout agent for repo research, docs lookup, and dependency-source inspection? | [
{
"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"
}
] | A | v1.14.42 | [
"anomalyco__opencode__release__v1_14_42"
] | [
{
"memory_node_id": "anomalyco__opencode__release__v1_14_42",
"answer_text": "add the Scout agent for repo research, docs lookup, and dependency-source inspection"
}
] |
anomalyco__opencode_release_window | anomalyco/opencode | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | Across the anomalyco/opencode releases, how does the image attachment handling differ between v1.14.47 and v1.14.48? | [
{
"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."
},
{
... | A | v1.14.47 auto-resizes large image attachments before sending, while v1.14.48 preserves original image attachments instead of resizing them. | [
"anomalyco__opencode__release__v1_14_47",
"anomalyco__opencode__release__v1_14_48"
] | [
{
"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 o... |
ant_design__ant_design_release_window | ant-design/ant-design | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the ant-design/ant-design releases, which release introduces the BorderBeam component for animated border beam effect? | [
{
"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"
}
] | B | 6.4.0 | [
"ant_design__ant_design__release__6_4_0"
] | [
{
"memory_node_id": "ant_design__ant_design__release__6_4_0",
"answer_text": "BorderBeam component added for animated border beam effect"
}
] |
ant_design__ant_design_release_window | ant-design/ant-design | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | Across the ant-design/ant-design releases, how does the Splitter component change from release 5.28.0 to release 6.4.0? | [
{
"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",
"te... | A | 5.28.0 adds onCollapse prop, while 6.4.0 adds destroyOnHidden prop and smooth transition animation for collapsible panels. | [
"ant_design__ant_design__release__5_28_0",
"ant_design__ant_design__release__6_4_0"
] | [
{
"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"
}
] |
apache__dubbo_release_window | apache/dubbo | q1_single_state_lookup | single_state_lookup | low | multiple_choice | 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? | [
{
"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"
}
] | B | dubbo-3.3.0 | [
"apache__dubbo__release__dubbo_3_3_0"
] | [
{
"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"
}
] |
apache__dubbo_release_window | apache/dubbo | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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 th... | A | 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. | [
"apache__dubbo__release__dubbo_3_3_0_beta_1",
"apache__dubbo__release__dubbo_3_3_0"
] | [
{
"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__d... |
appsmithorg__appsmith_release_window | appsmithorg/appsmith | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the appsmithorg/appsmith releases, which release introduces a multi-organization login page? | [
{
"option_id": "A",
"text": "v1.73"
},
{
"option_id": "B",
"text": "v1.74"
},
{
"option_id": "C",
"text": "v1.75"
},
{
"option_id": "D",
"text": "v1.76"
}
] | B | v1.74 | [
"appsmithorg__appsmith__release__v1_74"
] | [
{
"memory_node_id": "appsmithorg__appsmith__release__v1_74",
"answer_text": "Introduced multi-organization login page"
}
] |
appsmithorg__appsmith_release_window | appsmithorg/appsmith | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | Across the appsmithorg/appsmith releases, how does the handling of user sessions differ between v1.73 and v1.74? | [
{
"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."
... | A | v1.73 logs out users with expired sessions between page navigations, while v1.74 logs out users with expired sessions between page switches. | [
"appsmithorg__appsmith__release__v1_73",
"appsmithorg__appsmith__release__v1_74"
] | [
{
"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 betwee... |
appsmithorg__appsmith_release_window | appsmithorg/appsmith | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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 ... | [
{
"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"
}
] | A | 2 -> 1 -> 3 -> 4 | [
"appsmithorg__appsmith__release__v1_74",
"appsmithorg__appsmith__release__v1_82",
"appsmithorg__appsmith__release__v1_83",
"appsmithorg__appsmith__release__v1_94"
] | [
{
"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"
},
{
"memor... |
aquasecurity__trivy_release_window | aquasecurity/trivy | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the aquasecurity/trivy releases, which release introduces a dedicated SBOM command and adds vulnerabilities to CycloneDX? | [
{
"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"
}
] | B | v0.25.0 | [
"aquasecurity__trivy__release__v0_25_0"
] | [
{
"memory_node_id": "aquasecurity__trivy__release__v0_25_0",
"answer_text": "adding a dedicated SBOM command, adding vulnerabilities to CycloneDX"
}
] |
aquasecurity__trivy_release_window | aquasecurity/trivy | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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."
},
{
"op... | A | 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. | [
"aquasecurity__trivy__release__v0_21_0",
"aquasecurity__trivy__release__v0_23_0"
] | [
{
"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"
}
] |
aquasecurity__trivy_release_window | aquasecurity/trivy | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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 f... | [
{
"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"
}
] | A | 1 -> 3 -> 2 | [
"aquasecurity__trivy__release__v0_19_0",
"aquasecurity__trivy__release__v0_24_0",
"aquasecurity__trivy__release__v0_25_0"
] | [
{
"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... |
argoproj__argo_cd_release_window | argoproj/argo-cd | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | Across the argoproj/argo-cd releases, how does the handling of automatic refreshes differ between v3.2.9 and v3.2.10? | [
{
"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"... | A | v3.2.9 prevents automatic refreshes from informer resync and status updates, while v3.2.10 reverts that prevention. | [
"argoproj__argo_cd__release__v3_2_9",
"argoproj__argo_cd__release__v3_2_10"
] | [
{
"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 statu... |
aristocratos__btop_release_window | aristocratos/btop | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the aristocratos/btop releases, which release adds support for OSX? | [
{
"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"
}
] | A | v1.1.0 | [
"aristocratos__btop__release__v1_1_0"
] | [
{
"memory_node_id": "aristocratos__btop__release__v1_1_0",
"answer_text": "adds support for OSX"
}
] |
aristocratos__btop_release_window | aristocratos/btop | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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 AM... | A | v1.3.0 adds GPU support for Linux, while v1.4.0 adds Intel GPU support. | [
"aristocratos__btop__release__v1_3_0",
"aristocratos__btop__release__v1_4_0"
] | [
{
"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"
}
] |
aristocratos__btop_release_window | aristocratos/btop | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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. | [
{
"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"
}
] | A | 1 -> 2 -> 3 -> 4 | [
"aristocratos__btop__release__v1_2_0",
"aristocratos__btop__release__v1_3_0",
"aristocratos__btop__release__v1_4_0",
"aristocratos__btop__release__v1_4_7"
] | [
{
"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": ... |
aseprite__aseprite_release_window | aseprite/aseprite | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the aseprite/aseprite releases, which release introduces a new Text tool with the T key and diagonal symmetry? | [
{
"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"
}
] | B | v1.3.11-beta1 | [
"aseprite__aseprite__release__v1_3_11_beta1"
] | [
{
"memory_node_id": "aseprite__aseprite__release__v1_3_11_beta1",
"answer_text": "introduces a new Text tool with T key, new diagonal symmetry"
}
] |
aseprite__aseprite_release_window | aseprite/aseprite | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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."
},
{
... | A | 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. | [
"aseprite__aseprite__release__v1_3_11_beta1",
"aseprite__aseprite__release__v1_3_16_beta2"
] | [
{
"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/movabl... |
aseprite__aseprite_release_window | aseprite/aseprite | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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 'Widge... | [
{
"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"
}
] | A | 1 -> 2 -> 3 | [
"aseprite__aseprite__release__v1_3_11_beta1",
"aseprite__aseprite__release__v1_3_16_beta2",
"aseprite__aseprite__release__v1_3_18_beta1"
] | [
{
"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 e... |
astral_sh__ruff_release_window | astral-sh/ruff | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the astral-sh/ruff releases, which release introduces the rule RUF066 to detect unnecessary class properties? | [
{
"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"
}
] | A | 0.14.7 | [
"astral_sh__ruff__release__0_14_7"
] | [
{
"memory_node_id": "astral_sh__ruff__release__0_14_7",
"answer_text": "RUF066 detects unnecessary class properties"
}
] |
astral_sh__ruff_release_window | astral-sh/ruff | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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... | [
{
"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"
}
] | A | 1 -> 2 -> 4 -> 3 | [
"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"
] | [
{
"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"... |
astral_sh__uv_release_window | astral-sh/uv | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the astral-sh/uv releases, which release adds support for ROCm 7.2 and implements support for PEP 803? | [
{
"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"
}
] | A | 0.11.3 | [
"astral_sh__uv__release__0_11_3"
] | [
{
"memory_node_id": "astral_sh__uv__release__0_11_3",
"answer_text": "adds support for ROCm 7.2 ... implements support for PEP 803"
}
] |
astral_sh__uv_release_window | astral-sh/uv | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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."
... | A | 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. | [
"astral_sh__uv__release__0_11_0",
"astral_sh__uv__release__0_11_7"
] | [
{
"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",
"answe... |
astral_sh__uv_release_window | astral-sh/uv | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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... | [
{
"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"
}
] | A | 1 -> 2 -> 3 -> 4 | [
"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"
] | [
{
"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"... |
authelia__authelia_release_window | authelia/authelia | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the authelia/authelia releases, which release introduces LDAP connection pooling and reusable configuration definitions? | [
{
"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"
}
] | B | v4.39.0 | [
"authelia__authelia__release__v4_39_0"
] | [
{
"memory_node_id": "authelia__authelia__release__v4_39_0",
"answer_text": "new features such as ... LDAP connection pooling ... reusable configuration definitions"
}
] |
authelia__authelia_release_window | authelia/authelia | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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",
"... | A | v4.39.2 inadvertently removes legacy OIDC endpoints, while v4.39.6 disallows 'none' as an authorization_signed_response_alg value. | [
"authelia__authelia__release__v4_39_2",
"authelia__authelia__release__v4_39_6"
] | [
{
"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 r... |
authelia__authelia_release_window | authelia/authelia | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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 cod... | [
{
"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"
}
] | A | 1 -> 2 -> 3 -> 4 | [
"authelia__authelia__release__v4_38_14",
"authelia__authelia__release__v4_39_0",
"authelia__authelia__release__v4_39_18",
"authelia__authelia__release__v4_39_20"
] | [
{
"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 definition... |
AvaloniaUI__Avalonia_release_window | AvaloniaUI/Avalonia | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the AvaloniaUI/Avalonia releases, which release introduces the Container Queries feature? | [
{
"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"
}
] | C | 11.3.0 | [
"AvaloniaUI__Avalonia__release__11_3_0"
] | [
{
"memory_node_id": "AvaloniaUI__Avalonia__release__11_3_0",
"answer_text": "features include ... Container Queries"
}
] |
AvaloniaUI__Avalonia_release_window | AvaloniaUI/Avalonia | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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 r... | A | 11.3.7 reworks the clipboard, while 11.3.9 adds support for reading from and copying images to the clipboard. | [
"AvaloniaUI__Avalonia__release__11_3_7",
"AvaloniaUI__Avalonia__release__11_3_9"
] | [
{
"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"
}
] |
axios__axios_release_window | axios/axios | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the axios/axios releases, which release adds HTTP2 support to the http adapter? | [
{
"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"
}
] | B | v1.13.0 | [
"axios__axios__release__v1_13_0"
] | [
{
"memory_node_id": "axios__axios__release__v1_13_0",
"answer_text": "HTTP2 support is added to the http adapter."
}
] |
axios__axios_release_window | axios/axios | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | Across the axios/axios releases, how does the security fix in v0.30.3 differ from the security fix in v1.13.5? | [
{
"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... | A | 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. | [
"axios__axios__release__v0_30_3",
"axios__axios__release__v1_13_5"
] | [
{
"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... |
axios__axios_release_window | axios/axios | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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 rel... | [
{
"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"
}
] | A | 1 -> 2 -> 3 -> 4 | [
"axios__axios__release__v1_10_0",
"axios__axios__release__v1_13_6",
"axios__axios__release__v1_15_0",
"axios__axios__release__v1_16_0"
] | [
{
"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_... |
Blankj__AndroidUtilCode_release_window | Blankj/AndroidUtilCode | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the Blankj/AndroidUtilCode releases, which release adds BrightnessUtils and FlashlightUtils? | [
{
"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"
}
] | A | 1.23.2 | [
"Blankj__AndroidUtilCode__release__1_23_2"
] | [
{
"memory_node_id": "Blankj__AndroidUtilCode__release__1_23_2",
"answer_text": "adds ... BrightnessUtils and FlashlightUtils"
}
] |
Blankj__AndroidUtilCode_release_window | Blankj/AndroidUtilCode | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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 ... | A | 1.23.7 adds multi-process support and fixes LogUtils#file, while 1.24.1 fixes LogUtils writing to file. | [
"Blankj__AndroidUtilCode__release__1_23_7",
"Blankj__AndroidUtilCode__release__1_24_1"
] | [
{
"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"
}
] |
Blankj__AndroidUtilCode_release_window | Blankj/AndroidUtilCode | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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. | [
{
"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"
}
] | A | 1 -> 2 -> 3 | [
"Blankj__AndroidUtilCode__release__1_23_4",
"Blankj__AndroidUtilCode__release__1_25_2",
"Blankj__AndroidUtilCode__release__1_28_0"
] | [
{
"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": "ad... |
browser_use__browser_use_release_window | browser-use/browser-use | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the browser-use/browser-use releases, which release introduces the Browser Use CLI and skill for Claude Code/Codex agents? | [
{
"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"
}
] | A | 0.11.4 | [
"browser_use__browser_use__release__0_11_4"
] | [
{
"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"
}
] |
browser_use__browser_use_release_window | browser-use/browser-use | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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 few... | A | 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. | [
"browser_use__browser_use__release__0_11_4",
"browser_use__browser_use__release__0_12_3"
] | [
{
"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.... |
browser_use__browser_use_release_window | browser-use/browser-use | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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% accurac... | [
{
"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"
}
] | A | 1 -> 2 -> 3 -> 4 | [
"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"
] | [
{
"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": "brows... |
bumptech__glide_release_window | bumptech/glide | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the bumptech/glide releases, which release introduces a clearOnDetach() API on ViewTarget and a waitForLayout() API on ViewTarget? | [
{
"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"
}
] | A | v4.4.0 | [
"bumptech__glide__release__v4_4_0"
] | [
{
"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()"
}
] |
bumptech__glide_release_window | bumptech/glide | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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."
},
{
"o... | A | v4.13.0 adds an integration library for AVIF decoding, while v4.15.0 adds support for animated AVIF and RGB_565 in Avif. | [
"bumptech__glide__release__v4_13_0",
"bumptech__glide__release__v4_15_0"
] | [
{
"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"
}
] |
bumptech__glide_release_window | bumptech/glide | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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... | [
{
"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"
}
] | A | 1 -> 2 -> 3 -> 4 | [
"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"
] | [
{
"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"... |
caddyserver__caddy_release_window | caddyserver/caddy | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the caddyserver/caddy releases, which release introduces Encrypted ClientHello (ECH) and post-quantum key exchange with x25519mlkem768? | [
{
"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"
}
] | C | v2.10.0 | [
"caddyserver__caddy__release__v2_10_0"
] | [
{
"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"
}
] |
carbon_language__carbon_lang_release_window | carbon-language/carbon-lang | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the carbon-language/carbon-lang releases, which release includes the addition of a text mode for fingerprinting? | [
{
"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"
}
] | B | v0.0.0-0.nightly.2026.05.20 | [
"carbon_language__carbon_lang__release__v0_0_0_0_nightly_2026_05_20"
] | [
{
"memory_node_id": "carbon_language__carbon_lang__release__v0_0_0_0_nightly_2026_05_20",
"answer_text": "adding a text mode for fingerprinting"
}
] |
carbon_language__carbon_lang_release_window | carbon-language/carbon-lang | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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. | [
{
"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"
}
] | B | 2 -> 1 -> 3 | [
"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"
] | [
{
"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"
},
{... |
ccfos__nightingale_release_window | ccfos/nightingale | q1_single_state_lookup | single_state_lookup | low | multiple_choice | 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? | [
{
"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"
}
] | A | v8.0.0-beta.10 | [
"ccfos__nightingale__release__v8_0_0_beta_10"
] | [
{
"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"
}
] |
ccfos__nightingale_release_window | ccfos/nightingale | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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-be... | A | 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. | [
"ccfos__nightingale__release__v8_0_0_beta_8",
"ccfos__nightingale__release__v8_0_0_beta_8_3"
] | [
{
"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"
}
] |
ccfos__nightingale_release_window | ccfos/nightingale | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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 ... | [
{
"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"
}
] | A | 1 -> 3 -> 4 -> 2 | [
"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"
] | [
{
"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__nigh... |
ccxt__ccxt_release_window | ccxt/ccxt | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the ccxt/ccxt releases, which release introduces the Zebpay exchange integration? | [
{
"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"
}
] | A | v4.5.27 | [
"ccxt__ccxt__release__v4_5_27"
] | [
{
"memory_node_id": "ccxt__ccxt__release__v4_5_27",
"answer_text": "adds a new Zebpay exchange integration"
}
] |
ccxt__ccxt_release_window | ccxt/ccxt | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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"... | A | v4.5.30 integrates bydfi, while v4.5.32 integrates aster. | [
"ccxt__ccxt__release__v4_5_30",
"ccxt__ccxt__release__v4_5_32"
] | [
{
"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"
}
] |
ccxt__ccxt_release_window | ccxt/ccxt | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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 int... | [
{
"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"
}
] | A | 1 -> 2 -> 3 -> 4 | [
"ccxt__ccxt__release__v4_5_27",
"ccxt__ccxt__release__v4_5_30",
"ccxt__ccxt__release__v4_5_32",
"ccxt__ccxt__release__v4_5_43"
] | [
{
"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": "int... |
charmbracelet__bubbletea_release_window | charmbracelet/bubbletea | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the charmbracelet/bubbletea releases, which release introduces the new Cursed Renderer and a declarative view API? | [
{
"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"
}
] | C | v2.0.0 | [
"charmbracelet__bubbletea__release__v2_0_0"
] | [
{
"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"
}
] |
charmbracelet__bubbletea_release_window | charmbracelet/bubbletea | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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 d... | A | 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. | [
"charmbracelet__bubbletea__release__v1_3_0",
"charmbracelet__bubbletea__release__v2_0_0_beta_3"
] | [
{
"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... |
charmbracelet__bubbletea_release_window | charmbracelet/bubbletea | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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 ev... | [
{
"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"
}
] | A | 1 -> 2 -> 3 -> 4 | [
"charmbracelet__bubbletea__release__v1_3_2",
"charmbracelet__bubbletea__release__v1_3_3",
"charmbracelet__bubbletea__release__v1_3_4",
"charmbracelet__bubbletea__release__v1_3_5"
] | [
{
"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 restor... |
chartjs__Chart_js_release_window | chartjs/Chart.js | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the chartjs/Chart.js releases, which release adds a selfJoin option for doughnut graphs? | [
{
"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"
}
] | B | v4.5.0 | [
"chartjs__Chart_js__release__v4_5_0"
] | [
{
"memory_node_id": "chartjs__Chart_js__release__v4_5_0",
"answer_text": "adding selfJoin option for doughnut graphs"
}
] |
chartjs__Chart_js_release_window | chartjs/Chart.js | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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... | A | v4.4.1 fixes tooltips for null controller and null getParsed, while v4.4.4 fixes tooltip show for all invisible. | [
"chartjs__Chart_js__release__v4_4_1",
"chartjs__Chart_js__release__v4_4_4"
] | [
{
"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"
}
] |
chartjs__Chart_js_release_window | chartjs/Chart.js | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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 al... | [
{
"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"
}
] | A | 1 -> 4 -> 3 -> 2 | [
"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"
] | [
{
"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__Ch... |
ChatGPTNextWeb__NextChat_release_window | ChatGPTNextWeb/NextChat | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the ChatGPTNextWeb/NextChat releases, which release introduces a plugin system based on function calls similar to GPTs actions? | [
{
"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"
}
] | B | v2.15.0 | [
"ChatGPTNextWeb__NextChat__release__v2_15_0"
] | [
{
"memory_node_id": "ChatGPTNextWeb__NextChat__release__v2_15_0",
"answer_text": "introduces a plugin system (GPTs-like actions based on function calls)"
}
] |
ChatGPTNextWeb__NextChat_release_window | ChatGPTNextWeb/NextChat | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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 sam... | A | v2.10.1 adds Google Gemini Pro support, while v2.12.2 adds Anthropic Claude and gpt-4-turbo support. | [
"ChatGPTNextWeb__NextChat__release__v2_10_1",
"ChatGPTNextWeb__NextChat__release__v2_12_2"
] | [
{
"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"
}
] |
ChatGPTNextWeb__NextChat_release_window | ChatGPTNextWeb/NextChat | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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 add... | [
{
"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"
}
] | A | 1 -> 2 -> 3 -> 4 | [
"ChatGPTNextWeb__NextChat__release__v2_10_1",
"ChatGPTNextWeb__NextChat__release__v2_15_2",
"ChatGPTNextWeb__NextChat__release__v2_15_8",
"ChatGPTNextWeb__NextChat__release__v2_16_0"
] | [
{
"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": "ChatGPTNextWe... |
ChromeDevTools__chrome_devtools_mcp_release_window | ChromeDevTools/chrome-devtools-mcp | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the ChromeDevTools/chrome-devtools-mcp releases, which release introduces geolocation emulation and support for --user-data-dir? | [
{
"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"
}
] | B | v0.11.0 | [
"ChromeDevTools__chrome_devtools_mcp__release__chrome_devtools_mcp_v0_11_0"
] | [
{
"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"
}
] |
ChromeDevTools__chrome_devtools_mcp_release_window | ChromeDevTools/chrome-devtools-mcp | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | Across the ChromeDevTools/chrome-devtools-mcp releases, how does the feature set of v0.18.0 differ from that of v0.19.0? | [
{
"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 --s... | A | 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. | [
"ChromeDevTools__chrome_devtools_mcp__release__chrome_devtools_mcp_v0_18_0",
"ChromeDevTools__chrome_devtools_mcp__release__chrome_devtools_mcp_v0_19_0"
] | [
{
"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_... |
cilium__cilium_release_window | cilium/cilium | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the cilium/cilium releases, which release introduces a ztunnel daemonset controller and an xds control-plane for ztunnel? | [
{
"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"
}
] | A | v1.19.0-pre.3 | [
"cilium__cilium__release__v1_19_0_pre_3"
] | [
{
"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"
}
] |
cilium__cilium_release_window | cilium/cilium | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | Across the cilium/cilium releases, how does the handling of Helm chart publishing differ between v1.18.6 and v1.19.0-rc.0? | [
{
"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 | 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. | [
"cilium__cilium__release__v1_18_6",
"cilium__cilium__release__v1_19_0_rc_0"
] | [
{
"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"
}
] |
clash_verge_rev__clash_verge_rev_release_window | clash-verge-rev/clash-verge-rev | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the clash-verge-rev/clash-verge-rev releases, which release introduces a new IPC communication mechanism and a redesigned traffic monitoring interface? | [
{
"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"
}
] | B | v2.4.0 | [
"clash_verge_rev__clash_verge_rev__release__v2_4_0"
] | [
{
"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"
}
] |
clash_verge_rev__clash_verge_rev_release_window | clash-verge-rev/clash-verge-rev | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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... | A | v2.0.1 uses sysproxy.exe for Windows system proxy, while v2.4.4 no longer depends on sysproxy.exe. | [
"clash_verge_rev__clash_verge_rev__release__v2_0_1",
"clash_verge_rev__clash_verge_rev__release__v2_4_4"
] | [
{
"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 来设置代理"
}
] |
cli__cli_release_window | cli/cli | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the cli/cli releases, which release introduces the agent-task commandset for managing coding agent tasks? | [
{
"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"
}
] | B | v2.80.0 | [
"cli__cli__release__v2_80_0"
] | [
{
"memory_node_id": "cli__cli__release__v2_80_0",
"answer_text": "introduces the agent-task commandset for managing coding agent tasks"
}
] |
cli__cli_release_window | cli/cli | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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.... | A | 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. | [
"cli__cli__release__v2_76_0",
"cli__cli__release__v2_87_0"
] | [
{
"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 ... |
cli__cli_release_window | cli/cli | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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... | [
{
"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"
}
] | A | 2 -> 3 -> 1 -> 4 | [
"cli__cli__release__v2_80_0",
"cli__cli__release__v2_87_0",
"cli__cli__release__v2_90_0",
"cli__cli__release__v2_91_0"
] | [
{
"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_... |
clockworklabs__SpacetimeDB_release_window | clockworklabs/SpacetimeDB | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the clockworklabs/SpacetimeDB releases, which release introduces the spacetime dev command that automates the development loop? | [
{
"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"
}
] | B | v1.7.0 | [
"clockworklabs__SpacetimeDB__release__v1_7_0"
] | [
{
"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."
}
] |
clockworklabs__SpacetimeDB_release_window | clockworklabs/SpacetimeDB | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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 reint... | A | 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. | [
"clockworklabs__SpacetimeDB__release__v1_6_0",
"clockworklabs__SpacetimeDB__release__v2_0_1"
] | [
{
"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/... |
clockworklabs__SpacetimeDB_release_window | clockworklabs/SpacetimeDB | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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 TypeScrip... | [
{
"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"
}
] | A | 1 -> 2 -> 3 -> 4 | [
"clockworklabs__SpacetimeDB__release__v1_1_0",
"clockworklabs__SpacetimeDB__release__v1_10_0",
"clockworklabs__SpacetimeDB__release__v1_11_0",
"clockworklabs__SpacetimeDB__release__v1_12_0"
] | [
{
"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 intr... |
coder__code_server_release_window | coder/code-server | q2_cross_version_comparison | cross_version_comparison | high | multiple_choice | 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? | [
{
"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 reintro... | A | 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. | [
"coder__code_server__release__v4_111_0",
"coder__code_server__release__v4_122_0"
] | [
{
"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 th... |
Comfy_Org__ComfyUI_release_window | Comfy-Org/ComfyUI | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the Comfy-Org/ComfyUI releases, which release adds a Math Expression node with simpleeval evaluation? | [
{
"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"
}
] | A | v0.16.4 | [
"Comfy_Org__ComfyUI__release__v0_16_4"
] | [
{
"memory_node_id": "Comfy_Org__ComfyUI__release__v0_16_4",
"answer_text": "adds a Math Expression node with simpleeval evaluation"
}
] |
Comfy_Org__ComfyUI_release_window | Comfy-Org/ComfyUI | q3_temporal_version_ordering | temporal_version_ordering | high | multiple_choice | 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 a... | [
{
"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"
}
] | A | 1 -> 4 -> 2 -> 3 | [
"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"
] | [
{
"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... |
conductor_oss__conductor_release_window | conductor-oss/conductor | q1_single_state_lookup | single_state_lookup | low | multiple_choice | In the conductor-oss/conductor releases, which release introduces the Workflow Message Queue (WMQ) feature to push messages into running workflows? | [
{
"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"
}
] | C | v3.3.0.rc8 | [
"conductor_oss__conductor__release__v3_3_0_rc8"
] | [
{
"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"
}
] |
End of preview. Expand in Data Studio
TSSMRBench: Audited Release
TSSMRBench evaluates whether a memory system retrieves the version states that match a queried stage in an evolving memory trajectory. This audited release accompanies the ICASSP-format manuscript and supersedes the original 300-repository evaluation selection.
| Selection | Repositories | Memory nodes | Questions |
|---|---|---|---|
| Main audited selection | 261 | 7,830 | 646 |
| Subset retaining all three task families | 155 | 4,650 | 465 |
The main selection contains 241 single-state lookup, 215 cross-version comparison, and 190 temporal ordering questions. Every repository retains 30 normalized memory nodes. The complete subset is contained in the main selection; it is not a separate test set.
Files and usage
data/tssmrbench_audited_question_level_v3_public.json: full main selection, including memories, questions, and gold support.data/tssmrbench_audited_complete_v3_public.json: optional complete-trajectory subset.data/questions.jsonl: 646 question records for the dataset viewer.data/memories.jsonl: 7,830 memory records for the dataset viewer.manifest.json: counts and SHA-256 checksums.
from datasets import load_dataset
questions = load_dataset("l4st/TSSMRBench", "questions", split="test")
memories = load_dataset("l4st/TSSMRBench", "memories", split="test")
Join questions and memories by prototype_id and match source_chunk_ids to memory_node_id. Gold support and answer labels are evaluation annotations, not retrieval inputs. Each question contains options A–D; the evaluation answer model may abstain with E.
Construction and quality control
The source collection comprised 300 software release histories. Static checks and independent model review assessed node identifiers, supporting evidence, option consistency, and temporal ordering. Questions with flagged gold nodes were removed; flagged non-gold nodes remain as distractors. A repository added after the saved experiment snapshot was excluded because no corresponding retrieval traces were available. The resulting release and reported question selection both contain 646 questions from 261 repositories.
The published results score these questions against saved retrieval traces from the original shared index, which included additional background records. Running retrieval on only the 7,830 nodes in this release creates a different pool and should be reported as a new experiment. The earlier data/official_300_merged_public.json remains available for historical reference; it must not be mistaken for the audited selection.
Redistribution and limitations
This package removes original raw_text release notes and local merge metadata. It retains normalized memory_unit_text, source URLs, version identifiers, questions, and supporting-state annotations. The normalized text is a model-generated rewrite, not the original release note.
The evaluation is limited to software release histories, model-generated data with static and model-based quality checks, and a fixed offline answer protocol. Model auditing does not constitute comprehensive human verification.
Upstream materials have different licenses. See LICENSE for the existing multi-source redistribution notice and retain source attribution.
Code and manuscript
Code and ICASSP-format manuscript: https://github.com/ngyygm/llm-TSSMRBench. The manuscript is in ICASSP_paper_format/; export this package with python benchmark/scripts/99_export_audited_public_release.py.
- Downloads last month
- 48