Repository navigation
Conversation
bumpy-bot
force-pushed
the
bumpy/version-packages
branch
2 times, most recently
from
August 17, 2026 23:17
22760a4 to
ad71874
Compare
bumpy-bot
force-pushed
the
bumpy/version-packages
branch
from
August 25, 2026 19:03
ad71874 to
765db7a
Compare
bumpy-bot
force-pushed
the
bumpy/version-packages
branch
from
September 17, 2026 17:01
765db7a to
47d481c
Compare
bumpy-bot
force-pushed
the
bumpy/version-packages
branch
2 times, most recently
from
October 15, 2026 19:17
3eeba1b to
e1e3794
Compare
@varlock/bumpy@1.19.0
bumpy-bot
force-pushed
the
bumpy/version-packages
branch
from
October 15, 2026 19:41
e1e3794 to
a61115a
Compare
This branch has not been deployed
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.18.1 → 1.19.0 CHANGELOG.mddirectBump: falseper-package config for packages that only receive propagated bumps (e.g. platform binary packages in a fixed group with their core package) — they are excluded frombumpy add/bumpy generate, rejected when a bump file names them directly, andbumpy checkpoints at their fixed-group members instead. Fixed groups now sync drifted members to a bump of the group's highest version so they reconverge. (bump file)semverdependency with verkit — a smaller, tree-shakeable, zero-dependency SemVer library. No behavior changes, except invalid snapshot versions are now also refused (previously only stable versions were). (bump file)bumpy ci commentfailing to resolve the target PR for fork PRs. Underworkflow_run, the PR was looked up viaGET commits/{head_sha}/pulls, which only knows about commits in the base repo's own branches — for a fork PR it returns nothing, so the command exited with "Could not resolve a target PR" (defeating the whole point of the fork-safepull_request+workflow_runsplit). When that lookup is empty, bumpy now scans the repo's open PRs (paginated) and matcheshead.shaagainst the trustedworkflow_run.head_sha. The target still derives only from the trusted event, never from the artifact or fromworkflow_run.pull_requests[](which GitHub leaves empty for forks). (bump file)bumpy ci depsfor Dependabot / Renovate PRs (modeled on changesets-dependencies-action). It diffs each package'sdependencies/peerDependencies/optionalDependencies(plusreleaseTriggeringDevDeps, and catalog updates) against the base branch, writes one patch bump file per affected package listing the added / updated / removed deps, and commits + pushes them to the PR branch. Re-running is idempotent and removes stale files.bumpy generate --depsdoes the same locally without committing. (bump file)Also fix
ci checkon PRs into a channel branch: thepackage.jsonfield diff and catalog diff compared againstbaseBranchinstead of the PR's base, so dependency drift already merged into the channel was attributed to every later PR..0on registries that don't set alatestdist-tag (e.g. GCP Artifact Registry).npm info <name> versionsresolves throughlatestand prints nothing when it's missing, so bumpy now falls back to the channel's dist-tag and warns if the version list still can't be read. Snapshot idempotency now checks the exact version, and the OIDC new-package check no longer misreports packages withoutlatestas missing. (bump file)bumpy generatenow maps commits that change a catalog entry (pnpm-workspace.yaml,.yarnrc.yml, rootpackage.json) to the packages consuming it viacatalog:, so a catalog bump produces the bump filebumpy checkasks for. (bump file)