search

pksunkara / cargo-workspaces

A tool for managing cargo workspaces and their crates, inspired by lerna
MIT License
465 stars 46 forks source link

error: config value `http.cainfo` is not set #161

Closed patrickelectric closed 2 months ago

patrickelectric commented 2 months ago

I'm getting this message when using --no-git-push and with correct CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO }}

Action: https://github.com/mavlink/rust-mavlink/actions/runs/9996941544/job/27632356717

pksunkara commented 2 months ago

That error is harmless.

Current HEAD is already released, skipping versioning

is the actual message from publish command. --publish-as-is is the option you want. Please go through all the options in both the version and publish commands.

I am not even sure why you are trying to create a new version in CI on a tag. Please try to read each subcommand's and option's description closely.

patrickelectric commented 2 months ago

I am not even sure why you are trying to create a new version in CI on a tag.

The problem is that I want to create an automatic deployment system, for that I need to trigger the deployment somehow, and in this case I'm using a tag. The tag triggers an action that runs using cargo workspaces for deployment, at least that is what I'm trying to do. It's weird to say that the HEAD was released while crates.io is still not updated.

patrickelectric commented 2 months ago

--publish-as-is

I'm also accepting alternatives to do the automatic deployment.

patrickelectric commented 2 months ago

Btw, it's also not updating all TOML versions. It's a bit hard to test it locally, since dry-run does not exist and it's possible to accidentally to put the release on crates.io

pksunkara commented 2 months ago

The problem is that I want to create an automatic deployment system, for that I need to trigger the deployment somehow, and in this case I'm using a tag.

The version command relies on tags and thus says it has already been tagged & released.

Just run the publish command with the above-mentioned option and that should publish to crates.io from CI. But, it doesn't update the version in Cargo.toml.

So, for best practice, you will have to run the version command locally which updates the version and creates a tag, which triggers your CI containing the publish command.

It's a bit hard to test it locally, since dry-run does not exist and it's possible to accidentally to put the release on crates.io

Try testing locally with version command to see what the version changes are. Make sure to have --no-git-push, that way, it's not sent anywhere and you can reset things.

patrickelectric commented 2 months ago

Thanks for the tips! I'll checkout!

Em qui., 18 de jul. de 2024 às 16:06, Pavan Kumar Sunkara < @.***> escreveu:

The problem is that I want to create an automatic deployment system, for that I need to trigger the deployment somehow, and in this case I'm using a tag.

The version command relies on tags and thus says it has already been tagged & released.

Just run the publish command with the above-mentioned option and that should publish to crates.io from CI. But, it doesn't update the version in Cargo.toml.

So, for best practice, you will have to run the version command locally which updates the version and creates a tag, which triggers your CI containing the publish command.

It's a bit hard to test it locally, since dry-run does not exist and it's possible to accidentally to put the release on crates.io

Try testing locally with version command to see what the version changes are. Make sure to have --no-git-push, that way, it's not sent anywhere and you can reset things.

— Reply to this email directly, view it on GitHub https://github.com/pksunkara/cargo-workspaces/issues/161#issuecomment-2237340575, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJIYCMOZTXBWPGWJKZR6BDZNAG2JAVCNFSM6AAAAABLDHQPX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZXGM2DANJXGU . You are receiving this because you authored the thread.Message ID: @.***>

-- Patrick José Pereira Electronics Engineer