Skip to content

Fix release pipeline #363

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 1, 2022
Merged

Fix release pipeline #363

merged 1 commit into from
Sep 1, 2022

Conversation

Fraccaman
Copy link
Collaborator

No description provided.

@juped
Copy link
Contributor

juped commented Aug 21, 2022

noting that if they ever address their issue actions/checkout#882 in the future, we may be able to remove this

actually, it seems to suggest we would still have this issue even with depth 0?

@juped juped added this to the v0.8.0 milestone Aug 21, 2022
@Fraccaman
Copy link
Collaborator Author

Tested this on my fork, seems like its working

@Fraccaman Fraccaman added the CI label Sep 1, 2022
@tzemanovic tzemanovic merged commit afcdb2f into main Sep 1, 2022
@tzemanovic tzemanovic deleted the fraccaman/fix-ci-release branch September 1, 2022 15:22
phy-chain pushed a commit to phy-chain/namada that referenced this pull request Mar 1, 2024

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
* Implement better Ledger error handling for all cases

* Remove redundant reveal pk
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants