Skip to content

Commit 4ce9da1

Browse files
authored
Better prerelease docs
1 parent 3137c33 commit 4ce9da1

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

src/content/tools/pub/publishing.md

+6-4
Original file line numberDiff line numberDiff line change
@@ -270,7 +270,7 @@ To learn more about automated publishing, consult
270270
### Publish prerelease versions {:#publishing-prereleases}
271271

272272
As you work on a package, consider publishing it as a prerelease.
273-
Prereleases can be useful when _any_ of the following are true:
273+
Prereleases can be useful when:
274274

275275
* You're actively developing the next major version of the package.
276276
* You want beta testers for the next release candidate of the package.
@@ -285,12 +285,14 @@ Later, when you release version `2.0.0`, it takes precedence over all
285285

286286
As pub prefers stable releases when available, users of a prerelease package
287287
might need to change their dependency constraints.
288-
For example, if a user wants to test prereleases of version 2.1, then
288+
For example, if a user wants to test prereleases of version `2.1.0`, then
289289
instead of `^2.0.0` or `^2.1.0` they might specify `^2.1.0-dev.1`.
290290

291291
:::note
292-
If a stable package in the dependency graph depends on a prerelease,
293-
then pub chooses that prerelease instead of a stable release.
292+
While `pub` prefers stable releases the same way it prefers newer versions,
293+
the version solver does not attempt all solutions and may pick a prerelease,
294+
even when a resolution that doesn't use prelreases exists.
295+
Though this rarely happens in practice.
294296
:::
295297

296298
When you publish a prerelease to pub.dev,

0 commit comments

Comments
 (0)