[NejcS]

plain-forge now ships the render-spec skill of pyro 0.5.0, the release that renders explicit test scenarios.

What a user sees

render-spec reads the test plain files of a module from the folder that tests-folder names, writes one test per scenario and invents none. It stops the render when a test plain file binds to no functionality.

Before it works end to end

Nothing. This is the last change before the v1.1.0 release.

Summary by CodeRabbit

• Chores
  • Updated the bundled Pyro component to a newer revision.
  • No user-facing changes are noted in this update.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The vendor/pyro subproject reference changes from commit cc9116e8ea3599426d585b436bcec83ac8dcf11b to c8e6efaadfde06cf6ea36866529f416a7e548abe.

Changes: Pyro vendor revision

Layer / File(s)	Summary
Update Pyro reference vendor/pyro	The subproject reference changes to commit c8e6efaadfde06cf6ea36866529f416a7e548abe.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Feature

Possibly related PRs

• plainlang/plain-forge#43: Updates plain-parser for the test-file syntax and folder configuration consumed by the Pyro render-spec skill.
• plainlang/plain-forge#32: Defines test plain files and scenarios consumed by the Pyro render-spec skill.
• plainlang/plain-forge#38: Defines the tests-folder configuration used by the Pyro renderer.

Suggested labels: dependencies

Suggested reviewers: zanjonke

Merge Risk: Moderate · up to b1005

This bump ships a Pyro version that only looks for test plain files in a folder named "tests". Projects that configure a different tests-folder will have their authored test scenarios silently skipped during rendering. Resolve this, or confirm that the default folder is the only supported setup, before releasing.

- [ ] Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts