Skip to content

chore: release v1.6.2#465

Merged
jdx merged 1 commit intomainfrom
release-plz-2026-05-01T22-10-07Z
May 1, 2026
Merged

chore: release v1.6.2#465
jdx merged 1 commit intomainfrom
release-plz-2026-05-01T22-10-07Z

Conversation

@mise-en-dev
Copy link
Copy Markdown
Collaborator

@mise-en-dev mise-en-dev commented May 1, 2026

🤖 New release: v1.6.2

This PR bumps the workspace to v1.6.2 and regenerates CHANGELOG entries, aube.usage.kdl, the CLI docs, and release.json.

Manually pinned to 1.6.2 (overriding release-plz's natural feat:-driven 1.7.0 minor bump). Merge ASAP — any new push to main will retrigger release-plz-pr which will recompute 1.7.0 and force-push this branch.

See the diff for the full set of changes, or the per-crate CHANGELOG.md files for the release notes that will ship.


Generated by the release-plz-pr workflow, manually retargeted to v1.6.2.

@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented May 1, 2026

Greptile Summary

This is an automated release PR that bumps all workspace crates from 1.6.1 to 1.6.2, regenerates Cargo.lock, aube.usage.kdl, CLI docs, CHANGELOG entries, and release.json. However, the PR title and description both claim this is a v1.7.0 release while every changed file consistently targets 1.6.2 — this discrepancy should be confirmed before merging.

Confidence Score: 4/5

Safe to merge once the v1.7.0 vs v1.6.2 title/description discrepancy is confirmed as intentional or corrected.

All file changes are internally consistent at v1.6.2, but the PR title and description advertise v1.7.0. This mismatch is a P1 concern that warrants confirmation before merging.

release.json and Cargo.toml — version bump target contradicts the PR title

Important Files Changed

Filename Overview
release.json Version updated to 1.6.2 with a new timestamp — contradicts the PR title's claim of v1.7.0
Cargo.toml Workspace version bumped from 1.6.1 → 1.6.2; all internal crate path entries updated consistently
Cargo.lock All workspace crates regenerated at 1.6.2; lock file is internally consistent
crates/aube/CHANGELOG.md Adds 1.6.2 entry documenting the engines check feature from PR #458
crates/aube-resolver/CHANGELOG.md Adds 1.6.2 entry documenting the engines check feature from PR #458
docs/cli/commands.json Version field updated from 1.6.1 to 1.6.2; no other changes
docs/cli/index.md Version string updated from 1.6.1 to 1.6.2
aube.usage.kdl Version updated from 1.6.1 to 1.6.2 in the usage spec

Reviews (2): Last reviewed commit: "chore: release v1.6.2" | Re-trigger Greptile

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 1, 2026

Benchmark changes

Versions:

  • aube: 1.5.2 -> 1.6.2

Public ratios: warm installs vs Bun 6x -> 7x; warm installs vs pnpm 10x -> 12x.

Benchmark aube bun pnpm
Fresh install (warm cache) 230ms -> 258ms (+12%) 1488ms -> 1694ms (+14%) 2367ms -> 3083ms (+30%)
CI install (warm cache, GVS disabled) 564ms -> 1054ms (+87%) 1295ms -> 1593ms (+23%) 2361ms -> 2346ms (-1%)
CI install (cold cache, GVS disabled) 5800ms -> 4113ms (-29%) 4278ms -> 4334ms (+1%) 4823ms -> 5112ms (+6%)

9f7663d vs 3f67c94 | aube/bun/pnpm | 3 scenarios | 3 runs | 500mbit/50ms | generated by Codex.

@jdx jdx force-pushed the release-plz-2026-05-01T22-10-07Z branch from ffa2deb to 9f7663d Compare May 1, 2026 22:26
@jdx jdx changed the title chore: release v1.7.0 chore: release v1.6.2 May 1, 2026
Comment thread release.json
Comment on lines +2 to +3
"version": "1.6.2",
"releasedAt": "2026-05-01T22:10:07Z"
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 PR title/description mismatch with actual version bump

The PR title and description both claim this is a v1.7.0 release, but every file in the diff — Cargo.toml, Cargo.lock, release.json, aube.usage.kdl, the CHANGELOG entries, and the docs — consistently bumps the version to 1.6.2, not 1.7.0. Merging under the assumption that this is a minor-version release when it is actually a patch release (or vice-versa) could cause confusion in release tracking and downstream consumers pinning to version ranges.

@jdx jdx merged commit e7b8989 into main May 1, 2026
18 checks passed
@jdx jdx deleted the release-plz-2026-05-01T22-10-07Z branch May 1, 2026 22:33
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.

2 participants