Repository navigation
CI: ship the two libsqlite3.so.0 builds as one artifact, in per-target folders - #45
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The two libsqlite3.so.0 builds currently ship as separate single-file artifacts, so a release needs two attachments with bare files inside. This stages both into libsqlite3/{x86_64-linux-gnu,aarch64-linux-gnu}/ and uploads one combined libsqlite3.so.0 artifact in the bundle's per-target layout; the digests step follows the staged paths. Workflow files cannot be pushed by the connector, so the branch carries the new workflow as build.yml.new: rename it to .github/workflows/build.yml (web UI) before merging, and branch CI will exercise it.