google / google/rust_icu

After first release from `bazel` build, remove artifacts which were used in the old release process

Open
#394 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
140
Forks
34
Avg merge
5h 5m
Merged PRs (30d)
4

Description

**Prerequisite:** At least one bazel build based release process, governed by the `release-please` action must have already successfully been completed.

This includes, but is not limited to:
- docker container definitions of the build environments
- the versioning metadata (files `LAST_RELEASED_VERSION` and `NEXT_VERSION`)
- Makefiles
- The GitHub workflows relying on Makefiles and docker.
- When modifying the workflows, adapt the status badges for the builds in README.md

Contributor guide

Open the contributing guide

Research direction

Wait for a successful release governed by the release-please action and based on a Bazel build. Then inspect the Docker build-environment definitions, LAST_RELEASED_VERSION, NEXT_VERSION, Makefiles, and GitHub workflows that rely on them. Remove artifacts from the old release process and update the README.md build status badges when workflows change.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, github-actions, rust
Domain
build-system, ci-cd, release
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.