Release v1.2.0 - Add 2025 threat scenarios#3
Merged
joris-decombe merged 1 commit intomainfrom Dec 23, 2025
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release v1.2.0
This PR prepares the release of version 1.2.0, which includes the three new 2025 threat scenarios that were added in PR #2.
Changes in this PR
package.jsonCHANGELOG.mdwith comprehensive release notes for v1.2.0What's in v1.2.0
Three new cybersecurity scenarios based on real-world incidents from 2024-2025:
The "Deepfake" CFO (Easy) - Scenario code: 1461
The Poisoned Package (Medium) - Scenario code: 3164
Hypervisor Ransomware (Hard) - Scenario code: 5126
All scenarios include full English/French translations and follow NCSC R&R format.
Post-Merge Actions
After merging this PR:
v1.2.0Checklist