starred/pocket-id
1
0
Fork 0
mirror of https://github.com/pocket-id/pocket-id.git synced 2026-02-05 00:39:38 +03:00
Code Issues 61 Packages Projects Releases 10 Wiki Activity

🐛 Bug Report: 2.2.0 does not produce working binary (frontend is in broken state) but latest master works #613

New Issue
Open
opened 2026-02-04 20:39:35 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-04 20:39:35 +03:00
Owner
Copy Link

Originally created by @damex on GitHub (Jan 17, 2026).

Reproduction steps

hi,
i did try to produce my own binaries.
process either like in https://raw.githubusercontent.com/pocket-id/pocket-id/refs/heads/main/docker/Dockerfile
or as described here https://pocket-id.org/docs/setup/installation
it could be simplified to:
download tarball, unpack, run this:

pnpm --filter pocket-id-frontend install --frozen-lockfile
pnpm --filter pocket-id-frontend build
go install -C backend/cmd
CGO_ENABLED=0 go build \
 -C backend/cmd \
 -ldflags="-X github.com/pocket-id/pocket-id/backend/internal/common.Version=%{version} -buildid=%{version}" \
 -trimpath \
 -o $(pwd)/pocket-id

i tried shuffling around different versions of nodejs available for rhel10 / almalinux10, using nodejs build for rhel10/almalinux10 or using nodesource version. pnpm installed from npm (rhel and nodesource) or from corepack (nodesource) and etc.

but ... but it works on last master.

Expected behavior

i expect to be able to get actual release and be able to produce working binaries out of it

Actual Behavior

it loads resources successfully and produces broken pocket-id frontend when built using 2.2.0 release but works if built using last master.

Pocket ID Version

2.2.0

Database

does not matter
tried sqlite and postgresql 16 and postgresql 18.

OS and Environment

Alma Linux 10 or Red Hat Enterprise Linux 10.
nodejs 22.22.0 from nodesource or nodejs 22.19.0 from almalinux10 repos

Log Output

No response

Originally created by @damex on GitHub (Jan 17, 2026). ### Reproduction steps hi, i did try to produce my own binaries. process either like in https://[raw.githubusercontent.com/pocket-id/pocket-id/refs/heads/main/docker/Dockerfile](https://raw.githubusercontent.com/pocket-id/pocket-id/refs/heads/main/docker/Dockerfile) or as described here https://pocket-id.org/docs/setup/installation it could be simplified to: download tarball, unpack, run this: ``` pnpm --filter pocket-id-frontend install --frozen-lockfile pnpm --filter pocket-id-frontend build go install -C backend/cmd CGO_ENABLED=0 go build \ -C backend/cmd \ -ldflags="-X github.com/pocket-id/pocket-id/backend/internal/common.Version=%{version} -buildid=%{version}" \ -trimpath \ -o $(pwd)/pocket-id ``` i tried shuffling around different versions of nodejs available for rhel10 / almalinux10, using nodejs build for rhel10/almalinux10 or using nodesource version. pnpm installed from npm (rhel and nodesource) or from corepack (nodesource) and etc. but ... but it works on last master. ### Expected behavior i expect to be able to get actual release and be able to produce working binaries out of it ### Actual Behavior it loads resources successfully and produces broken pocket-id frontend when built using 2.2.0 release but works if built using last master. ### Pocket ID Version 2.2.0 ### Database does not matter tried sqlite and postgresql 16 and postgresql 18. ### OS and Environment Alma Linux 10 or Red Hat Enterprise Linux 10. nodejs 22.22.0 from nodesource or nodejs 22.19.0 from almalinux10 repos ### Log Output _No response_
OVERLORD commented 2026-02-04 20:39:44 +03:00
Author
Owner
Copy Link

@kmendell commented on GitHub (Jan 19, 2026):

IT should work, as the release would be broken if it didn't. How did you get the source for v2.2.0?

@kmendell commented on GitHub (Jan 19, 2026): IT should work, as the release would be broken if it didn't. How did you get the source for v2.2.0?
OVERLORD commented 2026-02-04 20:39:48 +03:00
Author
Owner
Copy Link

@damex commented on GitHub (Jan 19, 2026):

from github releases page. https://github.com/pocket-id/pocket-id/releases/tag/v2.2.0 -> https://github.com/pocket-id/pocket-id/archive/refs/tags/v2.2.0.tar.gz

i did try to test it further - it seem to produce working binary if used with nodejs 24 but not 22

@damex commented on GitHub (Jan 19, 2026): from github releases page. https://github.com/pocket-id/pocket-id/releases/tag/v2.2.0 -> https://github.com/pocket-id/pocket-id/archive/refs/tags/v2.2.0.tar.gz i did try to test it further - it seem to produce working binary if used with nodejs 24 but not 22
OVERLORD commented 2026-02-04 20:39:54 +03:00
Author
Owner
Copy Link

@stonith404 commented on GitHub (Jan 24, 2026):

Can you elaborate what you mean with a broken build? Are there any errors in the browser console?

@stonith404 commented on GitHub (Jan 24, 2026): Can you elaborate what you mean with a broken build? Are there any errors in the browser console?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
breaking
bug
bug
bug
documentation
feature
needs more upvotes
open to pull requests
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/pocket-id#613
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?