chore: release v0.1.69

[pavex-releaser]

🤖 New release

• pavex: 0.1.68 -> 0.1.69
• pavex_bp_schema: 0.1.68 -> 0.1.69
• pavex_reflection: 0.1.68 -> 0.1.69
• pavex_macros: 0.1.68 -> 0.1.69
• persist_if_changed: 0.1.68 -> 0.1.69
• pavex_tracing: 0.1.68 -> 0.1.69
• pavex_cli: 0.1.68 -> 0.1.69
• pavex_cli_deps: 0.1.68 -> 0.1.69
• pavex_miette: 0.1.68 -> 0.1.69
• pavexc_cli_client: 0.1.68 -> 0.1.69
• pavexc: 0.1.68 -> 0.1.69
• pavexc_rustdoc_types: 0.1.68 -> 0.1.69
• pavex_cli_client: 0.1.68 -> 0.1.69
• pavex_session: 0.1.68 -> 0.1.69
• pavex_session_memory_store: 0.1.68 -> 0.1.69
• pavex_session_sqlx: 0.1.68 -> 0.1.69
• pavexc_cli: 0.1.68 -> 0.1.69
• generate_from_path: 0.1.68 -> 0.1.69

Changelog

pavex

0.1.69 - 2025-01-21

Added

• When Pavex's Server fails to spawn a worker thread, capture that thread's name in the error message
• Add Server::try_serve to give users a chance to handle the case where no connection sources have been registered
• Cache accesses for path dependencies are now significantly faster, since 'cargo' is no longer in the hot path of determining the crate checksum
• Reduce the time spent generating JSON docs by leveraging 'cargo rustdoc' built-in caching mechanism for the single-crate usecase.
• Update Pavex's nightly to 2025-01-04. It unlocks the 2024 edition for Pavex users
• Enable backtraces for panics in the project template, being careful not to capture backtraces for normal errors in libraries such as anyhow. Update the command to force the toolchain install to work with the latest rustup version

Fixed

• Use hyper_util's GracefulShutdown utility to ensure connections are indeed shutdown gracefully
• Don't panic if we fail to serve a connection. Log the error as a warning.
• Lower the logging level to info when reporting about a failure to establish a connection. This event kind is common enough not to deserve a higher logging level.
• Use the blueprint location as the project fingerprint rather than the workspace path, since a workspace may contain multiple blueprints, as it happens for Pavex's UI tests
• The JSON documentation for path dependencies wouldn't be cached if the lock file could not be retrieved. The lockfile is now skipped when computing the dependency hash

Other

• Disable workspace hack before a release
• Rework graceful shutdown tests to remove flakiness
• Move 'tracing_log_error' in its own repository and consume it via crates.io
• Fix clippy lint
• Migrate all tracing events that touch errors to log_error! to ensure consistent field naming
• Clarify why it's fine to panic if tokio can't create a current-thread runtime inside a Pavex Server worker thread
• Re-enable workspace hack after a release
• Add a mechanism to export a profile showing where time is being spent in the setup for UI tests
• Improve span granularity for the computation of the package graph
• Enable tracing for UI tests
• Improve formatting and suggested resolution for a missing nightly toolchain
• Update outdated comment
• Fix clippy lints
• Allow reusing the same cargo metadata output to improve test throughput
• Allow UI tests to cache workspace crates to reduce cargo locking contention
• Fix spacing in error message
• Re-export error-related fields in pavex_tracing from tracing_log_error
• update Cargo.toml dependencies

---

This PR was generated with release-plz.