zenpy-release-poc 0.1.1__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- zenpy_release_poc-0.1.1/LICENSE +21 -0
- zenpy_release_poc-0.1.1/PKG-INFO +69 -0
- zenpy_release_poc-0.1.1/README.md +43 -0
- zenpy_release_poc-0.1.1/setup.cfg +4 -0
- zenpy_release_poc-0.1.1/setup.py +31 -0
- zenpy_release_poc-0.1.1/zenpy_release_poc/__init__.py +1 -0
- zenpy_release_poc-0.1.1/zenpy_release_poc/cli.py +14 -0
- zenpy_release_poc-0.1.1/zenpy_release_poc.egg-info/PKG-INFO +69 -0
- zenpy_release_poc-0.1.1/zenpy_release_poc.egg-info/SOURCES.txt +10 -0
- zenpy_release_poc-0.1.1/zenpy_release_poc.egg-info/dependency_links.txt +1 -0
- zenpy_release_poc-0.1.1/zenpy_release_poc.egg-info/entry_points.txt +2 -0
- zenpy_release_poc-0.1.1/zenpy_release_poc.egg-info/top_level.txt +1 -0
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2026 hassaku63
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|
|
@@ -0,0 +1,69 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: zenpy-release-poc
|
|
3
|
+
Version: 0.1.1
|
|
4
|
+
Summary: Minimal PoC validating GitHub Actions + PyPI Trusted Publishing release automation
|
|
5
|
+
Home-page: https://github.com/hassaku63/zenpy-release-poc
|
|
6
|
+
Download-URL: https://github.com/hassaku63/zenpy-release-poc/releases/tag/0.1.1
|
|
7
|
+
Author: hassaku63
|
|
8
|
+
Author-email: hassaku63@gmail.com
|
|
9
|
+
License: MIT
|
|
10
|
+
Classifier: Programming Language :: Python :: 3
|
|
11
|
+
Classifier: License :: OSI Approved :: MIT License
|
|
12
|
+
Requires-Python: >=3.9
|
|
13
|
+
Description-Content-Type: text/markdown
|
|
14
|
+
License-File: LICENSE
|
|
15
|
+
Dynamic: author
|
|
16
|
+
Dynamic: author-email
|
|
17
|
+
Dynamic: classifier
|
|
18
|
+
Dynamic: description
|
|
19
|
+
Dynamic: description-content-type
|
|
20
|
+
Dynamic: download-url
|
|
21
|
+
Dynamic: home-page
|
|
22
|
+
Dynamic: license
|
|
23
|
+
Dynamic: license-file
|
|
24
|
+
Dynamic: requires-python
|
|
25
|
+
Dynamic: summary
|
|
26
|
+
|
|
27
|
+
# zenpy-release-poc
|
|
28
|
+
|
|
29
|
+
Minimal proof-of-concept for the release-automation approach proposed for
|
|
30
|
+
[facetoe/zenpy#692](https://github.com/facetoe/zenpy/pull/692#issuecomment-5451069842):
|
|
31
|
+
a GitHub Actions workflow that publishes to PyPI via Trusted Publishing
|
|
32
|
+
(OIDC) whenever a GitHub Release is published.
|
|
33
|
+
|
|
34
|
+
Not a real package - just enough source (`zenpy_release_poc/`, a `setup.py`
|
|
35
|
+
build like zenpy's, and one CLI entry point) to exercise the workflow.
|
|
36
|
+
|
|
37
|
+
**Note:** this targets *production* PyPI, not Test PyPI. A successful run
|
|
38
|
+
permanently claims the `zenpy-release-poc` project name and publishes real,
|
|
39
|
+
unremovable files (PyPI does not allow re-uploading or deleting individual
|
|
40
|
+
release files, only yanking a version). Test PyPI's publishing settings
|
|
41
|
+
page was unreliable when this was tried, hence the switch - re-point
|
|
42
|
+
`publish.yml`'s pending-publisher target back to test.pypi.org and add
|
|
43
|
+
`repository-url: https://test.pypi.org/legacy/` to the publish step if you
|
|
44
|
+
want to retry there instead.
|
|
45
|
+
|
|
46
|
+
## Try it
|
|
47
|
+
|
|
48
|
+
1. Push this repo to `hassaku63/zenpy-release-poc` on GitHub.
|
|
49
|
+
2. On PyPI, add a pending publisher at
|
|
50
|
+
https://pypi.org/manage/account/publishing/ :
|
|
51
|
+
- PyPI project name: `zenpy-release-poc`
|
|
52
|
+
- Owner: `hassaku63`
|
|
53
|
+
- Repository: `zenpy-release-poc`
|
|
54
|
+
- Workflow: `publish.yml`
|
|
55
|
+
- Environment: (leave blank)
|
|
56
|
+
3. Tag the commit `0.1.0` (must match `zenpy_release_poc/__version__`) and
|
|
57
|
+
push the tag.
|
|
58
|
+
4. Create a GitHub Release from that tag and publish it.
|
|
59
|
+
5. Watch the Actions run - it should build and upload to
|
|
60
|
+
https://pypi.org/project/zenpy-release-poc/ with no secrets stored in
|
|
61
|
+
the repo.
|
|
62
|
+
|
|
63
|
+
## Local sanity check
|
|
64
|
+
|
|
65
|
+
```
|
|
66
|
+
pip install -e .
|
|
67
|
+
zenpy-release-poc --version
|
|
68
|
+
zenpy-release-poc
|
|
69
|
+
```
|
|
@@ -0,0 +1,43 @@
|
|
|
1
|
+
# zenpy-release-poc
|
|
2
|
+
|
|
3
|
+
Minimal proof-of-concept for the release-automation approach proposed for
|
|
4
|
+
[facetoe/zenpy#692](https://github.com/facetoe/zenpy/pull/692#issuecomment-5451069842):
|
|
5
|
+
a GitHub Actions workflow that publishes to PyPI via Trusted Publishing
|
|
6
|
+
(OIDC) whenever a GitHub Release is published.
|
|
7
|
+
|
|
8
|
+
Not a real package - just enough source (`zenpy_release_poc/`, a `setup.py`
|
|
9
|
+
build like zenpy's, and one CLI entry point) to exercise the workflow.
|
|
10
|
+
|
|
11
|
+
**Note:** this targets *production* PyPI, not Test PyPI. A successful run
|
|
12
|
+
permanently claims the `zenpy-release-poc` project name and publishes real,
|
|
13
|
+
unremovable files (PyPI does not allow re-uploading or deleting individual
|
|
14
|
+
release files, only yanking a version). Test PyPI's publishing settings
|
|
15
|
+
page was unreliable when this was tried, hence the switch - re-point
|
|
16
|
+
`publish.yml`'s pending-publisher target back to test.pypi.org and add
|
|
17
|
+
`repository-url: https://test.pypi.org/legacy/` to the publish step if you
|
|
18
|
+
want to retry there instead.
|
|
19
|
+
|
|
20
|
+
## Try it
|
|
21
|
+
|
|
22
|
+
1. Push this repo to `hassaku63/zenpy-release-poc` on GitHub.
|
|
23
|
+
2. On PyPI, add a pending publisher at
|
|
24
|
+
https://pypi.org/manage/account/publishing/ :
|
|
25
|
+
- PyPI project name: `zenpy-release-poc`
|
|
26
|
+
- Owner: `hassaku63`
|
|
27
|
+
- Repository: `zenpy-release-poc`
|
|
28
|
+
- Workflow: `publish.yml`
|
|
29
|
+
- Environment: (leave blank)
|
|
30
|
+
3. Tag the commit `0.1.0` (must match `zenpy_release_poc/__version__`) and
|
|
31
|
+
push the tag.
|
|
32
|
+
4. Create a GitHub Release from that tag and publish it.
|
|
33
|
+
5. Watch the Actions run - it should build and upload to
|
|
34
|
+
https://pypi.org/project/zenpy-release-poc/ with no secrets stored in
|
|
35
|
+
the repo.
|
|
36
|
+
|
|
37
|
+
## Local sanity check
|
|
38
|
+
|
|
39
|
+
```
|
|
40
|
+
pip install -e .
|
|
41
|
+
zenpy-release-poc --version
|
|
42
|
+
zenpy-release-poc
|
|
43
|
+
```
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
from setuptools import setup
|
|
2
|
+
import setuptools
|
|
3
|
+
from pathlib import Path
|
|
4
|
+
|
|
5
|
+
this_directory = Path(__file__).parent
|
|
6
|
+
long_description = (this_directory / "README.md").read_text()
|
|
7
|
+
|
|
8
|
+
setup(
|
|
9
|
+
name='zenpy-release-poc',
|
|
10
|
+
packages=setuptools.find_packages(),
|
|
11
|
+
version='0.1.1',
|
|
12
|
+
description='Minimal PoC validating GitHub Actions + PyPI Trusted Publishing release automation',
|
|
13
|
+
long_description=long_description,
|
|
14
|
+
long_description_content_type='text/markdown',
|
|
15
|
+
license='MIT',
|
|
16
|
+
license_files=('LICENSE',),
|
|
17
|
+
author='hassaku63',
|
|
18
|
+
author_email='hassaku63@gmail.com',
|
|
19
|
+
url='https://github.com/hassaku63/zenpy-release-poc',
|
|
20
|
+
download_url='https://github.com/hassaku63/zenpy-release-poc/releases/tag/0.1.1',
|
|
21
|
+
python_requires='>=3.9',
|
|
22
|
+
entry_points={
|
|
23
|
+
'console_scripts': [
|
|
24
|
+
'zenpy-release-poc=zenpy_release_poc.cli:main',
|
|
25
|
+
],
|
|
26
|
+
},
|
|
27
|
+
classifiers=[
|
|
28
|
+
'Programming Language :: Python :: 3',
|
|
29
|
+
'License :: OSI Approved :: MIT License',
|
|
30
|
+
],
|
|
31
|
+
)
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
__version__ = "0.1.1"
|
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
import argparse
|
|
2
|
+
|
|
3
|
+
from zenpy_release_poc import __version__
|
|
4
|
+
|
|
5
|
+
|
|
6
|
+
def main():
|
|
7
|
+
parser = argparse.ArgumentParser(prog="zenpy-release-poc")
|
|
8
|
+
parser.add_argument("--version", action="version", version=__version__)
|
|
9
|
+
parser.parse_args()
|
|
10
|
+
print(f"zenpy-release-poc {__version__}: release automation PoC is working")
|
|
11
|
+
|
|
12
|
+
|
|
13
|
+
if __name__ == "__main__":
|
|
14
|
+
main()
|
|
@@ -0,0 +1,69 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: zenpy-release-poc
|
|
3
|
+
Version: 0.1.1
|
|
4
|
+
Summary: Minimal PoC validating GitHub Actions + PyPI Trusted Publishing release automation
|
|
5
|
+
Home-page: https://github.com/hassaku63/zenpy-release-poc
|
|
6
|
+
Download-URL: https://github.com/hassaku63/zenpy-release-poc/releases/tag/0.1.1
|
|
7
|
+
Author: hassaku63
|
|
8
|
+
Author-email: hassaku63@gmail.com
|
|
9
|
+
License: MIT
|
|
10
|
+
Classifier: Programming Language :: Python :: 3
|
|
11
|
+
Classifier: License :: OSI Approved :: MIT License
|
|
12
|
+
Requires-Python: >=3.9
|
|
13
|
+
Description-Content-Type: text/markdown
|
|
14
|
+
License-File: LICENSE
|
|
15
|
+
Dynamic: author
|
|
16
|
+
Dynamic: author-email
|
|
17
|
+
Dynamic: classifier
|
|
18
|
+
Dynamic: description
|
|
19
|
+
Dynamic: description-content-type
|
|
20
|
+
Dynamic: download-url
|
|
21
|
+
Dynamic: home-page
|
|
22
|
+
Dynamic: license
|
|
23
|
+
Dynamic: license-file
|
|
24
|
+
Dynamic: requires-python
|
|
25
|
+
Dynamic: summary
|
|
26
|
+
|
|
27
|
+
# zenpy-release-poc
|
|
28
|
+
|
|
29
|
+
Minimal proof-of-concept for the release-automation approach proposed for
|
|
30
|
+
[facetoe/zenpy#692](https://github.com/facetoe/zenpy/pull/692#issuecomment-5451069842):
|
|
31
|
+
a GitHub Actions workflow that publishes to PyPI via Trusted Publishing
|
|
32
|
+
(OIDC) whenever a GitHub Release is published.
|
|
33
|
+
|
|
34
|
+
Not a real package - just enough source (`zenpy_release_poc/`, a `setup.py`
|
|
35
|
+
build like zenpy's, and one CLI entry point) to exercise the workflow.
|
|
36
|
+
|
|
37
|
+
**Note:** this targets *production* PyPI, not Test PyPI. A successful run
|
|
38
|
+
permanently claims the `zenpy-release-poc` project name and publishes real,
|
|
39
|
+
unremovable files (PyPI does not allow re-uploading or deleting individual
|
|
40
|
+
release files, only yanking a version). Test PyPI's publishing settings
|
|
41
|
+
page was unreliable when this was tried, hence the switch - re-point
|
|
42
|
+
`publish.yml`'s pending-publisher target back to test.pypi.org and add
|
|
43
|
+
`repository-url: https://test.pypi.org/legacy/` to the publish step if you
|
|
44
|
+
want to retry there instead.
|
|
45
|
+
|
|
46
|
+
## Try it
|
|
47
|
+
|
|
48
|
+
1. Push this repo to `hassaku63/zenpy-release-poc` on GitHub.
|
|
49
|
+
2. On PyPI, add a pending publisher at
|
|
50
|
+
https://pypi.org/manage/account/publishing/ :
|
|
51
|
+
- PyPI project name: `zenpy-release-poc`
|
|
52
|
+
- Owner: `hassaku63`
|
|
53
|
+
- Repository: `zenpy-release-poc`
|
|
54
|
+
- Workflow: `publish.yml`
|
|
55
|
+
- Environment: (leave blank)
|
|
56
|
+
3. Tag the commit `0.1.0` (must match `zenpy_release_poc/__version__`) and
|
|
57
|
+
push the tag.
|
|
58
|
+
4. Create a GitHub Release from that tag and publish it.
|
|
59
|
+
5. Watch the Actions run - it should build and upload to
|
|
60
|
+
https://pypi.org/project/zenpy-release-poc/ with no secrets stored in
|
|
61
|
+
the repo.
|
|
62
|
+
|
|
63
|
+
## Local sanity check
|
|
64
|
+
|
|
65
|
+
```
|
|
66
|
+
pip install -e .
|
|
67
|
+
zenpy-release-poc --version
|
|
68
|
+
zenpy-release-poc
|
|
69
|
+
```
|
|
@@ -0,0 +1,10 @@
|
|
|
1
|
+
LICENSE
|
|
2
|
+
README.md
|
|
3
|
+
setup.py
|
|
4
|
+
zenpy_release_poc/__init__.py
|
|
5
|
+
zenpy_release_poc/cli.py
|
|
6
|
+
zenpy_release_poc.egg-info/PKG-INFO
|
|
7
|
+
zenpy_release_poc.egg-info/SOURCES.txt
|
|
8
|
+
zenpy_release_poc.egg-info/dependency_links.txt
|
|
9
|
+
zenpy_release_poc.egg-info/entry_points.txt
|
|
10
|
+
zenpy_release_poc.egg-info/top_level.txt
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
zenpy_release_poc
|