kestra-io / kestra-io/docs

[CI] Auto tag upon releasing a new version

Open
#2,023 5 comments 1 reaction 0 assignees View on GitHub
area/backend
Dominant language
Astro
Stars
155
Forks
177
Avg merge
1d 20m
Merged PRs (30d)
192

Description

### Issue description

A tag for the closed version should be added upon releasing a new version (eg. if we release `0.21.0` we should add a `v0.20.x` tag automatically

Contributor guide

Open the contributing guide

Research direction

No file, workflow, or test is named. Start by locating the repository’s release and CI entry points, then define the expected tag for a release such as 0.21.0 and verify that a subsequent release creates it automatically.

Written by the indexing model from the issue text.

Assessment

Tech stack
git
Domain
ci-cd, release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.