🐸 Versioned release#121
Merged
Merged
Conversation
e0d6f7a to
b610b50
Compare
@varlock/bumpy@1.15.0
b610b50 to
deb281f
Compare
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.
This PR was created and will be kept in sync by bumpy based on your bump files (in
.bumpy/). Merge it when you are ready to release the packages listed below:@varlock/bumpy1.14.0 → 1.15.0 CHANGELOG.mdbuildCommand/publishCommandoutput live to the parent process and surface the child's real failure reason. Custom publish commands (vsce, ovsx, anything bespoke) previously ran through a buffering runner that discarded stdout and never streamed output, so a failure like an expired marketplace token produced only a genericCommand failedwrapper with no usable cause in CI logs. These commands now run through a streaming runner (spawnwith piped+teed stdio) that prints output as it happens and includes both stdout and stderr in the thrown error. The capturingrunAsync/runArgsAsynchelpers (still used for internal git/npm calls whose output is parsed) also now include stdout in their error messages. (bump file)*(type)*, PR link, "Thanks @user!") goes on its own line and the summary is rendered indented below it, instead of being jammed onto the same line. Short single-line summaries are unchanged and stay inline. Internal blank lines in a summary are now preserved so markdown paragraphs and lists render correctly. Applies to both the default andgithubformatters. (bump file)npm.pkg.github.com) were labellednpmin the GitHub release notes andbumpy status/bumpy ci planoutput, with a "Published to" badge linking to a non-existent npmjs.com page (404). The configured registry is now honoured: such targets are labelled GitHub Packages and link to the package page under the repo (https://github.com/<owner>/<repo>/pkgs/npm/<name>), resolving the repo from the package'srepositoryfield orGITHUB_REPOSITORY. Other custom/private registries no longer emit a dead npmjs.com link.buildPublishUrlnow honours its registry argument (previously the unused_registryparam). (bump file)package.json-field-aware: whenpackage.jsonis the only changed file in a package, bumpy diffs it against the base branch and only requires a bump file if a publish-affecting field changed. The newignoredPackageJsonFieldsoption (default["devDependencies"]) controls which fields are ignored, so a dev-only dependency bump (e.g. Dependabot) no longer requires a bump file — unless the changed dep matches the package'sreleaseTriggeringDevDeps. (bump file)ci checkno longer posts a "you're good to go" comment while exiting 1. When the check fails because changed packages have no bump file, the comment now matches the failing status, lists the uncovered packages, and points at an empty bump file (bumpy add --empty) to acknowledge an intentional no-release.Add a per-package
releaseTriggeringDevDepsoption: names/globs ofdevDependenciesthat affect a package's published output (most often because they're bundled in). A change to one requires a release, and a listed internal workspace dep's own releases cascade with a patch bump — shorthand for acascadeFromrule of{ trigger: 'patch', bumpAs: 'patch' }.findChangedPackages(used bycheck/ci check) andmapFilesToPackages(used bygenerate) matched changed files againstpkgRelDir + '/', but for the root package the relative dir is empty, so the check becamefile.startsWith('/')— always false for git's relative paths. As a resultci checkalways reported "No managed packages have changed" (never requiring a bump file or posting a PR comment) andgeneratenever attributed commits to the root package. The root package (empty relative dir) now treats every changed file as belonging to it, while still honoringchangedFilePatterns. (bump file)