Skip to content

Conversation

@suchapalaver
Copy link
Contributor

Still out on a limb seeing if the issue here is something we can fix without assuming it's a cargo workspace issue.

@suchapalaver suchapalaver force-pushed the suchapalaver/clean-target-directory-in-release-workflow branch from cc18512 to 4cdb207 Compare May 22, 2025 21:05
@coveralls
Copy link

coveralls commented May 22, 2025

Pull Request Test Coverage Report for Build 15196954956

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 76.053%

Totals Coverage Status
Change from base Build 15174930393: 0.0%
Covered Lines: 1318
Relevant Lines: 1733

💛 - Coveralls

@suchapalaver suchapalaver force-pushed the suchapalaver/clean-target-directory-in-release-workflow branch 3 times, most recently from 2fed7a3 to 7a0c94c Compare May 22, 2025 21:14
@suchapalaver suchapalaver force-pushed the suchapalaver/clean-target-directory-in-release-workflow branch from 7a0c94c to 8e39ceb Compare May 22, 2025 21:14
Copy link

@TypeLevelConsoli TypeLevelConsoli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How weird, cargo tree only shows alloy-signer-local-1.0.6
Hope this helps

@suchapalaver
Copy link
Contributor Author

How weird, cargo tree only shows alloy-signer-local-1.0.6

Hope this helps

Me too!

@suchapalaver suchapalaver merged commit 3047d45 into main May 23, 2025
8 checks passed
@suchapalaver suchapalaver deleted the suchapalaver/clean-target-directory-in-release-workflow branch May 23, 2025 13:54
@suchapalaver
Copy link
Contributor Author

How weird, cargo tree only shows alloy-signer-local-1.0.6 Hope this helps

It didn't! So reverting here along with a more plausible fix, hopefully 🤞

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.

4 participants