release: prepare v0.1.0-alpha.1 by flyingrobots · Pull Request #18 · flyingrobots/edict

flyingrobots · 2026-06-21T12:13:59Z

Summary

Set crates/edict-syntax to 0.1.0-alpha.1 and update Cargo.lock.
Move current changelog content into a dated v0.1.0-alpha.1 section.
Add draft release notes for the first front-end alpha milestone.
Link release notes from the docs index.

Release Boundaries

This remains a front-end milestone only:

no crates.io publish (publish = false remains in force)
no Core IR lowering
no canonical Core hash goldens
no target lowerers
no admission tooling

Refs #16.

Validation

cargo xtask verify
npx --yes markdownlint-cli2 CHANGELOG.md docs/README.md docs/releases/v0.1.0-alpha.1.md README.md ROADMAP.md
git diff --cached --check before commit

coderabbitai · 2026-06-21T12:14:12Z

Warning

Review limit reached

@flyingrobots, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 40 minutes and 19 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 1c287991-6908-4392-ac6d-22e674b8b8e6

📥 Commits

Reviewing files that changed from the base of the PR and between 89a4f1b and 1d1a072.

📒 Files selected for processing (4)

.github/workflows/release.yml
ROADMAP.md
docs/releases/v0.1.0-alpha.1.md
xtask/src/main.rs

Walkthrough

Prepares the v0.1.0-alpha.1 release: bumps the edict-syntax crate version from 0.0.0 to 0.1.0-alpha.1 in Cargo.toml, adds a placeholder entry in CHANGELOG.md, introduces a new draft release notes document at docs/releases/v0.1.0-alpha.1.md, and links it from docs/README.md.

Changes

v0.1.0-alpha.1 Release Preparation

Layer / File(s)	Summary
Crate version bump and CHANGELOG placeholder `crates/edict-syntax/Cargo.toml`, `CHANGELOG.md`	Version field updated from `0.0.0` to `0.1.0-alpha.1`; `CHANGELOG.md` gains a `No changes yet.` placeholder under `[Unreleased]` with adjusted spacing before the `[v0.1.0-alpha.1] - 2026-06-24` heading.
Draft release notes and docs index entry `docs/releases/v0.1.0-alpha.1.md`, `docs/README.md`	New 62-line release notes document defining target date, draft status, included scope, non-goals, verification checklist, and tagging commands; `docs/README.md` adds a bullet pointing to it.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related issues

Release v0.1.0-alpha.1 #16: This PR directly fulfills the release checklist items described in that issue — version bump to 0.1.0-alpha.1, CHANGELOG update, and creation of the draft release notes document.

Poem

A version is born, from 0.0.0 it rose,
alpha.1 emerges, as everyone knows.
The changelog whispers "no changes yet," sly—
Release notes drafted beneath a June sky.
Tag it, push it, let the alpha fly! 🚀

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'release: prepare v0.1.0-alpha.1' directly and clearly summarizes the primary objective of the changeset: preparing the v0.1.0-alpha.1 release.
Description check	✅ Passed	The description comprehensively details the changes made (version updates, changelog reorganization, release notes addition) and release boundaries, directly relating to the changeset contents.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/releases/v0.1.0-alpha.1.md`:
- Around line 17-21: The bullet point stating "publish = false remains in force
for all workspace packages" uses imprecise terminology. The root workspace
manifest (Cargo.toml at the repository root) does not have a publish field,
while only the member packages declare publish = false. Revise this bullet point
to clarify that publish = false applies specifically to "all workspace member
packages" rather than "all workspace packages," or alternatively add a note
clarifying that the root workspace manifest does not require this field.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5b8167f4-f6be-4fd0-b28c-4479b623fd01

📥 Commits

Reviewing files that changed from the base of the PR and between ec09644 and 89a4f1b.

⛔ Files ignored due to path filters (1)

Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (4)

CHANGELOG.md
crates/edict-syntax/Cargo.toml
docs/README.md
docs/releases/v0.1.0-alpha.1.md

📜 Review details

🧰 Additional context used

🪛 LanguageTool

docs/releases/v0.1.0-alpha.1.md

[style] ~36-~36: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...publish. - No canonical Core encoder. - No Core IR lowering from the source AST. -...