feat: usar token personal para evitar error 500 en gitea api
Some checks failed
Release con IA Local / release-please (push) Failing after 12s
Some checks failed
Release con IA Local / release-please (push) Failing after 12s
This commit is contained in:
@@ -16,15 +16,15 @@ jobs:
|
||||
- name: Checkout
|
||||
uses: actions/checkout@v4
|
||||
|
||||
# 1. Ejecutar Release Please (usa tu clon local)
|
||||
# 1. Usar PAT, que ya tiene todos los permisos
|
||||
- name: Release Please
|
||||
id: release
|
||||
uses: https://repo.eldiaservicios.com/dmolinari/gitea-release-please-action@main
|
||||
with:
|
||||
token: ${{ secrets.GITHUB_TOKEN }}
|
||||
release-type: simple # Lo mantenemos simple para esta prueba
|
||||
token: ${{ secrets.RELEASE_PLEASE_TOKEN }}
|
||||
release-type: simple
|
||||
|
||||
# 2. Si se creó un Release, llamar a tu PC (Ollama) para redactar notas épicas
|
||||
# 2. Generar notas con IA Local
|
||||
- name: Generar notas con IA Local
|
||||
if: ${{ steps.release.outputs.release_created }}
|
||||
env:
|
||||
@@ -66,13 +66,11 @@ jobs:
|
||||
const aiData = await aiRes.json();
|
||||
const aiNotes = aiData.response;
|
||||
|
||||
// Obtener ID del release para actualizarlo
|
||||
const relRes = await fetch(`${giteaUrl}/repos/${process.env.REPO}/releases/tags/${process.env.TAG_NAME}`, {
|
||||
headers: { "Authorization": `token ${process.env.GITEA_TOKEN}` }
|
||||
});
|
||||
const relData = await relRes.json();
|
||||
|
||||
// Actualizar el body del release en Gitea
|
||||
await fetch(`${giteaUrl}/repos/${process.env.REPO}/releases/${relData.id}`, {
|
||||
method: "PATCH",
|
||||
headers: {
|
||||
|
||||
Reference in New Issue
Block a user