Skip to content

fix(build): Correctly override release profile.#798

Merged
calavera merged 1 commit intomainfrom
ws_release_profile
Feb 26, 2025
Merged

fix(build): Correctly override release profile.#798
calavera merged 1 commit intomainfrom
ws_release_profile

Conversation

@calavera
Copy link
Collaborator

Always read the release profile info from the workspace manifest since it's the only one that Cargo cares about regardless of where you execute the build command.

Fixes #790

Always read the release profile info from the workspace manifest since it's the only one that Cargo cares about regardless of where you execute the build command.
@calavera calavera merged commit 8078efd into main Feb 26, 2025
6 checks passed
@calavera calavera deleted the ws_release_profile branch February 26, 2025 19:34
@github-actions
Copy link
Contributor

This pull request has been automatically locked. Create a new discussion if you'd like to continue the conversation. https://github.com/cargo-lambda/cargo-lambda/discussions/new?category=general

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 26, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

cargo lambda build --release doesn't read profile overrides from Cargo.toml when executed in subdirectory

1 participant