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

release: v0.1.11 #112

Merged
merged 4 commits into from
Dec 4, 2024
Merged

release: v0.1.11 #112

merged 4 commits into from
Dec 4, 2024

Conversation

notdanilo
Copy link
Contributor

@notdanilo notdanilo commented Dec 4, 2024

Status Type ⚠️ Core Change Issue
Ready Release No None

[0.1.11] - 2024-12-04

🐛 Bug Fixes

📚 Documentation

👷 CI/CD

♻️ Refactor

@notdanilo notdanilo changed the title [Release] v0.1.11 release: v0.1.11 Dec 4, 2024
Comment on lines +208 to +210
if [ "${DRY_RUN}" != "true" ]; then
cargo publish --manifest-path=cli/Cargo.toml --token $CRATES_TOKEN
fi
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@GabrielePicco
Unlike the other crates, I cannot run cargo publish --manifest-path=cli/Cargo.toml --no-verify because it fails with:

error: failed to prepare local package for uploading

Caused by:
  failed to select a version for the requirement `world = "=0.1.11"`
  candidate versions found which didn't match: 0.1.10, 0.1.9, 0.1.8, ...
  location searched: crates.io index
  required by package `bolt-cli v0.1.11 (/root/dev/magicblock-labs/bolt/cli)`

It happens because the crate isn't published yet. This verification is skipped on other crates, like bolt-lang, with -no-verify. But for some reason, it isn't working for bolt-cli.

Would it be probably because it's a binary crate? Idk

Copy link
Contributor

@GabrielePicco GabrielePicco Dec 5, 2024

Choose a reason for hiding this comment

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

@notdanilo Looks like it's searching on crates.io rather than resolving the world dependency from the local path. We may have to investigate, since with the above change we are not checking anymore that we can correctly publish the cli crate

@notdanilo notdanilo merged commit c22a97c into main Dec 4, 2024
21 checks passed
@GabrielePicco GabrielePicco deleted the release/v0.1.11 branch December 5, 2024 07:43
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