Cylc-rose

Latest version: v1.3.3

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

Scan your dependencies

Page 1 of 2

1.4.0

Features

[269](https://github.com/cylc/cylc-rose/pull/269) - Allow environment variables
set in ``rose-suite.conf`` to be used when parsing ``global.cylc``.

1.3.3

Fixes

[300](https://github.com/cylc/cylc-rose/pull/300) -
Fix issues which could cause "fcm_make" and "rose_prune" tasks intermittently
fail with the message
"Workflow database is incompatible with Cylc x.y.z, or is corrupted".

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.

Page 1 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.