pezkuwichain/pezkuwi-subxt
1
0
Fork 0
mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-06-09 20:11:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add Cargo.lock for deterministic builds (#795)

Browse Source 
* Remove Cargo.lock from gitignore

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>

* cargo: Add `Cargo.lock`

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>

* Update the releasing process

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
This commit is contained in:
Alexandru Vasile
2023-01-18 18:10:29 +02:00
committed by GitHub
parent b4bb17662a
commit c0198acea8
3 changed files with 4382 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitignore
-1
View File
@@ -1,5 +1,4 @@
/target
**/*.rs.bk
**/.DS_Store
Cargo.lock
cargo-timing*
Cargo.lock
Generated
+4371
View File
File diff suppressed because it is too large Load Diff
RELEASING.md
+11 -5
View File
@@ -28,7 +28,13 @@ We also assume that ongoing work done is being merged directly to the `master` b
4. Bump the crate version in `Cargo.toml` to whatever was decided in step 2 for `subxt-metadata`, `subxt-cli`, `subxt-codegen`, `subxt-examples`, `subxt-macro` ,`subxt`, `integration-tests`, `test-runtime`, `ui-tests`.
5. Update `CHANGELOG.md` to reflect the difference between this release and the last. If you're unsure of
5. Ensure the `Cargo.lock` file is up to date.
```
cargo generate-lockfile
```
6. Update `CHANGELOG.md` to reflect the difference between this release and the last. If you're unsure of
what to add, check with the Tools team. See the `CHANGELOG.md` file for details of the format it follows.
First, if there have been any significant changes, add a description of those changes to the top of the
@@ -44,11 +50,11 @@ We also assume that ongoing work done is being merged directly to the `master` b
provide `[+] Latest release tag: v0.16.0` ). Then group the PRs into "Fixed", "Added" and "Changed" sections, and make any
other adjustments that you feel are necessary for clarity.
6. Commit any of the above changes to the release branch and open a PR in GitHub with a base of `master`.
7. Commit any of the above changes to the release branch and open a PR in GitHub with a base of `master`.
7. Once the branch has been reviewed and passes CI, merge it.
8. Once the branch has been reviewed and passes CI, merge it.
8. Now, we're ready to publish the release to crates.io.
9. Now, we're ready to publish the release to crates.io.
1. Checkout `master`, ensuring we're looking at that latest merge (`git pull`).
@@ -80,7 +86,7 @@ We also assume that ongoing work done is being merged directly to the `master` b
If you run into any issues regarding crates not being able to find suitable versions of other `subxt-*` crates,
you may just need to wait a little longer and then run the remaining portion of that command.
9. If the release was successful, tag the commit that we released in the `master` branch with the
10. If the release was successful, tag the commit that we released in the `master` branch with the
version that we just released, for example:
```