chore: release

[pavex-releaser]

🤖 New release

• pavex: 0.1.38 -> 0.1.39
• pavex_bp_schema: 0.1.38 -> 0.1.39
• pavex_reflection: 0.1.38 -> 0.1.39
• pavex_macros: 0.1.38 -> 0.1.39
• persist_if_changed: 0.1.38 -> 0.1.39
• pavex_tracing: 0.1.38 -> 0.1.39
• pavex_cli: 0.1.38 -> 0.1.39
• pavex_miette: 0.1.38 -> 0.1.39
• pavexc_cli_client: 0.1.38 -> 0.1.39
• pavexc: 0.1.38 -> 0.1.39
• pavex_cli_client: 0.1.38 -> 0.1.39
• pavexc_cli: 0.1.38 -> 0.1.39
• generate_from_path: 0.1.38 -> 0.1.39

Changelog

pavex

0.1.39 - 2024-06-15

Added

• Add a workspace-hack crate to the generated starter project to minimise (re)build times
• Reshape singleton dependencies (#298)
• Add a new '--template' option to 'pavex new' and 'pavexc new'. It includes a dedicated 'quickstart' template as well as the 'api' template, the default.
• In the starter project, use a meaningful example to showcase how the configuration system works, rather than a dummy with no usage

Fixed

• Set new Cargo lint to allow 'cfg(pavex_ide_hint)' in Pavex, its snapshot tests and its scaffolded projects
• Reject non-static references if they are registered as singletons.
• Don't use colored logs if color is not enabled.
• Include super and self as valid prefixes for relative paths (#296)

Other

• Disable workspace hack before a release
• Add shorthand methods to tweak the default cloning strategy on constructors and prebuilt types
• Re-enable workspace hack after a release (#295)
• Update test expectations.
• Handle "unused" warnings
• Improve debug output on panics
• Use the [env] section of .cargo/config.toml as the go-to place for storing non-sensitive env variables used for local development

---

This PR was generated with release-plz.