Releases: picoCTF/cmgr
Releases · picoCTF/cmgr
Release v2.0.0
Changes
- Challenge types other than
remote-make
andstatic-make
are no longer supported.- Existing challenges of other types can be converted to
custom
by exporting their Dockerfile (cmgr dockerfile <type>
).
- Existing challenges of other types can be converted to
- JSON challenge specifications (
problem.json
) are no longer supported. Any existing challenges using this format must be converted to useproblem.md
instead.
Release v1.2.1
Changes
- Fixed an issue preventing ARM64 builds in GitHub release artifacts from working correctly.
- Linux ARM64 builds are no longer available.
Release v1.2.0
Changes
- The
cmgr update-schema
command andPOST /schemas/{schema_name}
cmgrd endpoint now function as upserts: if the specified schema does not yet exist, a warning is logged and it is created. This allows clients to easily apply updates to schemas without needing to consider whether they already exist (ca62a57)
Release v1.1.1
Changes
- Fixes bugs related to the use of
{{url}}
and{{lookup}}
templates in the Description field, as introduced in v1.1.0 (50de11d)
Release v1.1.0
Changes
{{url}}
,{{url_for}}
, and{{lookup}}
templates are now permitted in the Description section (2eefb47).
The primary motivation is to allow players to download artifacts prior to launching instances of on-demand challenges.
Release v1.0.0
Changes
- Updated seccomp profile to fix syscall issues in newer base images (c93ebcf)
- Reverted to cgo-based SQLite driver due to issues with concurrent transactions (0f6bee8)
- Added labels to challenge instance containers (e3e839e):
cmgr.managed=true
for all challenge instancescmgr.dynamic=<bool>
depending on whether the instance is of a build withinstance_count: -1