Please mark alpha/beta releases as "Pre-releases"

Open Beginner friendly
  • Is something wrong?
#16,147 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
release

Research direction

Start by inspecting the repository's release publishing workflow or entry point and compare the release metadata with the Ollama releases linked in the issue. Confirm how alpha and beta versions are identified; done means those releases are marked as pre-releases so automated discovery does not treat them as regular releases.

Written by the indexing model from the issue text.

Description

Currently you publish them as regular releases and our release auto-discovery system picks them up.

Look ho Ollama does it: https://github.com/ollama/ollama/releases

Dominant language
Rust
Stars
113k
Forks
4.2k
Avg merge
2d 8h
Merged PRs (30d)
82

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tauri-apps/tauri

All issues in tauri-apps/tauri

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.