8000 build: declare 0.7.0 as the next release by norrietaylor · Pull Request #1758 · gominimal/minimal · GitHub
[go: up one dir, main page]
Skip to content

build: declare 0.7.0 as the next release - #1758

Merged
norrietaylor merged 1 commit into
mainfrom
build/declare-0.7.0
Sep 29, 2026
Merged

build: declare 0.7.0 as the next release#1758
norrietaylor merged 1 commit into
mainfrom
build/declare-0.7.0

Conversation

@norrietaylor
@norrietaylor norrietaylor commented Sep 29, 2026 •
edited by coderabbitai Bot
Loading
Copy link
Copy Markdown
Member

Summary

v0.6.0 was tagged with package.version still at 0.6.0, so scripts/next-version.sh --check fails on main:

next-version: package.version 0.6.0 is not strictly greater than the newest tag v0.6.0 —
Cargo.toml must declare the NEXT release (the commits since v0.6.0 require at least 0.7.0)

That lint runs on every PR through the workspace package_version test and gates the nightly through the release workflow's verify-ci job, so every PR and the nightly are red until the version moves. The range since the tag carries three feat commits and two BREAKING CHANGE footers, which the 0.x rule maps to a minor, so 0.7.0 is the required value, not a choice.

Sets package.version in Cargo.toml and refreshes the seven workspace crate entries in Cargo.lock (cargo update -w; no dependency moved).

Testing

$ scripts/next-version.sh --check
next-version: package.version 0.7.0 satisfies the 67 commit(s) since v0.6.0 (minor bump, at least 0.7.0) and is greater than the newest tag v0.6.0

Checklist

  • Docs updated if behavior changed (none)
  • BREAKING CHANGE: footer present if this is a breaking change

Summary by CodeRabbit

  • Chores
    • Updated the workspace package version from 0.6.0 to 0.7.0. No changes to exported public entities are included in this update, and no end-user functionality changes are noted. This release note reflects the version update only; it does not imply changes to features, compatibility, or behavior.

@norrietaylor
build: declare 0.7.0 as the next release
060a866 
v0.6.0 is tagged, so the package version must move past it, and the
range since the tag carries three features and two breaking changes,
which the 0.x rule maps to a minor. `next-version.sh --check` fails on
main until this lands, through the workspace `package_version` test on
every PR and the release workflow's verify-ci gate in the nightly.
@norrietaylor
norrietaylor requested a review from a team as a code owner September 29, 2026 16:07
@coderabbitai
coderabbitai Bot commented Sep 29, 2026 •
edited
Loading
Copy link
Copy Markdown
Contributor

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Essentials

Run ID: 10da0987-fe39-458b-bf77-24c8742f221e

📥 Commits

Reviewing files that changed from the base of the PR and between 6727d04 and 060a866.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (1)
  • Cargo.toml

Included review availability: This review used your included allowance. 1 included review remains after this review. Your included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour.

📝 Walkthrough

Walkthrough

The workspace package version changes from 0.6.0 to 0.7.0.

Changes

Workspace Version Update

Layer / File(s) Summary
Update workspace version
Cargo.toml		 The workspace package version changes from 0.6.0 to 0.7.0.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Suggested reviewers: 0chroma

Merge Risk: ⚪ Minimal · up to 060a8

The workspace and release lockfile versions are synchronized at 0.7.0. The available evidence does not confirm the version gate’s calculated minimum, so rely on the tag-aware PR check before merging.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly describes the primary change: declaring version 0.7.0 as the next release. It is concise and follows the repository's Conventional Commit format.
Description check ✅ Passed The description includes the required Summary, Testing, and Checklist sections. It explains the reason for the version bump, identifies the affected files, provides test output, and addresses the chec…
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR

A rabbit checks the version line,
From six to seven, neat and fine.
One small edit marks the day,
The burrow hops along its way.
Soft paws leave the old tag behind.

Comment @coderabbitai help to get the list of available commands.

@minimal-foundry
minimal-foundry Bot commented Sep 29, 2026 •
edited
Loading
Copy link
Copy Markdown
Contributor

Approved: no findings at 060a866d6015.

Nothing to do.

Clobber: none: git log on both files shows the prior commits are dependency bumps / unrelated feature work; no recent fix reverted.

@norrietaylor
norrietaylor enabled auto-merge (squash) September 29, 2026 16:09
minimal-foundry[bot]
minimal-foundry Bot approved these changes Sep 29, 2026
View reviewed changes
@minimal-foundry minimal-foundry Bot left a comment
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minimal-review — approved

Verdict APPROVE — No findings.

@minimal-foundry minimal-foundry Bot added the review:approved minimal-review approved the current head label Sep 29, 2026
@norrietaylor
norrietaylor merged commit 3828ef8 into main Sep 29, 2026
28 of 33 checks passed
@norrietaylor
norrietaylor deleted the build/declare-0.7.0 branch September 29, 2026 16:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@mitodrummer mitodrummer mitodrummer approved these changes
@coderabbitai coderabbitai[bot] coderabbitai[bot] approved these changes
@bryan-minimal bryan-minimal bryan-minimal approved these changes
@minimal-foundry minimal-foundry[bot] minimal-foundry[bot] approved these changes

Assignees

No one assigned

Labels

review:approved minimal-review approved the current head

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@norrietaylor @mitodrummer @bryan-minimal
0