Skip to content

Add a CHANGELOG, pin the install URL to the tag, drop lint.yml#40

Merged
leogdion merged 3 commits into
v1.0.0-integrationfrom
release-1.0.0
Jul 25, 2026
Merged

Add a CHANGELOG, pin the install URL to the tag, drop lint.yml#40
leogdion merged 3 commits into
v1.0.0-integrationfrom
release-1.0.0

Conversation

@leogdion

@leogdion leogdion commented Jul 25, 2026

Copy link
Copy Markdown
Member

Merge order: 6 of 6, into v1.0.0-integration — merge last, so the pinned
curl URL lands immediately before the tag.

Closes #30, closes #33.

#30 — CHANGELOG and release notes

CHANGELOG.md in Keep a Changelog form with a
## [1.0.0] section. For a first release it describes the tool rather than a
diff:

Curl URL pinned to v1.0.0

Deliberately last: the README URL 404s in the window between this merging and
the tag existing, so the two should happen back to back.

#33lint.yml

A three-line comment-only file at the repo root saying linting moved to
.github/workflows/ci.yml. GitHub never ran it — it isn't in
.github/workflows/ — and it is tracked, so it would have shipped inside the tag
as a note to maintainers about a refactor that already happened. The commit that
moved the workflow is the durable record.

grep -rn 'lint\.yml' now returns only the CHANGELOG entry recording the
removal.

Scope notes

Release checklist

Then, to publish — this extraction command is verified against the file as
committed (sed -n '/## 1.0.0/,/## 0/p' from #30 does not terminate, since
there is no earlier version section):

gh release create v1.0.0 --title "v1.0.0" --notes-file <(
  awk '/^## \[1\.0\.0\]/{f=1} /^\[Unreleased\]:/{f=0} f' CHANGELOG.md
)

I have not cut the tag or created the release — that is outward-facing and
yours to run.

🤖 Generated with Claude Code

@coderabbitai

coderabbitai Bot commented Jul 25, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: b26cf164-8132-45c6-ba63-0754d4508309

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release-1.0.0

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.

@leogdion
leogdion changed the base branch from main to v1.0.0-integration July 25, 2026 17:43
CI and others added 2 commits July 25, 2026 15:04
**#30** — a first stable tag is where users and packagers start needing a record
of what the tool is and what its rough edges are. `CHANGELOG.md` follows Keep a
Changelog with a `## [1.0.0]` section. For a first release it describes the tool
rather than a diff: the five subcommands, the container layout, the four env
vars, the corrected bash requirement, the behavior worth knowing (that `add`
writes to the remote, and that `clean` is absent), every fix that landed in this
batch, and the known limitations.

**Curl URL** now points at `v1.0.0` instead of `main`, with a note that `main`
is a moving target. This lands last on purpose: the README URL 404s in the window
between merging this and cutting the tag, so the two should happen together.

**#33** — `lint.yml` was a three-line comment-only file at the repo root
explaining that linting moved to `.github/workflows/ci.yml`. GitHub never ran it,
and it would have shipped inside the tag as a note to maintainers about a
refactor that already happened. Removed; the commit that moved the workflow is
the durable record.

Closes #30, closes #33.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
1.0.0 is the first release, so an entry explaining that `clean` existed and was
pulled refers to a version nobody ran. State the property instead — nothing here
deletes — and drop the now-orphaned [#17] and [#34] link definitions.

The "branch names may not contain /" entry is also no longer true: branches with
slashes are supported and slug to `-` in the directory name. Restated, including
the feature/x vs feature-x collision that falls out of it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
A first release should list shipped features with PR links, not Keep a Changelog archaeology that implies a prior version.

Co-authored-by: Cursor <cursoragent@cursor.com>
@leogdion
leogdion merged commit d3e5c11 into v1.0.0-integration Jul 25, 2026
4 checks passed
@leogdion
leogdion deleted the release-1.0.0 branch July 25, 2026 19:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove the dead lint.yml at the repo root Add a CHANGELOG and v1.0.0 release notes

1 participant