Skip to content

Commit 2e44a1e

Browse files
authored
[Python] Include package prefix in semantic versioning (#11269)
* Make sure that semantic versioning should have a package prefix
1 parent 52dfe17 commit 2e44a1e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/platforms/python/configuration/releases.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,10 +20,10 @@ Include the `release` when you initialize the SDK. The release name cannot:
2020

2121
The value can be arbitrary, but we recommend [Semantic Versioning](https://semver.org/), [Calendar Versioning](https://calver.org/), or the Git commit SHA.
2222

23-
Releases are global per organization; prefix them with something project-specific (such as `"myapp@1.0.0"`) for easy differentiation.
23+
We recommend that your release is prefixed with a project-specific package identifier (such as `"mypackage@1.0.0"`).
2424

2525

26-
The behavior of a few features depends on whether a project is using semantic or time-based versioning:
26+
The behavior of a few features depends on whether a project is using semantic or time-based versioning including the `"mypackage@"` prefix:
2727

2828
- Regression detection
2929
- Data filtering by `release:latest`

0 commit comments

Comments
 (0)