Cylc-rose

Latest version: v1.4.2

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

Scan your dependencies

Page 1 of 3

1.4.1

No significant change - Updated to use feature added at Cylc 8.3.3.
See [336](https://github.com/cylc/cylc-rose/pull/336)

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``.

Fixes

[319](https://github.com/cylc/cylc-rose/pull/319) - Prevent Cylc Rose
from modifying Cylc's compatibility mode.

1.3.4

[312](https://github.com/cylc/cylc-rose/pull/312) - Fixed an issue that could cause the cylc-rose CLI options (`-S`, `-D`, `-O`) to be applied incorrectly.

1.3.3

Fixes

[302](https://github.com/cylc/cylc-rose/pull/302) -
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]`.

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.