thierryade/backend
Watch
2
0
Fork
You've already forked backend
 0
Code Issues Pull requests Projects Releases 2 Packages 1 Wiki Activity Actions
2 releases 3 tags
  • v1.1.0 141b33485f

    v1.1.0
    All checks were successful
    ci / test (push) Successful in 3m28s
    Details
    ci / e2e (push) Successful in 2m6s
    Details
    ci / docker (push) Successful in 1m47s
    Details
    ci / deploy (push) Successful in 12s
    Details
    Stable

    Gilles released this 2026-11-02 06:59:04 +00:00 | 2 commits to master since this release

    thierryade/backend 1.1.0 Docker image (git.stationmyr.net/thierryade/backend:1.1.0), bundling thierryade/frontend 1.2.0.

    ✨ Features

    • Expose the default PDF template content via the API (#38) by @Gilles — closes #37 feature: expose the default PDF template content via the API
    • Group the Forgejo issue-link confirmation comment per issue instead of per linked spec (#36) by @Gilles — closes #35 feature: group the Forgejo issue-link confirmation comment per issue instead of per linked spec
    • Generate a spec-scoped PDF extract and post its link on linked issues (#30) by @Gilles — closes #29 Generate a spec-scoped PDF extract and post its link on linked issues
    • Sync issue links via webhook, poll as fallback, detect spec codes in bodies (#28) by @Gilles — closes #27 Sync issue links via webhook, with a polling fallback, and detect a spec code typed in an issue
    • Link specs to Forgejo issues (model, manual link, create-issue button) (#26) by @Gilles — closes #25 Link specs to Forgejo issues (data model, manual link, create-issue button)
    • Export the project's current (draft) state as a PDF (#22) by @Gilles — closes #21 Export PDF de l'état actuel du projet (specs en brouillon incluses)
    • Async PDF export of validated specs (#20) by @Gilles — closes #19 Export PDF des spécifications (async, templates par organisation/projet)

    🐛 Bug fixes

    • Recreate the Forgejo webhooks instead of editing them (#34) by @Gilles — closes #33 resend_forgejo_webhooks doesn't repair the hooks: Forgejo's edit-hook ignores the secret
    • Send the Forgejo webhook secret inside the hook config (#32) by @Gilles — closes #31 Forgejo webhook deliveries are all rejected (invalid signature)
    • Let staff bypass object-level project permission checks (#24) by @Gilles — closes #23 Staff user gets 403 retrieving/downloading an object on a project they have no membership in

    Contributors: @Gilles

    Full changelog: v1.0.0...v1.1.0

    Downloads