Prepare for initial re-release #30
Conversation
|
@einarmo not the right place to discuss it , but you shold rename the repository to async-opcua too so it is possible to google it knowning the crate name |
|
I also hope you have a script so you do not need to do all of that for every release... |
|
The changelog needs a script, but I committed one for bumping all the version numbers, using We should probably rename the repo, yes. |
einarmo
force-pushed
the
release-pipeline
branch
from
9ff84c8 to
3f892c0
Compare
Maybe... But then again the Python repo is also just called |
Fair enough. Let's rename the repo. I'll do that before actually cutting the release so that the metadata on crates.io isn't instantly out of sync. |
|
Looks like the default rust version on github actions went up to 1.84 after I made the PR, fixed it in #32. |
Create a couple of scripts using cargo-release to simplify bumping versions and release management. Since we have so many crates it's a little hairy, so I added some scripts to make it more manageable. Set versions on all the crates we intend to publish for now. In the future we may want to find a good way to publish opcua-codegen too, but since it's a binary, not a crate, we will have to look into publishing it as a cargo tool or something along those lines. The first release will need to be done manually. Not only are we exceeding the per minute limit of new crates (5), but cargo-release doesn't play that well with new releases of interdependent crates. I hope to create a proper release pipeline to automate this in the future.
einarmo
force-pushed
the
release-pipeline
branch
from
3f892c0 to
349d57b
Compare
Create a couple of scripts using cargo-release to simplify bumping versions and release management. Since we have so many crates it's a little hairy, so I added some scripts to make it more manageable.
I also wrote a rough changelog on the keep-a-changelog format. The old changelog is a little confusing in context, and uses a different format, so I moved it into docs as old_changelog.md.
Set versions on all the crates we intend to publish for now. In the future we may want to find a good way to publish opcua-codegen too, but since it's a binary, not a crate, we will have to look into publishing it as a cargo tool or something along those lines.
The first release will need to be done manually. Not only are we exceeding the per minute limit of new crates (5), but cargo-release doesn't play that well with new releases of interdependent crates. I hope to create a proper release pipeline to automate this in the future.