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.

Sign up for GitHub

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

Jump to bottom

Update the release notes to work for current releases #1842

Merged
merged 1 commit into from
Oct 25, 2024
Merged

Update the release notes to work for current releases #1842

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 15 additions & 6 deletions RELEASING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,14 +76,23 @@ We also assume that ongoing work done is being merged directly to the `master` b

```
(cd metadata && cargo publish) && \
(cd lightclient && cargo publish) && \
(cd codegen && cargo publish) && \
(cd macro && cargo publish) && \
(cd subxt && cargo publish) && \
(cd signer && cargo publish) && \
(cd cli && cargo publish);
(cd lightclient && cargo publish) && \
(cd utils/fetch-metadata && cargo publish) && \
(cd codegen && cargo publish) && \
(cd macro && cargo publish);
```

Now, remove the dev dependencies from `subxt-core` (to avoid circular deps), and then run:

```
(cd core && cargo publish) && \
(cd subxt && cargo publish) && \
(cd signer && cargo publish) && \
(cd cli && cargo publish);
```

Finally, put back the dev dependencies in `subxt-core`.

11. If the release was successful, tag the commit that we released in the `master` branch with the
version that we just released, for example:

Expand Down
Loading