Prepare v0.1.0-alpha.1 release#33
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3fbe99baa9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| run: | | ||
| set -euo pipefail | ||
| tag="${GITHUB_REF_NAME}" | ||
| if [[ ! "${tag}" =~ ^v[0-9]+\.[0-9]+\.[0-9]+(-(alpha|beta|rc)\.[0-9]+)?$ ]]; then |
There was a problem hiding this comment.
The release policy added in docs/releases.md requires release tags to point at main after CI, but this workflow accepts any matching v* tag and the publish step only uses gh release create --verify-tag, which the gh manual documents as checking that the tag already exists. If a maintainer accidentally pushes a semver tag from an unmerged release-prep or feature branch, these jobs can still publish archives and a GitHub release for code that never landed on main; add a git branch --remotes --contains "$GITHUB_SHA"/origin/main containment check before publishing.
Useful? React with 👍 / 👎.
| --repo "${GITHUB_REPOSITORY}" \ | ||
| --verify-tag \ | ||
| --title "FTWDB ${GITHUB_REF_NAME}" \ | ||
| --notes-from-tag \ |
There was a problem hiding this comment.
The new process relies on annotated tags to carry the release notes, but --notes-from-tag does not enforce that: the gh manual says a non-annotated tag falls back to the commit message. If someone pushes a lightweight v... tag, this workflow still publishes a release, but the notes can omit the known limits/platform support required by the release policy; add an explicit git cat-file -t "$GITHUB_REF_NAME" check for tag in the verify job.
Useful? React with 👍 / 👎.
1 participant
Summary
0.1.0-alpha.1SHA256SUMS, and creates the GitHub releaseWhy
FTWDB has no tag or release yet, while its merged code and CI now support a useful evaluation build. This change makes the first release an explicit alpha and records the gaps that still block beta or stable status.
The release stays on GitHub. Publishing to crates.io remains a separate choice.
Validation
actionlint .github/workflows/ci.yml .github/workflows/release.ymlpython3 -m unittest -v bench.adapters.test_questdbcargo fmt --all -- --checkcargo clippy --all-targets --all-features --locked --offline -- -D warningscargo test --all-targets --all-features --locked --offlinecargo test --doc --all-features --locked --offlinecargo build --release --locked --offlinecargo package --locked --offlineLocal result: 151 main tests and 11 emulator tests passed. The verified crate contains 66 files and is 2.7 MiB compressed.
Release limits