Skip to content

chore: set the version to 1.0.0-prerelease.9 #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kieronlanning merged 1 commit into from
Oct 27, 2026
Merged

chore: set the version to 1.0.0-prerelease.9 #17

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -191,7 +191,8 @@ Commit messages follow Conventional Commits enforced by the `commit-msg` lefthoo
`purview-dev/build/.github/workflows/purview-build.yml`, with pack and validation enabled.
- `.github/workflows/release.yml` runs the shared release pipeline with `release-mode: NuGet` on a push to a
`release/**` branch (or a manual dispatch), **not** on a push to `main`. Cut a release by merging the
version bump into `main`, then pushing `release/<major>.<minor>` from it. `.config/purview-build.json`
version bump into `main`, then pushing a `release/v…` branch named after the version from it (for
example `release/v1.0.9` for `1.0.0-prerelease.9`). `.config/purview-build.json`
sets the `TrunkReservesMinor` eligibility policy; a version whose `v<version>` tag already exists is
skipped (`REL002`), so every release needs a new `package.json` version. See
[Release Flow](docs/wiki/Release-Flow.md).
Expand Down
9 changes: 5 additions & 4 deletions docs/wiki/Release-Flow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,15 +62,16 @@ and keep `purview-build.json` pointing at `src/Containers.slnx`.

1. Bump `version` in `package.json` on a branch (keep the `-prerelease.N` suffix), and merge it into
`main` through a pull request.
2. Push a release branch for that version's `<major>.<minor>` line from `main`, for example:
2. Push a release branch named after the version from `main`. The convention is `release/v<major>.<minor>.<N>`,
where `N` is the prerelease number, for example `release/v1.0.9` for `1.0.0-prerelease.9`:

```bash
git switch main && git pull
git push origin main:refs/heads/release/1.1
git push origin main:refs/heads/release/v1.0.9
```

3. The Release workflow runs on that push. Further fixes for the same line are released by bumping
`package.json` again and pushing the `release/<major>.<minor>` branch.
3. The Release workflow runs on that push. Each release is a new `package.json` version and a new
release branch.

Check the decision locally before pushing with `dotnet tool run purview-build -- release-explain`. It runs
nothing and publishes nothing; it reports the verdict and the rule that decided it.
Expand Down
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "containers",
"version": "1.1.0-prerelease.1",
"version": "1.0.0-prerelease.9",
"description": "Testcontainers-style library for .NET that runs throwaway Linux containers for integration testing, on Microsoft WSL Containers or Docker.",
"license": "MIT",
"author": {
Expand Down
Loading