Skip to content

chore(qa): 🤖 relax constraints on "latest" tag usage #984

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
punkbit wants to merge 4 commits into
base: main
Choose a base branch
from
Open

chore(qa): 🤖 relax constraints on "latest" tag usage #984

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
a415a31
chore: 🤖 remove create-release step
punkbit Apr 13, 2026
c86c96c
docs: 📝 update stable releases to include less strict usage of tag
punkbit Apr 13, 2026
5708e7b
fix: 🐛 correct github warning
punkbit Apr 13, 2026
c682d88
docs: 📝 warn about possible downgrades
punkbit Apr 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 0 additions & 8 deletions .github/workflows/create-release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,14 +30,6 @@ jobs:
contents: write
pull-requests: write
steps:
- name: Validate branch for latest release
if: inputs.release_type == 'latest' && github.ref_name != 'main'
run: |
echo "👹 Oops! Cannot release 'latest' from branch '${{ github.ref_name }}'!"
echo "💡 The 'latest' release type can only be created from the 'main' branch."
echo "💡 Maintenance branches should use 'stable' instead."
exit 1

- name: Checkout Repo
uses: actions/checkout@v6
with:
Expand Down
8 changes: 6 additions & 2 deletions docs/package-release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -218,15 +218,19 @@ git push origin chore/v1.0.0

### Promoting to stable release

Stable releases are created from `chore/v*` branches. Once a stable release is published, the pre-release mode is switched off and `main` must be updated to reflect the version bump and exit from pre-release mode.
Stable releases (`stable` or `latest`) can be created from `chore/v*` branches. Once released, the pre-release mode is switched off and `main` must be updated to reflect the version bump and exit from pre-release mode.

> [!WARNING]
> Use `latest` only when you want this version to become the **default** installed by `npm install @clickhouse/click-ui`.
> Publishing `latest` from an older maintenance branch (e.g., `chore/v1.x.x`) **will downgrade** the default for all users who haven't pinned a version, even if a newer `v2.x.x` was previously `latest`.

Follow these steps:

1. Ensure your pre-release has been tested and is ready for production

2. Run the [Create Release](https://github.com/ClickHouse/click-ui/actions/workflows/create-release.yml) workflow from the `chore/v*` branch:
- Select the maintenance branch (e.g., `chore/v1.0.0`)
- Choose `stable` as the release type
- Choose `stable` or `latest` as the release type
- Confirm the release type and branch name

3. Review and merge the release PR into the maintenance branch
Expand Down
Loading