Unify release pipelines for related packages
Open
area/extensions
engsys
- Dominant language
- Go
- Stars
- 569
- Forks
- 364
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 136
Description
We should mirror what we've done for data plane language repos so we can release updated packages together and avoid versioning mismatches (i.e., the ability to release all Foundry packages or just some subset).
Contributor guide
Research direction
Start by reviewing the existing release approach for data plane language repositories and identifying how Foundry packages are currently versioned and released. Done means related packages can be released together, either as all Foundry packages or as a selected subset, without versioning mismatches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100