Skip to content
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

Create the v0.1.14 release - 2nd attempt #110

Merged
merged 3 commits into from
Oct 18, 2023
Merged

Create the v0.1.14 release - 2nd attempt #110

merged 3 commits into from
Oct 18, 2023

Conversation

oxarbitrage
Copy link
Contributor

This replaces #109 but with the versions bumped.

In #109 i created a branch with the same name as the tag so i can't push anymore so created the new v0.1.14_2 branch here.

Then i think we will have to manually tag here in github as the new version was upgraded in crates.io (https://crates.io/crates/zcash_script) but the tag was not created in github:

oxarbitrage@oxarbitrage-Lenovo-ideapad-320S-14IKB:~/zebra/zcash_script_v0.1.14/2/zcash_script$ cargo release --execute patch
Release zcash_script 0.1.14? [y/N] 
y
   Upgrading zcash_script from 0.1.13 to 0.1.14
[v0.1.14 392123b] chore: Release zcash_script version 0.1.14
 4 files changed, 6 insertions(+), 3 deletions(-)
  Publishing zcash_script
    Updating crates.io index

...

note: Waiting for `zcash_script v0.1.14` to be available at registry `crates-io`.
You may press ctrl-c to skip waiting; the crate should be available shortly.
   Published zcash_script v0.1.14 at registry `crates-io`
error: object is no commit object; class=Invalid (3)
oxarbitrage@oxarbitrage-Lenovo-ideapad-320S-14IKB:~/zebra/zcash_script_v0.1.14/2/zcash_script$ 

arya2
arya2 previously approved these changes Oct 18, 2023
CHANGELOG.md Outdated Show resolved Hide resolved
@oxarbitrage oxarbitrage merged commit 6c2eb13 into master Oct 18, 2023
15 checks passed
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.

2 participants