matrix-org / matrix-org/matrix-rust-sdk
Release process bugs
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.3k
- Forks
- 500
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 106
Description
-
The main crate depends on the
ffi-macroscrate which isn't part of the release process. -
The generated changelogs don't work well, changes from one crate bleeds into the changelog of another. (We switched back to manually written changelogs)
-
The main crate, when the
testingfeature is enabled depends on thematrix-sdk-testingcrate. -
edit - I hijacked this issue as a general release process bugs issue
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how releases are assembled for the main crate and inspect its dependency declarations for ffi-macros and the testing-feature dependency on matrix-sdk-testing. Check the changelog generation path and release checklist; done means both dependencies are included correctly and crate-specific changelogs remain isolated, with release validation covering the listed cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100