Skip to content

Commit

Permalink
chore: release v0.1.69 (#421)
Browse files Browse the repository at this point in the history
  • Loading branch information
pavex-releaser[bot] authored Jan 21, 2025
1 parent 5c9dfc1 commit afc0209
Show file tree
Hide file tree
Showing 23 changed files with 74 additions and 258 deletions.
26 changes: 26 additions & 0 deletions libs/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,32 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

## [0.1.69](https://github.com/LukeMathWalker/pavex/compare/0.1.68...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 shut down 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 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

### Other

- 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
- Improve suggested resolution for a missing nightly toolchain
- Re-export error-related fields in `pavex_tracing` from `tracing_log_error`
- Update dependency versions

## [0.1.68](https://github.com/LukeMathWalker/pavex/compare/0.1.67...0.1.68) - 2025-01-05

### Fixed
Expand Down
117 changes: 19 additions & 98 deletions libs/Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion libs/Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ edition = "2021"
repository = "https://github.com/LukeMathWalker/pavex"
homepage = "https://pavex.dev"
license = "Apache-2.0"
version = "0.1.68"
version = "0.1.69"

[workspace.dependencies]
vergen-gitcl = { version = "1.0.5", features = ["build"] }
Expand Down
1 change: 0 additions & 1 deletion libs/generate_from_path/Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -20,4 +20,3 @@ indicatif = { workspace = true }
walkdir = { workspace = true }
sanitize-filename = { workspace = true }
regex = { workspace = true }
px_workspace_hack = { version = "0.1", path = "../px_workspace_hack" }
Loading

0 comments on commit afc0209

Please sign in to comment.