Enable producing native debug symbols in canary/dev releases #9679
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
↪️ Pull Request
Added
debug = true
to the canary release profile, this produces binaries with symbol debug information included. Existingstrip
operations take care of stripping these back out for the@parcel/rust
package itself, however before westrip
we now use platform specific tools to extract debug symbols out to a separate file / artifact.At "build and release" time these are combined into a single
debug-symbols
artifact for ease of use. Any additional work is gated to only the dev/canary releases - there's a minor impact to build time, especially uploading the combined artifact, but it's pretty minor.This has no impact on final
@parcel/rust
binary size (as the debug info is stripped), and it will be on our end when we bump to a canary to download the debug symbols artifact and upload it to Sentry.Example dev-release with these changes: https://github.com/parcel-bundler/parcel/actions/runs/8902598798