Skip to content

Callers pinned before #11 cannot sign their next release #12

Closed

Description

@ddespinoza

Problem

instalador#317 removed apps.pub from instalador. #11 points the signing check at gestion-aio's aps/provisionador/apps.pub, which holds the same key, as of 064711d. Every caller pinned before that commit fails at «Sign and publish» with signify: can't open suite/apps.pub, and publishes nothing. Estadística hit this on v0.3.0 and is already moved to 064711d.

Callers still on an old pin:

Repo Pin
farmacia, epidemiologia, territorio, totem, buscador-documental, eurooffice 7884528
side_menu, IntraVox 6fa99e3
files-upload-guard, files-fulltextsearch b2d2739

What to do

In each caller, move release.yml's pin to 064711d or later, in one small PR per repo, before that app's next tag. The commits in between only add opt-in inputs: shipped-bundle and php-only.

Acceptance criteria

  • Every caller above pins 064711d or later.

Activity

  1. ddespinoza commented on Nov 11, 2026

    @ddespinoza
    ContributorAuthor

    All ten callers pin 064711d on main: farmacia#114 (it also fixes farmacia main's red since 2026-11-01, an openapi.json still at 0.12.0), epidemiologia#173, territorio#263, totem#93, buscador-documental#132, eurooffice#3, side_menu#2, IntraVox#21, files-upload-guard#4, files-fulltextsearch#2. Each PR's «Build and pack» ran the new pin green.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentFully specified, ready for an AFK agent

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions