Add TinyBus module integration and release binaries #2
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,73 @@ | ||
| #!/usr/bin/env bash | ||
| set -euo pipefail | ||
|
|
||
| minimum="${1:-90}" | ||
| report="${2:-coverage.json}" | ||
| workspace_root="$(pwd -P)/" | ||
| source_root="${workspace_root}src/" | ||
|
|
||
| cargo llvm-cov \ | ||
| --locked \ | ||
| --all-targets \ | ||
| --all-features \ | ||
| --json \ | ||
| --output-path "$report" | ||
|
|
||
| covered_files="$(jq --arg source_root "$source_root" ' | ||
| [ | ||
| .data[].files[] | ||
| | select(.filename | startswith($source_root)) | ||
| | select(.summary.lines.count > 0) | ||
| ] | ||
| | length | ||
| ' "$report")" | ||
|
|
||
| if [[ "$covered_files" -eq 0 ]]; then | ||
| echo "coverage report contains no files with executable lines under src/" >&2 | ||
| exit 1 | ||
| fi | ||
|
|
||
| summary="$(jq -r --arg workspace_root "$workspace_root" --arg source_root "$source_root" ' | ||
| .data[].files[] | ||
| | select(.filename | startswith($source_root)) | ||
| | select(.summary.lines.count > 0) | ||
| | [ | ||
| (.filename | ltrimstr($workspace_root)), | ||
| (.summary.lines.percent | tostring), | ||
| (.summary.lines.covered | tostring), | ||
| (.summary.lines.count | tostring) | ||
| ] | ||
| | @tsv | ||
| ' "$report")" | ||
|
|
||
| printf 'File\tLine coverage\tCovered lines\tCoverable lines\n' | ||
| while IFS=$'\t' read -r file percent covered count; do | ||
| printf '%s\t%.2f%%\t%s\t%s\n' "$file" "$percent" "$covered" "$count" | ||
| done <<< "$summary" | ||
|
|
||
| if [[ -n "${GITHUB_STEP_SUMMARY:-}" ]]; then | ||
| { | ||
| printf '### Per-file line coverage\n\n' | ||
| printf '| File | Coverage | Lines |\n' | ||
| printf '| --- | ---: | ---: |\n' | ||
| while IFS=$'\t' read -r file percent covered count; do | ||
| printf '| %s | %.2f%% | %s/%s |\n' "$file" "$percent" "$covered" "$count" | ||
| done <<< "$summary" | ||
| } >> "$GITHUB_STEP_SUMMARY" | ||
| fi | ||
|
|
||
| failures="$(jq -r \ | ||
| --arg workspace_root "$workspace_root" \ | ||
| --arg source_root "$source_root" \ | ||
| --argjson minimum "$minimum" ' | ||
| .data[].files[] | ||
| | select(.filename | startswith($source_root)) | ||
| | select(.summary.lines.count > 0) | ||
| | select(.summary.lines.percent < $minimum) | ||
| | "\(.filename | ltrimstr($workspace_root)): \(.summary.lines.percent)%" | ||
| ' "$report")" | ||
|
|
||
| if [[ -n "$failures" ]]; then | ||
| printf '\nFiles below %s%% line coverage:\n%s\n' "$minimum" "$failures" >&2 | ||
| exit 1 | ||
| fi |
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🩺 Stability & Availability | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: tinyhumansai/tinydocs
Length of output: 159
🏁 Script executed:
Repository: tinyhumansai/tinydocs
Length of output: 273
🏁 Script executed:
Repository: tinyhumansai/tinydocs
Length of output: 544
🏁 Script executed:
Repository: tinyhumansai/tinydocs
Length of output: 11173
🌐 Web query:
Cargo cargo update --workspace after manifest version changes documentation💡 Result:
The cargo update --workspace command is designed to update dependencies as recorded in the Cargo.lock file, specifically targeting packages defined within your workspace [1][2]. According to the official Cargo documentation, the --workspace (or -w) flag is primarily useful for updating Cargo.lock after you have manually changed version numbers in your Cargo.toml files [1][2]. When you use this flag, Cargo attempts to update only the packages defined in the workspace, while other packages are updated only if they do not already exist in the lockfile [1][3]. It is important to note that the cargo update command does not automatically modify or write to your Cargo.toml files to reflect new version requirements [4]. The command updates the dependency versions pinned in the Cargo.lock file based on the constraints already present in your manifest [2][5]. If you are looking to automatically update the version requirements inside your Cargo.toml files (e.g., upgrading a dependency to the latest version), you would typically use external tools like cargo-edit (specifically the cargo upgrade command) rather than cargo update [4][6]. In summary: - cargo update --workspace: Updates Cargo.lock to match changes you have already made in Cargo.toml [1][2]. - Cargo.toml changes: You must manually edit these or use other tools; cargo update will not update them for you [4].
Citations:
cargo-upgrade) rust-lang/cargo#10498Update the whole workspace lock after the version edits.
The release workflow edits both
Cargo.tomlandcrates/tinydocs-module/Cargo.toml, then recordsCargo.lockand later uses--lockedbuilds.cargo update -p "$CRATE_NAME" --precise "$NEXT_VERSION"only refreshestinydocs; runcargo update --workspaceinstead so both workspace package entries in the lockfile stay aligned.🤖 Prompt for AI Agents