Skip to content

Commit b5283e3

Browse files
committed
add note on re-releasing
1 parent b6995fb commit b5283e3

File tree

1 file changed

+14
-0
lines changed

1 file changed

+14
-0
lines changed

RELEASING.md

+14
Original file line numberDiff line numberDiff line change
@@ -97,6 +97,20 @@ It will be promoted to stable next week, pending feedback.
9797
It's traditional to include notable changes from the changelog, but not
9898
required.
9999

100+
### Re-releasing a version
101+
102+
Re-releasing a version (i.e. changing the commit a tag points to) is
103+
*sometimes* possible, but it depends on how far into the release process it got.
104+
105+
The two points of no return are:
106+
* If the PyPI package has been published: PyPI disallows using the same
107+
filename/version twice. Once published, it cannot be replaced.
108+
* If the BCR package has been published: Once it's been committed to the BCR
109+
registry, it cannot be replaced.
110+
111+
If release steps fail _prior_ to those steps, then its OK to change the tag. You
112+
may need to manually delete the GitHub release.
113+
100114
## Secrets
101115

102116
### PyPI user rules-python

0 commit comments

Comments
 (0)