Cylc-rose

Latest version: v1.5.0

Safety actively analyzes 723177 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 3

1.3.2

[284](https://github.com/cylc/cylc-rose/pull/284) - Allow use of Metomi-Rose 2.2.*.

1.3.1

Fixes

[250](https://github.com/cylc/cylc-rose/pull/250) - Prevent project
name being manually set to an empty string.

[225](https://github.com/cylc/cylc-rose/pull/225) - Prevent totally invalid
CLI --defines with no = sign.

[248](https://github.com/cylc/cylc-rose/pull/248) - Make sure that
rose stem sets variables in `[jinja2:suite.rc]` not `[jinja2]`.

1.3.0

Fixes

[229](https://github.com/cylc/cylc-rose/pull/229) -
Fix bug which stops rose-stem suites using the new `[template variables]` section
in their `rose-suite.conf` files.

[231](https://github.com/cylc/cylc-rose/pull/231) - Show warning about
`root-dir` config setting in compatibility mode.

1.2.0

Fixes

[192](https://github.com/cylc/cylc-rose/pull/192) -
Fix bug where Cylc Rose would prevent change to template language on reinstall.

[180](https://github.com/cylc/cylc-rose/pull/180) -
Rose stem gets stem suite's basename to use as workflow name when not otherwise
set.

1.1.1

Fixes

[171](https://github.com/cylc/cylc-rose/pull/171) - Fix bug where Cylc Rose
passed `rose-suite.conf` items commented with `!` or `!!` to Cylc regardless.

[172](https://github.com/cylc/cylc-rose/pull/172) - Allow getting a workflow
name when source is not an SVN repo.

1.1.0

Fixes

[140](https://github.com/cylc/cylc-rose/pull/140) -
Support integers with leading zeros (e.g `001`) to back support Rose
configurations for use with cylc-flow>=8.0rc4 which uses Jinja2 v3 which
no longer supports this.

[155](https://github.com/cylc/cylc-rose/pull/155) -
Use the public rather than private database for platform lookups. This resolves
a database locking issue with the `rose_prune` built-in app.

Page 2 of 3

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.