Skip to content

Bump compat for StridedViews to 0.5#53

Merged
mtfishman merged 1 commit intomainfrom
mf/bump-stridedviews-0.5
Apr 23, 2026
Merged

Bump compat for StridedViews to 0.5#53
mtfishman merged 1 commit intomainfrom
mf/bump-stridedviews-0.5

Conversation

@mtfishman
Copy link
Copy Markdown
Member

@mtfishman mtfishman commented Apr 23, 2026

Combined weakdep + test compat bump for StridedViews 0.5. Original CompatHelper pair PRs were merged+reverted due to need for combined testing.

Changes

  • root/Project.toml: StridedViews = "0.4.1""0.4.1, 0.5"
  • test/Project.toml: StridedViews = "0.4""0.4, 0.5"
  • Project.toml: version 0.4.140.4.15

Supersedes (auto-close on merge)

🤖 Generated with Claude Code

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 23, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.12%. Comparing base (f729905) to head (c2e5658).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #53   +/-   ##
=======================================
  Coverage   78.12%   78.12%           
=======================================
  Files          10       10           
  Lines         160      160           
=======================================
  Hits          125      125           
  Misses         35       35           
Flag Coverage Δ
docs 8.44% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

mtfishman added a commit to ITensor/ITensorActions that referenced this pull request Apr 23, 2026
## Summary

Small bug in the shared \`FormatCheck.yml\` concurrency config. The
group was:

\`\`\`yaml
concurrency:
group: \"\${{ inputs.concurrent-jobs && github.run_id || github.ref
}}:\${{ github.workflow }}\"
cancel-in-progress: \${{ !inputs.concurrent-jobs &&
inputs.cancel-in-progress }}
\`\`\`

For \`pull_request_target\` events, \`github.ref\` is the target branch
(\`refs/heads/main\`), so every open PR's format check ended up in the
same
concurrency group. With \`cancel-in-progress: true\`, whenever any PR
triggered
a new format check, it cancelled in-progress format checks on all other
PRs —
which is why PRs frequently show \"Format Check / Check Formatting:
cancelled\"
for no visible reason.

Observed concretely on
[ITensor/FunctionImplementations.jl#53](ITensor/FunctionImplementations.jl#53):
the Format Check was cancelled when a different CompatHelper PR started
a run
on the same repo.

## Fix

Key the group on \`github.event.pull_request.number\` when it's
available, so
each PR has its own group. Fall back to \`github.ref\` for non-PR
triggers
(e.g. scheduled or manual dispatch).
@mtfishman mtfishman merged commit c05cc5b into main Apr 23, 2026
28 of 31 checks passed
@mtfishman mtfishman deleted the mf/bump-stridedviews-0.5 branch April 23, 2026 12:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant