vectordotdev / vectordotdev/vector
Publish source tarballs containing vendored dependencies
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
Some users might like to have the ability to download an archive with source code for both Vector itself and all dependencies bundled using cargo vendor. Creation of such an archive can be a part of our release workflow in CI.
This would ensure that in the future it would still be possible to build all versions of Vector from source, even if some of its dependencies become removed from crates.io for any reason.
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 with the release workflow in CI and the existing source-archive process, then check how cargo vendor can bundle Vector's dependencies. Done means release artifacts include a downloadable source tarball containing Vector and all vendored dependencies, and the archive can be used to build the project offline.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100