mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-25 17:25:57 +03:00
[PR #3639] [CLOSED] release optimization #3322
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#3322
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/dani-garcia/vaultwarden/pull/3639
Author: @tessus
Created: 7/3/2023
Status: ❌ Closed
Base:
main← Head:build/release-optimization📝 Commits (1)
4fa4600release optimization📊 Changes
1 file changed (+7 additions, -3 deletions)
View changed files
📝
Cargo.toml(+7 -3)📄 Description
This optimization is not only for size but also runtime. Who doesn't want to use less CPU cycles? ;-)
Since releases are not done that often and usually via build machines and pipelines, I don't see it as an issue that the build time doubled.
That being said, if this is too extreme for a default release, I can also add another profile (e.g. called
productionor something similar).Build command:
cargo build --features sqlite,mysql,postgresql --release🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.