starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-26 14:25:59 +03:00

[GH-ISSUE #1632] v1.9.0 not available as Docker image #457

New issue

Closed

opened 2026-02-26 18:47:08 +03:00 by kerem · 6 comments

kerem commented

2026-02-26 18:47:08 +03:00

Owner

Originally created by @bashgeek on GitHub (Feb 4, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/1632

v1.9.0 does not seem to be available as Docker image just yet:
https://hub.docker.com/r/documenso/documenso/tags
lists v1.8.1 as latest available

Thank you!

Originally created by @bashgeek on GitHub (Feb 4, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/1632 v1.9.0 does not seem to be available as Docker image just yet: https://hub.docker.com/r/documenso/documenso/tags lists [v1.8.1](https://hub.docker.com/layers/documenso/documenso/v1.8.1/images/sha256-03e641c66326ef9df547acd140e3553881f0b43ed8fa84e8931b181ccf9fed71) as latest available Thank you!

kerem

2026-02-26 18:47:08 +03:00

closed this issue
added the
status: triage
label

kerem commented

2026-02-26 18:47:08 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 4, 2025):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

@github-actions[bot] commented on GitHub (Feb 4, 2025): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)

kerem commented

2026-02-26 18:47:08 +03:00

Author

Owner

@ephraimduncan commented on GitHub (Feb 4, 2025):

Hello @bashgeek, 1.9.0 is available but not really specified.

You can access it here: https://hub.docker.com/layers/documenso/documenso/b9ae27704161908cd409179a73d5f82bf0ad6432/images/sha256-22f18fce0c47ac14466194cdc32469c957ede9688957f1bb858d177bd01fab09

@ephraimduncan commented on GitHub (Feb 4, 2025): Hello @bashgeek, 1.9.0 is available but not really specified. You can access it here: https://hub.docker.com/layers/documenso/documenso/b9ae27704161908cd409179a73d5f82bf0ad6432/images/sha256-22f18fce0c47ac14466194cdc32469c957ede9688957f1bb858d177bd01fab09

kerem commented

2026-02-26 18:47:08 +03:00

Author

Owner

@sebiweise commented on GitHub (Feb 6, 2025):

Hello @bashgeek, 1.9.0 is available but not really specified.

You can access it here: https://hub.docker.com/layers/documenso/documenso/b9ae27704161908cd409179a73d5f82bf0ad6432/images/sha256-22f18fce0c47ac14466194cdc32469c957ede9688957f1bb858d177bd01fab09

The version tag for the v1.9.0 wasn´t added to the latest docker image, tahts why you cannot find it using the version tag directly.

@sebiweise commented on GitHub (Feb 6, 2025): > Hello [@bashgeek](https://github.com/bashgeek), 1.9.0 is available but not really specified. > > You can access it here: https://hub.docker.com/layers/documenso/documenso/b9ae27704161908cd409179a73d5f82bf0ad6432/images/sha256-22f18fce0c47ac14466194cdc32469c957ede9688957f1bb858d177bd01fab09 The version tag for the v1.9.0 wasn´t added to the latest docker image, tahts why you cannot find it using the version tag directly.

kerem commented

2026-02-26 18:47:09 +03:00

Author

Owner

@david-loe commented on GitHub (Mar 26, 2025):

Reason is a bug in getting the APP_VERSION in the github workflow:

github.com/documenso/documenso@c82388c40a/.github/workflows/publish.yml (L40)

this leads to APP_VERSION being undefined

and because only valid semvers are released as latest, also latest doesn't get updated

ChatGPT suggests APP_VERSION=$(git describe --tags --exact-match 2>/dev/null || echo 'unknown') and

- name: Checkout repository
  uses: actions/checkout@v4
  with:
    fetch-tags: true

git describe --tags --exact-match instead of git name-rev because it's more precise and reliable.

Problems with `git name-rev`

It may return the nearest tag, not the exact one.
It can fail if tags are not fetched properly.
The additional filtering (sed and head) can cause unexpected results.

Why `git describe --tags --exact-match` is better

✅ Returns only the exact tag if the commit is tagged.
✅ No extra filtering needed—it provides the correct version directly.
✅ Fails gracefully—if no tag exists, it returns "unknown" instead of breaking the workflow.

This makes it a safer and more accurate solution in GitHub Actions. 🚀

APP_VERSION is also used at other places, maybe they also need a revisit

@david-loe commented on GitHub (Mar 26, 2025): Reason is a bug in getting the `APP_VERSION` in the github workflow: https://github.com/documenso/documenso/blob/c82388c40a260ea3ca3fa4a8136800135b8928e5/.github/workflows/publish.yml#L40 this leads to `APP_VERSION` being undefined ![Image](https://github.com/user-attachments/assets/809ce99b-5a0f-421c-9115-8640c6c2bb54) and because only valid semvers are released as `latest`, also `latest` doesn't get updated --- ChatGPT suggests `APP_VERSION=$(git describe --tags --exact-match 2>/dev/null || echo 'unknown')` and ```yaml - name: Checkout repository uses: actions/checkout@v4 with: fetch-tags: true ``` `git describe --tags --exact-match` instead of `git name-rev` because it's **more precise and reliable**. ### **Problems with `git name-rev`** - It may return the **nearest tag**, not the exact one. - It can fail if **tags are not fetched properly**. - The additional filtering (`sed` and `head`) can cause **unexpected results**. ### **Why `git describe --tags --exact-match` is better** ✅ **Returns only the exact tag** if the commit is tagged. ✅ **No extra filtering needed**—it provides the correct version directly. ✅ **Fails gracefully**—if no tag exists, it returns `"unknown"` instead of breaking the workflow. This makes it a **safer and more accurate** solution in GitHub Actions. 🚀 --- `APP_VERSION` is also used at other places, maybe they also need a revisit

kerem commented

2026-02-26 18:47:09 +03:00

Author

Owner

@david-loe commented on GitHub (May 10, 2025):

Looks like tagging is working again: https://hub.docker.com/r/documenso/documenso/tags

@david-loe commented on GitHub (May 10, 2025): Looks like tagging is working again: https://hub.docker.com/r/documenso/documenso/tags

kerem commented

2026-02-26 18:47:09 +03:00

Author

Owner

@bashgeek commented on GitHub (May 10, 2025):

Perfect, solved the issue for me :)

@bashgeek commented on GitHub (May 10, 2025): Perfect, solved the issue for me :)

kerem referenced this issue

2026-02-26 19:31:19 +03:00

[PR #457] [MERGED] chore: sync #985

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#457

No description provided.

Rows
Columns

[GH-ISSUE #1632] v1.9.0 not available as Docker image #457

Problems with git name-rev

Why git describe --tags --exact-match is better

Problems with `git name-rev`

Why `git describe --tags --exact-match` is better