offetestci 0.1.0__py3-none-any.whl
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.
offetestci/__init__.py
ADDED
|
@@ -0,0 +1 @@
|
|
|
1
|
+
__version__ = "0.1.0"
|
offetestci/py.typed
ADDED
|
File without changes
|
|
@@ -0,0 +1,59 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: offetestci
|
|
3
|
+
Version: 0.1.0
|
|
4
|
+
Author: Beltrán Offerrall
|
|
5
|
+
License-Expression: MIT
|
|
6
|
+
License-File: LICENSE
|
|
7
|
+
Requires-Python: >=3.10
|
|
8
|
+
Provides-Extra: dev
|
|
9
|
+
Requires-Dist: mypy; extra == 'dev'
|
|
10
|
+
Requires-Dist: pytest; extra == 'dev'
|
|
11
|
+
Requires-Dist: ruff; extra == 'dev'
|
|
12
|
+
Description-Content-Type: text/markdown
|
|
13
|
+
|
|
14
|
+
# offetestci
|
|
15
|
+
|
|
16
|
+
Paquete de prueba para validar el flujo completo de CI y publicación
|
|
17
|
+
automática a PyPI vía GitHub Actions (trusted publishing, sin tokens).
|
|
18
|
+
No tiene funcionalidad real; existe solo para comprobar que el pipeline
|
|
19
|
+
funciona de principio a fin.
|
|
20
|
+
|
|
21
|
+
## Publicación a PyPI — registro previo (importante)
|
|
22
|
+
|
|
23
|
+
El workflow de publicación (`.github/workflows/publish.yml`) sube el
|
|
24
|
+
paquete usando **trusted publishing**: GitHub se autentica ante PyPI con
|
|
25
|
+
un token OIDC temporal, sin guardar ningún secreto en el repo.
|
|
26
|
+
|
|
27
|
+
Para que eso funcione, PyPI tiene que confiar en este repo **de antemano**.
|
|
28
|
+
Como el paquete aún no existe en PyPI, se registra como *pending publisher*:
|
|
29
|
+
|
|
30
|
+
1. Entra en [pypi.org](https://pypi.org) (con 2FA activado).
|
|
31
|
+
2. Ve a los ajustes de tu cuenta → **Publishing**
|
|
32
|
+
(no dentro de un proyecto, sino en la cuenta).
|
|
33
|
+
3. Añade un *pending publisher* de tipo **GitHub** con estos datos exactos:
|
|
34
|
+
|
|
35
|
+
| Campo | Valor |
|
|
36
|
+
|---|---|
|
|
37
|
+
| PyPI Project Name | `offetestci` |
|
|
38
|
+
| Owner | `offerrall` |
|
|
39
|
+
| Repository name | `offetestci` |
|
|
40
|
+
| Workflow name | `publish.yml` |
|
|
41
|
+
| Environment | *(vacío)* |
|
|
42
|
+
|
|
43
|
+
4. Guarda.
|
|
44
|
+
|
|
45
|
+
> **El error típico:** "Workflow name" es el nombre del **fichero**
|
|
46
|
+
> (`publish.yml`), no el `name:` que pone dentro del YAML. Si pones el de
|
|
47
|
+
> dentro, PyPI rechaza la publicación con un error poco claro.
|
|
48
|
+
|
|
49
|
+
Una vez registrado, la primera publicación crea el proyecto en PyPI y
|
|
50
|
+
establece el trusted publisher de golpe.
|
|
51
|
+
|
|
52
|
+
## Publicar
|
|
53
|
+
|
|
54
|
+
1. Sube la versión en `src/offetestci/__init__.py`.
|
|
55
|
+
2. En GitHub → **Releases** → crea un release con su tag (ej. `v0.1.0`).
|
|
56
|
+
3. El workflow `publish.yml` se dispara solo: verifica, construye y sube.
|
|
57
|
+
|
|
58
|
+
Tras el registro previo, todo el flujo es desde GitHub — sin tokens, sin
|
|
59
|
+
publicar desde tu máquina.
|
|
@@ -0,0 +1,6 @@
|
|
|
1
|
+
offetestci/__init__.py,sha256=kUR5RAFc7HCeiqdlX36dZOHkUI5wI6V_43RpEcD8b-0,22
|
|
2
|
+
offetestci/py.typed,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
|
|
3
|
+
offetestci-0.1.0.dist-info/METADATA,sha256=YL1RgbAKg_hIq2Ks2yRmK5y0zWrXLJU1GpL98GtBQlI,2104
|
|
4
|
+
offetestci-0.1.0.dist-info/WHEEL,sha256=mffPy8wBnZQn2VnJUU5jE99KsxaSfiyMHV9Yt0aLVxs,87
|
|
5
|
+
offetestci-0.1.0.dist-info/licenses/LICENSE,sha256=dSa4wU3mKdQBPOHIZ6eVHBVEglRaham7KW5HdCqdIR4,1075
|
|
6
|
+
offetestci-0.1.0.dist-info/RECORD,,
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2026 Beltrán Offerrall
|
|
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.
|