Skip to content

Commit c35abda

Browse files
committed
Version packages
@varlock/bumpy@1.18.0
1 parent 3bff4dc commit c35abda

3 files changed

Lines changed: 12 additions & 10 deletions

File tree

.bumpy/snapshot-releases.md

Lines changed: 0 additions & 9 deletions
This file was deleted.

packages/bumpy/CHANGELOG.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,16 @@
11
# Changelog
22

3+
## 1.18.0
4+
5+
<sub>2026-06-25</sub>
6+
7+
- [#133](https://github.com/dmno-dev/bumpy/pull/133) _(minor)_
8+
Add snapshot releases — transient, one-off preview publishes for private packages (the private-registry counterpart to pkg.pr.new).
9+
10+
`bumpy publish --snapshot <name>` computes the pending release plan, derives a unique prerelease version per package (e.g. `1.4.0-pr-123-a1b2c3d`), exact-pins in-plan internal deps, publishes to a non-`latest` dist-tag (default: the snapshot name), then restores the working tree. It never consumes bump files, writes changelogs, commits, creates git tags, or makes GitHub releases. `bumpy ci release --snapshot <name>` runs the whole thing and, on a PR, posts/updates a comment with the published versions and install instructions. Requires pending bump files; mutually exclusive with `--channel`.
11+
12+
Version uniqueness is configurable via the new `snapshot.versionStrategy` option: `"sha"` (default — `<target>-<name>-<short-sha>`, idempotent per commit so re-runs skip) or `"timestamp"`. Consumers install via the dist-tag regardless, so the exact version string is just an implementation detail.
13+
314
## 1.17.0
415

516
<sub>2026-06-25</sub>

packages/bumpy/package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "@varlock/bumpy",
3-
"version": "1.17.0",
3+
"version": "1.18.0",
44
"description": "Modern monorepo versioning and changelog tool",
55
"keywords": [
66
"bump",

0 commit comments

Comments
 (0)