1
0
Fork 0

Adding upstream version 4.6.0+dfsg.

Signed-off-by: Daniel Baumann <daniel@debian.org>
This commit is contained in:
Daniel Baumann 2025-04-21 10:42:01 +02:00
parent f3ad83a1a5
commit 167a3f8553
Signed by: daniel
GPG key ID: FBB4F0E80A80222F
275 changed files with 30423 additions and 0 deletions

View file

@ -0,0 +1,78 @@
# Dev Releases
## About
To make use of a `.dev` suffix, as per
[PEP440](https://peps.python.org/pep-0440/#developmental-releases).
If more than one active branch attempts to create a tag, relative to the main
branch, there is the possibility that each will attempt to create the _same_
tag, resulting in a collision.
Developmental releases aim to avoid this by including a `.dev` segment which
includes a non-negative integer unique to that workflow:
```txt
X.Y.devN
```
!!! note
As noted in
[PEP440](https://peps.python.org/pep-0440/#developmental-releases),
although developmental releases are useful in avoiding the situation
described above, depending on the value passed as the developmental
release, they can be _"difficult to parse for human readers"_.
## How to
### Example 1: CircleCI
For example, CircleCI [provides](https://circleci.com/docs/variables/)
`CIRCLE_BUILD_NUM`, a unique number for each job which will increment with each
run:
```sh
--devrelease ${CIRCLE_BUILD_NUM}
```
This will result in a unique developmental release of, for example:
```sh
1.3.2.dev2478
```
### Example 2: GitHub
GitHub also
[provides](https://docs.github.com/en/actions/learn-github-actions/variables#default-environment-variables)
`GITHUB_RUN_ID`, a _"unique number for each workflow run"_ which will also
provide a unique number for each workflow:
```sh
--devrelease ${GITHUB_RUN_ID}
```
This will result in a unique developmental release of, for example:
```sh
1.3.2.dev6048584598
```
### Example 3: Unix time
Equally, as the developmental release needs only a non-negative integer, it is
possible to use the Unix time (i.e. the number of seconds since 1st January
1970 UTC).
This would create the possibility of a collision if two builds occur at
precisely the same second but this may be sufficient for many cases:
```sh
--devrelease $(date +%s)
```
This will result in a unique developmental release of, for example:
```sh
1.3.2.dev1696238452
```