Repository navigation
aube 1.18.1 - #286742
Merged
Merged
aube 1.18.1#286742
Conversation
botantony
approved these changes
Jun 7, 2026
Contributor
|
🤖 An automated task has requested bottles to be published to this PR. Caution Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Created by
brew bumpCreated with
brew bump-formula-pr.Details
release notes
(install) Regenerate conflicted lockfiles (#843 by @jdx) — When
aube-lock.yamlstill contains Git conflict markers (<<<<<<<,=======,>>>>>>>), install now treats it as a recoverable prefer-frozen parse failure rather than aborting. It emits the newWARN_AUBE_LOCKFILE_CONFLICT_MARKERSwarning and regenerates the lockfile frompackage.json, so a plainaube installafter a messy merge just works.(update) Support global updates (#840 by @jdx) —
aube update --global(andaube update -g <pkg>) now routes through the global install directory instead of requiring a projectpackage.json, so it works from any directory — including outside a repo. Each global install runs the normal update pipeline with--latestand exact manifest pins, then bin shims are relinked and stale executables removed. Named packages resolve by alias; unknown names fail withnot globally installed. When combined with a workspace--filter,--globaltakes precedence and leaves workspace manifests untouched. Fixes #839.Security
lockfile-include-tarball-url=trueor npm-alias entries), install now fetches per-version registry metadata and comparesdist.tarballto the lockfile URL before downloading. Mismatches abort with the newERR_AUBE_TARBALL_URL_MISMATCH(exit 34). Exact matches pass, and lockfile URLs onregistry.npmjs.orgare still accepted on alternative hosts when the/-/…tgzpath matches, so Verdaccio and other local mirrors continue to work — but tampered paths or arbitrary hosts impersonating npm are rejected.Changed
Full Changelog: aubepkg/aube@v1.18.0...v1.18.1
💚 Sponsor aube
aube is part of en.dev — an independent developer-tooling studio run by @jdx, also behind mise. Work on aube is funded entirely by sponsors.
If aube is saving your team install time or CI minutes, please consider sponsoring at en.dev. Individual and company sponsorships are what keep the project fast, free, and independent.
View the full release notes at https://github.com/endevco/aube/releases/tag/v1.18.1.