-
-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
addy.io 1.0.8 #260
addy.io 1.0.8 #260
Conversation
Build on arm doesn't look good 😞: https://github.com/anonaddy/docker/actions/runs/7948027904/job/21697548411?pr=260#step:7:4324
It says linux arm is not supported but then it's clearly specified in the supported platforms 🤷♂️ |
Hmm, that's strange. Do you think that's why the anonaddybot on https://hub.docker.com/repository/docker/anonaddy/anonaddy/general hasn't built the last tag |
This is not related but I forgot to push the tag my bad, here you go: https://github.com/anonaddy/docker/releases/tag/1.0.5-r0 |
Ah yes, I forgot about that too! |
rollup seems something new since anonaddy/anonaddy@fef0c1b#diff-053150b640a7ce75eff69d1a22cae7f0f94ad64ce9a855db544dda0929316519R659 (v1.0.7) so linked to dependencies update. @willbrowningme Do you know what imports https://github.com/anonaddy/anonaddy/blame/31d206ac41523961d1f90b4792f9bc5655e79dfa/package-lock.json#L659-L827? Vite v5 maybe? |
Ah actually |
@willbrowningme Seems rollup/rollup#5194 (comment) would solve the issue. In your case with vite: rollup/rollup#5194 (comment) |
@crazy-max great find! I've just updated package.json, do I need to tag a new release to trigger a build? |
Shall I close this PR? |
Co-authored-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
not needed, updated your changes to 1.0.8, let's see how it goes 👀 |
Awesome, thanks! |
No description provided.